When Xstore theme is activated and Gravity Forms is activated, we were unable to edit pages. It would spin for a bit and then come back with
This page isn’t working
XXXXXXXX.com didn’t send any data.
This only affected pages. We could still edit posts and Custom Post Type posts.
If we deactivate Gravity Forms, we are able to edit pages.
If we kept Gravity Forms activated and then deactivated our XStore child theme and reverted back to the stock XStore theme, the issue continued to happen. So the issue appears to happen when any of the Xstore parent or child theme is activated and when Gravity Forms is activated.
If we deactivated XStore parent theme and activated Twenty Seventeen theme, and also keep Gravity Forms activated, we are able to edit pages just fine.
The conflict is between XStore and Gravity Forms. Nothing is logged in the php error log.
Extending the PHP Max Execution time to 200 allowed the pages to finally be able to be edited, but it takes almost 30 seconds for the pages to load editor.
We deactivated all plugins and turned them back on 1 by 1 to determine that Gravity Forms was causing XStore to not load pages. We have Gravity Forms running successfully on many other websites running different themes.
We noticed several other people in the support forums reporting similar issues over the past week – no one reported Gravity Forms, so I am passing this info on to you. We are running the latest version of Gravity Forms – 2.6.3Site URL: hidden Theme version: 8.1.5 WooCommerce version: 6.5.1
Could you, please, provide us with the server error logs and with the FTP access to your site? We need to check if you get any errors related to our theme in the error log and then fix them in case you have something.
There is nothing being recorded in the server log as the error we get occurs because no data is received as part of the server response.
The production server does not have FTP access. We can however grant you SFTP access if you are able to provide us with your public SSH key.
Alternatively we can move the site to a testing server where we do have FTP access and grant you access there.
Note we moved the to our local development server last week and error persisted, so I feel confident that if we move to a pubic testing server that it would present itself there as well. Either way works for us, just let us know if you can provide an SSH key or if you’d like it move to a different server with FTP.
I think that it would be better if you create a staging site (full copy of the production site) and provide us with WP Dashboard and FTP or SFTP access. Also, provide us with a video of your actions to reproduce the issue. And we’ll take a closer look at this problem and try to fix that.
We are still working to get the site on a staging server for your review.
Ok. Take your time. Provide us with access once you finish.
We have moved the production site over to a testing server. See private info for login creds.
You must be logged in to reply to this topic.Log in/Sign up
One standard license is valid only for 1 project. Running multiple projects on a single license is a copyright violation.