I've developed a magento website with the fishpig extension, and as soon as I turned on my Lesti's FPC, i got a white page without any errors on the homepage.
I've managed to trace the error down to the post collection, but I don't know how to fix this issue. Someone had any experience with this?
This is what my post collection looks like:
<?php $posts = Mage::getResourceModel('wordpress/post_collection')
->addPostTypeFilter('sliders')
->load();
?>
I'm pretty sure this error has nothing to do with Lesti FPC. If you have a white page without any errors, this just means that an error has occured but your PHP error display settings prevent it from being displayed. To display the error, open up your Magento index.php file and uncomment the following line:
ini_set('display_errors', 1);
This will reveal the PHP error message. That being said, your issue will probably be fixed by performing the following steps:
Upgrade Magento WordPress Integration to the latest version. Also update any add-on extensions for Magento WordPress Integration.
Check System > Configuration > WordPress for any errors/warnings and fix every single one.
Check var/log/ for a wordpress.log file. Delete this file and then go back to the page that triggers the error. See whether any new errors are added to the file.
Please perform these 3 steps (these steps should be followed for any error with Magento WordPress Integration) and see whether the error persists. If the error does remain after following these steps, please update your question with the specific error message (but only after following these 3 steps).
Related
when i click print invoice in a magento invoice if im in chrome instead of the pdf download it just gives me a blank page, if im in IE it gives me a 500 internal server error.
i already tried the magento cleanup script, reindex, cache and recompile and nothing
can you give me a hand?
did not get many help with you guy's but i will post the awnser that i found for my own problem you just install the patch SUPEE-2629 for compatibility with php 5.4 you can find it here
https://www.magentocommerce.com/download
In my magento shop I see the following error after installing magento 1.9:
Fatal error: Call to undefined method Mage_GoogleAnalytics_Helper_Data::getAccountId() in /var/www/magento/app/design/frontend/base/default/template/googleanalytics/ga.phtml on line 29
When I disable Mage_GoogleAnalytics in my settings the error disappeared and my site is working again.
Could anyone help me to fix this?
When you upgrade magento then all core files not update sometimes then this issue come.
You need to make sure all files for GoogleAnalytics available and updated. You can check here:
/app/code/core/Mage/GoogleAnalytics/
/app/design/frontend/base/default/layout/googleanalytics.xml
/app/design/frontend/base/default/template/googleanalytics/ga.phtml
You can compare these files from new installation and update if need.
After that clear cache.
This will work.
Just need to tweak your settings and flush cache.
Open magento admin panel and under system->configuration ensure you have your google analytics account entered. If you have multiple website/store scopes visit each one to be sure.
Make sure to flush all caches afterwards.
Try as I might, I can't get proper error messages in Joomla 3.1.5. No matter what I do, I get redirected to a nice "Error 0" page which doesn't tell me what happened where. I've tried setting error reporting to both maximum and developer in the admin console, and turning on developer mode. Is there any way to get proper error messages instead of friendly error messages to display in Joomla 3.1.5?
If you're not seeing the errors it's likely that you have an extension installed that is calling set_exception_handler(), while I don't have an STS 3.1 version anywhere to test the 3.2's we do have don't have any issues with reporting errors. (And as far back as I can remember, I don't believe Joomla core calls set_exception_handler().
We write Joomla extensions for clients as our primary business and I can tell you that the error reporting works. We have found in the past that some more dodgy extensions install their own exception handlers to hide issues in their code which is why we always develop and test on clear default Joomla installations.
Updated
Just saw your answer…
If that work's it means something is definitely calling set_exception_handler() which I don't believe is Joomla, I don't have have STS 3.1 installation but my current 1.5, 2.5 and 3.2's do not call set_exception_handler() in the Joomla core.
Few thoughts:
Check in Joomla the PHP information - see the error reporting local
value.
Check for a local php.ini file
Check if there is any ini_set code in your template...
Try adding a code like below, in your template's index.php file.
code:
<?php
ini_set('display_errors', 'on');
ini_set('error_reporting', E_ALL & ~E_NOTICE);
?>
Figured it out -- calling restore_exception_handler() gets rid of the poxy Joomla page and lets me read the text of the error.
Hi i am going through very strange issue in magento , i have several categories i magento with child categories , i need to update a category information ,i am able to update the many categories but when i try to update the first category under the default category , it didn't work and the browser keeps on loading .I have tried to found the issue on google but nothing was there , in some places it was suggested that it happens due to upgrade but i haven't upgrade the magento or any other module .Please suggest me what can be the issue .
Thanks
This happens in some cases where the category name contains special characters.
This is for sure a javascript error, otherwise you would have got a response from the server, in this case the you are not getting a response and hence the loading continues. What you could do is check the server response and monitor the firebug / inspect element to get some ideas.
You can check for these javascript elements in the
/app/design/adminhtml/default/default/template/catalog/category/tree.phtml file.
You should add some more info to the question starting with the Magento version, but follow these steps:
Enable error printing in general by adding these lines to your .htaccess
SetEnv MAGE_IS_DEVELOPER_MODE 1
php_value display_errors 1
Enable logging in Magento in System->Confihuration->Developer->Log Settings
Do as Keyut suggested and try to update the erroneous category with the console open, monitoring the XHR calls. Check the response of the call invoked after you clicked "Save" for errors.
Do as Tobias suggested and check the logs found under var/log in your Magento folder.
By now you should have at least found the error, so you can solve it or ask for further help.
I've just installed Magento on my website, but I can't access the backend. The frontend works fine, but in the backend once I successfully login, it takes me to a blank screen. I've read there's an issue with cookies and I've tried a range of commenting out lines in varien.php, but didn't work.
Go to /var/log/exception.log and check for any errors.
Alternatively in index.php just before the last line:
Mage::run($mageRunCode, $mageRunType);
put this
Mage::setIsDeveloperMode(true);
ini_set('display_errors', 1);
It should throw some sort of error now, and go from there.
Blank screen is almost always a PHP error of some kind (as opposed to a Magento Exception). Check/turn-on your PHP error logs and you should find the error you're looking for.
For the cookies issue, install and access Magento using htp://127.0.0.1/magento/ instead of htp://localhost/magento/
Please clear var/cache/ folder and var/session/ folder and refresh .