Campaign Monitor

At this time, the current version of the plugin triggers deprecated warning messages in PHP 8.x. However, these are warnings rather than errors, and the plugin’s functionality should not be affected. We currently don’t have a specific timeline for an update to address these warnings, but we are monitoring the situation and will review potential updates based on future PHP releases. Since the warnings relate to potential future changes, there should not be a need to disable the plugin at this stage.

The vulnerability reported by Wordfence applies to an earlier version that has since been patched, so new users installing the latest version will not be affected.

If you already have the plugin installed, please make sure you update to the latest version.

Hi chazmcgaz, sorry to hear you had some trouble using our plugin. We’re happy to further investigate, but we’ll need some more details from you. Can you please reach out to our Support team by logging into your account, clicking on the question mark found in the bottom right-hand corner, then choosing “Get support” so we can work with you further? Thank you.

Hi lamichi, you cannot make the default Name field required but you can set a custom field to required, if you were to consider using a custom field for the name field instead??

On the Customize Your Form page you can choose an existing custom field—or create a new one—to add to your form. When doing so, you have the option to make it required.

Hi ngoclx, this has now been fixed.

Hi @treasureseason ,

The issue you’re encountering is likely separate from the one brought up in this thread. I’ve gone ahead and replied to your thread here so we can troubleshoot this further with you.

Thanks!

Hi @treasureseason ,

Thanks for getting in touch. It is possible that WP Bakery or another plugin you have installed is conflicting with our plugin here.

• Would you be able to share a link to the page where you’re seeing this issue?
• Can you confirm that the issue is only occurring in Firefox and not in other browsers?
• Do you see the same issue on pages that aren’t built in WP Bakery?
• Have you tried disabling any other plugins to see if this resolves the issue?

Thanks so much — We’ll keep an eye out for your reply!

Hi @leecollings ,

Thanks for following up! In this situation, output buffering within our plugin would not help you. If we did output buffering, we would close it as the function exits. This is essentially the same with the current implementation.

We believe the issue is due to the way you echo the shortcode. As your article suggested, have you tried to do output buffering for the code that calls the shortcode?

Also, if you have access to the development environment within WordPress, then you should be able to access our plugin code (it’s in the plugin folder within WordPress). You could try modifying the plugin code if you believe that ob_start within the plugin would resolve your issue. Feel free to give that a try and let us know how that goes.

Hi @leecollings ,

Thank you for your patience with this. We do not use ob_start, however, looking at https://codex.www.ads-software.com/Shortcode_API in the Output section:

The return value of a shortcode handler function is inserted into the post content output in place of the shortcode macro. Remember to use return and not echo – anything that is echoed will be output to the browser, but it won’t appear in the correct place on the page.

We have followed this process, in which our shortcode uses “return” rather than “echo.” ob_start is another option and is not mandatory.

We are unable to look at how you used our code, but a few things come to mind:
1. Are you using our shortcode nested within a different shortcode by any chance?
2. Given the rendering of the shortcode below the Instagram feed, can that Instagram code be removed temporarily to verify that it wasn’t the one that caused the issue?

The 108 error you’re seeing when the form isn’t rendering properly may be a side effect of the main issue (i.e., some scripts may not load properly due to interference from another plugin, impacting both rendering and functionality).

Hi again @leecollings,

In the case of the other user, they found that a CloudFlare plugin was the cause.

Could we ask if you might have a similar plugin or any other plugins that you could temporarily disable and let us know if you still experience the issues?

Can you please share which form you have used and on which page? Does the issue also occur when in incognito mode?

Thanks and hear from you soon!

Hi @gvnet,

Appreciate the reply and details – Thanks again!

Hi @leecollings,

Thanks for taking the time to reach out.

We’ve reached out to the other user to see if they have any further details to share, which might help in your case as well.

We shall wait to hear back and pending on the information, will treat this as a separate case if need be.

Appreciate the patience and we’ll be in touch again soon!

Hi again @gvnet,

Could we ask if there was another plugin which might have been the cause, in your case?

If you have any further details to share that would be much appreciated!

Hi @gvnet,

We’re glad you were able to find the cause and sort that out.

Thanks for taking the time to reach out and follow up to let us know.

Have a great rest of the day!

Hi @erodalex ,

Thank you so much for following up! Really glad to hear that you were able to resolve the issue.

Thanks also for these suggestions regarding translating the email field and displaying the shortcode on the form’s list page. I’ve added your feedback and votes for these features to our feature request list.

If you run into any other questions about the plugin, please feel free to create a new thread and we’ll be happy to help. Hope you have a great day!