Szabi – CodeRevolution

I am glad to help! 🙂

If you like the plugin, please give it a rating on CodeCanyon, it is really appreciated!

Hi,

Thanks for the details.

The feeds are updating, Blogtrottr just isn’t seeing it. WordPress sends a 304 when it thinks nothing changed, based on your last regular blog post, not on CCRF updates. So Blogtrottr skips downloading the feed even though the items are new.

That’s why the feed looks fine in the browser, but Blogtrottr keeps getting “304 Not Modified”.

Quick things to try:

exclude your feed URLs from any cache (Cloudflare, caching plugin, host cache)
open the feed in a private window to confirm the new items are there
in Blogtrottr, remove and re-add one feed (or add ?v=2 to the URL once) so it does a fresh fetch
I’ll also look at fixing this in the plugin so 304 is based on the actual CCRF feed update, not WordPress posts. I should release an update with this, soon.

Thanks,
Szabi – CodeRevolution

Hello,

First of all, thank you for your purchase.

Please send me your old domain or your purchase code to my email kisded@yahoo.com

I will help with this.

Regards,
Szabi – CodeRevolution.

Hello,

1. If you leave Affiliate Link Mode set to Use Discovery API links as-is, the plugin will use the links returned directly by the Ticketmaster Discovery API/feed. So newly created posts should be as correct as the data Ticketmaster provides through their API. This will continue to work, but if you have also an Impact affiliate account, you can switch directly to using it and wrapping the links in Impact tracking, as this is the new method they promote now.

2. If you switch to Wrap links with my Impact tracking template, then the plugin will force the Ticketmaster event URL through your Impact tracking link. I think that one generic Impact template should work, as long as it accepts the final Ticketmaster URL as the destination/deep link parameter.

My recommendation is to test both approaches, to see if both work for you well and go with Impact if it works ok for you.

Regards,
Szabi – CodeRevolution.

Hello,

Thanks for the detailed explanation.

I think the current setup makes sense, but the weak point is Ticketmaster’s metadata consistency, not really your script. Different countries and organizers classify events very differently, so even a solid fallback matcher will sometimes get it wrong.

That said, since Tmomatic already exposes Ticketmaster’s own classification fields like %%item_classification_genre%% and %%item_classification_subgenre%%, I’d probably simplify the setup and use those directly instead of relying on post-import detection logic. Those values should generally be more reliable.

Your current code is actually very good as a normalization fallback, but using the native classification data directly should reduce mismatches.

Let me know if this helped.

Regards,
CodeRevolution

Hello, yes, the license is lifetime and support is expiring. If you no longer need support, you can redownload the latest version of the Aimogen Pro plugin from CodeCanyon and activate it using your Envato purchase code, it will work.
If you need also support, I recommend you migrate to WPBay, you can use the generated coupon to get 1 year free usage and support, afterwards the support will be 59$ yearly.
I hope this info helps, if you have more questions, let me know by email kisded@yahoo.com
Regards,
Szabi – CodeRevolution

Hello,

Please contact your hosting’s support, as this is not normal behavior, your hosting should not be suspended if you install the Echo RSS plugin. Please contact their support and ask details about this, your hosting should be restored.

If you no longer want to use the Echo RSS plugin, you can make a refund request here: https://codecanyon.net/refund_requests/new

Regards,
Szabi – CodeRevolution

Hello,
I checked, but I don’t find an account created with this email. Can you try again, please? I made some changes to the registration process, please check if it will work now.
Let me know.
Regards.