Danila Vershinin

And they deleted the tag for older versions so those can’t be installed ??

@Auctollo?in case of this plugin, .xml files are no longer generated. So there’s no caching validator like last-modified or etag available via filesystem. It is the plugin’s responsibility to provide those headers because .xml is dynamically generated on every request.

In the latest release, v1.5, I’ve revised the regular expression used in cases when markup is generated.

Before, it would only generate markup for an abbreviation that is at the very beginning of a line; either in between other words (has spaces on either side) or at the end of a sentence or a phrase (followed by a comma or a dot).

The new algorithm will generate markup for a few more cases, most importantly when an abbreviation is at the beginning of a tag’s contents. For example, <p>SEO is ...</p> will trigger markup generation, while before it didn’t.

Kindly check the latest version and see if it works better for you.

Hi Daniel,

Pardon as this thread reached me very late.

Perhaps, you’re expecting it to replace all abbreviations on the page? The plugin functions by design if it makes markup only for the first occurrence of an abbreviation.

E.g. if SEO is your abbreviation, that is placed many times on the page, only the very first occurrence will be getting markup for abbreviation.

Thank you for letting me know. Fixed in the latest version.

On a related note (to save from opening another thread):

Is it possible to have the plugin immediately visit purged URLs?

Or have a sort of function to add the purged URLs to transient storage to be picked up later by a cron job for warming up the cache nearly immediately after purging?

You’re very right. I am passing $_SERVER['HTTP_HOST'] to deal with other plugin’s errors in CLI context ??

You should keep both. One applies to static files, while the other to WordPress pages themselves.

If anyone finds this thread and want the proper cron: I have posted an article detailing how you can use real Linux cron with recent Mailpoet.

Would you please add it as an option to have native WordPress crons run Mailpoet tasks, even if that would be an invisible option that has to be enabled by changing a value in database.

I understand the removal of native WordPress cron option is for the sake of the majority users.

But this is not electing a president – it’s possible not to take away things from the minority. You could hide it from UI but keep it.

Thanks.

If you’re so unwilling to improve your plugin, I assume all the readers would know the quality of the PRO version makes it a bad choice. Not using WordPress conventions for starting PHP sessions and referring to a PRO version for support – shows plain lack of development expertise and culture.

Thank you, sir.

Hi Marco, I’m just new to your plugin: just created a fresh bot ?? and things did not work (neither for channel nor private message) with “Incorrect parameters” in the log. Please see this thread:

https://www.ads-software.com/support/topic/error-incorrect-parameters-and-solved?replies=1

Hope you can update plugin so it works out of the box without manually editing the code.

+1, thanks to sergioucoes

Removing reply_markup from below line makes things work for me:

$data = compact('chat_id', 'text', 'parse_mode', 'reply_markup');