Jump to content

Search the Community

Showing results for tags 'centos'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Welcome to ProcessWire
    • News & Announcements
    • Showcase
    • Wishlist & Roadmap
  • Community Support
    • Getting Started
    • Tutorials
    • FAQs
    • General Support
    • API & Templates
    • Modules/Plugins
    • Themes and Profiles
    • Multi-Language Support
    • Security
    • Jobs
  • Off Topic
    • Pub
    • Dev Talk

Product Groups

  • Form Builder
  • ProFields
  • ProCache
  • ProMailer
  • Login Register Pro
  • ProDrafts
  • ListerPro
  • ProDevTools
  • Likes
  • Custom Development

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 2 results

  1. I have been able to easily install processwire in the past locally and on servers, but I recently added Vagrant to my development process, and I can't seem to get processwire installed correctly. Everything is right as far as the required components for the install. I go through ans rename the site-default to site and htacess.txt to .htaccess. Then I chmod /site/assets and /site/config.php to 777. Everything passes the check correctly, and then I enter the database info etc. There are no errors here. Everything looks like it gets installed correctly, but when I log in I get the "This request was aborted because it appears to be forged." error. I have come across this error before, and know how to fix it normally. I have confirmed that the sessions, cache, logs, files folders were created. I have even tried to chmod the whole site to 777, but nothing has worked. I have set $config->protectCSRF to false, and it gets rid of the error; however, it doesn't actually log me into the site but it redirects me back to the processwire login page with no errors and the form fields cleared. Any ideas?
  2. I've now twice noticed a problem after I deployed a version to a live server. For example the top buttons in Admin. Usually they are in the order: Pages Setup Modules Access Only when I pushed everyting (incl database export) live the order seems to have changed to Pages Modules Setup Access I also noticed a simple selector seems to ignore the sort I used, and used I think the ID for sorting. It was a critical moment so I quick-hacked a sort after the selector got it results, and thus was not able to get the source ot the problem. The production server uses CentOS with Php 5.2.17 and MySQL 5.0.51a Before I lose hours in debugging and testing, maybe anyone has noticed the same issues and already figured out what was wrong?
  • Create New...