Crafting Web Experiences
//
Dockerfile: NGINX default.conf:
Wuxt – https://github.com/northosts/wuxt
To increase the memory limit on WordPress, add these configurations into the wp-config.php file:
Be careful, this might cause caching issues on your site. If you have a proxy caching system set up, your changes on your assets may not be reflected to the site.
Reference: https://developer.wordpress.org/cli/commands/config/create/
It will be enough running this once.
For testing/staging purposes, sometimes you need to create new block or content based pages before taking them fully live. To check or show them without making them publicly visible to visitors, you can add “stage-” prefix to that new private pages with the hook below. When you’re logged in, you’re automatically redirected to the new…
# Download using curl # Give the execution permissions # Install WordPress Coding Standards # Apply the new coding standards # Update the default standard # Install the VS Code Extension PHP Sniffer & Beautifier: https://marketplace.visualstudio.com/items?itemName=ValeryanM.vscode-phpsab # Add these settings to the settings.json file of VS Code
You need to install WP-ENV globally or project based first. Then, create a “.wp-env.json” file to the root folder which has “wp-content” folder in it. .wp-env.json: (Most optimized config, here for details) To Run Server: (might take long at first) To Import Existing DB: To Export DB: Rewrite Flush: (Not working. Enter Settings > Permalinks…
If you want to completely disable the trash: If you want trash to be emptied in 30 days:
In some cases, you might need to clone a multisite for testing or staging purposes, but you might want to use the same database on both clone and production websites. This can be needed not to deal with data synchronization between staging and production sites when it’s ready to take the changes live. It’s especially…
Another method for multiple plugin entries:
Also, to exclude these pages and categories from the site: