iframe disappearing from page when saved

[robi]

@p44 should this be fixed in the WP App package for all new installs?

[girish]

This change was added as part of https://forum.cloudron.io/topic/3520/disallow-unfiltered-html-in-wp-config-php . Currently, it's present only in the unmanaged WP as the default. Like many other things, it seems more security === breaks something.

@p44 thanks for the solution!

[humptydumpty]

@girish I think it's fine to keep it as it is. I only embed iframes on 1 out of 4 WP installs that I have running so I can see the benefit of having it set like that by default.

I've never went through this before and had no idea what to look for after I ruled out any plugins/themes as being the culprit. It just left me scratching my head. It would be nice if you could add a mention of it in the docs though https://docs.cloudron.io/apps/wordpress-unmanaged/

[girish]

@humptydumpty Done

[humptydumpty]

@girish The changes aren't showing up for me in a new private window. I'm guessing you need to clear the cache on your end?

https://docs.cloudron.io/apps/wordpress-unmanaged/

Unless I'm looking at the wrong page

[girish]

@humptydumpty https://docs.cloudron.io/apps/wordpress-developer/ is the correct page

[humptydumpty]

@girish On the WP (managed) doc page --> Database Access --> ARI Adminer - if you follow the link it'll show that it has been closed for security issue. https://wordpress.org/plugins/ari-adminer/

As an alternative, if someone needs a GUI, I've used Adminer before and it works well but requires manual upload of the file as it's not a plugin and isn't specific to Wordpress. https://www.adminer.org/

[humptydumpty]

@girish Cool, thanks. It loads the "unmanaged" version in the left sub-menu if I browse to the link directly even though it's opened in a private window so if I'm not mistaken, it shouldn't be a browser cache issue on my end.

[girish]

@humptydumpty Yes, I noticed that as well. I think this is some surfer quirk . @nebulon will know.

[nebulon]

Hm surfer will send cache-control: public, max-age=0 so I am not sure why it would cache as such, the etag also should have changed if the source content was updated.