Access to the Tagdiv builder context menu. I can no longer make these menus work, so I can’t copy or delete a column element or a content element.
Hello!
Check this guide: https://forum.tagdiv.com/tagdiv-composer-tutorial/
More about mega menu functionalities here: https://forum.tagdiv.com/mega-menu/
Check out this guide about a page mega menu: https://forum.tagdiv.com/page-menu/
Simple menu: https://forum.tagdiv.com/main-menu/
Modal popup: https://forum.tagdiv.com/modal-popup/
I hope that helps you!
Thank you!
Hello, thank you for your message. However, this is a specific issue I’m facing: what I refer to as the contextual menus settings of the builder are the tab options proposed for rows, columns, and elements that make up the building blocks of your TagDive plugin (see attached screenshot). These tabs no longer expand.
Regarding this, I noticed that some users mentioned a potential conflict with other plugins. As a reflex — being familiar with WordPress — I immediately disabled all other plugins to test, but the issue persists.
I also checked the browser console to see if any JavaScript errors were being thrown, but there’s nothing noticeable there either.
I’m truly at a loss and losing a lot of time, as I can’t continue working on our NGO’s website (planet-keeper.org) without access to these contextual menus.
Thank you for your help.
Best regards,
Hi,
Thank you for sharing with us the process you have been done. If the problem persist when there are no other plugins except the tagDiv plugins, then what can be is related to the browser that is used (usually this situation can appear on mac), what I can suggest is to try with multiple browsers to see if the problem persist or not.
Thank you!
Contextual Menus Not Working in TagDiv Composer – Persistent React Error #200
Issue Description
The contextual menus (e.g., row settings, column settings) in the TagDiv Composer builder are not opening or responding on all browsers (Chrome, Brave, Firefox). The browser console shows the following React error:
text
Uncaught Error: Minified React error #200; visit https://reactjs.org/docs/error-decoder.html?invariant=200 for the full message or use the non-minified dev environment for full errors and additional helpful warnings.
at react-dom.min.js?ver=18.3.1.1:10:128046
at classic-editor.js?ver=d439270160c30dd62b3a:525:5674
at window.yoast.initEditorIntegration (classic-editor.js?ver=d439270160c30dd62b3a:525:6011)
Steps Already Taken
Disabled all plugins except TagDiv Composer, Cloud Library, and essential TagDiv plugins – issue persists.
Increased PHP memory limit to 256M in wp-config.php.
Added the recommended .htaccess directives for TagDiv builder functionality at the end of the .htaccess file (including SubstituteMaxLineLength 10M and Header always append X-Frame-Options SAMEORIGIN).
Reset theme options via Theme Panel > Support > Reset Theme.
Tested with default WordPress theme (Twenty Twenty-Three) – TagDiv builder not available for testing there.
Verified no 403/404 errors on admin-ajax.php requests in the network console.
Noted Google Maps warnings related to deprecated markers but confirmed API key is valid.
Tested the issue on multiple browsers (Chrome, Brave, Firefox) with the same result.
Technical Environment
Theme: Newspaper 12
Active TagDiv Plugins: Composer, Cloud Library, etc.
Hosting: Infomaniak
PHP Version: 8.1+
Apache modules confirmed active: mod_headers, mod_rewrite
mod_substitute is enabled (confirmed with hosting support)
No server-side errors related to permissions or timeouts found.
Request for Support
Please help identify the root cause of the React error in classic-editor.js, which seems related to Yoast SEO integration.
Confirm compatibility of TagDiv Composer with React 18+ and the latest WordPress versions.
Advise on any necessary server configurations or known conflicts that could cause this issue.
Provide guidance on ensuring proper DOM targeting and iframe handling within the builder to restore contextual menu functionality.
Attachments
PHP and server error logs (available via Infomaniak Manager).
Full browser console logs including Console and Network tabs.
Exported theme settings from Theme Panel.
Additional Note:
The .htaccess directives recommended by TagDiv for the builder’s proper operation have been added at the end of the .htaccess file and are present on the server.
Thank you very much for your assistance. Looking forward to your guidance to resolve this issue.
Best regards
Hi,
We received your email along with the temporary access details. Let’s continue this discussion via email.
Thank you!
What is the exact name of the meta key used for the native “Subtitle” field in article posts?
Sébastien
Hi,
The subtitle meta key filed is “td_post_theme_settings” – and you’ll need to look for meta_value “td_subtitle” – https://i.imgur.com/3gU7I0s.png
Thank you!
Well no! It’s clearly not the right meta key. Not for lack of trying dozens of times. https://planet-keeper.org/wp-content/uploads/2025/05/Capture-decran-2025-05-09-a-10.14.15.jpg https://planet-keeper.org/wp-content/uploads/2025/05/Capture-decran-2025-05-09-a-10.13.53.jpg
Hi,
The mentioned subtitle will work only for articles and if you want to display it you need only to drag the subtitle element from tagdiv Composer to single post template – https://i.imgur.com/Kb51MsL.jpeg – https://i.imgur.com/sS0V02K.jpeg
Now in case that you want to use it on cpts the you’ll need to add a a custom filed element as text on that cpt and use it that one as subtitle.
Thank you!
This is bullshit, impossible to get anything into your subtle! with your “td_post_theme_settings” or “td_subtitle” nor with the form nor with WP-ALL-IMPORT PRO!?
Hi,
Please keep your calm.
Were do you want to use the subtitle? If is on single post template, then you used my above suggestion to us ethe theme element – https://i.imgur.com/CsLQJvD.png – https://i.imgur.com/PnD7Ti8.png ?
There is nothing coming in, it’s incredible, there must be a meta key for this custom field ? https://planet-keeper.org/wp-content/uploads/2025/05/Capture-decran-2025-05-26-a-16.56.47.jpg
Hi,
Unfortunately I don’t understand how this is supposed to work, based on the screenshots this is beyond support, but what I do know and maybe it will help you is that on the loop-single.php file this code https://pastebin.com/dBQEUhdA can be used to display the subtitle. Maybe this will help you, if not then I’m afraid you will need a developer to help you.
Thank you for your understanding!
I created my own custom field and I solved my problem… Now your theme bug with an insert of a ReVSlider shortcode on the home page. This permanently blocks the front TagDiv editing again. I can no longer remove the problematic content. I turned off the revslider plugin and all the others but nothing moves anymore!! Look at my screenshot, here is my home page is no longer editable. It is impossible to find the section that is causing the problem in the code mode in traditional editing. In short, I am starting to really regret my choice. I am wasting hours in problems that do not exist with editors like Elementor or Avada, to name just a few. You are the site admin, I will let you solve this problem. copy screen
Problem solved by deleting the contents in code mode!! I’m still cautious with RevSlider. Do you have any feedback on problems with version 5? Your TagDiv revslider widget doesn’t recognize the created sliders!?
Hi,
For the problem with Rev Slider I think that it will be need to contact us via email at contact@tagdiv.com provide temporary wp-admin access and a few details related to the slider you want to use and the page you want to be set.
Thank you!
