When importing items from your sources, there might be times when some or all of a source’s items are not imported. This can happen for a number of reasons. Follow the steps below to locate and solve any potential issues that may be causing this to happen.
Check the Source
Start by confirming that the source URL you are using is correct and accessible. Open the URL directly in your browser to verify that it is active and publicly available. If the source has restrictions, such as requiring authentication or being protected by geo-blocks, it may prevent Aggregator from importing content.
Additionally, ensure that the source provides well-formed data that can be parsed by the plugin. In some cases, sources may have structural issues that make it difficult for the plugin to extract items. To do this, test the URL using the W3C Feed Validation Service.
If everything looks good with the source you’re testing, try testing another source to see if Aggregator imports its items correctly, which helps isolate the issue.
Review Limits in Settings
Aggregator has settings that can limit the number of items imported. Check the following limits to make sure that they’re not preventing the source from importing any items:
Limit the amount of stored items to:(Reference)Update strategy(Reference)Limit the number of stored items by age(Reference)Activate feed(Reference)Pause feed(Reference)
Each of these limits is controlled from within the source settings, as referenced above.
Assess Your Automation Rules
Automation rules in Aggregator can control when and how items are imported or processed. Review a source’s filtering rules to confirm that none are preventing items from being imported.
For example, automation rules that filter items based on keywords or tags may lead to some items being excluded if they do not exactly match the specified criteria.
Here are some suggestions to test this out:
- Temporarily pause automation rules and test importing items to determine if a rule is causing the issue.
- Edit rules to include more flexible criteria if too many items are being excluded.
- Review the order of rules to ensure the most critical conditions are prioritized.
Test for Stuck Cron
Aggregator relies on WordPress’s built-in cron system to schedule and run imports for each source. If the cron is stuck or not functioning properly, scheduled imports may fail to execute. Check for any indications that your cron jobs are stuck or failing to run by following these troubleshooting steps.
Test for Conflicts
At times, another plugin or theme on your site might conflict with Aggregator and cause the importing process to fail. Check out our conflict testing guide to see whether running Aggregator alone on your site will get the import to work correctly.
