This topic has 15 replies, 3 voices, and was last updated 7 years, 2 months ago ago by Rose Tyler
It just kept on a non responsive state.
I have updated all the plugins and theme, when I deactivate the theme to standard theme and deactivate all plugins, post, page is working fine but not for products too…
i am so lost, please help
Hi kyle0103
Recently I was facing the same issue on ‘Products’ section when I clicked on product to edit, it shows me ‘500 http error’. To solve this go to ‘php.ini’ editor set the values as shown below;
max_input_vars = 5000
memory_limit = 1024M
As I changed these values my product section is working again. I hope this will be helpful for you.
Hello, @kyle0103,
Please try previous suggestion. Let me know result.
Regards
Hi,
I tried, it is still non responsive…
Hello,
Sorry, but wp-admin credentials are incorrect. Please check them.
If the problem with edit products persists with default theme (Storefront) too then it’s not related to our theme, you can contact woocommerce support for further solutions.
Regards
Hi, I have corrected the password, it is now
could you please take a look to ensure it is not the problem of the theme???Because when I switch to the default theme, post, page is working fine..
Please check credentials one more time http://prntscr.com/gncvm6
Regards
really sorry…..it is as per above..
Please describe your problem in details, because I do not face any problem on product http://prntscr.com/gnd1f7 http://prntscr.com/gnd112
Regards
Please clear cache and check now http://prntscr.com/gndwo8
Regards
this is very weird…I still cant get it to work even I cleared browser cache, wordpress cache, changed different browser…..
I can’t recreate the problem using Chrome browser. Please check and describe how can I see the problem.
Regards
I solved the problem, it was all due to cloudflare wouldn’t cache the tinymce…..I added a page rule and it is all good now….
Hello,
I am glad that you sorted out.
Regards
The issue related to '‘unable to edit content (products, post, page)’' has been successfully resolved, and the topic is now closed for further responses