Tribulant Software

Your signup form looks great! We encourage our clients to customize it the way they’d like and you can use CSS for that. Themes can affect the way our forms look and that’s normal.

About the features. We added new features actually in the Settings of a Subscribe Form. Both free and paid versions. We fixed a few issues too. Have a look at the changelog and see if one of those may have caused a change in your form. Perhaps one of the issues we fixed is now showing something you had there that wasn’t showing before, for example.

In case anyone else needs the solution here, add this code to your custom template:

<meta http-equiv="Content-Type" content="text/html; charset=utf-8">

I apologise for what you’re experiencing and we would like to attempt to resolve it. You can reach out to us on our support site over at https://tribulant.com/support/ by creating a ticket.

We are unable to replicate this issue after trying for a few more hours. We tried everything we could.

Either a configuration that is forcing the encodings to change, or your SMTP server preprocesses the texts somehow. This is only an assumption.

If the issue continues, could you try our plugin on a new staging website without anything else installed; just a fresh WordPress installation? Use default templates and send the same newsletter with the default templates and see if it helps.

Have you tried sending that same email to other email systems like Gmail, Outlook, etc.? We would like to confirm if this is happening in all email programs.

utf8mb4_unicode_ci is also fine. Would be great if you can confirm all of the tables, starting with “{WP_PREFIX}_wpml*” that are also using the same collation.

Thanks for your message!

What could be wrong is the encoding of the tables in the database (DB). We recommend taking a full backup of the DB, and then try to change the encoding of the database tables to utf8_general_ci and try again by sending the emails. If that didn’t help, we’ll need you to submit a ticket on our website for further investigation, because we copied a Portuguese text, made sure it contains those latin characters, and then sent it both as a post newsletter and creating a new newsletter and both worked fine. We could see the characters fine in our inbox. However, our inbox is web based, and there is a possibility that you need to configure the encoding of your mail client in case it renders characters based on any other encoding rather than UTF8.

That is correct. It should be working like that. In our tests, it works with both required and not required states. About your second question, if you use the manage subscription shortcode, by default, in the profile tab, it shows the consent field and that works well. And, it would not matter if the consent field is a required field or not, as when users have consented, it will be checked by default.

You could also open a ticket on our website if you’d like to provide more details: https://tribulant.com/support/

Sorry for the delay! Sorry about the theme editing also. We hope to improve that in the future.

The consent field, regardless of what type it is (checkbox, radio, dropdown) should be selected by default when the user checks his manage subscription page. We tested both our lite and paid version and it worked on our end. We even tested with a custom field and it worked as well. Something may be affecting this functionality on your website specifically, unfortunately. We are not sure what is causing this. Could you send us a screenshot of the WordPress admin page of that custom field?

If you haven’t been using our plugin for a while and don’t have much data, perhaps you could deactivate it, delete it, then remove all database tables manually and reinstall our plugin. Deleting our plugin from the Plugins page doesn’t remove all data, as of now.

I would say that in case a subscriber wants to amend his consent to no longer consent. It can happen and it’s important to have it there. It also proves to them that they consented.

We recommend that Consent be set to the Field Type: Checkboxes. That way, there’s only a checkbox to tick or untick.

Set the Field Options to something like: “I give Company-Name-Here permission to collect and use my data submitted in this form.”

Validation: Not Empty.

Let me know if the above helps.

Thanks for your message!

To begin, our demo is using quite an old version of our plugin that doesn’t have the latest features. It also uses a customised version so we’re looking at the best way to update this to keep it up to date from now on.

About the issue you’re experiencing, since we’re unable to replicate it, and it is working fine on our end, it looks to be theme related. Since there are thousands of themes out there, it’s not possible to support them all out of the box, especially since many have their own styling and variations.

Could you navigate to Newsletters > Configuration and scroll down to Theme, Scripts & Custom CSS. Change the “default” to “default2”.

If that doesn’t work, revert back to default, and let us know. We’ll see what we can do, though most likely it will require optimisation for your theme.

• This reply was modified 7 months ago by Tribulant Software.

That’s great to hear!

We have resolved the issues. We’re launching v1.6 now after testing it. Please make sure to read the changelog if you’re unable to update to it automatically from WordPress.

Once more, thank you so much for reporting this and so sorry for the issues caused!

We’re very sorry for the trouble and we thank you for your report. We’re currently verifying the update and will launch the next version hopefully today when the issues are found. We did experience the same long error when updating a plugin. We’re starting with that one.

Thank you for your positive review :)!