Hi @luizcarlosfaria
This sounds like it might be a conflict with another plugin.
https://docs.pods.io/faqs/plugin-theme-conflicts/
You could try to clear your cache first (Pods > Settings > Clear cache)
Please let me know!
Cheers, Jory
I came here looking for an answer for the same problem as the OP describes.
I tested our website by disabling all plugins one by one and the culprit (in our case) is Yoast Duplicate Post, a very common plugin.
I have no clue where the fault actually lies, but I see the same happing on 3 websites, where we use both plugins. So this might be worth looking into?
I have disabled Yoast Duplicate Post for the time being, as I can easily live without it but not without Pods 😉
Hi @0rca and @luizcarlosfaria
I’ve tested the issue with the Yoast Duplicate Post active but cannot reproduce the issue.
Maybe a latest update from this plugin fixed the issue?
Cheers, Jory
Hi Jory,
I just checked, but the issue is still there with Yoast Duplicate Post 4.3.
Wanna have a look at the system in question?
Cheers,
Michael
Hi @0rca
We are not allowed to log into your installation because of WordPress forum policies.
Is the error happening only on CPT’s or also on WP core post types (posts and pages)?
If you can, please provide a step by step instruction on how to reproduce this on a clean installation.
Cheers, Jory
I dug a little deeper and found another plugin that contributes:
Essential Grid 3.0.13 by ThemePunch, a paid plugin (CodeCanyon)
I have switched the theme to a vanilla Twenty Twenty-One and deactivated all plugins expect for these 3:
Yoast Duplicate Post 4.3
Essential Grid 3.0.13
Pods 2.8.8.1
As soon as I deactivate either of these, editing posts (any posts, not only Pods CPT) works again, otherwise I get the timeout. Going back to Pods 2.8.5. also helps and editing posts is possible. So whatever conflict is happening between these 3 plugins, it was introduced with on of the latest Pods updates.
Hi @0rca
Ah check, another issue with the Duplicate Post plugin.
This has been reported several times.
I’ve added a report on GitHub so this issue gets tracked: https://github.com/pods-framework/pods/issues/6379
Cheers, Jory