badshark

Hi!

Marco from MailPoet here.

I’d like to clarify how the MailPoet cron URL works, and explain a little bit more on why you are seeing those files in your folder.

On UNIX systems, having output from a cron job is an expected and required behaviour, for the purpose of debugging issues and reporting to system administrators. So, after the execution of a cron job is completed, two things happen on a standard Linux server:
– The output of the script is sent to the standard output, and logged.
– An email will be sent to the administrator, in case of error exit codes.

In this specific case, since the cron job has been set up with wget, a file is being downloaded too. That’s because wget is a download utility, and its normal behavior is not to just visit an url, but download the page.

Now, let’s see how we can avoid these three events from happening, and have a real silent cron ??

This is your current cron job:
$ wget “https://mailpoet.com/cron”

Here’s what it’s doing:
1. Download that page to a file named cron.
2. Output the wget standard output to the console and to a log file.
3. Send an email to the admin in case wget can’t download that page.

Here’s how to stop it:

1. Stop downloading the file.
Curl is the proper utility to visit an URL without downloading anything, instead of wget. So, let’s replace wget with:
$ curl –silent “https://mailpoet.com/cron”

2. Stop outputting to the console.
Let’s redirect the command to null:
$ curl –silent “https://mailpoet.com/cron” > /dev/null

3. Stop sending emails in case of errors.
If the curl call exits with an error status code, even if we are redirecting the output to null, we’ll get an email. We need to tell the cron job that we want to consider error exit codes (2) as normal exit codes and send them to null too, so we add this at the end:
$ curl –silent “https://mailpoet.com/cron” > /dev/null 2>&1

This is a truly silent cron job. ??

Hi Ann,

Thanks for reporting this.

We did a few tests but we are unable to replicate this issue.

I suspect it’s not directly related to MailPoet, but it could be related to a low memory limit set on your server, that could block the crunching, since we do have our own defined image size.

Could you get in touch with us at https://support.mailpoet.com/feedback/ ?

We’ll be able to test your server to understand where’s the issue.

Thanks!

Hi,

Many thanks for testing it!

We are running more tests here to understand what’s causing the issue.
All browsers seems to work fine, except Chrome.

We’ll let you know as soon as possible, we are on it.

Thanks guys!

Hey guys,

Thanks for reporting this!

We are looking into the issue, but unfortunately we are unable to replicate it.
We tested it on 3.7.1 and 3.6 as well.

The only reason we can think of is a plugin conflict.
Could you let us know your plugins list?
Let’s try to find if you are using a particular plugin that might be causing a conflict.

Don’t worry, we are on it ??

Thanks!

Hi,

Great you found it!

Here’s a guide about the shortcodes:
https://support.wysija.com/knowledgebase/guide-to-first-and-last-names-newsletter/

Thanks!

Hi,

This is generally something related to a particular email client.

Could you please open a support ticket at: https://support.wysija.com/feedback/

We’ll take care of it as soon as we can.

Thanks!

Hi,

Thanks for asking!

Unfortunately we don’t have this feature yet.

You can send automatic newsletters filtering by categories, but sending the latest “popular” posts is not something we support right now.

Thanks again!

Hi,

It could be a plugin conflict that it’s blocking the popup load.
Could you please open a ticket with out support team?
https://support.wysija.com/feedback/

We’ll take care of this issue as soon as we can.

Thanks!

Hi Byron,

I checked all the code we are inserting when adding a form, and I can’t see any problems. There are no missing divs or missing closing elements.

Would you mind opening a ticket with our support team?
You can do it at https://support.wysija.com/feedback/

We’ll look into this issue, it’s something related to your theme or a plugin conflict.

Thanks!

Hi Adrian,

About the strict standards warnings, they will be fixed in the next releases, but they are just warnings when you use PHP 5.4, since from PHP 5.4 strict standards suggestions will be flagged as warnings.
These warnings are not affecting your website at all.

About the first two errors, we are investigating, did you see some errors in the WordPress panel too, or just in the logs?

Thanks!

Hi!

Yes, you are right, translations are still not working on these shortcodes, we just launched this new functionality and we’ll surely support translations in the future.

Right now, we don’t have a shortcode for the leading zero in day or month, but we’ll introduce it in the next versions of the plugin.

You can use the hook (filter) to customize the shortcodes as you want.

Thanks!

Hi!

I can surely help you in setting up the hook, but I think that in your case is not necessary to use the hook.

The shortcodes for all types of dates are already built into the plugin.

In the editor, when adding a text, you can click on the shortcodes button (the profile icon) and you’ll be able to select all type of dates.

You can do it manually too, here are the date shortcodes for your example:

– Tuesday 19th February 2013
– [date:dtext] [date:dordinal] [date:mtext] [date:y]

Let me know if it works.

Thanks!