I'm having problems removing pages from a fresh Silverstripe installation (version 4.2.1).
What I'm doing is:
Press batch action
Select the page I want to remove
Choose "Unpublish and archive" in the dropdown
Press go button
The result is a popup saying "Internal Server error".
I have tested this on multiple installations with the same error.
It is probably something wrong with my setup (I'm using MAMP 4.5).
But viewing the logs doesn't reveal any problems. I have checked the following logs:
apache_error.log
mysql_error.log
php_error.log
I have also set the SS_ENVIRONMENT_TYPE = "dev" in .env file.
Is there somewhere else where I can get a more explaining error message so I can find out what the problem is?
This is a bug in Silverstripe: https://github.com/silverstripe/silverstripe-admin/issues/579
Related
We have installed freePBX 13 on RHEL. Everything was working until today. Today, after logging in to the GUI we are getting "Please Select the Default Locales of the PBX" screen.
I have observed that it is rendering from \admin\modules\soundlang\views\oobe.php file and method “oobeRequest()” inside admin\modules\soundlang\Oobe.class.php is calling that page.But unable to trace how it is getting triggered. Are there any hooks which are calling this method dynamically?
Can anyone tell me why this screen keeps coming though I have not updated any modules in frePBX. How to fix this issue.
I'm getting started with Sylius. Symfony version is 3.2.7. On some pages I have some errors. The pages show text:
Oops! An Error Occurred
The server returned a "500 Internal Server Error".
Something is broken. Please let us know what you were doing when this error occurred. We will fix it as soon as possible. Sorry for any inconvenience caused.
I want the errors to be displayed in browser, with full stacktrace.
I know I can see the error in var/prod.log, but it doesn't show the whole stacktrace, only the last frame. And seeing the error in browser would be more convenient: that's what I'm used to after a lot of working with Yii and Magento.
Is that possible with Symfony/Sylius?
I added /app_dev.php to the url to run the website in development environment, and there I can see the stack trace.
That is, https://[my_domain]/app_dev.php/[page] instead of https://[my_domain]/[page]
By default Symfony show trace in dev environment. In prod environment it show simple error message. For running your project in dev you can use built-in PHP Web Server or Web Server Bundle
Also you can use symfony installer app to serve request
Use symfony serve --no-tls in symfony folder.
It will show you requests and errors in red.
I currently have DNN 7 installed and have been unable to get your module to work.
I do a typical module install of 2sic_2SexyContent_08.04.07_Install with apparently no issues.
When I drag the Content module to a pane there's an exception created in the log although the module does show up on the page.
I then click "Auto configure..." and then OK in the pop-up
It shows "installing Getting Started Templates" but then a pop-up shows error 500
The log shows:
"The given key was not present in the dictionary" and "Object reference not set to an instance of an object."
I checked github but couldn't find a resolution.
Is there an easy fix to this as I'd really like to get this installed. Heck, even if it's not easy, I still want to get it installed.
Thanks
Bob
I created a short video for you so you see what you should get: http://2sxc.org/en/blog/post/moving-discussions-from-codeplex-to-stack-overflow
Here another guess
make sure your domain-names/paths are correct in DNN - these are portal settings and if something is wrong there, you will probably get funny redirects
Also: pls post some screenshots etc. - because that will help to understand which part is generating a 500
Note that it's also possible that whatever caused the initial error, did something which is hard to fix for inexperience users. So just to start, it's probably best to first create a new DNN, install 2sxc and when that works, figure out what is different in the two installs.
Keeps showing:
Please configure app/js/config.js before running!
I updated my Firebase URL in config.js, enabled email/password and anonymous login in Forge.
Even changed text in the above error msg to:
"TEST Please configure app/js/config.js before running!"
, in app.js -- and my modified text doesn't show up even. Why? I restarted the web server between changes.
node scripts/web-server.js
Crazy, I can't figure this out.
I figured this out. I also had the ZIP archive in my Trash folder on Mac OS, somehow my console was in my Trash path, (no friggin idea how it got there, as I never cd'd to it), hence changes to my main folder weren't getting detected by the web server running on my Trash folder. Stupid user error -)
I have just updated a site that is using Drupal and have now experienced the horrible WSOD.
I have searched through Google looking for any sort of solution/error log to help me find and fix the issue but nothing has worked. I have tried adding in the 'display errors' code in the index.php file and looked at the error_log file in the public directory and nothing.
I can not login to the admin page and check any modules as the login page for this is returning a 403 error.
Any suggestions?
Please go to Apache Error log. You will exact error messages there.
The log file's location is different for different OS and versions.
e.g httpd/log/error.log
Maybe your Drupal registry is broken.
Fix this using the registry_rebuild script (this is no module!)
There are times in Drupal 7 when the registry gets hopelessly hosed and you need to rebuild the registry (a list of PHP classes and the files they go with). Sometimes, though, you can't do this regular cache-clear activity because some class is required when the system is trying to bootstrap.
You might get something like:
PHP Fatal error: Class 'EntityAPIControllerExportable' not found in ...sites/all/modules/rules/includes/rules.core.inc on line 11
If this happens when you're trying to run update.php, and happens when you're trying to clear your cache, well, you have some trouble. That's what Registry Rebuild is for.
It also may happen that you've moved some module that Drupal requires to bootstrap, and you get a horrible error. Registry Rebuild will also rebuild the system table to get the modules in the right place so you can bootstrap.
You will need PHP-CLI or drush to run this.
https://drupal.org/project/registry_rebuild