• As of update 3.5 the auto poster keeps digging up 10 year old posts (3 at a time) and posts them to all socials.

Viewing 3 replies - 1 through 3 (of 3 total)
  • aiswaryaxyzscripts

    (@aiswaryaxyzscripts)

    Hi,

    The latest update (3.5) introduced Threads support, but there were no changes related to publishing behavior. Please check if any action or plugin is triggering the publishing of your old posts, as the auto-poster will only share posts when a publish action occurs.

    Additionally, ensure that auto-posting in edit is set to disabled in the Social Media Auto Publish settings. If any issues persist, try clearing the cache and deactivating/reactivating the plugin after the update.

    Let me know if you need further assistance!

    Thread Starter xxxLesy

    (@xxxlesy)

    Checked the following:

    • Old articles weren’t being edited or touched in any way, and auto post on edit is disabled.
    • Cleared redis object cache.
    • Disabled and re-enabled SMAP.
    • Checked cron jobs for anything related to those IDs. Found nothing.

    The same has started happening on my other 2 sites after updating SMAP to 3.5. So I’m going to rule out php 8.4.5 update that happened rought the same time (because that happened at the same time on all 3 sites).

    Other things I’ve noticed:

    • All normal posts are getting published, so there isn’t a case of mistaken article IDs.
    • Debug doesn’t show any errors, related to SMAP.
    • Other things that could potentially interfere: Events Manager events, Advanced Ads ads (both schedule posts via cron jobs, but post IDs don’t match, and their post types aren’t selected in SMAP settings).
    • I’m also using MWW Scheduled Post Trigger (checks for missed scheduled posts and posts them – because sometimes cron jobs fail). Perhaps that could somehow interfere?
    • I’ve downgraded to 3.4.1 on 2 of my more important sites. I’ve noticed the log page looks different to 3.5 version. In 3.5 entries are grouped by social channel and ascending (newest on bottom), while in 3.4.1 entries are mixed and sorted by date descending (newest on top). Seems minor, but perhaps something is different.

    I’ll continue monitoring and testing. For now I downgraded SMAP on 1 site, disabled MWW scheduled post trigger on a second, and left the third as is.

    Edit: P. S. I checked post_meta and noticed new (properly published) posts have a line xyz_smap = 1 and either nothing else or xyz_smap_insert_og = 0, while old ones have both xyz_smap = 1 and xyz_smap_insert_og = 1. Not sure if this is relevant.

    • This reply was modified 1 day, 3 hours ago by xxxLesy.
    • This reply was modified 1 day, 2 hours ago by xxxLesy.

    Hi,

    The log changes in SMAP 3.5 are purely for better organization and have no impact on publishing behavior. Since SMAP only triggers when a post is published, something else is likely causing old posts to be reposted.Possible Causes:

    • MWW Scheduled Post Trigger might be treating old posts as “missed” and republishing them.
    • Other plugins (Events Manager, Advanced Ads, etc.) could be modifying posts in a way that triggers SMAP.
    • Post Meta Differences – The xyz_smap_insert_og setting is related to Open Graph tags and does not affect publishing.
    • Cache & Cron Jobs – Caching plugins or delayed cron jobs might be causing unintended actions. Try clearing your cache and checking logs for unusual activity.

    Please try disabling MWW Scheduled Post Trigger on one site and monitor if the issue stops.
    Let us know what you find!

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.