I'm trying to regenerate images for my shop in the backoffice but i get a ERROR 500 page without any stack trace or anything.
so i changed "_PS_MODE_DEV_" to true (and checked that's it's actually true in the code) but i still get the error500.html page content instead of the debug version with the stacktrace.
I tried wiping everything in 'PrestaShopException.php' but i still got the error500.html page content despite the fact that'PrestaShopException.php' is the only file using "error500.html" in its code in the entire prestashop project.
I need to get the stacktrace so i can debug. i don't have access to apache logs
I already deleted the cache folder but nothing changed, my modifications of 'PrestaShopException.php' are totally ignored and when i check the file on the server it's correctly modified..
Related
I have a WooCommerce website that has been created by other party. When I was editing a template file and checking a minor change, a PHP error appeared on top of the page (literally the first line in the document, above )
[12-Jun-2017 19:08:58 UTC] PHP Fatal error: Call to undefined function add_action() in /home/SITENAME/public_html/wp-content/themes/booklovers/widgets/top10.php on line 8
I do know what it means, but it appears that the error itself is not the issue. The time does not change, it constantly displays 19:08:58. I've also tried renaming/moving the file to see what happens - and nothing happens at all. It is being executed, because the page results with a white screen when I put exit; in it. Renaming made no difference. Checking this path by file_exists() called in index results with false. In my opinion it has something to do with Wordpress, because if I put exit; on top of the index.php the page is totally blank, without error, so it is not being merged with the response by Apache or something. Also setting the error reporting in index/config has no effect (I realize that this is generally a bad idea, and would not leave production with a workaround like this).
My guess is that the error might be some kind of a cached artifact. But this WooCommerce has no cache plugins installed so far... I have only a minor experience with Wordpress, I do know the basics, but debugging this type of issues is a terrible pain. I would appreciate any tips suggesting where should I look.
Additional information worth mentioning: shared hosting on GoDaddy (not my choice...), php 5.6.
Resolved. A theme's error_log file was being prepended to the response.
I am trying to build a site which saves a (checkbox) value using PHP to a txtfile. And everything worked fine. However, I'm rearranging the files on the server in order to make it easier later to create more.
I think I rewrote the path's to the files right (including fopen(_ DIR _ . 'pathname')), but when I'm changing the checkbox (which is a form that submits on-click) I get a "ERR_CONNECTION_TIMED_OUT" error and the site links to the error page of my host.
My question is, how can I debug this error? via console I can't find any errors and it's not giving me any information about missing links or files on the server.
Sorry, this is question don't have a code snippet but a situation. I've a Laravel application which was running fine on my localhost and server. Today I made some updates to the controllers and some views. The changes was working fine in the localhost. So I uploaded the files to the server. But when I tried to login in the server, I could see the home page, login pages and all. But getting a white blank page after login.
When I manually try to navigate to other pages in the logged in section, it redirects to the dashboard and blank page comes. Everything is working fine in the localhost. I didn't make any updates to the server configuration. Everything was as before.
OS: CentOS 6.6 (Final)
PHP version: 5.6
Laravel 4.2
Server version: Apache/2.2.15 (Unix)
I checked several answers from other similar questions such as this one and this one. But they all had some updating situation. But in my case not so.
What would be the problem? If you need any additional information, just let me know.
I can give some more information:
When I access a course page (which I need to login to see), it shows a 302 Found status code in the Network tab and then redirects to the Login page where it again shows a 302 Found status code and then to the dashboard with a 200 ok code. Session is being created. Thats' why it's redirecting back to the dashboard page. But the page is still empty.
A blank white screen usually means either
Your'e rendering a template with no content
A fatal PHP occurred before Laravel could completely bootstrap itself
The "right" thing to do here is to check your web server error logs, or your PHP error logs. I'm going to guess you don't know where those are or if they're setup properly. If that's the case you'll want to temporarily change PHP's display_error ini setting. In Laravel 4.2 I'd do this by setting the ini in the following file
#File: boostrap/start.php
<?php
ini_set('display_errors','1');
//... rest of file
This should result in the error being displayed on the screen, and from there you can debug further.
This might be something easy, but it drives me crazy right now.
Joomla 1.5.26 -> site was running until this morning. Now I get an Internal Server Error 500 for the frontpage(html source shows nothing), backend(admin panel) works just fine.
A single editor has worked on some articles, nothing suspicious to me there.
What I have tried so far:
Unpublished all recently created articles
Unpublished modules with dynamic content (calendar, news feeds, recent photos)
reset .htaccess to the original state
reset permissions (all directories 775, all files 644)
enabled all PHP error reporting in configuration.php ( ini_set( 'display_errors', true ); error_reporting( E_ALL ); ) - no error, just a few warinings "PHP Deprecated: Function split()", but I can even get rid of those warings by unpublishing one plugin, after which page is still blank
backend still works
index.php exists and contains the original code, template exists and is assigned
database works, no waiting processes
deleted cache in browser as well as the Joomla cache in the backend
As I have only FTP access to the server, I cannot access any apache logfiles, except the PHP error log. What other options are there to track down such an issue? My hosting company tells me the webserver is working fine, they also told me that they have restarted the server with no changes in site behaviour.
This usually happens when your host upgrades PHP and/or MySQL on the server hosting your website.
Check this post: http://www.itoctopus.com/are-you-suddenly-seeing-an-error-on-every-page-of-your-joomla-website . Your problem is most likely 2.2 (point #2, subpoint #2).
I'm pretty sure that the Apache error logs will reveal something.
I've set up a new server for my magentocommerce.
Unfortunatly when I moved the domain to the new location (tests have been done using another domain) a weird issue started happening: when the login page displays on the frontend, or the backend and I (and customers, of course) do submit the right credentials the page refresh, the cookie gets set but the form is displayed again. It's such a cache being served instead of the right content (catalog).
The only solution actually is delete the cache on the browser and retry.
I've used varnish http accelerator for two days, but since I've had too much issues dealing with it I uninstalled it and cleaned things up (now there's only the apache instance to serve user requests).
I also installed APC caching and Fooman Speedster.
What can it be to cause this issue?
Can you please help me to get in the right direction to fix this issue? On the old server it was not happening, but since that time there have been some modification to the store (nothing to do with authentication anyway).
The apache error log does not report anything, the only thing in there is PHP: syntax error, unexpected BOOL_TRUE in /etc/php5/apache2/conf.d/apc.ini on line 4 which has to do with the line apc.enabled = 1.
Look at the System -> Configuration -> Web tab in the admin panel and see if the Cookie Path and Cookie Domain are set correctly for the new server. You can do it directly in the database as well. In this case, search for rows with web/cookie/cookie_path and web/cookie/cookie_domain paths. Setting them to empty values in the admin panel or NULL in the database may also help.
You should also clear Magento cache (System -> Cache Management) and APC cache (here's how to do it: How to clear APC cache entries?).
I don't know if it solves your specific form problem but we had the same error in the apache error log.
Our failure was, we've copied the apc.ini code from http://magebase.com/magento-tutorials/speeding-up-magento-with-apc-or-memcached/. They use "#" for comments.
Turns out we had to use ";" for comments. After these changes, there were no more errors in the apache error log.