Before Reporting a Bug
- Have you read the FAQ?
- Have you tried disabling all other plugins on your site? A lot of problems are caused by other plugins misbehaving
- Have you tried clearing your browser cache? If you are using Cloudflare or an equivalent caching service then please also try clearing your page cache
- Take a look at the WordPress.org forum to see if others have the same problem
- Take a look in the Github repository to see if a similar problem has been reported
Reporting a Bug
If you’ve made it through all those steps (and my apologies for having so many) you can create a bug report in the Github repository. Click the green New Issue button.
If Redirection is displaying an error message then please report the bug through Redirection itself – this will include additional details.
Be aware that your details will be public. If you do not want this then report the bug directly.
Reporting a Bug Directly
If you wish to report a bug directly to me use the contact form on this site, or use the email option on the Support page of the plugin.
Please include these details in any bug report:
- Your WordPress, PHP, and plugin version
- A description of what you are trying to do
- A real example, hopefully with something I can actually see and test. For example, a URL that isn’t working
- A screenshot demonstrating the problem
Generally a bug can be identified from this information alone, but sometimes I may need more details. Also, sometimes it helps to have access to your site, so if you are able to provide a login when asked it is a big help. Don’t worry if you don’t want to provide this though.
Using Browser Developer Tools
Sometimes it can help to see what requests your browser is making. Most browsers have a set of developer tools that you can enable. For example, on Chrome it is accessible from View > Developer > Developer Tools.
Once enabled you should see a window appear. If you click the ‘network’ tab you can see any requests your browser makes:
With this window open if you reload your page in Redirection you should see a lot of requests. Anything in red is an error, and clicking this will show information:
This information can be very useful.
Sometimes the only way to debug a problem is by having access to the server on which it is running. There are two kinds of access:
- A WordPress admin login – create a new admin account and share the username and password
- Direct file system access. Usually via FTP/SFTP
I appreciate that some sites are live and you may not want to give access. That’s perfectly fine. If you are ok providing access then a WordPress login is the usual place to start, and a lot of problems can be solved this way.
If the problem requires further debugging then access to the file system access may be required. This can either be via FTP/SFTP or SSH.