Archived topic
Does not work on WordPress network
13 replies · Started by aranyklinika on January 4, 2021
Hello,
I have installed the GP Premium into my WordPress website (on WP network and only 1 website) and i have selected a theme from site library name “Ethos” but when I edit anything and update nothing happened, the content not updated. (Classic and the Gutenberg editor is not installed only the GenerateBlocks)
I am waiting for your response.
Thank you!
Hi there,
when you make changes in the editor, are those changes saved ? ie. do you see the changes when returning to the page editor ?
I don't see the changes when i returning to the page editor.
This is WordPress core function that the theme has no control over, so it must be a WP / Server settings issue.
Check your server error logs to see if any errors are reported after saving changes to the post. This should give you a pointer as to what is going wrong.

Full log: https://easyupload.io/fa25ra
Can you try disabling GenerateBlocks for now and see if the content saves that way?
I turned off the Generateblocks plugin and then switched from block editor to classic in the settings and network settings. I modified the post and still didn't save it.
The next step was to turn the Generateblocks plugin back on and then switch to the classic editor inside the editor, so it saved. Unfortunately i don't see the styles in classic editor.
Hi there,
Those console.log errors won't prevent the page from saving, but they do show that something isn't right.
What version of GenerateBlocks do you have installed?
GenerateBlocks - 1.2.0
GP Premium - 1.12.3
GeneratePress - 3.0.2
Can you try deactivating all of your other plugins to see if one of them is breaking the editor?
We're not aware of any issues with that combination of versions.
Yes. I turned off all plugins except GP Premium, GenerateBlocks. This does not save the pages.
The fact that your pages still weren't saving without GenerateBlocks activated shows me that there's likely something up with your WordPress installation/server. We haven't had any other reports of similar issues since you've mentioned this.
If you create a test site on the same server, is this issue reproducible?
We found the error! Caused by a redirect in htaccess...
Glad you got it sorted :)