0rca

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 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

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 ??

This was indeed a caching issue and Doeke pointed me in the right direction.
Thank you very much Doeke!

Awesome! I had entered a few other shortcodes from the theme and those worked, but now CCS is being parsed too.
Thanks a million Peter!

Oh, and because somebody else here got it wrong before: I am talking about explicit consent, not implicit, i.e. you have to click “Yes” and not just ignore the message and keep on using the site. Only explicit consent can save your ass if somebody really wants to rattle your cage.

Cookies can contain a lot of personally identifiable information, like your user name, your email and so on. But those are usually first party cookies, which might be ok, if you explain your users, why you are allowed to save them and that you do so. And you have to do this explanation before you save that cookie, so the only legally safe way is to wait for the consent before saving anything.

All third party cookies on the other hand might or might not contain any PII per se, but their whole function and purpose is simply to identify a user – so you can’t every save those without prior consent or you risk severe penalties.

Hi Peter,

thank you very much! I will have a look at the code and then see if it is feasible for our customer to make the excerpt mandatory.

Thanks again

Michael

Hi Eliot,
as always, awesome support, thank you so much.

We’re working with MainWP and after many long but successful support sessions their backup system is now working very reliable. On top of that they started to develop plugins for all major backup solutions, so you should be able to find the perfect backup setup for your specific situation.
The rest of MainWP is awesome anyway, they have plugins for almost anyhing you could think of and then some. And their pricing model is more than fair – the one reason I have never even tried ManageWP.
Overall I am now very happy with our WP management solution.

I completely agree. I am not one usually to complain, much less one to give 1-star ratings, but our experiences over the past 1.5 years tells me, they have stopped investing in development and support and are only trying to cash in.

rockethead2 is totaly right. We have worked with InfiniteWP for 1.5 years, spent a few hundred bucks and had many, many problems. So we stopped working with the software and looked at better alternatives. For various reasons we decided to give them another go recently, but that went really bad. Their support is pretty bad and all they do is feed you good will messages, but they actually haven’t solved any of our problems. Now they stopped responding to our tickets at all. Beware!

<script> within a list is correct HTML5.

I know that the basic fault lies with TinyMCE, but I specifically mentioned stuff, that happens differently with the plugin enabled. Just thought you might want to know.

Works perfectly now. Thanks a million!!

Hi Eliot,
thanks for your answer and especially for adding the CSS option, awesome!!
Regarding the code tags, that was my own stupidity, I must have inserted the shortcode with the code tags, I guess by copy-pasting from here. Sorry, my bad, I should have checked that…

Right now the inserted titles gets a before and a </p> afterwards. Any idea why?

My text:
<p>Wollen Sie mehr über [content field="title"] erfahren? Fragen sie uns! Wir stehen Ihnen gerne zur Verfügung.</p>

Result as seen in Firebug:

<p>
Wollen Sie mehr über

Software

</p>
<p> erfahren? Fragen sie uns! Wir stehen Ihnen gerne zur Verfügung.</p>

[Moderator Note: Please post markup between backticks or use the code button. Your posted code may now have been permanently damaged by the forum’s parser.]