Blog

How to use Post template feature inside campaign editing ?

How to use Post template feature inside campaign editing ?

This answer also apply for: How to add all fetched enclosures or media files in the post content ? How to add a Gallery with all images in the post ? How to add shortcodes automatically in the fetched post contents ? Campaign post template 

Error when loading Settings page

Error when loading Settings page

It sounds like cURL is not activated in your hosting. Can you see writing below the WPeMatico section in your WP Settings? Try checking the box for “Hide Reviews on Settings”.    

Jump duplicate posts

Jump duplicate posts

The name of the option in the Settings is Continue fetching if found duplicated items”. (This was previously named Jump Duplicates).

Keep in mind that the campaign works with the items in the order they are found in the feed. If a duplicate item is found, that means that all the following items were already fetched in a previously executed campaign. (This happens when the campaign has some time running automatically, not the first time.)

That’s why the campaign is interrupted when it finds the first duplicate post.

  • It is strongly recommended that you deactivate Jump Duplicates to get better behavior.

If you deactivate the “Jump Duplicates” option, you can run the campaign more times in an hour so you don’t miss any posts.

You will not miss new posts because the feed items are ordered by date/time in almost all cases.  When the campaign runs, it goes item by item from newest to oldest, and stops when it finds the first duplicated item, this mean that all items after it (the older ones) are also duplicated.

We are talking about autoblogging, meaning new items are added automatically. Focus your mind on the future, not the past

Example 1: If you fetch 4 out of 10 items in a feed, then you missed 6, but just the first time.  After the first run, the campaign stops when it finds the first duplicated post, in this case, item #4.  Then, if you run the campaign often enough, it will not miss any posts unless the feed adds too many posts between campaign runs.

 

Example 2: If you have a feed that has 34 items, then:

You must set the campaign to work from now to the future, and then you can deprecate old items (or try to manually run a campaign to fetch the 34 items, but this is pointless for the main purpose).

Then, you must know how many new items are added per hour (or per two hours, or per day). This depends of the source site.

If you see that the main site is adding around 10 posts a day, you could say that getting 2 posts per hour is enough. You’ll get better performance if this value is as low as possible, and you won’t miss any items because the main site doesn’t have more than 1 new post per hour.

If you think that more than 2 posts can be added in an hour, then you can fetch every 30 minutes.

This is also better for performance.

 

  • If you are using the Custom Titles feature from the Professional version, you’ll also lose Duplicate Titles checking, because the original title will be saved always as a different title.
Post de Prueba

Post de Prueba

Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmodtempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam,quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodoconsequat. Duis aute irure dolor in reprehenderit in voluptate velit essecillum dolore eu 

WPeMatico New 2.5 Version

WPeMatico New 2.5 Version

Highly recommended update, this version has important changes in terms of plugin security. Almost all of them requested by WordPress.org plugin moderators after a strict revision to follow the development standards of WordPress coding. It is recommended to test it on development servers before implementing 

New major version WPeMatico 2.4

New major version WPeMatico 2.4

We released version 2.4 of WPeMatico.

In this version there is an outstanding feature that is the new external cron process.
From now on we have deprecated the calling to the old file wpe-cron.php
We still have it to keep the compatibility backwards, but if you use external cron you would have to modify the call to the new URL that follows the WordPress standards.
We’ll keep it a few more weeks and we’ll announce in the administration screens that it will be removed.

This new process to run with cron follows strictly the WordPress standards, cancelling external calls to configuration files, improving performance and data processing for the execution of the campaigns.

So much in so little.

A major version composed of several minor versions.

Although it seems that there are no big changes because it is a major version, we have divided all the new features and fixes in several small releases.
This helps not to deal with all the changes together, reducing dramatically the error margins and the generation of bugs with their corresponding support tickets.

So many of the features listed below were added and several more that come in the following minor releases.

