mbeckerle

Hi,

sorry, did not see the question. In such cases easiest is to just drop us an email to [email protected].

I guess your usecase is something like an optional “I want to receive the newsletter” checkbox. In this case I would probably place it around the request. In the example I placed a check for the form name:

if ($record->get_form_settings( ‘form_name’ ) == “Maileon Form”)

However, you can also just query the value of a form field, here:

if ($form_data[‘register_for_newsletter’] == “yourValue”)

If the field “register_for_newsletter” yould pass value “yourValue”, the contact will be sent to Maileon, if not, nothing further will happen.

Hope this helps,
Marcus

Hi,

thank you, I am looking forward to the release containing this feature ??

Kind regards,
Marcus

I will close the issue now.

…

• This reply was modified 4 years, 6 months ago by mbeckerle. Reason: Wrong setting

For your information: with version 2.9.0 we added a new configuration page, which also names the absolute folders for templates and lists all available found templates.

It has been updated also online, now.

Kind regards,
Marcus

Hi,

placing templates inside the plugins own directory is not recommended as wordpress deletes the whole folder, when updating.

I looked into the issue and placed a template in wp-content/uploads/xqueue-maileon/views. I tested it under WordPress 5.3.3 and 5.4.1 but was not able to reproduce the problem.

Are you using a multipage setup and can you maybe tell me what version of WordPress you are using?

What was the displayed error message (there should be the expected path)?

Kind regards,
Marcus

Hi,

thank you for reporting this mistake, I fixed it.
It should be updated in some minutes.

Kind regards,
Marcus

No, your Plugin is fine ??

It just ececuted the shortcode of the other plugin twice, which should not be an issue but as the other plugin had side effects, they also were “executed” twice.

Thank you for the hint!

I meant as a shortcode (tag) should not have side effects, the other plugin has a “bug by design”. It needs some restructuring.

BTW: I ended up using “ez_content_exclude_by_selector”. Nice plugin ??

Hi Pascal,

thank’s for the hint.
I just included it in the new version and validated the functionality against the upcoming 4.8.

It is included in the 2.2.4

Kind regards,
Marcus