| 开发者 | fernandofas2909 |
|---|---|
| 更新时间 | 2026年11月12日 03:46 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
/old-page and /new-page. Relative paths are converted to URLs for the current site.
Standard URL redirects
Use a standard rule when a page has moved, a URL has changed or visitors should be sent to a different destination.
https://example.com/wordpress, both /old-page and /wordpress/old-page resolve to the same source without adding the subdirectory twice.
Dates use the WordPress site timezone shown next to the start field. A scheduled 302 is inactive before its start and stops at its end. The original page then resumes its normal behaviour. Legacy imported rules without dates remain compatible; edit them to add an end date. Redirect responses send cache-control headers to avoid retaining a scheduled redirect past its end. A 302 is a different HTTP status from a 301 even without a schedule.
First-login redirects
Enable Only apply on first login to use a rule as a one-time destination for a user's first detected login.
The plugin records login state in WordPress user metadata. When a qualifying user logs in, the first enabled and unexpired first-login rule is applied once and then marked as completed for that user. Tracking begins after the plugin is activated, so the first login detected by this plugin is treated as the user's first login for this feature.
First-login rules can be useful for sending a new user to an onboarding page, account instructions or another administrator-selected destination. They do not replace WordPress role and capability controls.
Settings export and import
The Export / Import screen can download this plugin's redirect rules as a JSON settings file and restore a compatible FFAS Redirection Manager settings file on another site. Review imported destinations before using them on a production website.
The plugin stores its rules in the WordPress database. It does not write redirect rules, robots.txt or LLMS.txt files into the WordPress installation directory.
Use 301 for a permanent move. Use 302 when the redirect is temporary or should expire.
Yes. Values such as /old-page and /new-page are converted to URLs on the current site. Complete URLs are also supported.
Yes. An administrator can enter a complete external destination URL. Only trusted administrators with the manage_options capability can create or change rules.
The end date stops a 302 rule at the selected site-local date and time. The optional start date postpones when it begins. End must be later than start. Permanent 301 rules do not use either date field.
The plugin tracks whether the user has a pending first detected login and records when a first-login rule has been used. The rule is then skipped for that user on later logins.
No. Redirect rules and login tracking data are stored through WordPress options and user metadata.
The current release retains its saved rules and login-tracking metadata to avoid destructive data loss.