I had FPC (full page cache) enabled
There is one category containing subcategories and 900+ products. it was working fine but suddenly it started pushing 500 internal server error.
i have not add any new product or any major change. so now when i disable the FPC, the category start working and when i re enable FPC, again internal server error 500.
i have already applied couple of solutions but no success.
tried with removing cache at all, re indexing, crons, have check the htaccess also all things are fine, i had try with creating new category but when i assigned the same block to load on that category, again same issue started.
log is saying that
The problem is in the function getIdentities()
can anyone help with this? thanks in advance.
i resolved this issue.
Here is the solution:
When we will have a bulk products in a category we can either enable Varnish cache or Full page cache. we cannot enable both simultaneously, otherwise it will through internal server error if both caches will be enabled.
Related
I have extended Manage journal Entries app in Web Ide. Haven't added any extra code. Just saved it and run to check whether the app is opening as expected or not. But I am facing error " Could not open app, Please try again later".
Come across few threads regarding similar issue but my issue is not while launching, It is when extending manage journal entries app.
Fiori : Could not open App
Pre Requisite which I have checked:
SICF Service is Active.
component UIS4HOP1 200 SP 0000 is installed in my FrontEnd Server.
Thanks,
Srilaxmi
From the error message in the commments section it seems like you have problems with the namespace of the component. Did you check that the path and the namespace for your extension project matches the deployed app? This can very easily mess up the component loading mechanism in FLP and lead to the described result...
Magento 2.1 admin:-
When updating configurable product I am getting the following issue.
You don't have permission to access /admin/catalog/product/validate/id/3316/type/configurable/store/0/set/4/key/11c0d458dc11fc072a5fdef7f5fb3fe633c433bbf0342175b987f10588ee2b2c/
Thanks in advance.
I have fixed that.
Just checked the server log and found that it was mod_security extension is enable.
That should be disabled.
Okay, How many products are you going to create or assign while creating configurable product.
I have experienced the same issue and I have sorted out with creating a configurable product with few product assignment.
I hope this may help you
Thanks
We were getting the following error -:
=======
403 Forbidden
You don't have permission to access /admin/catalog/product/validate/id/966/type/simple/store/0/set/9/
=====
Emailed hosting provider and they did change the setting at the server level. As soon as they changed the setting the error went straight away.
If they can’t change the setting on the server for some reason then look for product data. You will find malicious code, in our case it was iFrame code snippet which was causing that trouble.
I have installed the wordpress seo (yoast) plugin on my wordpress site, but if i am activating the plugin it breaks the site. I can access the backend (dashboard) but nothing is visible on front end. It's showing an error message
"The page isn't redirecting properly
Firefox has detected that the server is redirecting the request for this address in a way that will never complete.
This problem can sometimes be caused by disabling or refusing to accept cookies."
I have already gone through the plugin support but couldn't find anything related to this.
Please provide any solution to resolve the issue.
Thanks!
There might many causes of breaking site after activating plugin. In your case, may be the reason is memory limit. Please try to add support for more limit. You can use WP_MAX_MEMORY_LIMIT to increase it.
You can debug the site using WP_DEBUG in wp-config.php, set it true you will get all the warnings and fatal errors to check the main cause of break.
I Request you to enable debug the site using WP_DEBUG in wp-config.php, set it true you will get all the warnings and fatal errors to check the main cause of break. as mentioned above by #Trimantra Software Solutic.
Go to wp-config.php and find define('WP_DEBUG', false); replace with below
define('WP_DEBUG', true);
After then you will find the error !
I want to update a TYPO3 Project from 4.1 to 6.2.9. In order to do that I need to upgrade it to find the most compatible extensions. So I've updated the TYPO3 to 4.5. Now the back end loaded and it shows some arguments that are printed. Also in front end it shows this error.
The requested page didn't have a proper connection to the tree-root!<br /><br />(Broken rootline (failed on page with uid 7))
I fixed this issue.
After going to Install tool. In DB Analyser there are so many tables are not properly indexed. After fixing that this issue has been fixed.
Truncate realURL-tables and clear Cache via InstallTool.
This works for me.
I have a problem, that whenever I make changes to my custom API extension WSDL file, the changes are not visible immediately. It takes a day or two for them to appear. I have tried to clear the Magento tmp directory, but there is nothing to be cleared. Also, I have tried restarting my local apache server, and cleaning its /tmp directories, from where I make API calls, but no help.
Does anyone have idea why is this, and how it can be corrected? Thanks for any advice.
In order to get changes for the various xml files to take effect in a more timely manner you have to clear the magento cache. It can be found in $magentoinstall/var/cache
When you do that it forces magento to reprocess all the config and your change should appear right away.
I hear tell you can use the magento admin panel to accomplish this as well
Go to System -> Cache Management
Click on “select all” in the upper left corner
Under “action” click on “refresh” and click submit
Then click on these buttons:
Flush Magento Cache
Flush Cache Storage
I've never used the 2nd method. See here for more information.
http://www.magentocommerce.com/wiki/modules_reference/english/mage_adminhtml/system_cache/index
Clearing cache from System -> Cache Management seems to have 0 affect on WSDL.
While testing you can prevent Mage from caching WSDL with this code:
$client = new SoapClient('http://somewhere.com/?wsdl', array('cache_wsdl' => WSDL_CACHE_NONE) );
On the server side you can disable Magento Wsdl cache at System->Configurations->Services->Magento Core API->Enable WSDL Cache.
Maybe you should remove all files from var/cache/ folder.
On the client side (api client) you can simply add
ini_set("soap.wsdl_cache_enabled", 0);
to avoid SoapClient lib caching.