Changelog

  • Added custom statuses to campaigns.
  • Improved from scratch external cron processes . If you use external cron, you should take a look at the new URLs in Configuration.
  • Improved insertion of tags and categories in messages.
  • Added possibility to add tags in the post type Topics of BBPress.
  • Resolves a problem when getting the source coding chrset
  • Solves a problem in the controls of duplicated by hash.
  • We changed the transient name from encoding_hosts to wpematico_encoding_hosts.
  • Increased transient cache time of encoding_hosts to 6 hours.
  • Improved security when saving data in all admin screens.
  • Fixes a reported vulnerability that was only available to users who could access the WPeMatico Settings screen.
  • Implementation of the sections by WordPress filters in the different tabs of the Settings.
  • Installed extensions are now showed in the plugins page in the row of the WPeMatico plugin.
  • Fixes some warnings on the Licenses page.
  • Fixes the Uncaught Error: Calling a get_columns() member function on the page…
  • Changed the constants printed in the debug file to a limited white list of them.
  • Fixes some problems with multiple alerts in the campaign edit js.
  • We fixed many bugs based on your feedback. Thanks for helping us out!

Take a look and download it from WordPress.org by clicking here!

WPeMatico New 2.5 Version

WPeMatico New 2.5 Version

Highly recommended update, this version has important changes in terms of plugin security. Almost all of them requested by WordPress.org plugin moderators after a strict revision to follow the development standards of WordPress coding. It is recommended to test it on development servers before implementing 

EDD MercadoPago 1.3.2 version

EDD MercadoPago 1.3.2 version

MercadoPago is one of the largest and most important payment gateways for many Central and South America countries. This platform allows the payment of products and services electronically through many different payment methods. They work with national and international credit cards. Payment links, QR payments, 

New major version WPeMatico 2.4

New major version WPeMatico 2.4

We released version 2.4 of WPeMatico.

In this version there is an outstanding feature that is the new external cron process.
From now on we have deprecated the calling to the old file wpe-cron.php
We still have it to keep the compatibility backwards, but if you use external cron you would have to modify the call to the new URL that follows the WordPress standards.
We’ll keep it a few more weeks and we’ll announce in the administration screens that it will be removed.

This new process to run with cron follows strictly the WordPress standards, cancelling external calls to configuration files, improving performance and data processing for the execution of the campaigns.

So much in so little.

A major version composed of several minor versions.

Although it seems that there are no big changes because it is a major version, we have divided all the new features and fixes in several small releases.
This helps not to deal with all the changes together, reducing dramatically the error margins and the generation of bugs with their corresponding support tickets.

So many of the features listed below were added and several more that come in the following minor releases.

Changelog

  • Added custom statuses to campaigns.
  • Improved from scratch external cron processes . If you use external cron, you should take a look at the new URLs in Configuration.
  • Improved insertion of tags and categories in messages.
  • Added possibility to add tags in the post type Topics of BBPress.
  • Resolves a problem when getting the source coding chrset
  • Solves a problem in the controls of duplicated by hash.
  • We changed the transient name from encoding_hosts to wpematico_encoding_hosts.
  • Increased transient cache time of encoding_hosts to 6 hours.
  • Improved security when saving data in all admin screens.
  • Fixes a reported vulnerability that was only available to users who could access the WPeMatico Settings screen.
  • Implementation of the sections by WordPress filters in the different tabs of the Settings.
  • Installed extensions are now showed in the plugins page in the row of the WPeMatico plugin.
  • Fixes some warnings on the Licenses page.
  • Fixes the Uncaught Error: Calling a get_columns() member function on the page…
  • Changed the constants printed in the debug file to a limited white list of them.
  • Fixes some problems with multiple alerts in the campaign edit js.
  • We fixed many bugs based on your feedback. Thanks for helping us out!

Take a look and download it from WordPress.org by clicking here!

Novi koševi u „SBB Jezeru“

Novi koševi u „SBB Jezeru“

Sportsko privredno društvo Radnički neprekidno radi na poboljšanju trenažnih uslova u svim objektima pod svojom ingerencijom. Tako su pre par dana u „SBB halu Jezero“ postavljeni novi koševi, dopremljeni direktno iz beogradske „Štark Arene“. Ova donacija je plod uspešne poslovne saradnje Sportskog privrednog društva Radnički