Archived topic
GenerateBlocks PRO causing conflict with PHPFPM.
11 replies · Started by Sergio on January 18, 2021
Hi Tom
I had to uninstall the new GB PRO because it causes conflict with PHPFPM.
My hosting provider is Cloudways with a server at Digital Ocean
I think the information is important because it is not possible to use the plugin.
Thanks in advance
Hi there,
are you receiving any server errors ? Any logs you can share so we can see what the issue maybe?
Hi David
I copy and paste the logs from one of the apps (in private information)
But each app released a different error so I don't think it's worth anything.
What I can say is that it affected all the apps on my cloud server. That is, just by installing GB PRO in one app, it already affected all the apps in the server.
Thank you very much
Hmmm.... can't see what GB Pro would do to cause that issue.... if you don't mind ill pass this onto to Tom to see if he can shed some light on this.
OK. Thanks David
Hi there,
I'm not seeing anything related to GenerateBlocks in there.
I have quite a few sites on Digital Ocean using GenerateBlocks with no issues.
The only thing I can think of is a server setting is conflicting with the external CSS file generation. Have you tried setting it to inline in "GenerateBlocks > Settings"?
Hi Tom
I'll try that CSS inline.
But it's the PRO that gives me problems, the free one doesn't give me any problems
Can you:
1. Clear your error_log so it's empty.
2. Activate GenerateBlocks Pro
3. Check your fresh error_log and provide us with the results to our GenerateBlocks Pro support: https://generateblocks.com/support
Thanks!
Hello Tom
I upgraded the plugin to the new version and have had no further problems.
But other problems are cropping up.
I attach a private video of something very strange: I select a container to put a link, and the cursor selects another container.
The attached video shows it perfectly
Thank you in advance
Hi there,
This is a known issue with the "Hidden Link" container link option.
For now, try the "Wrapper" option inside the container link options.
This will be fixed in the next version :)
Thanks Tom!! :)
No problem!