Archived topic
Publishing failed – I can´t publish
12 replies · Started by Johannes on August 21, 2019
Hi there,
I bought the GP premium couple days ago, it's the first time using GP themes. Until now I have been working with other themes.
Now I have started making myself familiar with theme I discovered that I can't publish a page.
I get a note telling me publishing doesn't work.
Can you help me?
Thanks and best, Johannes
Hi there,
Can you try disabling all plugins except GP premium to eliminate any plugin conflicts first?
Let me know :)
Hi Leo,
did that already yesterday before I wrote you. Didn't work.
Any other suggestions?
Thanks a lot.
Best, Johannes
Hi there,
can you check you server settings for the PHP version (at least 7.x) and PHP Memory Limit ( at least 256meg).
Secondly, can you use the browser dev tools, right click inspect the editor, to see if any errors appear in the console when you try to publish post.
If still a problem then activate try step 2 here:
https://docs.generatepress.com/article/debugging-tips/
Hi David,
I am on PHP Version 7.something and my memory limit is at 256 meg.
Don't know what I can do.
Thanks, Johannes
Can you try the other debugging steps i mentioned?
hi David,
tried out different things and now it works. don't why, but ok ;-)
Very odd - but glad to hear its working.
Hello,
I have the same problem since the last update... when I click on the publish button nothing happens, and I have this menu that I didnt saw before.
Any suggestions ?
I know the post is old, but describes my issue...
Hi there,
the Action menu which displays the Publish/Save Draft/Schedule should only appear if you click the Cog Icon in the Publish button. Is that appearing if you click elsewhere on that button?
Hi David and thank you for your reply. I'm sorry but I didnt explain the issue, whenever I tried to change anything into Appearance -> Customize OR Appearance -> Customize -> Additional CSS and I would click the publish button, nothing will happen...
Weird enough, now seems like everything is working fine... I need to mention that I have a caching plugin installed and my guess is that might be what was causing this.
Anyway, thank you very much for the prompt response, and if this issue will occur again, ill make a separate post describing the issue better. Can be closed now, thank you!
As a general rule i disable any cache/optimization plugins when working in the Customizer.
The customizer relies heavily on Javascript so it can easily break if a cache plugin is messing with that.
Glad to hear you got it resolved.
