Last test failed with error “Use of undefined constant ‘do_shortcode’ “

Hi, are you using the plugin latest version?

Stefano.

Yes, 6.4.2. Everything except for the Mailing (test) item on the System Status page is green. WordPress 5.3.2 PHP 7.3.2

I’ve tried sending a newsletter, doing the test from the status page and creating a new newsletter and using the test button on that. All are generating this error. I have the plugin in debug mode to see if it would tell me anything else.

• This reply was modified 5 years, 2 months ago by gb.wp.
• This reply was modified 5 years, 2 months ago by gb.wp.

In debug mode, you can find a php-xxxxxx.txt file in the logs listed on status page, maybe they can help.

The weird thing is the “‘do_shortcode’” as singlular since there is no reference apparently of that word in our code while we use do_shortcodes.

But maybe a version merge created the conflict I need to check it.

if you set the blog in debug mode with the wp_debug constant, the line number generating the error is not reported?

Stefano.

The do_shortcode was being called in a theme. I’ve now switched to the default Twenty Twenty theme.

The test is still not sending, but the error is now:

FAILED (No error message reported)

With wp_debug on there aren’t any further errors being shown. Only the “main” files are being down on the System Status page, no phpxxxxx files.

To have the phpxxxx file you need to set the plugin in debug mode (not only the log level) on Newsletter main setting. But if the wp_mail() is returning simply “false” it’s hard to find out the real problem.

Can you ask the provider if there are mailing problem in your hosting?

Stefano.

Hi, another question: are you using PHP 7.4?

Working with the host, but still haven’t found anything. I’m using PHP 7.3.2

Hi, contact me at stefano [] thenewsletterplugin.com so we can setup a debug session with you to try to find out the problem.

Stefano.

Problem solved. The site is apparently on an older server and WP’s mail isn’t compatible with PHP 7.3. I rolled it back to 7.2 and it’s working again.

Thank you for your help in trying to track this down. I really appreciate it.