Forum Replies Created
-
Posts
-
Yes, we’re required to remove it to adhere to some WP best practices. We’re going to release a free extension to get them back as a separate plugin.
And, yes, the url will change.Stefano.
Where did you set the SMTP? If you set the SMTP in Newsletter and it is active, the SMTP is used, there is no need to actually validate it. Eventually set some wrong parameter in the SMTP setting and the emails should stop.
Postman is a plugin for wordpress, there is no need to use it, it’s just an alternative.
Stefano.
Hi, actually, reading the error, probably your form is sending under the key you set as containing an email an array of values. This is why the is_email() function is giving back that error.
Stefano.
Newsletter collects some stats about the frequency the scheduler is activated. Check on diagnostic panel the average time between call, it should be around 300 seconds. If much greater the plugin still work but it could not reach the optimum performances while delivering.
If you just setup the external trigger, wait at least one day since the stats updates slowly.
Stefano.
Hi, can you explain me better what is your need? The newsletter is actually a pure HTML (stored in the database).
Stefano.
Hi Greta, do a test from the diagnostic panel as see if you blog has problem with emails and if the diagnostic messages are delivered.
Which is your provider?Stefano.
Try to use an SMTP, you can try to use the SMTP for your regular email if your provider is managing even the emails for your domain. Or an external service, like mailjet, mailgun, …
Stefano.
ps: the spam is almost surely due to your webserver not trusted from email receivers (gmail, …)If you bought the extensions from this site you have a license key in your account page and you can copy it in that panel to benefit of the automatic updates.
Stefano.
Hi, Newsletter uses a semaphore that should avoid concurrent sending. Did you triggered manually the delivery engine few times in a row? I wonder if there is a bug in checking the semaphore with manual triggering.
Thank you for your help in debugging it!
Stefano.
Error number 500 is logged in the error log of the server. Can you ask the provider where you can get that log?
Stefano.
Subscribed user could see the locked content if they have not a cookie, like when they login. They should start from a link in a newsletter, a link generated by {unclock_url}. Send them a newsletter announcing your new content reserved to them.
Stefano.
Already contacted wordfence, this is a false positive since the ace library is ok and they’re aware of it.
Stefano.
Which messages? The confirmation and welcome messages use a tewmplate you can edit in the message template panel.
Stefano.
Hi, those kind of error are logged by the server in a special log file, named error.log. Ask the provider this file and check if your php version (on newsletter diagnostic panel) is 5.3 or greater.
Stefano.
Il problema lo sta creando il plugin wp-minify, non vedo riferimenti a Newsletter negli errori della pagina. In ogni caso basta disabilitare i vari plugin finché il problema non scompare per capire quale causa il problema. Newsletter non dovrebbe interferire in alcun modo con la resa grafica di un blog.
Possibilmente disabilitare e ripulire ogni plugin di cache o di ottimizzazione javascript, css, html.
Stefano.
Hi checking the code there should be no more references generated by Newsletter to that file. Are you sure it has not been added to your theme?
Stefano.
Uhm, the gray.css should not referenced, thank you for your report. Probably the option is still effective and should be corrected.
Stefano.
The problem is not in the plugin, but you almost surely have another plugin that makes relative the media URLs. In this case you need to correct the URLs by hand.
Stefano.
Hi, do a test from the diagnostic panel. If you get back a success but no email is actually delivered, your provider is applying some kind of filter and you should open a ticket with them.
Stefano.
Ciao, hai verificato se i contatti che stai importando e che falliscono non siano già presenti? PErché non c’è motivo per cui alcuni elementi non te li carichi senza darti errori specifici.
You have something that intercept the submit of the form making it a get without the email field. Check the javascript.
Stefano.
Hi check if in your database (new) there are the tables named wp_newsletter*. If not the backup was incomplete.
Stefano.
If you use an external delivery system integrated with our extensions the bounce management is automatic. Otherwise you should “import” a list of bounced emails so they will be marked as bounced and not contacted anymore.
Stefano.
Probably yes. Clearly your webserver does not support a so massive import of users and blocks for whatever reason.
Stefano.
Hi did you make a test from the diagnostic panel? Does it report “success”? If so and the emails are not delivered it means Newsletter pass over the email toy your server and it does not deliver them.
Let me know, Stefano.
The welcome email is included in Newsletter standard configuration, the followup extension lets to create a serie of 20 email to be sent at regular intervals.
Stefano.
The do folder was removed. The plugin should not generate links to the folder anymore (actually since long time), why you still have confirmation email with those link? The correct subscription link is now http://www.yourcomain.com/?na=s and the confirmation http://www.yourcomain.com/?na=c plus the user key.
Stefano.
Bounce detection requires a delivery error message analyzer. If you use external SMTP service which give you that feature (sendgrid, mailjet, …) Newsletter integrations with those system are able to get back the bounces. Otherwise you can try to use the Bounce plugin from the WP directory.
Stefano.
Do a delivery in the diagnostic panel and check for reported messages. If the diagnostic reports “success” open a ticket to your provider since there is in place some kind of block.
Stefano.
Long delays are always due to your mail service (the one the provider supply in to your web space) since the plugin sends the emails immediately. Try to open a ticket with your provider.
And do few tests from the diagnostic panel of Newsletter. And ask the provider how many email you can send per hour.Bye, Stefano.
Hi, the ticket system is working, I’ll check you account and your tickets may be there were not notified problems.
Stefano.
You should let the blog to contact http://www.thenewsletterplugin.com in port 80 to check for updates. No other activation process is required.
Stefano.
