p tags added

Having the same issue here. P tags are automatically inserted whereas they weren’t before.

I think I found a solution:

in gcb.class.php where the array is set to wpautop = false I’ve changed the function at line 514 to:

<?php
if (function_exists(‘wp_editor’)) {
wp_editor(
htmlspecialchars_decode(stripslashes($record[‘value’])),
“gcbvalue”,
array(
//”wpautop” => false,//we do not need auto paragraphs
“force_p_newlines” => false,
“force_root_block” => false,
)
);
}
?>

You can actually remove the “wpautop” => false, from the line as I have it commented out.

the issue with this solution is now any new lines created in the editor in a global block don’t become paragraphs automatically so you have to manually create the <p> tags yourself.

TinyMCE Advanced conflicts with this plugin. It seems if you have the “stop showing” checked it also affects how this plugin acts in regards to <p> tags.

Not sure how to resolve this without leaving it unchecked and using the above hack…but a proper fix needs to be done.

This issue seems to come and go, regardless of the number of suggestions there are for fixes. This will be the third batch of fixes since I took the plugin over. I’ll ask the hard question: What is the consensus for removing TinyMCE and simply using a textarea instead? That would certainly resolve this.

What is the consensus for removing TinyMCE and simply using a textarea instead?

No, I think TinyMCE is still useful.

Is it possible to always load a Content Block at the Text tab from TinyMCE? that could solve this issue.

The issue I’m having is with creating the Content Block itself.

When editing the text, if I want a content block to simply be a link with no <p> so it can be inserted in the middle of a paragraph it breaks the paragraph when the <p></p> is auto wrapped around the link.

The default WP Editor seems to adopt TinyMCE Advanced plugin settings globally no matter what – as long as it uses the WP Editor.

Not sure how to get around this unless this plugin has an ‘advanced config’ section that allows you to modify TinyMCE settings that only directly affect this plugin such as the root_block and p_newlines, etc.

Removing the editor functionality totally is a mistake as I find it valuable being able to use the variables for literally anything from a movie, image, etc.

Is there a way to remove TinyMCE entirely, just make it a textarea but then incorporate a ‘variable type’ that adopts the characteristics of that type?

For example if I create a variable with some text and want it to be a link, I choose “variable type: link” and it provides me with an area for URL to link to, new window/same window, etc. then upon publishing the content block it wraps the textarea in the proper “a” tags.

if I choose variable type: text it wraps it in “p” tags. etc.

Just an idea, otherwise I’m stumped for the time being.

This is a show stopper. Sad to see such a potetionally useful plugin destroyed by @#$%^&*? autop and no one seems to be addressing it despite multiple threads clearly identifying it as a MAJOR PROBLEM. As for now I can waste no more time because deadlines approach.

I’ll follow this in case somebody fixes it for good. I would give movey if it worked, but the script adding p tags to code that it claims in it’s materials that it will not do is way unacceptable.

Maybe you just need a plugin https://www.ads-software.com/plugins/dont-muck-my-markup/

Don’t Muck, and toggle_wpautop and etc don’t work with GCB. I use WP EditPro instead of TinyMCE, which has a toggle wpautop function built in which can be toggled by post type. GCB isn’t listed as an option. Using the toggle autop per page.post, the toggle doesn’t appear on the GCB page. I would settle for no WYSYWYG, just a text area if that could be an option.

I found this that solves the issue, https://www.ads-software.com/plugins/easy-code-placement/ sadly it isn’t GCB,and is really only good for code you want left alone while leaving autop alone for your other content, but it is straightforward and doesn’t meddle with the formatting.

Did anyone found a solution to this?

>What is the consensus for removing TinyMCE and simply using a textarea instead? That would certainly resolve this.

If that’s what’s required to fix things, I’m in favor.