Many problems after Updates

  • Resolved nowforever

    (@nowforever)


    1 month ago

    Since update to the last big Version there are many Questions which makes Headaches and Problems.

    First of all, Feed Updates do not work – some do not at all and some are not updating as configured. The whole logic lacks to me since the updates and the usabiity makes no sense anymore.
    Before all Update to V4 there was no Problems, now i am considerung usiing external Zapier or Make for such workflows. I did put a lot of workaround in configurations, Unique Cron-Job but everything fails.

    The only way i can manage feed update right now is manually, everthing else is Gambling….


Viewing 1 replies (of 1 total)
  • Plugin Support Hendra Setiawan

    (@hendcorp)

    4 weeks, 1 day ago

    Hi @nowforever

    Thank you for sharing the details about the issues you’re experiencing after the update. I’m sorry to hear that the feed updates have become unreliable for you. I understand how frustrating that can be, especially if everything was working smoothly before.

    One thing that may help us narrow this down is checking whether any of the feed sources are currently encountering errors. If one or more sources repeatedly fail to update, it can sometimes interrupt or slow down the automatic import process for other sources as well.

    Could you please try the following?

    1. Go to Aggregator → Sources in your WordPress dashboard.
    2. Check if any of the sources show a “!” icon next to them (this indicates that the source is encountering an error).
    3. If you find any sources with this icon, try pausing those sources temporarily.
    4. After that, wait for the next automatic update cycle and see whether the other feeds begin updating normally again.

    This will help us determine whether a problematic source might be affecting the automatic updates.

    Please let us know what you find, and we’ll be happy to continue investigating this with you.

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.