Problem using force_run

I understand that you are using my demo and basic template unchanged as they came during the install. That is strange because they are both tested. STC sends notifications via wp_mail(). In does not know anything of plugins hooking on to wp_mail().

So if STC works with the one template and not with the other it should not be related to MailGUN.

Not sure what MailGun does because WP mail SMTP sends mail on its own.

Maybe MailGUN has variable names that interact with STC but again if the one template works?

I do not think you should have WP mail SMTP working together with the MailGun it look to me they are both doing the same hooking into WP_mail()

Hi,

So if STC works with the one template and not with the other it should not be related to MailGUN.

I’m investigating this but apparently the problem occurs only with the STC Demo E-mail Template. The Demo templates are working correctly. So, I can continue working on the mail templates (by the way, is there any repository where STC users are sharing templates ?).

I do not think you should have WP mail SMTP working together with the MailGun

I’m not using the MailGun plugin for now. Only WP Mail SMTP. I’m currently evaluating MailGun but it’s not a definitive choice and WP Mail SMTP is very practical when switching between various services.

Thanks for the quick reply.

Patrick

Please explain your issue with the force_run problem

> Please explain your issue with the force_run problem

I explained it above. I published a test post and I didn’t want to wait for the scheduler to send the notification message. So, I clicked on the “Click here to send immediately” button (approximate translation since I’m using the french version). Then I immediately got a popup error message containing the text mentioned above :

Problem calling: force_run
Code: undefined
Exception: undefined

and the queued notification was not sent.

I switched to another template and this time I didn’t get the error message and things went smoothly.

Patrick

If you try again the template of which you had the problem with does it then happen again?

If you try again the template of which you had the problem with does it then happen again?

Yes. See attached screen capture. Template used is STC Demo E-mail Template .

Oooooops ! No image attached, see here : https://www.dropbox.com/s/djhazg7l3k12gd0/error.jpg?dl=0

• This reply was modified 4 years ago by samoreen.

Please give me admin access and a link to the login page.

Sorry, I can’t. The site is under construction, not protected and contains a lot of sensitive information. I’m not allowed to do this. I can give you all the information you need and I can do any test you could ask me to do (although I’m not a WordPress specialist, I’m a former software and system engineer).

Patrick

The placeholder list issue is more important to me than the problem with the above mentioned template since all other templates don’t show the same problem.

What version is the demo template?

As mentioned above, the version causing the error is STC Demo E-mail Template without any version number. No problem with the others

STC Basic E-Mail Template V2.0
STC Demo E-mail Template V2.0
STC Demo E-mail Template V1.3
STC Demo E-mail Template V1.1

Or with the one I just created.

Only versions V2.0 will work all other older versions you can delete. My guess is that the one without the version number is the oldest and shuld also be removed

OK. I’ll delete the old ones.

Thanks.

Patrick

Older versions of the templates where not deleted. They are not backwards compatible and one should always use the latest version.

• This reply was modified 4 years ago by vandestouwe.