This forum has moved to a new location and is in read-only mode. Please visit talk.octobercms.com to access the new location.
Hello all,
While I was doing some maintenance on my website, I noticed I couldn't write any new files in the assets folder but I can still create folder as usual. I checked my ftp and all the folders ave the permission 777. It was working fine before and the only thing I changed was updating the CMS to the latest version.
The error message I get is this one: Error saving file 'random.css'. Please check write permissions.
Any idea?
Last updated
I'll add that I can create files everywhere else. Partials, Pages, Layouts etc... everything works but those damn files in the assets section.
edit: I can create files directly from the ftp, and then I can save them directly through the backend.
edit 2: I tried to rename the files I created from my ftp. I got this error code instead of the previous one: Error creating directory . Please check write permissions.
Last updated
You'll actually want the changes from https://github.com/octobercms/october/commit/3a1f547adb0bef8245691fc5df0612cf865d90d7 and https://github.com/octobercms/library/commit/5feb7b872f2ab4e1e09b7980b61b2d7048d3fc17 to fix the issue properly.
These will be included in the next build, Build 469
Heya,
I'm afraid I have to ask further, as with build 469 this does not work for me. Here's what I have tested so far:
- Setting the CHMOD in the cms.php to 777, 764, 744, 755 and 775 as well as "null" (according to the current cms.php in the master branch of the GitHub repo)
- Setting chmod on the assets-directory to anything from 744 to 777.
It is most certainly not a permissions issue. Furthermore I found out that the creation CHMOD 777 is hard-coded in the class, so I'm not sure if that's intended as well …?
This is happening both on a fresh wizard-install (about 4 weeks old) since the beginning as well as on an older but fully updated install (about 4 years old), before I began tampering with the configuration and directory permissions.
LukeTowers said:
Try updating to v1.1 via composer
I am still having this problem with build 469 and not sure how to update to v1.1 or even what needs updating. Any help very much appreciated
Try the composer install, that'll install 1.1 by default. Don't forget to set disableCoreUpdates
to true in config/cms.php
https://octobercms.com/docs/console/commands#console-install-composer
Unfortunately for one site I manage I do not have console access. Is there another fix for this?
-- oh, I found a solution -- just add files through FTP.
Last updated
LukeTowers said:
Try updating to v1.1 via composer
Can and should we update october via composer, when it was installed via web wizard?
See https://octobercms.com/docs/console/commands#console-install-composer on how to convert your wizard install of October to a Composer install instead.
Vladimir said:
https://github.com/octobercms/october/commit/b1954e92586f33a345068d56b957d7e366a5ba71
Dope. This worked perfectly. Use this guys. ^
<3 October. It's so fast! Just started my WP rebuild of my portfolio on this platform and it's a lot of work translating everything over but it's going good. Can't wait to incorporate Greensock into this build! :)
I'm going naked-jQuery.
Last updated
Glad to hear it! Would really just recommend switching to v1.1 with composer though, the fix was completely revised in 1.1.1 with the new PathResolver class and it's a lot better now.
1-15 of 15