"Sort", "Audit Trail", "Republish entire site" hang/block/no response when clicked from "Do something else"
Hello everyone. This is a for information post for those that might run into this issue. The folks at Umbraco helped resolve it, big thanks!
Description of the problem: when trying to sort content inside a node, or when you try to republish the entire site (and maybe other functions under "Do something else"), the CMS just hangs without giving any response. Like below:
Turns out this started after running health check on the CMS and deciding to secure it further by preventing content from being included in an iframe. Which is done via the "X-Frame-Options" custom header in web.config.
So when this is set to "DENY" instead of "SAMEORIGIN", some of the functions under "Do something else" will stop working.
Turns out this started after running health check on the CMS and deciding to secure it further by preventing content from being included in an iframe. Which is done via the "X-Frame-Options" custom header in web.config. Above post has solution.
"Sort", "Audit Trail", "Republish entire site" hang/block/no response when clicked from "Do something else"
Hello everyone. This is a for information post for those that might run into this issue. The folks at Umbraco helped resolve it, big thanks!
Description of the problem: when trying to sort content inside a node, or when you try to republish the entire site (and maybe other functions under "Do something else"), the CMS just hangs without giving any response. Like below:
Turns out this started after running health check on the CMS and deciding to secure it further by preventing content from being included in an iframe. Which is done via the "X-Frame-Options" custom header in web.config.
So when this is set to "DENY" instead of "SAMEORIGIN", some of the functions under "Do something else" will stop working.
Therefore the fix is to use this:
So here it is! I caused this myself by changing the security settings so thought someone else might run into it too. Thx. Genc
Turns out this started after running health check on the CMS and deciding to secure it further by preventing content from being included in an iframe. Which is done via the "X-Frame-Options" custom header in web.config. Above post has solution.
is working on a reply...