Hendra Setiawan
Forum Replies Created
-
Hi @worlok
Thank you for following up.
Please rest assured that the issue is still actively being worked on, and we’ll keep this thread updated as soon as we have more information.
Thank you again for your patience.
Hi @yesdesign
Thank you for reporting this and for including the full error message.
I’ve tested the connection on my end using both connection methods: Basic (via Instagram) and Advanced (via Facebook). In both cases, the connection completed successfully, so I wasn’t able to reproduce the error on my test site.
To help us investigate further, could you please let us know:
- Is Spotlight already updated to the latest version (v1.7.5)? If not, please update it first and try connecting again.
- Are you connecting via the Basic or Advanced method?
Once we have those details, we’ll be able to check this further and determine whether there’s something specific about the account or connection flow causing the issue.
Hi @todga
Thank you for the update.
Since all sources are affected, we’d like to gather a bit more information to better understand what’s happening before recommending the next steps.
Could you please let us know:
- If you go to
Aggregator→Sourcesand click Fetch on one of the affected sources, does it import new items successfully? - Could you share one or two of the RSS feed URLs that are affected?
- Please also share your Site Health information. You can find it under
Tools→Site Health→Info→ Copy site info.
Before posting the Site Health information here, please review it and remove or redact any sensitive details.
Once we have that information, we’ll be happy to investigate further.
- This reply was modified 6 days, 3 hours ago by Hendra Setiawan.
Hi @todga
Thanks for reaching out!
Before we look into setting up cron jobs, we’d like to gather a bit more information to better understand what’s happening.
Could you please let us know:
- Are all sources affected, or only specific ones?
- What is the RSS feed URL for the affected source?
- If you go to
Aggregator→Sourcesand click “Fetch” on one of the affected sources, does it import new items successfully?
It would also be helpful if you could share your Site Health information. You can find it under
Tools→Site Health→Info→ Copy site info.Please make sure to remove or redact any sensitive details before posting it here.
Once we have that information, we’ll be happy to investigate further.
Hi @dany897
Thank you for reporting this and for providing the details of your investigation.
To help us reproduce the issue on our end, could you let us know which plugin is triggering the fatal error? If possible, please also share the full error message or stack trace.
We’ll review the compatibility issue further once we have a bit more information about the environment where it’s occurring.
Thank you for your help.
Hi @kcisme
Thank you so much for the kind words and for taking the time to leave a 5-star review. We’re really glad we could help get things resolved, and we truly appreciate your patience throughout the process.
Thanks again for your support!
Hi @worlok
Thank you for the honest feedback. We completely understand your frustration, especially when your previous setup was working reliably.
We’re continuing to improve v5 compatibility and migration stability, particularly around edge-case feeds, duplicate handling, and feed update reliability.
Regarding the Reddit-related issues you mentioned, I’ve replied in your newer thread here with more details about our current investigation and progress.
We’ve already identified the underlying issue there and are currently working on a fix.
Thanks again for continuing to share detailed feedback with us. We truly appreciate your patience while we continue improving these areas in v5.
Hi @worlok
Thank you for reporting this, and I completely understand how frustrating this has been.
At the moment, Reddit feeds can fail for two main reasons:
- Reddit may return 403 or 429 responses due to blocking or rate limiting.
- Reddit feeds do not fully validate as standard RSS feeds. We confirmed this by testing the feeds using the W3C Feed Validation Service. Validation issues can affect parsing reliability and may cause the feed update to fail.
We also confirmed during testing that simply changing the User-Agent alone does not consistently resolve the issue.
The good news is that we’ve already identified the underlying problem and are currently working on a fix for this. Based on our investigation so far, this appears to be related to how Reddit responds to certain feed requests.
We’ll keep this thread updated as soon as we have more progress to share or once the fix is included in an upcoming release.
Thank you again for reporting this and for your patience while we work on it.
Thanks for confirming that.
Regarding the pinned posts, at the moment, there is no option to keep pinned Instagram posts fixed at the top of the feed, so they will still appear according to their actual publish date rather than their pinned position on Instagram.
I hope this clarifies things. Please let me know if you have any other questions.
Thanks for reaching out and for sharing the detailed troubleshooting steps. That is very helpful.
I checked the latest Instagram posts, and it looks like they are collaborative posts. Spotlight can only display posts where the connected Instagram account is the owner of the post. If the connected account was invited as a collaborator, Spotlight will not be able to display that post due to Instagram’s API limitation.
Could you please check whether the missing posts were created by the connected account, or whether the account was only added as a collaborator?
Hi @worlok
I’m really sorry to hear that the migration hasn’t gone smoothly for your sites.
We understand how frustrating this is, especially when v4 was working well for your setup. We’re continuing to improve v5 and address the reported issues, including feed compatibility, duplicate posts, and update-related problems.
Thanks again for your patience while we continue working through these improvements.
Hi @helijobs
Thanks for the update.
That makes sense, and no worries at all. When you are ready to move forward with the migration, we recommend testing it on a staging copy of the site first. This will let you confirm that everything works as expected before applying the changes to the live site.
Please feel free to reach out again if you need any help when you are ready to proceed.
Hi @helijobs
Thanks for reporting this and for sharing the error message.
Based on the file path in the error, it looks like the issue is coming from the older v4 codebase inside the plugin. Updating the plugin to version 5.0.12 does not necessarily mean that the site has already completed the migration to v5.
Could you please confirm whether you have already run and completed the v5 migration on this site?
If the migration has not been completed yet, we recommend completing it, as that should resolve the issue. We also recommend testing this on a staging copy of your site first, so you can make sure everything works as expected before applying the change to the live site.
I hope this helps. Please let me know how that goes.
Hi @whatsupmf
We’re really glad to hear that Aggregator has been working well for your multisite setup. Thank you for mentioning your positive experience with our support team as well.
Just to clarify for anyone reading, Aggregator does offer a free version, and we also provide support here in the plugin forum.
Thanks again for the kind review and for taking the time to share your experience!
Hi @worlok
Just a quick update on this.
Our team is still working on improving how Aggregator handles feeds like this, and a fix is planned for an upcoming version of the plugin.
That said, I also noticed you mentioned that your site has not yet been migrated. The upcoming fix will be part of the latest version of Aggregator (v5), so in order to benefit from it, the site would need to be migrated when you’re ready.
As a quick reminder, v4 is no longer supported, so we do recommend planning the migration to v5 when possible. You can take your time and test this on a staging site first to ensure everything works as expected.
For now, I’ll go ahead and mark this thread as resolved since there isn’t anything actionable on your current setup, but please don’t hesitate to reply here again once you’ve migrated, or if you have any questions along the way. I’ll be more than happy to continue assisting you.
Thanks again for your patience and understanding.