I’m on the latest version 12.7.3
I’m on the latest version.
I’ll create an admin account for you.(contact@tagdiv.com)

psw: neuro2026
https://neuro.swiss/wp-content/uploads/2025/12/Capture-decran-2025-12-15-a-14.30.22.png

This is a mobile mode code error affecting the menus… I’ve temporarily hidden it with this code: // Hide PHP warnings
error_reporting(E_ERROR | E_PARSE);
ini_set(‘display_errors’, ‘0’);

Incredible It was Claude who informed me about this “bug” or “defect” of TagDiv: if you put even a transparent color in the background color of the site, your website goes into Boxed mode!

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

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

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

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

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

What is the exact name of the meta key used for the native “Subtitle” field in article posts?

Sébastien

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

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,

• This reply was modified 1 year by Sebshot69.