Forum Replies Created
-
Posts
-
Hi Adam, I setup a fresh installation with Newsletter and Translatepress and the redirects are ok, so I don’t think it’s a problem of our integration, it could be a specific configuration OR other plugins in your site.
Please contact me at stefano@thenewsletterplugin.com so we can setup a way to debug that specific problem.S.
Hi, there is still a possible problem, since the plugin always set the charset to utf8. If you receive the message with another encoding, another plugin or the mail service is reencoding it. That’s not a problem IF the message is actually re-encoded correctly. About the subject, the encoding of the subject is not connected to the encoding of the content, it is specified in the subscjet itself.
Hi, all our messages can be so on Subscription/Settings, but that one seems a WP message. Could it be you have the antispam active and the error comes from the antispam system? Check Subscription/Antispam/Logs.
Hi, that is not an error by the Newsletter plugin, probably the full error details have been mailed to the admin address (set on WordPress Settings).
It is usually a fatal error (it could have been triggered by the Newsletter, btw).
Or you can try to set the plugin in debug mode (see Newsletter/Settings/Advanced – one of the latest options), generate the error and check for a php-nnnn.txt file on Newsletter/Help/Logs.If possible send a test email to test@thenewsletterplugin.com so I can check the source to see if something can be identified.
Hi, if the emails generated by Newsletter are not sent by wp mail smtp, you probably have one of our delivery addon, please check for it. Anyway, the charset is set by some external code since we set the charset to utf8.
Hi, thank you for reporting. We changed the post loop to be more compatible with plugins that change the author/date. I’ll check what could be and revert.
Hi, the form is a pretty standard form without special elements, I don’t know why that ad blocked should hide it. Coulf you contact the ad blocker author and report that issue?
Hi, if you need to add a new subscriber you should use the /subscribers endpoint, it seems you’re using the /subscriptions endpoint which is used to start a subscription flow.
https://www.thenewsletterplugin.com/documentation/api-reference/
If you need to send the welcome email it’s ok to use the /subscription and in that case, you can specify the option mode to ask form confirmation or not.
Hi, about the error when trying to send an email, see this post:
https://www.thenewsletterplugin.com/documentation/error-could-not-instantiate-mail-function/
your provider disabled the mailing for your hosting space.
(Uhm, could be a bug, can you reset the second color? When the color picker is open on the top right you can “empty” the selected color.
Hi, the link addresses the subscriber to the public page of the newsletter, where only the [newsletter] shortcode should be present.
Or on that page the [newsletter_form] is used, or there is something removing the URL parameters blocking the plugin from recognizing the subscriber.
In the first case you should have a notice on the admin panels of the plugin.Hi, probably they’re mail scanners. On Subscribers/Unsubscription, revert the text to the default one so the unsubscription must be confirmed pressing a button instead of following a link. That should block the bots.
Here are some details: https://www.thenewsletterplugin.com/documentation/subscribers-and-management/cancellation/#unwanted-unsubscribe
Hi, it’s very easy: on Newsletter/Settings, you can disable the tracking, so every new newsletter starts without the tracking active. The tracking on/off can be set per newsletter as well.
If you still want the tracking but with a different link format, you can change to the standard one on Newsletter/Settings/Advanced.Hi, not all delivery addons have been updated to use those methods. They’ve been recently introduced.
If you ask the provider to disable the mod_security, possibly selectively for the admin side of the blog, the problem will be resolved definitively, otherwise you need to empty or change the text part of the newsletter every time.
Hi, it seems the Automated addon is not active (and this is not connected to an expired license). Go to your plugins page and seek for Newsletter – Automated and activate it.
Usually this is due to a security module of apache (mod_security). Try to empty the text part of the newsletter when you’re in the page where you select the lists and other targeting filters. If it saves, definitively is a security filter.
Hi, the expired license does not block the Automated addon. What do you mean by “not working”? What’s the problem?
Hi, it would be more easy to set the speed on the Newsletter/Settings configuration to 50 emails per hour.
Hi, probably you have a multilanguage plugin installed, just switch the admin side to “all languages” and you’ll see the full set of options.
Here more about multilangiage sites: https://www.thenewsletterplugin.com/documentation/installation/multilanguage/
Possibly, having a license, please open a ticket from your account page to get support so the right person can help.
Thanks.
Probably creating an integration is complex, so why not invert the offer? make the wheel an option of the subscription.
Subscribe our newsletter(*) and try to win…
(*) here you explain what you’re offering with your newsletter
Hi, if you can expose just the “home” of the site managing the newsletter and set the action links on Newsletter/Settings to the standard format, the tracking link reach the newsletter manageing site and then will be redirected.
You can possibly write a rule to accept a link only if it contains the na=aaa parameter.The shortcode works only when used on the content set on Unsubscription or Profile Edit panel and when a subscriber reach that page from a newsletter (so the link has the codes to identify the subscriber).
Maybe that is the problem you’re facing.
Let me know!
Hi, about the refund, it should be asked to us via ticket so we can process the request. I see you have a license purchased today (so from now on you should be able to open a ticket, the previous licenses has been expired one month ago).
Since you have old licenses, you don’t need to change the license in your blog, just check if you used the UNNN-NNNNN license format (with a starting U) on your Newsletter/Settings.
Hi, if you’re running a multilanguage blog (Polylang, WPML, Translatepress) it could be the Newsletter/Settings page is not showing all the options, you need to switch to all languages on the WP admin black bar.
But on the options panels, you should see a notice about that.Do you have an already-opened ticket about this issue? If you have a license you can open a ticket from your account page on this site.
Hi, sorry, just checked, it could be a bug, but the message is shown only to administrators, don’t worry no one is seeing it.
It will be fixed on next version.Hi, you’re probably using the [newsletter_field name="lists"]. To have the list checkboxes shown, you need to set on Subscription/Form which list you want to show. Otherwise you can alternatively use one or more single list field [newsletter_field name="list" number="X"]
Hi, it seems you have an option, probably set on Yoast SEO, to remove the URL parameters. That causes in your blog the redirection to the /newsletter page without parameters hence the message for the new subscriber cannot be shown.
Just tested the standard form on the links you shared with two email addresses (you can delete them from your database now) and the redirect is correct.
For your tests, are you using the widget on the bottom of the page? Since that’s not a form generated by Newsletter and there the language hidden field is wrong (it is set with the WP_LANG).
Hi, just tested and it works for me. Registered address test @ thenewsletterplugin.com. Could be you’re using an already registered email and that subscriber has the language set to FR?
Ok, that is correct. Could you share the page where the subscription form is published? If could be a problem of the language in the subscription form (we see that problem with some themes and the widget cached by the theme and not generated correctly for each language).
Another thing to check: is the Newsletter plugin updated to the latest version? We change something about the multilanguage management (specifically for WPML) but it could positively affect even Polylang.
Anyway I test is even with polylang to see if a similar change is needed even for that plugin.Ok, so the public pages should be set correctly. You can check it by going to the blog pages list, set “all languages” and see if there are pages with the note from our plugin “used by newsletter…”.
Hi do you have a notice on the admin side about the missing public page setting for one or more of your languages?
Hi, in your CSV the first line needs to be the column description, from the second line only data. Probably you have more header lines.
Hi, but the registration of users (not subscribers) is managed using the WP registration standard functions? If so, using our wp users addon (or the wp user’s pro version since you have the autoresponder hence I imagine you have a valid license), the subscriber can be created during the registration.
Hi, the events block does not know about members and non-members, you should have specific list of subscribers for members and non-members and two channels and, for example, categories to filter out the members’ only events.
In your situation probably a custom block would be the best solution.Hi, that happens when there is a connection problem between the blog and our server, please, get the zip from your account page on this site an upload it manually from the plugins/add new page.
The addon (which is a regular WP plugin) will be updated.Hi, if you’re using a blog in the German language, is a problem of that transition provided by the community.
Go to Subscriber/Profile page, customize the page content option and be sure in the content you have only the [ newsletter_profile ] shortcode (without spaces).
If on that page you already have the “customize” flag unselecting it and using the default value for the page content option could solve the problem.Hi, later I checked it, but I assume it is Azure. I say that because 90% of the times the unsubscription started from azure.
Could be the provider uses an antispam service on Azure or the whole email service is there.Hi, to check that specific case, enter the details of your test subscriber and you have a “log” panel.
You should see the unsubscription event with an IP address. Can you send it to me? We can check where this IP address is used and maybe we can find more info!Hi, you’re not alone, this is something that started to be a problem (not only for our plugin but generally for all email platforms) at the beginning of 2024.
We analyzed many of those situations and almost always, the unsubscription was started by a system on a data center, “masking” the request as if it had been started from a real browser.We think they are Mail Scanners trying to grab info from the links in newsletters. Even our antibot was not effective (we use the same techniques that are widely implemented even by big brands).
What to do: since you have an old installation, probably you have the old default settings and they’re less protective against this problem.
Go to the unsubscription configuration page of our plugin, and revert the “confirm” message you should see as customized) to the default one. You’ll see on the default message the link to confirm the unsubscription is no longer present and there is instead a shortcode like “newsletter_unsubscribe_button”. That generates a button that is much harder for mail scanners to follow.
Hope this helps, you may consider setting as confirmed the email addresses that have been unsubscribed.
Hi, for the Automated addon, please, open a ticket so the right person can take care of it. At first sight, you probably just need to enter the config of the automated addon (on the bottom of the page where the channels are listed) and set to “run” as an administrator.
When the newsletter is generated, Automated is in the “cron” context of WP, as an anonymous user, so the PMP filters are 99% removing the events from the query.
I have a note on my desk to change the “test” of an automated channel to execute on that context so it will be easier to detect those situations.
On your page, the language on the main form is “el” (correct) but the language on the footer form (which is probably the only one used) is “en”.
I don’t know how that form is generated. I saw a problem recently with a page builder that caches the footer block keeping only one copy with a specific language.
Or it could be that form has been added as HTML code manually.What site builder are you using?
Note: your main form on the https://educraft.tech/el/newsletter-2/ is unusable to me, the button is not visible (using Chrome).
Hi, the image is a placeholder, of course when you select a real image from your gallery the placeholder is removed.
About the content URL, that value is ok – it is a full URL, you should not have the “MAYBE” flag on our System page, it should be OK.
So, if the emails are sent with a relative URL, that is a plugin.
Check if you have a root relative plugin, make paths relative plugin or like.WP has a main configuration file, wp-config.php, that is in the root folder of the blog installation where that constant could be present. Note: this is not a WP standard, someone explicitly set it.
If you go to Newsletter/Help/System (I wrote status before, sorry) and search on that page for wp_content_url, you should find it with its value.
Let me know how it is set, if so.
Your site uses relatove paths for images, but this is not working with emails. Check on Newsletter/Help/Status, probably the constant WP_CONTENT_URL is set on your wp-config.php file to get a relative path for images.
That configuration should be removed.
Hi, be sure to run the newsletter plugin version 8.5.4, change a global setting of your newsletter and press “apply” the problem should disappear.
Hi, on Newsletter/Settings, where you can change the public page you should change the current admin language.
Do you have the translatepress addon for the Newsletter plugin installed? Maybe it’s missing.Hi, when you have the public pages created for every language, the {profile_url} tag should redirect to the page with the language of the subscriber.
Be sure on the Settings to have those page selected for each language.Hi, the link redirects to an “action point” the should then redirect to the correct page. You should have a page for each language and on the Newsletter/Settings, changing the adin language on the topbar (WPML, PolyLang), you can set the correct page for each language.
Of course, the per-language pages can be the translation of the main public page.
This complication is because, with the multilanguage plugins, there are some time issues to get the correct link to the translated page.
Hi, the page the subscriber is redirected to, is determined by its language. You should check if the subscriber has the language of the page shown.
If not, you should check on the Newsletter/Settings if a public page has been set for each language.
Anyway, you should have a notice on the plugin admin pages if the pages are not setup correctly.Hi, thank you for reporting, it means the update is wrongly setting that format… I’ll check suddenly!
Hi, on Newsletters/Templates, you should see the list of the templates, the name should be the subject. Editing them you can change the template and the name as well.
If you want the link to be untracked, you can disable the tracking on Newsletter/Settings/Tracking, which applies to the newly created newsletters OR you can disbale it separately on each newsletter.
Then the tracking is off, no stats are collected but the links are not changed.Hi, on Newsletter/Settings/General Advanced tab, set the action links to the standard format. That format can be blocked by caches, CDN, and so on. I suggest unlocking the wp-admin/admin-ajax.php file because it is designed even for anonymous calls.
Why not use the welcome email as first welcome and to send some content? Or you can evaluate to use an email series.
Hi, you can give a try to our latest addon which which integrated even EventPrime. It’s a beta since we coded it but we’re waiting for the author support to know exactly how to extract the events in the correct way. But the integration seems to work :-).
Stefano.
Hi, the import feature has ben added. Check out the updated documentation to see if it suits your needs.
https://www.thenewsletterplugin.com/documentation/addons/integrations/pmpro-extension/
Thank you!
Sorry, I missed it. No, there is no import button, but let me have a word with developers about whether it can be added.
Hi, thank you for asking, I’ve just corrected the description: lists are assigned based on the member’s level even during the first registration, not only when the level is changed.
Hi, check on the Newsletter Main Settings if the “Public Page” is correctly set to a WP page (it is usually generated on first installation). That page must contains only the [newsletter] shortcode.
Let me know.
Stefano.
Hi, you’re probably logged in with the wrong account, please contact me at stefano @ thenewsletterplugin.com with your license so we can find out the right account and fix the ticket problem.
About the import, are you importing customers from woocommerce? Or WP users as subscribers?
Hi,
on each user details page there are the logs of the status changes: of course is it useful if you know the email address marked as bounced.
if you need detailed logs of the bounce addon, you need to enable the logging at debug level on the Newsletter’s general settings.Hi, if you look at the user logs the bounce time should be registered. The spam detection is an attempt to interpret the bounce reason to detect if it’s a spam report.
PS: the old search method is integrated with the new search: results should be displayed after the first inline answer.
That message is by Amazon and it’s a fatal error so the plugin stopped the newsletter (but you can restart it). About the error, you should contact Amazon reporting the error identifier.
Hi, the “check and restart” should be a link to the delivery panel where the newsletter with errors should be listed. You can “edit” each one, restarting them or pausing/aborting them.
That should remove the message.
Hi, thank you for sharing. Time ago I thought about invitations, but they require an attachment so I need to change several things in the plugin core (and in all delivery integrations).
It could be that autumn is the right time to rethink it! 🙂Hi, thank you for reporting it’s an error in the addons manager addon. Fixed on version 1.3.2.
To see the update notice, just save the Newsletter’s general options to reset the version cache.Stefano.
Hi, to help me debug, is the subscription collected with the standard form or another from (for example by CF7)?
Hi, that should not happen, can you share a screenshot of your configuration? Are you referring to the welcome email or the activation email (sent when the double opt-in is active).
Hi, it’s a bug, the patch will be published shortly. Thank you for reporting. The problem is when a custom field is “reset”: that information is not correctly propagated to the form configuration which keep in processing it (but only when the admin is looking at the form).
Hi, go to Subscription/Form where there are the settings of the default form and save them (possibly for each language): probably there is a stale configuration save on the database.
Godaddy email system is not reliable (but depends on the hosting plan). Sometimes emails are delivered sometimes not. Is not about the scheduler. Ask Godaddy support which SMTP you can use and install an SMTP plugin to connect the blog to that SMTP (if they give you one).
If they give sn SMTP, usually that solves the problem. Connecting the bog to an external SMTP typically does not work with Godaddy since the blocks that kind of connection.
A good alternative is to use a pro delivery service (SendGrid, mailjet, …) and connect to them with a plugin that uses their API, Godaddy cannot block those kinds fo connections. That is what we do with our delivery addon, for example, not coded for godaddy but to have better performance and bounce management.
Some free SMTP plugins have specific integration with delivery services using the API and they could be a solution when dealing with Godaddy.
Anyway start reporting the problem to Godaddy.
Hi, I see some reports about that error with the PHP XML library, I’ll try to add a check, but it seems to be something related to the PHP version or installation.
Anyway, a check on our code won’t hurt!You don’t need to enmter once again the email address, get the license from this site, go to the account page and set the license on the newsletter main options.
Hi, that message does not block the addition of an addon.
Download it from your downloads page in your account page (this site) and use the zip to upload the addon from your plugins page inside the blog.
If you go on the main settings of the newsletter plugin and save, you could have a more clear error message reported: could be your blog cannot connect to the validation service.
But you can anyway download the addons and install them.
Sorry, it’s not clear what is the issue. This site has no data about your subscribers, all data is stored in your blog’s database.
The import/export is a plugin you can add to the blog where the Newsletter plugin is installed to import/export the subscribers.Sorry for my ignorance but what do you mean with “I am a VA”?
Hi, since you’re logged in to post in the forum, go to the account page and you can have the free license to set on the plugin main settings and the download page if you want just get the addon to be installed (Plugins/Add new/Upload from the Plugins WP panel).
It’s recommended to install our addon manager (can be done only manually) to have then an easy way to update or install other addons.
If you need to change your profile try this link when you’re logged in: https://www.thenewsletterplugin.com/wp-admin/profile.php
Hi, it sounds like there is a problem with the addon. I see it on my test blog within the add-ons page.
Do you have some kind of noticed on the admin side? Maybe a Newsletter update requirement or like?
Hi, just released version 8.4.0 should address your issue (it’s a database configuration in your site different than the standard which raise an error – it’s not something you should change, we need to have compatible code, sorry for this problem).
You should see the update shortly, try the WP/Upcate panel a do a “check again”.
Let me know if the problem is solved with that version.
ok, that is what I need. it is an error in our code, now I’ll check the origin since it should not happen!
Hi, that means the Newsletter plugin is not probably loaded when the error happens. Since the error is intercepted by your WP, you have two options:
1. ask the hosting provider to check the error logs where the error details are reported
2. you can add to your wp-config.php the line of code below to disable the error handler and, if we’re lucky, the error is displayed:define( ‘WP_DISABLE_FATAL_ERROR_HANDLER’, true );
please, if you ass that line, retype the single quotes since the copy and paste usually breaks them.
Another option is to enable the WP debug mode. Always changing the wp-config.php you should add (or modify if already present):
define(‘WP_DEBUG’, true);
define(‘WP_DEBUG_LOG’, true);
define(‘WP_DEBUG_DISPLAY’, false);errors should be intercepted and logged to the file wp-content/debug.log.
NOTE: the wp debug mode does not capture only the errors, it capture even warning notices and many non-fatal conditions.
If even that file is not created, you probably have a specific PHP configuration, You can try to set:
define(‘WP_DEBUG_DISPLAY’, true);
and hope the error is displayed.
Hi, if you share the site address I can test myself. To have the full error details you should ask the provider for the “error log”.
You can even try that:
1. on the main newsletter’s plugin setting, advanced tab, activate the debug mode (it’s one of the last options)
2. reproduce the error
3. check on newsletter’s admin Help/Logs if there is a php-aaa.txt file: it could contain the error details
4. disable the debug mode at point 1
5. copy here the error if any has been recordedHi, if you have a critical error, and it’s a WP message, you should have received an email at the address set on WP main settings with the error details. But, if the error is related to the mailing system, you don’t have such an email.
In this case, from the admin side, go to the Newsletter/Help/Delivery and run a test: what’s reported? If everything is fine, please check on your WP main settings the email address and change it if it’s not a working mailbox.
If the error page is reporting more information about the error, please copy them here.
Hi, since I have not an env. where to test the proxy configuration, could you check if the changes I made to the code are ok?
Could be in your case one of the constants is not defined?if (defined(‘WP_PROXY_HOST’) && defined(‘WP_PROXY_PORT’)) {
curl_setopt($ch, CURLOPT_PROXY, WP_PROXY_HOST . ‘:’ . WP_PROXY_PORT);
}You only need to add the line
define(“NEWSLETTER_TRACKING_TYPE”, “ajax”);
in your wp-config.php.
Keep a copy of your wp-config.php before any modification AND be sure to retype the double quotes if you coppy the text above, since they’ll be copied in the wrong format.
Hi, that link is correct and it is a tracking link, but your blog is not “passing” it to the Newsletter plugin, maybe a security plugin or a server configuration is blocking it.
I can suggest to change the link format adding to you wp-config.php the linedefine(“NEWSLETTER_TRACKING_TYPE”, “ajax”);
just after the define about the database.
Keep a copy of your wp-config.php before any modification AND be sure to retype the double quotes if you coppy the text above, since they’ll be copied in the wrong format.Then, if you send a test newsletter you’ll se the new link format, something like
https://soylagunanoticias.com/wp-admin/admin-ajax.php?…
That kind of link should not be blocked.
Let me know!
Thank you very much, the addon has been updated. Save the Newsletter’s main setting to see the update notice (version 1.2.2).
Let me know if it works on your env.Stefano.
Hi, try to upgrade to the latest version, where the subscription has been refactored. Probably the recent review to address an XSS problem introduced that warning.
Hi the initial 9 email are just a sample of the data, useful to see if the parsed parameters are correct.
Hi, while the email is registered as unique, if someone uses a second form, the data is “merged” with the existing one—the multiple subscription settings on the Subscription Configuration Panel control that.
For example, a second subscription could require confirmation before having it merged (otherwise anyone could use other’s emails and update their data!). So the new collected data is “parked” and then merged once confirmed with the activation email.
Yes, it happens if you add more subscribers while it is sending (or they subscribed or they changed the profile and match the targeting filters). BTW we’re thinking of changing that behavior: it’s sometimes useful, sometimes confiusing.
And the email field has been mapped? The parse list of email is only a sample of the whole set you pasted.
Hi, what you see is a preview of the parsing of you data. You should check if that parsing is working correctly or changing the field separator, for example. And in that page you should map the fields from your data to the subscriber’s fields.
You data has a first line with the field names?Hi, you have an SMTP plugin installed, you should run the tests from that plugin since even the emails sent by Newsletter are delivered by that plugin.
Meanwhile if you can edit the file, where you find the line
$news = json_decode(wp_remote_retrieve_body($response), true);
change it to
$news = [];
and the problem should disappear.
Ho, thank you for reporting. Probably the site cannot connect to our server, we need to intercept that condition. Wuill be fixed on next release (on monday).
Hi, I was able to replicate the problem it happens with the “activation required” message, we’re already working to fix it.
Your configuration is ok!Uhm, it seems ok on my blog, but we could have different configuration. Could you check on Newsletter’s main setting the public page set for the EN language? Enter the settings panel, change the top bar language to English and check the public page setting.
Probably it’s ok, I would use a similar configuration.Another simple check: on your “pages” panel, set the top bar language to all, and you should have two pages with a “warning” similar “Newsletter public page”.
Hi, probably this happens if you subscribe with an already registered address that is associated to that language. Could you check for that?
Hi, of course, that should not happen and that version has nothing changed in the “version change” code. Which settings have been lost or reset?
Hi, the forms are ok, both have the language (it’s an hidden form field).
I subscribed with test@ and stefano@, could you check the language of those two subscribers?
The first should be DE the second EN.Hi, the error could be connected to the mailing problem. Can you go to the Help/Delivery panel and run a test?
In this moment there is a bug on the plugin dashboard that can lead to an error, just start from another side menu entry, like “subscribers”.Uhm, that means the form is not transmitting the language. Could you kindly share the link of the subscription page so I can check it? Could be a bug of something related to the form or the multilanguage plugin. Which plugin are you using?
Hi, it could be a public page configuration issue. You should have 2 pages to be used by the newsletter plugin (one for the EN and one for the DE languages). Both the pages should contain only the [newsletter] shortcode.
The plugin should detect if there is a problem with that configuration and show a warning on the admin side.
Please, check on the Newsletter’s main settings if those pages are correctly set as “public page”. You should set this option for both your languages, switching the admin side language using the black top bar.
Let us know, if all that is setup correctly we should look somewhere else.
Hi, the save button is working now. It was blocked by the browser since the custom URL for both the activation page and the welcome page was set with a wrong value (an URL starting with // and not with https://). Since the welcome page select was not selected to the “custom URL” option, those fields were not visible and (that is a bug of the browsers) nothing was shown. Yhe only way to see the “error” is to use the browser debug console.
We’re changing the plugin to avoid that kind of browser oddity in the next release.
Stefano.
Hi, to just send with that service, you can install the SMTP addon (o generally an SMTP plugin). They provide API as well, but there is no much benefit to implement the integration since an SMTP plugin will do as well as a direct integration.
They do not provide a webhook to be notified on bounced addresses, which is now of the key feature of a delivery service. Maybe in the future they’ll be able to add that feature and then it’s worth to code a whole integration.
Thanks!
Hi, our plugin is not related to pages and articles, you probably are inside the admin panels and on top bar it’s selected a language without article translated in that language.
You should ask for support to the polylang plugin authors.Hi, I’ve tried just now but I’m unable to reproduce the error. Could you kindly reported the error details?
If the error has been intercepted by WP, it should have been sent to the administration email (the one set on the main WP settings).
If there is no email, the server error logs should contain the details.
Another way is to set the Newsletter plugin in debug mode, there is an option on Newsletter’s main settings (note: it’s not the logging level, it’s a setting specific for the debug mode).
Once active a notice is shown on top of our administration pages.
Them if you reproduce the error, a log file should be available under Help/Logs with name php-xxx.log.Hi, yes, that is a recent change, we sent a newsletter about that :-). On the admin side, there should have been a couple of warnings about that required change.
That is a step we took to reduce the multilanguage management problems (as you see it is not so easy to manage it…).Thank you for your collaboration!
Hi Julie, the page shown should be connected to the subscriber language, so the redirect should redirects to the public page for german if the subscriber language is german.
It it’s not working there something we need to check (I’ve make some tests with success, I need to try other combinations).
Have you make the test with a not registered email address?Hi, it is a general problem with multilanguage, double opt-in, and custom welcome emails. It will be fixed with today’s release.
Just a note: while testing, if an already registered email address is used to try a second signup, the signup language and the language of the existing subscriber could create some glitches: we’re looking at them as well.
For tests, we recommend using a email address not already registered.
Hi, it seems a bug for multilanguage installation, we’re checking. And specifically for the welcome email designed with the composer.
I’ll get back tomorrow when I can complete some tests (and probably a fix release will be published).When you send a newsletter with links (with tracking active) and the subscriber follows a link a cookie is set. That grants the access.
Newsletter has not a login system, of course, but with that cookie the subscriber is recognized: it’s like the magic login link some services send by email.Hi, thank you, I’m going to add a check right now. It happens when no custom fields is set to be displayed on the profile form (or when custom fields are not used).
Arghhh! That version shouldn’t have been distributed, it was an error on the 8.2.2 package suddenly replaced… but of course, it was not. See the 8.2.3, it’s just a republishing of the correct package with a new version number, to be sure the correct code is distributed.
Thank you very much for reporting!
Hi, you need to check WP Mail SMTP, probably it is sending using the standard mail() function of PHP and it is not configured to use an SMTP. WP Mail SMTP, if not configured, does nothing.
I suggest to copy the configuration you set on Newsletter – SMTP to setup WP Mail SMTP so it will use there SMTP.
Then no other problems of bad headers. 🙂
Hi, you don’t need the Newsletter SMTP addon, just keep wp mail smtp (or fluent smtp) and set it to use the SMTP service. Newsletter automatically uses that plugin.
WordFence could use a different method to send emails than the standard WP method (so the SMTP plugin would be activated), but is shouldn’t.Since you have come problems with the provider, I suggest to have a single plugin connected with the SMTP: this way all communication generated by the blog (notification, newsletters, ..) should be managed directly by the SMTP plugin.
There is even a maillogging plugin, if I remember well, so you can check what’s happening (there is no need to use the pro version of wp mail smtp).
Hi, the Newsletter plugin uses WP to send email IF no delivery addons are installed. Please check if you have the Newsletter – SMTP addon active, and remove it.
Hi, if the test is ok, the plugin can send emails from your site. When the confirmation email is not sent, probably it is dropped by your provider (spam filters). Try to change the subject and a bit the content of that email (see the Subscripton/Settings/Activation tab).
If you kindly share you site address, I can do a test subscription to see if I receive the email.
Have you checked the spam folder?
Since it could help others, with JSP we checked all the possibilities and the provider is changing the email headers when the site’s public side starts them and not when they’re sent (like tests) from the admin side.
This is done even by other providers, including the originating of PHP scripts and other information to identify if needed, hacked sites. That is a problem, anyway, because the antispam filter does not like too much that added information.
With email headers I mean some meta information that is not visible in the email client, you need to get the email source (for example with Gmail or Thunderbird).
Hi, the PHP mailer is actually used to encode the mail since amazon ses is faulty in managing utf-8 content, but it is not related to encryption.
Could be when you test from the admin some filters are/are not applied as when you send (subscribe) from the public side? Maybe your theme or a plugin is applying some filters!
Hi, the widget just collects a subscriber, it cannot affect the sending of an email, it’s a core process identical for newsletters and notifications.
Belive me, I wrote the code of the delivery part.
You can use our widget, a shortcode, a custom form and nothing will change. For example, open the newsletter public page, you’ll find the subscription form. If subscribing using that form you find the same problem, that’s a confirm it’s not the form influencing the delivery.So we need to check elsewhere.
1. goto the Newsletter’s main settings, there you have a sender and a return path: what’s in them?
2. share the page where I can test the subscription with my addresses so I can see the messages and I can look at the source of those messages
3. send me a test that does not shows up the to test@thenewsletterplugin.com: from where do you run the test? From our Help/Delivery panel or from WP Mail SMTP?Thank you!
Hi, I installed it on a couple of blog getting it from the documentation page or this link
https://www.thenewsletterplugin.com/get-addons-manager
and it works. Could be when you download the zip package it is unpacked and you’re trying to upload the folder and not the zip file?
Hi, the previous message was sent to the wrong request sorry. To be notified via email for each new subscriber, just enable the notification on Subscription/Settings. You can specify an email address where those notifications should be sent.
A similar notification option is presented on the Subscription/Unsubscription configuration panel, of course to get notified of cancellations.
That is an IP of the Microsoft Azure cloud, you can check it here.
https://www.maxmind.com/en/geoip-demo
So 100% is a mail scanner. The latest version of Newsletter has a better antibot to try to block them. You can even enable the double step unsubscription, it helps.
This is something we started to see since a couple of months, probably some more aggressive antispam/anti ransomware deployed usually by big companies.Hi, that input field is the one used by Newsletter is not created by Elementor. Could be you have some customization in your site made by a developer?
Could you share the URL where the form is visible so I can get a look?
Hi, that is something already seen. When you send an email with a client it is delivered, when send with a hoster mailing system it is not. Probably some providers do no accept emails from IP of specific hosters or not whitelisted.
That is not connected to the plugin, it just create an email, it’s the mailing system of the provider. I can suggest to try with a pro delivery service, like amazon, sendgrid, …, smtp2go, …, or ask the provider if you can use their smtp.Hi, plugin.php of newsletter-amazon plugin? we do not use the PHP mailer to set the headers? are you using our smtp addon?
Hi, that message is added by the email client, I’m pretty sure many other clients do not add it. That client recognizes the email as a newsletter because it contains the mandatory unsubscribe headers.
Hi, sendy is a SaaS service, they have much more power than the server where a site is hosted and they can work in parallel. You can enable the turbo mode on the Amazon SES addon, but the limitations of PHP are there. If you need performances like Sendy, you should use a VPS with Postfix configured as smart host and set Amazon SES as the SMTP service for Postfix. In that case all the resources of the server can be used to send emails.
BTW, most of the times, when a sending process is completed, what’s compete is actually the enqueuing of emails, the real delivery can take much more.Hi, the code you pasted probably has been filtered. You should use the [newsletter_form] in a “shortcode block” for your sidebar or use our widget.
Hi, could be. But is sounds more like to be a caching problem. Are you sure there is not a frontend cache (not installed in the blog), like Cloudfront, varnish or similar?
When you create a channel, you can select to create a channel using the obsolete theme system (on bottom of the automated channel list), or the standard theme, create with the composer. Probably you have an old installation where only the old theme system was available.
Hi, the captcha has not js… weird, is the problem still there? Debugging on a mobile browser is really complicated, but if you share a link we can try to test.
Hi, so you’re creating a form with Elementor? Elementor forms should have the placeholder setting for fields.
The error you have is not related to a timeout of PHP but a timeout on the Apache server. Tables you need to look at are wp_newsletter_*, in particular wp_newsletter contains the subscribers.
Hi, that is not from the newsletter plugin, we use the placeholder attribute. Where is the form placed? Is it a widget? Could you share a link?
Hi, actually not, the post are shown in the order returned by WP (which is of course the publishing date).
Hi, bad problem. When you save the url should be changed with the newsletter ID. It means something went wrong while saving the data to the database (ask the provider to run a table analysis for your DB).
I saw that problem after a site migration where the database has been reconstructed without all the correct definitions.
You should even check the System/Logs panel for errors. You can collect more information by enabling logging on Newsletter’s main setting and setting the login level to error (or more).That is the tracking image to know when the email is opened, if you disable the tracking is it not added anymore.
Probably or the email client or some other filter is showing that code.Hi, there was a bug recently solved, do you still see that problem?
Thank you for your collaboration!
Hi, automated, or better the “posts” block, uses the “featured” image of a post. If the image is not set on that post, nothing is shown.
You can try to install a plugin like “thumbnails” which has a feature to automatically set a featured image choosing the first one between the ones uploaded for that post.Hi, the pubic page should not contain the [newsletter_form] shortcode but the [newsletter] shortcode. When created automatically, that is the short code added, probably it was edited.
Using the correct shortcode all messages are shown on that page.Hi, no, it is actually not possible, you should write come custom code to do that (possibly even with javascript).
Hi, it sounds like an installation problem. Try to download the zip package from your account page on this site and install it from the plugins panel/add new.
Hi, the plugin (and addons) does not have a connection between lists and post categories. You can create automated channels that extract specific posts from specific categories and let users to choose between lists connected to those channels.
Usually, a blog has many categories and could be confusing for a subscriber to choose between all of them. It is easier to choose a topic that probably aggregates many categories. Of course, it depends on the blog organization!
Hi, the webhook and the API don’t have data formats compatible, sorry. They have been built to be integrated to servicers like Zapier where the data format can be defined on that platform.
Anyway, I toke note of your need since it could be useful for development, thank you.
Send it to me at stefano@ thenewsletterplugin.com.
BTW the latest version of the Newsletter has a new antibot protection that should help a lot in blocking unwanted traffic.
I always suggest using Wordfence as well, since they block many IP based on bad behavior or bad user agents.We have not specific unsubscription statistics, but with the Reports addon for each newsletter, you can see how many subscriber unsubscribed from that newsletter.
Hi, there was a bug in the welcome email management with Polylang, it should be solved. Could you check once again? Some other issues have been solved on latest version, always related to multilanguage configurations, for example, the welcome email was not picked up in the correct language.
Let me know if the problem persists, dealing with multilanguage plugin is not always easy.
If you use custom forms, you can add the language to those forms with an hidden field named “nlang”. That value is stored with the subscribers’ data and should drive all messages (except when there are nugs :-).
Thank you for your collaboration!
Hi, different welcome email as supported on all our form managers integration and we’re extending them to all forms, but right not the standard forms (widget, shortcodes, and so one) don’t have the ability to send a custom welcome email.
Hi, probably it’s not a placeholder and you’re using a custom form (maybe provided by the theme). If you can edit the HTML, likely you’ll find the value attribute set, for example:
value=”placeholder text”
while the placeholder attribute should be used:
placeholder=”placeholder text”
if you share the URL of the page where the form is visible I can check it.
Hi, no, there is not that kind of setting in the plugin. I can suggest, seen the real low number of email you’re sending, to get a free plan on one of the many delivery providers (all them can be used via SMTP just installing an SMTP plugin).
You can look at sendgrid, mailjet, mailgun, smtp.com (maybe that one has not a free plan, I don’t remember), sparkpost, and elastic email.
