I am trying to: Add a Types CPT Custom Field (shortcode) in the Content Template editor
I visited this URL:
I expected to see: The shortcode settings overlay for the field
Instead, I got: Overlay with not settings dialog.
Error in Console:
Refused to display 'hidden link' in a frame because it set multiple 'X-Frame-Options' headers with conflicting values ('SAMEORIGIN, DENY'). Falling back to 'deny'.
load-scripts.php:3 GET hidden link net::ERR_BLOCKED_BY_RESPONSE
(anonymous) @ load-scripts.php:3
Ha @ load-scripts.php:3
append @ load-scripts.php:3
n.fn.(anonymous function) @ load-scripts.php:3
a @ jquery.colorbox-min.js:7
complete @ jquery.colorbox-min.js:7
d.complete @ load-scripts.php:4
i @ load-scripts.php:2
fireWith @ load-scripts.php:2
i @ load-scripts.php:4
n.fx.tick @ load-scripts.php:4
I'm solving the problem manually, so just to let you know.
Thank you for contacting Toolset Support. I am not able to reproduce this issue at my end.
1. Can you please also try to check it by deactivating all third-party plugins (except Toolset) and switching back to the Default Theme (e.g. Twenty Sixteen theme) to see for any possible conflicts with any of the plugins or themes?
2. I have checked your site and it looks like Toolset server requirements are not same as required. You can see the minimum Toolset requirements here: https://toolset.com/toolset-requirements/
- MySQL 5.5.5 version in your site, is lower than the required for Toolset.
Okay, so your SQL version is up to date. The JS error looks like some conflict or something like that, if you could explain that how you are resolving it manually then we can debug further.
I'm manually typing up the shortcodes for those specific custom fields into the editor. I've completed the update to the content template and have moved on to other things.
If you want to log onto the site to see the problem for yourself, then I'll configure a user for you.
I therefore don't need any specific assistance to resolve this issue. I logged the ticket more to highlight the issue for your attention, in case it is a problem in the plugin that you can pass on to your developers for resolution.
Thank you for sharing more details, it helped us to understand the actual issue. I have again checked this on multiple sites, but not able to reproduce it. So it definitely appears to be some conflict or compatibility thing between plugins.
Thank you for reporting this issue. As you are already using a workaround, I will keep an eye on this and if it will be reported again then I will be more than happy to forward this to our 2nd tier support for further investigation.
