





3:30 am

December 2, 2024

I'd like to humbly request an update to the "Must Be Newer Than" content filter setting. As it stands now it does not actually respect the "published" date from YouTube XML, but pulls the "last updated" date. This means content could be two years old but the thumbnail or something was updated, and it would pass as "within 1 day" should you try to filter that way.
My entire setup is based on fresh content. This one setting has caused me to spend hours trying to filter out posts that are outside of 24 hours for the publish date. This includes using the CyberSEO GPT code assistant to create pre-process filters or custom PHP filters. So far nothing has worked, as something with an old post date always slips through.
I'm still testing, but if possible I recommend changing this filter to two settings as follows:
1) "Must Be Newer Than" -> "Must Be Published Within __ days"
+
2) "Last Updated Must Be Within __ days"
This would make the current filter more accurate and function as intended for anyone that needs only fresh YouTube XML content, or is trying to target the "published" date field.
Thanks for the suggestion - we've seen similar requests before, and you're absolutely right that there is a real need to distinguish between publication and last update dates, especially with YouTube XML feeds.
Currently, the filter uses the update date because many users rely on it to catch all recent changes - not just new uploads, but also changes to titles, thumbnails, etc. That said, we completely understand your use case, and you're not alone - filtering by original publication date is just as important for setups that focus strictly on fresh content. We're looking at ways to solve it.
Meanwhile, since CyberSEO Pro supports custom PHP snippets, your task can be solved right now with a single line of PHP code. The publication date is available as $xml_tags['published']['val'], while the update date is in $xml_tags['updated']['val']. You can compare either of these to the current time and your preferred range. If the condition isn't true, just set $post = false; - this tells the plugin to skip the post.
Here's a simple example that skips posts published more than 1 day ago:
Login to see the code
Or use updated instead of published, depending on your needs.
If you're not comfortable writing code, feel free to ask our GPT Assistant here: Login to see this link - it's great at generating snippets like this for CyberSEO Pro.
2:44 am

December 2, 2024

Ok, thanks for the code, I will test it. I was using the ChatGPT CyberSEO assistant and it kept recommending preprocess code that didn't seem to work well.
Side note - when using this custom php, should I keep "must be newer than" enabled?
Also, hopefully this custom php occurs before any API requests are submitted, to save on requests. Ideally it filters the post first, then handles any AI requests, etc.
It doesn't matter what options you have enabled in the feed settings, including "must be newer than" or anything else. Your custom PHP snippet will be executed according to the plugin's internal workflow, regardless of these settings.
All content processing (e.g. translation, rewriting, filtering, etc.) should be done inside the PHP snippet using CyberSEO Pro API functions. Therefore, the corresponding options should be disabled in the plugin settings. When communicating with the GPT Assistant, be sure to clearly state that you're looking for a solution that uses only custom PHP, without relying on preprocessing or other plugin settings. Ask it to use API functions to implement your specific use case - unfortunately you didn't mention exactly what you are trying to achieve (translation, rewriting, filtering, etc.).
Please note that the PHP snippet example I provided is just an alternative workaround. After evaluating all possible solutions to your problem, we've decided to change the behavior of the plugin itself. For YouTube feeds, the "must be newer than" filter in 12.000 will use the date of publication instead of the time of update. According to YouTube's own policy, content updates (such as thumbnail changes) don't change the video itself - so checking the updated date doesn't make sense for your use case.
Most Users Ever Online: 541
Currently Online:
7 Guest(s)
Currently Browsing this Page:
1 Guest(s)
Top Posters:
ninja321: 86
s.baryshev.aoasp: 68
Freedom: 61
harboot: 56
Pandermos: 54
MediFormatica: 49
Member Stats:
Guest Posters: 337
Members: 2980
Moderators: 0
Admins: 1
Forum Stats:
Groups: 1
Forums: 5
Topics: 1694
Posts: 8666
Newest Members:
raffaellabonaschi, matogon, nduwawep, burakaltanalisan, info.magicbytes, ioannis.mavroudisAdministrators: CyberSEO: 4086