let’s sum up the current issue:
Note that the whole issue is related to the corrupted JS file which is preventing the dashboard to be loaded correctly. Therefore we have to understand where the corruption happened.
The creation of users is a different story. And of course it is possible to create the first user with the dashboard. The process is described on the getting started page in the docs and is very easy. But that process requires of course a working dashboard.
Also note that users are moved as well when moving a site.
I‘ll keep you updated.
Hi @mad ,
yes! and the website works ont he developed server, you can see it here:
When download the complete directory from here http://php.webkusthosting.be/ , and upload to another server, it doesn't work on the new server. Check here:
A while ago a moved a Automad website to another server without problems, this was version 1.2.2.
Maybe the issue is only on the latest version 1.2.3 ?
ctuxboy for me, the front-end works, but site.local/dashboard doesn't take me to dashboard, just the front-end. There are no errors for me however in the console.
hmfit here the same, only frontend works!
See the screenshot:
@ctuxboy totally frustrating, as I really want to use this CMS. It is the best flatfile CMS I have found that meets my needs exact. My issue is not being able to use the dashboard at all. I click on the link in the standard theme that is default upon installation, but the link goes nowhere, even though the URL changes. I need to be able to create a custom theme for clients, but can't switch to my starter site to get things rolling. BTW are you using nginx or apache?
hmfit yes it's an awesome cms. For more advanced website use Wordpress (booking system or e-commerce solutions) but for 'standard' websites, i really like this cms.
Used Automad for my 2nd webproject. i hope soon there is a solution for this problem, before current webproject is done after 2-3 weeks, so i can move to the production server without problems.
The webserver is Apache/2, see here for more info:
ctuxboy thanks for sharing. I want to run vapid for all static sites as well, but want to use Nginx for these type of sites and Apache for heavy CMS/WP sites as well. I haven't tried to run automad on apache locally yet. But I will try. Are you using MAMP, XAMMP, Local by Flywheel ect.. for local dev?
I investigated a bit more and did some tests. I have installed fresh copies of version 1.2.3 on Apache on both, Mac and Windows and had no problems loading the dashboard. I also tested the updater without any issues. So far I have not been able to reproduce the problems you are experiencing. I have the feeling that either on downloading your first site or while uploading it to the other server, the JS file got corrupted. The only weird thing is that your fresh installation has the same issues. Are you really sure that you have installed a clean vanilla version on your local machine?
Let me emphasize that the only problem right now is the reported syntax error in the automad/gui/dist/libs.min.js file of the dashboard. Replacing that file with a freshly downloaded one, will resolve your issue.
when I access dashboard I get dashboard with no styles or JS working. Also, the reason for this is because if using Laravel Valet, it returns the full path to valet and dashboard as missing/404 error in console.
but if I visit the site.test/index.php I get front-end with inpage editing. I need to be able to access via dashboard
I personally have not so much experience with Laravel Valet. But I think you will have to set up redirection properly to make it work. The CMS is tested on Apache and Nginx and therefore you can find instructions on how to get it running in the docs on the getting started page. There is also an Nginx guide on that page. As you can see in the URL of the dashboard assets you posted, your redirection now is not configured correctly. You won't have such trouble on Nginx or Apache. I would recommend trying XAMPP for testing.
Hope that helps.
I have some basic knowledge about servers and hosting, nothing more.
Locally i used MAMP (apache), but the most of the time developing online. I know, a lot of developers are dissapointed developing online. But for me, it's the best solution there i develop on several laptops/pc's so only what i do for continue developing, is login remote sometimes with my MacBook or a Chromebook. The 2nd reason is the automatic backups on the hosting, so if my laptop crashed, all the stuff is online and nothing lost ;-)
Last but not least, every night, received a backup from the hosting on my Qnap NAS.
Sorry for my poor english.
mad thanks so much for looking into this. I believe this is and will be a solid solution for basic sites. I appreciate you. Great work!
mad Thanks again @mad , I am wondering if you get any issues on nginx?
Hi @mad and @hmfit i download and testing the previous Automad version 1.2.2 and this works without problems. Also move to other servers gives no problems with version 1.2.2.
Tomorrow i try download and testing again the latest 1.2.3 version.
Tested version 1.2.3 locally.
Now that works @mad
Tommorrow tested remote
@mad download and upload version 1.2.3 and now all works!!!! No error anymore when login!
Very happy, and thanks a lot for the awesome support ?
ctuxboy You’re welcome! ?
@mad I have it working now, but only for apache, nginx still gives me issues. However, I get this error when creating a custom theme:
Template "/app/public/packages/custom/humble_start/portfolio.php" not found!
The site I am developing will not have this file, is the file mandatory?
thanks again for such great work!
Hi, those issues are actually off topic here in this discussion. It would be great to open a new discussion for new topics in the future.
However, the Nginx issues you experience are not really related to the cms. Configuring Nginx can be a bit tricky. I think in your case, you didn’t configure PHP correctly. There is a guide and an example nginx.conf in the docs on the getting started page.
And the other error you posted just tells you that your new theme doesn’t have a portfolio template. So you have to choose a template for the page which actually exists in your theme. That’s it.