{"id":27617706,"url":"https://github.com/plsr/processwire","last_synced_at":"2025-04-23T04:17:24.854Z","repository":{"id":22398842,"uuid":"25735928","full_name":"Plsr/processwire","owner":"Plsr","description":"Giving processwire a try","archived":false,"fork":false,"pushed_at":"2014-10-26T19:06:42.000Z","size":13952,"stargazers_count":0,"open_issues_count":0,"forks_count":0,"subscribers_count":2,"default_branch":"master","last_synced_at":"2025-04-23T04:17:18.847Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":null,"language":"PHP","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"gpl-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/Plsr.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE.txt","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2014-10-25T15:26:59.000Z","updated_at":"2014-10-25T15:29:52.000Z","dependencies_parsed_at":"2022-08-20T12:20:51.327Z","dependency_job_id":null,"html_url":"https://github.com/Plsr/processwire","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Plsr%2Fprocesswire","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Plsr%2Fprocesswire/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Plsr%2Fprocesswire/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/Plsr%2Fprocesswire/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/Plsr","download_url":"https://codeload.github.com/Plsr/processwire/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":250366716,"owners_count":21418772,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2025-04-23T04:17:24.263Z","updated_at":"2025-04-23T04:17:24.842Z","avatar_url":"https://github.com/Plsr.png","language":"PHP","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Welcome to ProcessWire 2.5\n\nThis document is in Markdown. An HTML formatted version of this document \ncan be read at: http://processwire.com/download/readme\n\n## Table of Contents\n\n1. [About ProcessWire](#about-processwire)\n2. [Installing ProcessWire](#installation)\n   - [Requirements](#requirements)\n   - [Installation from ZIP file](#installation-from-zip-file)\n   - [Installation from GitHub](#installation-from-github)\n   - [Troubleshooting Installation](#troubleshooting-installation)\n       - [The homepage works but nothing else does](#the-homepage-works-but-nothing-else-does)\n       - [Resolving an Apache 500 error](#resolving-an-apache-500-error)\n       - [Resolving other error messages or a blank screen](#resolving-other-error-messages-or-a-blank-screen)\n3. [Upgrading ProcessWire](#upgrades)\n   - [Best Practices Before Upgrading](#best-practices-before-upgrading)\n   - [General Upgrade Process](#general-upgrade-process)\n       - [Replacing the /wire/ directory](#replacing-the-wire-directory)\n       - [Replacing the /index.php file](#replacing-the-indexphp-file)\n       - [Replacing the .htaccess file](#replacing-the-htaccess-file)\n       - [Additional upgrade notes](#additional-upgrade-notes)\n   - [Upgrading from ProcessWire 2.4](#upgrading-from-processwire-24)\n   - [Upgrading from ProcessWire 2.2 or 2.3](#upgrading-from-processwire-22-or-23)\n   - [Upgrading from ProcessWire 2.1](#upgrading-from-processwire-21)\n   - [Upgrading from ProcessWire 2.0](#upgrading-from-processwire-20)\n   - [Troubleshooting an Upgrade](#troubleshooting-an-upgrade)\n4. [Debug Mode](#debug-mode)\n5. [Support](#support)\n\n## About ProcessWire\n\nProcessWire is an open source content management system (CMS) and web \napplication framework aimed at the needs of designers, developers and their \nclients. ProcessWire gives you more control over your fields, templates and \nmarkup than other platforms, and provides a powerful template system that \nworks the way you do. Not to mention, ProcessWire's API makes working with \nyour content easy and enjoyable. Managing and developing a site in \nProcessWire is shockingly simple compared to what you may be used to.\n\n* [Learn more about ProcessWire](http://processwire.com)\n* [Download the latest ProcessWire](http://processwire.com/download/)\n* [Get support for ProcessWire](http://processwire.com/talk/)\n* [Browse and install ProcessWire modules/plugins](http://modules.processwire.com)\n* [Follow @ProcessWire on Twitter](http://twitter.com/processwire/)\n* [Contact ProcessWire](http://processwire.com/contact/)\n\n\n## Installation\n\n### Requirements\n\n* A web server running Apache. \n* PHP version 5.3.8 or newer.\n* MySQL 5.0.15 or newer.\n* Apache must have mod_rewrite enabled. \n* Apache must support .htaccess files. \n\n\n### Installation from ZIP file\n\n1. Unzip the ProcessWire installation file to the location where you want it\n   installed on your web server. \n\n2. Load the location that you unzipped (or uploaded) the files to in your web\n   browser. This will initiate the ProcessWire installer. The installer will\n   guide you through the rest of the installation.\n\n\n### Installation from GitHub\n\nGit clone ProcessWire to the place where you want to install it:\n\n```\ngit clone https://github.com/ryancramerdesign/ProcessWire \n```\n\nLoad the location where you installed ProcessWire into your browser. \nThis will initiate the ProcessWire installer. The installer will guide\nyou through the rest of the installation.  \n\n\n### Troubleshooting Installation\n\n#### The homepage works but nothing else does\n\nThis indicates that Apache is not properly reading your .htaccess file. \nFirst we need to determine if Apache is reading your .htacess file at all.\nTo do this, open the .htaccess file in an editor and type in some random\ncharacters at the top, like `lkjalefkjalkef` and save. Load your site in \nyour browser. You should get a \"500 Error\". If you do not, that means \nApache is not reading your .htaccess file at all. If this is your case,\ncontact your web host for further assistance. Or if maintaining your own\nserver, look into the Apache *AllowOverride* directive which you may need\nto configure for the account in your httpd.conf file. \n\nIf the above test did result in a 500 error, then that is good because we\nknow your .htaccess file is at least being used. Go ahead and remove the \nrandom characters you added at the top. Now look further down in the \n.htaccess file for suggested changes. Specially, you will want to look at \nthe *RewriteBase* directive, which is commented out (disabled) by default. \nYou may need to enable it.\n\n#### Resolving an Apache 500 error\n\nThe presence of an Apache 500 error indicates that Apache does not\nlike one or more of the directives in the .htaccess file. Open the\n.htaccess file in an editor and read the comments. Note those that \nindicate the term \"500 NOTE\" and they will provide further instructions\non optional directives you can try to comment out. Test one at a time,\nsave and reload in your browser till you determine which directive is\nnot working with your server.\n\n#### Resolving other error messages or a blank screen\n\nIf you are getting an error message, a blank screen, or something\nelse unexpected, see the section at the end of this document on \nenabling debug mode. This will enable more detailed error reporting\nwhich may help to resolve any issues. \n\nIn addition, the ProcessWire error log is located in the file:\n/site/assets/logs/errors.txt - look in here to see if more information\nis available about the error message you have received. \n\nIf the above suggestions do not help you to resolve the installation\nerror, please post in the [ProcessWire forums](http://processwire.com/talk). \n\n\n## Upgrades\n\n### Best Practices Before Upgrading\n\n1. Backup your database and backup all the files in your site.\n2. When possible, test the upgrade on a development/staging site \n   before performing the upgrade on a live/production site. \n3. If you have 3rd party modules installed, confirm that they are \n   compatible with the ProcessWire version you are upgrading to. \n   If you cannot confirm compatibility, uninstall the 3rd party \n   modules before upgrading, when possible. You can attempt to\n   re-install them after upgrading. If uninstalling is \n   inconvenient, just be sure you have the ability to revert if for \n   some reason one of your modules does not like the upgrade.\n   Modules that are compatible with ProcessWire 2.4 are generally\n   going to also be compatible with 2.5. \n\nIf you prefer an automatic/web-based upgrade, an\n[upgrade module](https://github.com/ryancramerdesign/ProcessWireUpgrade)\nis available for upgrading to 2.5. \n\n\n### General Upgrade Process\n\nUpgrading from one version of ProcessWire to another is a matter of \ndeleting these files/directories from your old version, and putting \nin fresh copies from the new version:  \n\n```\n/wire/\n/index.php\n/.htaccess \n```\n\nDeleting and replacing the above directory/files is typically the \nprimary thing you need to do in order to upgrade. But please see \nthe version-to-version specific upgrade notes documented further \nin this section. Below are more details about how you should \nreplace the files mentioned above.\n\n*NOTE: Renaming is an alternative to deleting, which gives you a quicker \npath to revert should you want to. For example, you might rename\nyour /wire/ directory to be /.wire-2.4.0/ with \".wire\" rather than \n\"wire\" to ensure the directory is hidden, and the 2.4.0 indicating the \nversion that it was. Once your upgrade is safely in place, you could \ndelete that .wire-2.4.0 directory (or keep it around).*\n\n\n#### Replacing the /wire/ directory\n\nWhen you put in the new /wire/ directory, make sure that you remove or \nrename the old one first. If you just copy or FTP changed files into\nthe existing /wire/ directory, you will end up with both old and new\nfiles, which will cause an error. \n\nNote that the /wire/ directory does not contain any files specific to \nyour site, only to ProcessWire. All the files specific to your site \nare stored in /site/ and you would leave that directory alone during \nan upgrade. \n\n\n#### Replacing the /index.php file\n\nThis file doesn't change often between minor versions. As a result,\nyou don't need to replace this file unless it has changed. But when\nin doubt, you should replace it. \n\n\n#### Replacing the .htaccess file\n\nThis is also a file that does not always change between versions.\nBut when it changes, it is usually important for security that you \nare up-to-date. When in doubt, replace your old .htaccess file with\nthe htaccess.txt from the new version. \n\nThis file is initially named htaccess.txt in the ProcessWire source.\nYou will want to remove your existing .htaccess file and rename the\nnew htaccess.txt to .htaccess\n\nSometimes people have made changes to the .htaccess file. If this is\nthe case for your site, remember to migrate those changes to the new\n.htaccess file. \n\n\n#### Additional upgrade notes\n\n- If using Form Builder make sure you have the latest version,\n  as past versions did not support ProcessWire 2.4/2.5. \n\n- If using ProCache you will need to go to the ProCache\n  settings after the upgrade to have it update your .htaccess file\n  again (since it was presumably replaced during the upgrade). \n\n- After completing the upgrade test out your site thoroughly\n  to make sure everything continues to work as you expect. \n\n- ProcessWire 2.4/2.5 come with new admin themes. After completing\n  your upgrade, you may install or configure these admin themes. \n\n\n### Upgrading from ProcessWire 2.4\n\nThe general upgrade process may be followed to perform this upgrade.\nIn addition, please note the following:\n\n- **New .htaccess and index.php files**    \n  While not urgent, you *will* want to replace your [.htaccess](#replacing-the-htaccess-file)\n  and [index.php](#replacing-the-indexphp-file) files as part of the upgrade. \n  If you have modified either of those files, it's okay to leave them in \n  place temporarily, as you can still use ProcessWire 2.5 with the old \n  .htaccess and index.php files in place. But we recommend updating them\n  when you can. \n  \n- **Does your site depend on other sites loading it in an iframe?**  \n  Related to the above point, the new .htaccess file contains an option\n  that you will need to disable if your site relies upon other sites\n  loading yours in an `\u003ciframe\u003e`. If this is your case, please delete or \n  comment out this line in your .htaccess file:   \n  `Header always append X-Frame-Options SAMEORIGIN`\n\n- **TinyMCE rich text editor was replaced with CKEditor**    \n  2.5 drops TinyMCE as the rich text editor and replaces it with \n  CKEditor. After installation of 2.5, you will see an error message\n  on any pages that use TinyMCE. From this point, you may either \n  [install TinyMCE](mods.pw/7H) or switch your fields using TinyMCE\n  to CKEditor. To switch to CKEditor, go to Setup \u003e Fields \u003e [field] \u003e Details,\n  and change the *Inputfield Type* to CKEditor (it may already be\n  selected), then be sure to Save. \n  \n- **Already have CKEditor or HTML Purifier installed?**   \n  A couple of modules that were previously 3rd party (site) modules \n  are now core (wire) modules in ProcessWire 2.5. If you have either\n  the *InputfieldCKEditor* or *MarkupHTMLPurifier* modules installed,\n  you will get warnings about that after upgrading. The warnings will \n  tell you to remove the dirs/files for those modules that you have in \n  /site/modules/. Don't be alarmed, as this is not an error, just a \n  warning notice. But it is a good idea to remove duplicate copies \n  of these modules when possible. \n\n\n### Upgrading from ProcessWire 2.2 or 2.3\n\nProcessWire 2.4 and 2.5 have two new software requirements: \n\n- PHP 5.3.8+ (older versions supported PHP 5.2)\n- PDO database driver (older versions only used mysqli)\n\nPlease confirm your server meets these requirements before upgrading.\nIf you are not certain, paste the following into a test PHP file and \nload it from your browser:\n\n```\n\u003c?php phpinfo();\n```\n\nThis will show your PHP configuration. The PHP version should show \nPHP 5.3.8 or newer and there should be a distinct PDO section \n(header and information) present in the output. \n\n**To proceed with the upgrade** follow the [general upgrade process](#general-upgrade-process)\nabove. You *will* want to replace your index.php and .htaccess \nfiles as well.\n\n**In addition** we recommend adding the following line to your \n/site/config.php: \n```\n$config-\u003ehttpHosts = array('domain.com', 'www.domain.com'); \n```\nReplace domain.com with the hostname(s) your site runs from.\n\n\n### Upgrading from ProcessWire 2.1\n\n1. First upgrade to [ProcessWire 2.2](https://github.com/ryancramerdesign/ProcessWire/tree/2.2.9).\n2. Follow the instructions above to upgrade from ProcessWire 2.2.\n\n\n### Upgrading from ProcessWire 2.0\n\n1. [Download ProcessWire 2.2](https://github.com/ryancramerdesign/ProcessWire/tree/2.2.9) \n   and follow the upgrade instructions in that version's [README](https://github.com/ryancramerdesign/ProcessWire/blob/2.2.9/README.txt) \n   file to upgrade from 2.0 to 2.2. \n2. After successfully upgrading to 2.2, follow the general upgrade \n   process above.\n\n\n### Troubleshooting an Upgrade\n\nIf you get an error message when loading your site after an upgrade,\nhit \"reload\" in your browser once before doing anything else. If the error\nis now gone, the error was normal and your upgrade was successful. \n\nIf your site is not working after performing an upgrade, clear your\nmodules cache. You can do this by removing all of these files:\n/site/assets/cache/Modules.*\n\nIf using Form Builder, make sure you have version 0.2.2 or newer, as older\nversions did not support ProcessWire 2.4/2.5+. \n\nIf your site still doesn't work, remove the /wire/ directory completely. \nThen upload a fresh copy of the /wire/ directory. \n\nIf your site still doesn't work, view the latest entries in your error\nlog file to see if it clarifies anything. The error log can be found in:\n/site/assets/logs/errors.txt\n\nIf your site still doesn't work, please post in the\n[ProcessWire support forums](http://processwire.com/talk/). \n\n\n## Debug Mode\n\nDebug mode causes all errors to be reported to the screen, which can be\nhelpful during development or troubleshooting. When in the admin, it also\nenables reporting of extra information in the footer. Debug mode is not\nintended for live or production sites, as the information reported could\nbe a problem for security. So be sure not to leave debug mode on for\nany live/production sites. \n\n1. Edit this file: `/site/config.php`\n2. Find this line: `$config-\u003edebug = false;` \n3. Change the `false` to `true`, like below, and save. \n\n```\n$config-\u003edebug = true; \n```\n\nThis can be found near the bottom of the file, or you can add it if not\nalready there. It will make PHP and ProcessWire report all errors, warnings,\nnotices, etc. Of course, you'll want to set it back to false once you've \nresolved any issues. \n\n\n## Support\n\nGet support in the ProcessWire forum at:\n[http://processwire.com/talk/](http://processwire.com/talk/)\n\n------\n\nProcessWire, Copyright 2014 by Ryan Cramer Design, LLC\n\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fplsr%2Fprocesswire","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fplsr%2Fprocesswire","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fplsr%2Fprocesswire/lists"}