Actions and Filters Deprecation Guide
Migrating from Aggregator v4 to v5 removes several actions and filters used in v4 for customizing feed imports and post processing. As of now, there are no direct alternatives to these hooks, which means any custom code that relies on them will no longer function. Below is a list of deprecated hooks and steps to help you migrate safely.
Deprecated Hooks
The following actions and filters from v4 have been deprecated in v5:
Core Plugin
| Hook Name | Description |
wprss_populate_post_data |
Modify post data during import |
wprss_insert_post_item_conditionals |
Apply conditional logic to post imports |
wprss_before_curl_exec |
Execute custom code before the cURL request |
Feed to Post
| Hook Name | Description |
wprss_ftp_post_args |
Modify post arguments before saving |
wprss_ftp_post_meta |
Adjust metadata for imported posts |
wprss_ftp_link_post_title |
Customize title linking behavior |
wprss_ftp_post_content_filter_priority |
Set priority for the content filter |
wprss_ftp_converter_post_title |
Fix encoding issues in imported post titles |
wprss_ftp_force_delete_by_source |
Force permanent deletion of posts by source |
wprss_ftp_add_source_link_method |
Customize how source links are added |
wprss_ftp_trimming_keep_tags |
Preserve specific HTML tags during trimming |
Templates
| Hook Name | Description |
wprss_et_allowed_tags_in_excerpts |
Define which HTML tags are allowed in excerpts |
Migration Steps
- Identify Custom Code: Locate any use of these hooks in your
functions.php, custom plugins, or snippets. - Test on Staging: Before migrating your live site to v5, create a staging or development copy. Install v5 and test all customizations relying on these hooks.
- Why: With no v5 alternatives, this code will stop working, potentially disrupting feed imports or post handling.
- Assess Impact: Evaluate how the removal affects your site. Test feed imports, post creation, and displays to identify gaps left by these hooks.
- Remove Obsolete Code: Since no replacements exist, remove these hooks from your codebase. Rely on v5’s default behavior or explore manual workarounds (e.g., settings adjustments).
- Validate Thoroughly: After migrating on staging, ensure core functionality meets your needs without these customizations.
Potential Issues
Without alternatives, custom logic for feed processing, post formatting, or cleanup will cease, possibly altering how your site handles feeds. Thorough testing is critical to adapt to v5’s default functionality.
Recommendation
Test extensively on a staging environment before migrating to v5 on your live site. Remove outdated code and adjust workflows to align with v5’s built-in features, as no direct replacements are available at this time.