Knock out those items and we can troubleshoot from there if it doesn't fix the problem.I have a bunch of stuff to blog about today, and I sat down expecting to write a long rambling post, but then I got sidetracked into some grammar checking stuff, so now I’m writing a post about grammar checking.Īs part of my general mucking around with AI stuff, I decided to finally give in and sign up for a Grammarly account. env config to make sure you're running either PHP 7.4 or 8.0 (depending on your PW version) just in case Devilbox's defaults to PHP 8.1 which PW isn't fully compatible with yet AFAIK. Could be more info there.ĭouble check that $config->debug is set to true in config.php to see if you can squeeze out any more information from your 500.Ĭheck your. I would start with ProcessWire's logs first in case it's able to catch that error when it executes. If you're getting a 500 error with a page title before failure then PHP is booting properly. Some recommendations (and me thinking out loud). And I see no foolishness here :) Working inside the container itself (using the shell script in the Devilbox directory) shouldn't be needed so no worries there. The files you work with will always be on your local machine. (I also dont know if it's an issue that I created the folder and copied files on my mac and not in the container.?) html etc files ok but my processwire files return a title then a internal server error which i cant find the logs for. I probably foolishly am starting from a duplicate of an existing site having copyied the files into the data/sitename/htdocs/ folder and imported the db using phpmyadmin, but getting 500 errors. Just getting set up with a docker and Devilbox after lots of chat about it on the recent share you setups topic.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |