Warnings on Edit Page after 1.5.0 update

Good day @matthisamoto

IT feels like you may possibly have a different plugin or perhaps your active theme that has an older copy of CMB2 or possibly even a copy of https://github.com/WebDevStudios/Custom-Metaboxes-and-Fields-for-WordPress in it.

Do you know if this is the case, to the best of your ability to identify?

Asking because some code being added/run may not be compatible with the copy of CMB2 that we have shipped with 1.5.0’s release today, and it being passed to this latest version as opposed to some other bundled older copy of CMB2.

A quick plain text search for CMB2 inside the plugins directory shows only one hit that’s not in the Constant Contact plugin, which is Custom Post Type UI. However the references are only in two files and seem to be reference links and not actual inclusions of the library:

[path]/wp-content/plugins/custom-post-type-ui/inc/support.php:
  212  								printf(
  213  									esc_html__( 'We recommend checking out %s, the latest iteration of "Custom Metaboxes and Fields for WordPress". Both are maintained by WebDevStudios.', 'custom-post-type-ui' ),
  214: 									'<a href="https://www.ads-software.com/plugins/cmb2/" target="_blank">CMB2</a>'
  215  								); ?>
  216  							</div>

[path]/wp-content/plugins/custom-post-type-ui/readme.txt:
   19  Official development of Custom Post Type UI is on GitHub, with official stable releases published on www.ads-software.com. The GitHub repo can be found at [https://github.com/WebDevStudios/custom-post-type-ui](https://github.com/WebDevStudios/custom-post-type-ui). Please use the Support tab for potential bugs, issues, or enhancement ideas.
   20  
   21: [Pluginize](https://pluginize.com/?utm_source=cptui&utm_medium=text&utm_campaign=wporg) was launched in 2016 by [WebDevStudios](https://webdevstudios.com/) to promote, support, and house all of their [WordPress products](https://pluginize.com/shop/?utm_source=cptui-&utm_medium=text&utm_campaign=wporg). Pluginize is not only [creating new products for WordPress all the time, like CPTUI Extended](https://pluginize.com/product/custom-post-type-ui-extended/?utm_source=cptui&utm_medium=text&utm_campaign=wporg), but also provides ongoing support and development for WordPress community favorites like [CMB2](https://www.ads-software.com/plugins/cmb2/) and more.

I’m not using the Custom Metaboxes plugin but CPTUI is from the same group. Also using Advanced Custom Fields, however I didn’t see that pop up any results for CMB2.

One thing to keep in mind with CMB2 and the legacy Custom-Metaboxes-and-Fields-for-WordPress item referenced earlier is that they are libraries first, that can be bundled in with other plugins(like we do) or even themes. So it won’t hurt to check the theme as well. Try searching both plugins folder and themes folder for something like cmb_meta_boxes which is the legacy way of adding new metaboxes.

Also if your theme has a folder named “metaboxes” or “meta” or something similar, that may be it as well.

I’ve built a custom theme, so that library is not included there. I did add a metabox area using the traditional methods in WordPress (do_meta_boxes), and I did check that by commenting that out to see if it affected anything, and it did not.

I stepped up the search to the whole WordPress instance and the only mentions of CMB2 are the same ones I shared earlier.

I also deactivated every other plugin except yours and it continued to show these warnings.

Futhermore I decided to really strip things down and try it on a new installation of WordPress, and it still shows me these warnings, with the default theme enabled (no other plugins installed).

• This reply was modified 5 years, 11 months ago by matthisamoto.

Hmm. Thanks for being willing to dig in so much with this.

Give is a chance to try some extra things out and see if we can reproduce in the same way. We definitely want to prevent the error for showing up for others, and definitely didn’t intend to ship with anything like that occurring. This is why we’ve requested yourself checking other spots that may have had conflicting code.

Lastly, just in case something is potentially stored there, is there anything in a wp-content/mu-plugins/ folder for you?

Sure thing. I definitely have debug mode on so I’m seeing things like warnings, but I appreciate that you’re looking into it.

Not using mu-plugins on this build.

Last question at the moment, are you willing to provide a list of the plugins you’re currently using for the site?

We can provide emails to send this info to, if you prefer to not publicly post them.

You can provide the email but please keep in mind I tried your plugin on a WordPress installation with no other plugins installed and still had the same issues, so I’m not sure it’s going to be of use.

Just in case they’re playing a part, the original install that had some would work. We also have some leads on our own end as well, that we’ll be investigating soon.

[email protected] and cc of [email protected] will reach the appropriate people.

Still looking into a permanent solution, but some of our debugging has revealed that simply getting a form created, should help get you going back into overall development of your site.

One last update in that we feel we have found a viable solution to this, and will be rolling it out soon.

Let us know if you’re interested in helping to test and confirm the errors going away. We’d appreciate the extra confirmation.

I’m also having issues with the 1.5.0 plugin update today. My WPBakery Visual Composer will not let me edit my pages. If I disable the CC plugin, it works fine. It was working fine prior to installing today’s update to 1.5.0. Further, I have the WP original editor installed as a plugin to my site and in text view you can’t view the editor boxes to add links, text formats, etc. I’m talking about the “b” “i” “link” etc. buttons like in this reply box. I don’t know what happened with today’s update, but it is not playing nice with WordPress. I think the last time I updated this plugin as well it had a bug in it and had to be fixed. I’ve had to disable Constant Contact for the time being. Thank you.

• This reply was modified 5 years, 11 months ago by raptureforums.
• This reply was modified 5 years, 11 months ago by raptureforums.

@raptureforums See our comment at https://www.ads-software.com/support/topic/warnings-on-edit-page-after-1-5-0-update/#post-11406020 for a quick workaround until we’re ready to have some proper code fixes tested out.

Just to also note that there is an issue with the Yoast SEO plugin and not being able to edit page titles and meta descriptions when the 1.5.0 CC plugin is enabled. I’ll take a look at the link above. Thank you.

ETA: Looked at the link above and will eagerly await a fix. Thank you for checking into it. ??

• This reply was modified 5 years, 11 months ago by raptureforums.

@matthisamoto @raptureforums Can both of you try out the following patched version?

https://www.dropbox.com/s/5ykj0jw9dgsn507/constant-contact-forms-1.5.1-beta.zip?dl=0

It’ll still list its version as “1.5.0” in the WP admin at the exact moment, despite the zip filename. That’ll get taken care of after the fact once confirmed that this version fixes the reported issues.