####WARNING: This latest version is not live yet. Use with caution!
404 to 301 - No more 404 errors!
Automatically redirect all 404 errors to any page using 301 redirect to boost your SEO in WordPress. This plugin also can log all 404 erros and list it to you. Also you can optionally get email alerts on 404 errors!
Requires at least: WordPress 3.0
Tested up to: WordPress 4.9
Stable tag: 3.0.1
Before starting development make sure you read and understand everything in this README.
Also, don't forget to document your code properly.
Working with Git
Clone the plugin repo and checkout the
# git clone email@example.com:Joel-James/404-to-301.git # git fetch && git checkout dev
Installing dependencies and initial configuration
# curl -sL https://deb.nodesource.com/setup_10.x | sudo -E bash - # sudo apt-get install -y nodejs build-essential
Install the necessary npm modules and packages
# npm install
After that for the first time, run below command to create updated assets.
# npm run compile
Set up username and email for Git commits
# git config user.email "<your email>" # git config user.name "<your name>"
Build tasks (npm)
Everything (except unit tests) should be handled by npm. Note that you don't need to interact with Grunt in a direct way.
||Build pot and mo file inside /languages/ folder|
||Build release version, useful to provide for testing|
Follow semantic versioning http://semver.org/ as
package.json won't work otherwise. That's it:
X.X.0for mayor versions
X.X.Xfor minor versions
X.X[.X||.0]-rc.1for release candidates
Do not commit on
master branch (if you are on a forked repo, no need to worry).
dev is the code
that accumulates all the code for the next version.
- Create a new branch from
git checkout -b branch-name origin/dev. Try to give it a descriptive name. For example:
release/X.X.Xfor next releases
new/some-featurefor new features
fix/some-bugfor bug fixing
- Make your commits and push the new branch:
git push -u origin branch-name
- File the new Pull Request against
- Once the PR is approved it will be merged to the
If you are sending pull requests from your forked repo, follow the same steps.