Hendra Setiawan

Hi @worlok

Thanks for sharing the feed URL!

Similar to the Reddit feed case discussed here, I checked the feed using the W3C RSS validator and found that the feed is not a valid RSS feed. This can affect how Aggregator processes and updates items, especially in version 5, which relies more strictly on feed standards.

We understand that this feed was working as expected in version 4, and we appreciate you pointing out the difference in behavior. We will raise this with our development team to investigate further and see whether any improvements or adjustments can be made on our end.

We will get back to you once we have more information. Thanks for your patience while we look into this.

Hi @worlok

Thanks for sharing the feed URLs.

I checked them using the W3C Feed Validator and found that the RSS feeds are not valid. Because of this, Aggregator is not able to process and import the content correctly.

Aggregator requires a valid RSS feed in order to work as expected, and this is especially important in version 5, which follows stricter feed parsing and validation rules than previous versions.

At this point, the best next step would be to have the feed issues resolved at the source. Once the feeds validate successfully, Aggregator should be able to import them without any problems.

If you have any other feed URLs you would like us to test, feel free to share them and we will be happy to take a look.

Hi @worlok

Thanks for sharing the details so far.

To help us investigate this further, could you please share the exact RSS feed URL that is returning the 403 error? Once we have the specific feed URL, we can test it on our end and take a closer look at how it is responding to requests.

This will allow us to better understand what is causing the issue and determine the best possible solution for your setup.

Looking forward to your reply.

Hi @latashaaluu

Just to clarify, version 5.0.10 was actually released this week. That said, 5.0.10 is indeed the latest version, and yes, you can definitely try reinstalling the plugin to ensure everything is in place.

As a precaution, we strongly recommend taking a full backup of your site first, just in case anything unexpected happens during the process.

If the issue persists after reinstalling and attempting the migration again, could you please share the following details from Tools → Site Health → Info?

• WordPress version
• PHP version
• PHP memory limit
• Active plugins list
• Server information

There’s no need to paste the full Site Health report. Please also make sure to remove or redact any sensitive information before sharing. This should give us enough context to review your environment and help identify what might still be preventing the migration from completing.

Looking forward to your update.

Hi @thetheme

Thanks for reaching out!

When you mention that V5 shows old feed items and doesn’t allow you to limit the number displayed, could you let us know how you’re currently displaying the feed items? Are you using a shortcode?

In V5, we introduced a new system for managing and displaying feeds called Displays. It may be worth reviewing this guide on how to convert your old shortcodes into the new format:

Converting Migrated Shortcodes into Displays

That should help you regain control over what’s shown and how many items appear.

Let me know what you find, happy to guide you through it further if needed!

@laurelfulford We’re glad to see the issue has been resolved with the updated copy from @tw2113 , and appreciate you confirming that everything is working well on your end.

That said, we do recognize this type of dependency conflict could affect others in the future, so we’ll be implementing a more robust solution in an upcoming Aggregator update to help prevent similar issues.

Since things are now working as expected with the temporary fix, we’ll go ahead and mark this thread as resolved for now.

Let us know if anything else comes up, we’re always happy to help!

Hi @latashaaluu

Thanks for reaching out and sorry for the trouble you experienced during the migration.

When the migration screen gets stuck on the spinner, it usually means something is failing in the background, often due to a PHP error, server limitation, or a conflict with another plugin or theme. To help us understand exactly what’s happening on your site, could you please share your PHP debug logs with us?

If WordPress debugging is not enabled yet, you can do so by editing your wp-config.php file and adding or updating the following lines:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

After enabling this, please try running the migration again until it gets stuck. Then, you can find the log file at:

/wp-content/debug.log

Please copy the contents of that file and share it here, or attach it if possible.

Once we have the PHP error details, we should be able to identify why the migration is not completing and advise on the next steps.