Skip Navigation

[Resolved] There's an issue when creating New Post Form, plugin CMSMasters Content Composer

This support ticket is created 3 years, 10 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 - -
13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 - -

Supporter timezone: America/New_York (GMT-04:00)

This topic contains 10 replies, has 2 voices.

Last updated by Christian Cox 3 years, 10 months ago.

Assisted by: Christian Cox.

Author
Posts
#1921793

I am trying to:

I found that there is an issue when creating New Post Form, when plugin CMSMasters Content Composer is active, because the page goes blank. When I deactivated the plugin, I was able to add New Post Form just fine

Thanks

Link to a page where the issue can be seen:

I expected to see:

Instead, I got:

#1921823

Hello, I can check this out but I don't have access to the CMSMasters Content Composer plugin. Can you upload the plugin and any other required components to Drive or Dropbox and provide a download link?

#1921911

hey there, thats the link to all the plugins which relate to the Theme

hidden link

Cheers

#1921969

Okay it seems that I need a CMSMasters theme as well to activate these plugins. Can you provide a download link for the theme you are using?

#1922021

Thats the link to the theme

hidden link

#1922095

Okay thank you. When I activate this theme and the 4 required CMSMasters plugins, I am able to see the same problem in Toolset > Post Forms > Add New. The page appears blank. There are no PHP errors thrown, but I do see a JavaScript error in the console:

Uncaught TypeError: CodeMirror.overlayMode is not a function
    at codemirror_shortcodes_overlay (codemirror_shortcodes.js?ver=2.6.6:202)
    at getMode (codemirror.js?ver=5.46.0:732)
    at loadMode (codemirror.js?ver=5.46.0:4671)
    at attachDoc (codemirror.js?ver=5.46.0:4769)
    at new CodeMirror (codemirror.js?ver=5.46.0:7874)
    at CodeMirror (codemirror.js?ver=5.46.0:7828)
    at Function.fromTextArea (codemirror.js?ver=5.46.0:9659)
    at toggleCodeMirror (icl_editor_addon_plugin.js?ver=4.0.10:1107)
    at Object.codemirror (icl_editor_addon_plugin.js?ver=4.0.10:1150)
    at Toolset.CRED.PostFormsEditor.Toolset.CRED.EditorPagePrototype.initCodemirror (editor.prototype.js?ver=2.6.6.1611847214:188)

It seems to be a conflict with the CodeMirror library we use to display code editors. Let me escalate this to my 2nd tier support team to see what we can do to resolve this. I'll let you know what I find out. In the meantime, it may be necessary to temporarily deactivate the CMSMasters Content Composer plugin while editing Toolset Forms.

#1926739

A quick update to let you know our 2nd tier support team has escalated this issue to the developers as a compatibility problem. I will keep you updated as I receive more information.

#1927839

Ok, thanks, I hope it can be fixed

#1928287

I have an update from our developers. The main issue we see is that the CMSMasters Content Composer plugin is forcing the block editor on all posts that do not use their page editor, and this includes our Form builder posts in wp-admin. From our developers:

Basically, every post that does not hold a given postmeta flag for their own page builder is managed as if it used the blocks editor. As a test:
- Create a new post tpe with Types and tell it to use the Classic editor.
- Create a new post in that type and notice that it loads the blocks editor.

From their code:

// Class Cmsmasters_Gutenberg
add_filter( 'use_block_editor_for_post', array( $this, 'block_editor_disable' ) );

public function block_editor_disable() {
	$is_composer = $this->is_built_with_composer( get_the_ID() );
	return $is_composer == 'false' || $is_composer == '';
}

public function is_built_with_composer( $post_id ) {
	return get_post_meta( $post_id, 'cmsmasters_gutenberg_show', true );
}

In my opinion, a support ticket against that other premium product is required, urging them to stop enforcing the blocks editor into every post that does not use their own page builder. I see that similar issues have been mentioned in different internet resources (I cna not access their support forum, though).

This is something that should be discussed with the support team for the CMSMasters Content Composer plugin, since we cannot resolve it in Forms.

#1929505

Hi Christian

I contacted the support CMSMasters team and i got a message as such

"I can recommend you update the theme and all the plugins that come with it, this may solve your problem.
The current version of the theme is 1.1.4 and it is available on ThemeForest.

I should note that we do not provide support regarding third-party plugins, as in fact we do not guarantee the third-party plugins compatibility with the theme, and alas there is not much we can advise regarding this. There are tons of different plugins available and we cannot ensure compatibility with the theme for all of them. Appreciate your understanding."

First I am going to try updating Theme template, and see if anything changes
If it is not going to help it, Is there a chance that I develop the Contact Form with the CMSMasters Content Composer OFF and then display it with CMSMasters Content Composer ON, can I test it anyhow?

Thanks

#1929591

First I am going to try updating Theme template, and see if anything changes
That sounds like a good plan, and I hope it solves the problem.

If it is not going to help it, Is there a chance that I develop the Contact Form with the CMSMasters Content Composer OFF and then display it with CMSMasters Content Composer ON, can I test it anyhow?
Yes, that sounds reasonable to me. If you temporarily deactivate the Content Composer plugin, you should be able to use Toolset Forms successfully, then reactivate the Content Composer plugin later when you are finished developing the Form. Feel free to test if you'd like...I suspect there may be other issues like this, not limited to Forms development, when the Content Composer plugin is active, based on the way they force the block editor.

It's a shame the CMSMasters team does not provide compatibility support for 3rd-party plugins. Without their collaboration, we cannot provide a better solution to this problem in our software.