- Reuse reduces risk
- Add limitations
- Change adds time
Validate on submit:
- https://johnnycode.com/2014/03/27/using-jquery-validate-plugin-html5-data-attribute-rules/
- https://jqueryvalidation.org/validate/#highlight
- https://jqueryvalidation.org/reference/#link-markup-recommendations
- https://stackoverflow.com/questions/14962973/validation-rules-applied-to-all-elements#24812910
- https://jqueryvalidation.org/validate/#errorplacement
- https://stackoverflow.com/a/15195924/6850747
If you forget to create a development branch before developing, then need to patch master:
- Create a branch from the last commit
- Stash any uncommitted changes
- Reset the master branch to the last tagged release (or whenever)
git push -f [email protected]:dotherightthing/reponame.git
If you try to do (4) via SourceTree then Github will complain that "github Updates were rejected because a pushed branch tip is behind its remote"
- This is not possible using UpdraftPlus.
- Go into SequelPro, locate the tables used by the subsite, Export as SQL
- Open the SQL file in a text editor
- Find & Replace the table prefix as necessary, to match the single site's wp-config (
$table_prefix
) - Create a new WordPress site for the standalone single site
- Go into SequelPro, File > Import: The SQL file
- Also in SequelPro, under the “option_name” column header, change “wp_user_roles” to “YOUR_PREFIX_user_roles“. This fixes the error "Sorry, you are not allowed to access this page" when you visist /wp-admin (https://www.naijatechzone.com/wp-admin-login-error-sorry-you-are-not-allowed-to-access-this-page/)
- Use https://interconnectit.com/products/search-and-replace-for-wordpress-databases/ to replace
YOUR_OLD_DOMAIN_NAME
withYOUR_NEW_DOMAIN_NAME