Hendra Setiawan
Forum Replies Created
-
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.
Hi Laurent,
Thanks for checking in, and we really appreciate your patience on this.
At the moment, we don’t have a specific ETA to share just yet. That said, please know that our team is actively working on a fix, and it will be included in an upcoming version of the plugin.
We understand how important this is, especially with the number of sources you’re managing, and we’re doing our best to get this resolved as soon as possible.
We’ll be sure to update the thread as soon as there’s any news or when the fix is released.
Thanks again for your patience and understanding.
Hi Irene,
Thank you for the update, I’m really glad to hear that everything is running smoothly again on v5 🙂
It’s possible that switching between versions helped reset certain settings or processes behind the scenes. Additionally, we’ve included a few improvements to the migration handler in the latest version of Aggregator, which may have contributed to resolving the issue.
At this point, since things are working as expected again, I’d recommend continuing to monitor the updates over the next few days. If anything unusual comes up, please don’t hesitate to let us know and we’ll be happy to take a closer look.
Thanks again for your patience throughout this!
Hi @emswpuser
Thanks so much for your kind words and the 5-star review! We’re really glad to hear the plugin is working well for you, and it’s great to know our support team was able to help when needed.
If you ever have any questions or need anything else, feel free to reach out anytime, we’re always happy to help 🙂
Hi Johny,
Thanks for sharing this, and I’m glad you were able to identify the cause and get it working on your end.
We appreciate you posting the fix as well, this will definitely help others who might run into the same issue with Elementor and OceanWP.
If anything else comes up, feel free to reach out anytime 🙂
Hi @worlok
Thank you for reaching out and for sharing the feed URL.
I’ve taken a closer look at the feed, and it appears that it does not include a
<guid>element for the items. This is typically required for Aggregator to properly identify and process each entry, and its absence can cause the plugin to treat the feed as invalid or fail to import it correctly.I’ve gone ahead and passed this along to our development team for further review to see how we can better handle feeds like this. I’ll be sure to share any updates with you as soon as I have more information.
In the meantime, if you have access to the feed source, you may want to check if it’s possible to include a
<guid>element, as that would help ensure compatibility.Thank you for your patience, and please let me know if you have any questions.
Hi Irene,
Thank you for the update.
At this stage, continuing to monitor the behavior is the right approach. If the automatic updates still do not resume consistently, please let us know.
We’ll be happy to continue investigating with you if needed.
Hi Laurent,
Thank you for your continued patience and for taking the time to go through all the troubleshooting steps with us. We really appreciate your cooperation throughout this process.
At this point, we’ve identified that the issue with automatic feed updates is related to a problem on our side. Our team is actively working on a fix, which will be included in an upcoming version of Aggregator.
In the meantime, we understand this is not ideal, especially with the number of sources you’re managing, and we truly appreciate your patience while we work on resolving this.
We’ll keep you informed as soon as the fix is released. Please don’t hesitate to reach out if you have any questions in the meantime.
Thank you for your detailed explanation, it really helps clarify your use case.
From your question, particularly the reference to
wprss_ftp_post_meta, it looks like this relates to the Feed to Post add-on from Aggregator v4, which is part of the Premium plugin.To make sure we can properly assist you, we kindly ask that you reach out to us via our contact form, as this forum is intended for the free version only.
We’ll be happy to continue helping you there. I appreciate your understanding.