Third party modules

We can vouch for the security of the code that we write in the ProcessWire core, but we can't vouch for the security of third party modules. Follow these guidelines to maximize your security with third party modules.

ProcessWire doesn't require any third party modules in order to run and accomplish most tasks, so use care in deciding which third party modules to install.

  • Install only those modules that solve an important need for your site. The fewer 3rd party modules you have installed, the less to keep track of and fewer developers you are dependent upon.

  • Verify that the module is still actively supported by developer in the ProcessWire support boards.

  • Keep third party modules up-to-date (the ProcessWireUpgrade module is a good way to track versions).

  • Uninstall and erase any 3rd party modules that you have installed but are not using.

Twitter updates

  • This week we’ve got a couple of really useful API-side improvements to the core in 3.0.151, including predefined image settings and static language translation improvements— More
    21 February 2020
  • New post in the blog about all the fun we had driving around a DDOS attack on our forums, how we got it back under control, and what we learned along the way. Plus PW 3.0.150 dev details and links! More
    7 February 2020
  • New post: ProcessWire core updates (January 31, 2020)— More
    31 January 2020

Latest news

  • ProcessWire Weekly #301
    In the 301st issue of ProcessWire Weekly we're going to check out the latest core updates, introduce brand new third party modules RockDaterange and Modules Manager 2, and highlight a brilliant new site of the week. Read on!
    Weekly.pw / 15 February 2020
  • ProcessWire 3.0.151 core updates
    Blog / 21 February 2020
  • Subscribe to weekly ProcessWire news

I just love the easy and intuitive ProcessWire API. ProcessWire rocks!” —Jens Martsch, Web developer