Jump to content

pmichaelis

Members
  • Posts

    73
  • Joined

  • Last visited

Everything posted by pmichaelis

  1. Hey everybody, I think the permission to manage files is missing in the module config. I added this line in "getModuleInfo" order to grant access for non-admin users: 'permission' => 'manage-files',
  2. Hey totoff, thanks for your fast reply on that. Do you mean it's a user problem, because the files belong not to the "www-data" user?
  3. Hello Everybody, after I moved to a new server yesterday, processwire always logs me out of the admin page. If i click on an menu item in the backend sometimes it takes me to the clicked page, sometimes I get redirected to the login page. Does this has anything to with the session handling? I think after the migration something is wrong with the file permissions. I deleted the old session files. After that I wanted to delete the AIOM cache, but that throws the error below: Error: Exception: The permissions (chmod) to delete old cache files could not be changed. (in /var/www/public/site/modules/ProcessWire-AIOM-All-In-One-Minify-AIOM-/AllInOneMinify.module line 646) #0 /var/www/public/site/modules/ProcessWire-AIOM-All-In-One-Minify-AIOM-/AllInOneMinify.module(837): AllInOneMinify::_clearCache(true) #1 /var/www/public/wire/core/Wire.php(411): AllInOneMinify::ClearCacheFromBackend(Object(HookEvent)) #2 /var/www/public/wire/core/Wire.php(344): Wire->runHooks('render', Array) #3 /var/www/public/wire/modules/Process/ProcessPageView.module(171): Wire->__call('render', Array) #4 /var/www/public/wire/modules/Process/ProcessPageView.module(171): Page->render() #5 [internal function]: ProcessPageView->___execute(true) the asstes directory has a 755 permission, aswell as the sessions, aiom and cache directory Thanks for any hints on that topic!
  4. Yep, you are right. I didn't have this problem before. Maybe it occurs rarely. Anyway, thanks for helping.
  5. The "session.save_handler" was set to "user", but must be set to "files". DONE Many thanks for help!
  6. Hello SiNNuT, thanks for your quick reply! I removed the install.php manually after the installation process, but the error still exsists. Do you mean it might be a good idea to check if there are some old files with the same name (install.php) located anywhere else? I havo no clue ...
  7. Hey Everybody, As I was trying to move an exsisting site form my local dev (xampp) to a production server, the following error appeared: Error: session_start(): Failed to initialize storage module: user (path: /usr/local/www/services/.../data/tmp) (line 103 of /home/.../html/wire/core/Session.php) This error message was shown because /install.php still exists. Error has been logged. I searched the forum for help, but the only related topic I could find is this one: Problems with ProcessWire on Cloud Hosting https://processwire.com/talk/topic/5089-problems-with-processwire-on-cloud-hosting/ The thread says, that it might have something to do with some isses in the master branch of pw. So I downloaded the dev branch (2.4), and made a fresh install. There are no problems with the requirements, nor with mod_rewrite. In the last installation step, after the admin user creation the error message from above appears again. Is it usual, that pw creates a tmp/data diretory? I changed the file permissions for the assets and changed the htaccess, but still there is no change. Thanks for any hints on that. And thnaks for that lovely CMS
×
×
  • Create New...