This documentation details the workflow for ProcessWire sites.

1. Installation
2. Local Development
3. Upgrading
4. Troubleshooting
5. Support

• ProcessWire
• About ProcessWire
• Support forums
• Documentation
• API reference
• Downloads
• Modules/plugins
• Showcase

Install the LTS Version of node.js and npm

sudo apt install nodejs npm

Navigate to installation directory folder and execute the installer within the folder.

npx pw-installer

1. Install Local WP
2. Create a new site from a blueprint or blank template
3. Open site folder, and delete the Wordpress installation
4. Run the installation CLI command in the app/public directory npx pw-installer
5. Open the site and complete the ProcessWire install.

You can use hot reload to automatically reload the browser when you make changes to your files. This is done by using a proxy server that watches for changes in your files and reloads the browser when a change is detected. This is useful for development, but not recommended for production.

To enable hot reload, install the templates dependencies with node package manager (npm).

npm install

Then run the hot reload command

npm run hot

This will start the proxy server and open the browser. You can now make changes to your files and the browser will automatically reload when a change is detected. This will not reload the domain set in Local WP, so you will need to manually refresh the browser.

First install Lando & Docker API reference so that you can create the LAMP stack container. From the root of the project public/ run the command lando start to initialize the docker container & image or to start an existing docker instance.

Upgrading is easy and usually just a matter of replacing your /wire/ directory with the one from the new version. But to be safe, before proceeding with any version upgrade, please see the Upgrading ProcessWire guide and perhaps keep it open during your upgrade in case you need to refer back to it.

When upgrading from one 3.x version to another, please use the general upgrade process. This consists primarily of making sure you've got everything backed up and then just replacing your /wire/ directory with the one from the newer version.

• If you are upgrading from a 3.x version prior to 3.0.135 then please also follow these instructions.

• If you are upgrading from any 2.x version then please see upgrading from ProcessWire 2.x.

• If you run into any trouble upgrading, please see our troubleshooting upgrades guide.

• FormBuilder version 0.5.3 or newer recommended.

• ListerPro version 1.1.5 or newer recommended.

• ProFields the latest versions of all ProFields (10 modules) are recommended.

• LoginRegisterPro version 7 or newer recommended.

• ProCache version 4.0.3 or newer recommended. After upgrading, go to your ProCache settings in the admin (Setup > ProCache) and see if it suggests any modifications to your .htaccess file.

• For all other Pro modules not mentioned above we recommend using the latest available versions when possible.

Debug mode causes all errors to be reported to the screen. This can be helpful during development or troubleshooting. When in the admin, it also enables a “Debug” link (see footer) for reporting of extra information in a panel. Debug mode is not intended for live or production sites, as the information reported is for the developer only. Do not leave debug mode on for any live/production sites, as it could be a security concern. However, we think you'll find it very handy during development or when resolving issues.

1. Edit this file: /site/config.php
2. Find this line: $config->debug = false;
3. Change the false to true like below, and save.

$config->debug = true; 

This can be found near the bottom of the file, or you can add it if not already there. It will make PHP and ProcessWire report all errors, warnings, notices, etc. Of course, you'll want to set it back to false once you've resolved any issues.

• ProcessWire Support Forums
• ProcessWire Weekly News
• ProcessWire Blog
• Sites running ProcessWire
• Subscribe to ProcessWire Weekly email
• Submit your site to our directory
• Follow @processwire on X-Twitter
• Contact ProcessWire developer
• Report issue