this one is driving me nuts, I can't seem to give a content editor access to read/write files in my /assets/ directory! In fact only a sudo user can even see the assets directory from the modx browser.
What could be causing this??
- checked config.in.php = fine
- cleared cache multiple times including deleting the contents of the cache directory
- checked file system permissions and ownership 644/755/777 does not seem to matter
- does not seem to matter if the owner is apache or the web user
- on closer checking it just folders that don't show for the user, most files appear to be there.
- triple checked the content editor access policy ~ everything that says anything like "file" or "folder" is checked...
- the filesystem media source is "/" it's relative path is also "/"
Like I said only a sudo user seems to be able to see directories.
HELP!!
*** Not just websites, we also create signage, banners, print, trade show displays and more! ***
Sean Kimball CLP, CLS.
Technical Director / Sr. Developer | BigBlock Studios
._______________________________________________.
Bigblock Studios
http://www.bigblockstudios.ca Web site design & development.
27-1300 King Street East. Box 167 Oshawa, Ontario L1H8J4 Canada.
phone/fax: 905-426-5525
-
☆ A M B ☆
- 24,524 Posts
Ok, I created a user, not sudo, and assigned him to the Administrator group. He has no problem with the file browsers, including a Media Source as you described.
yea - I don't have ANY idea whats up with it now... logged in this morning and all the folders were visible!! ?
has to be cache.
*** Not just websites, we also create signage, banners, print, trade show displays and more! ***
Sean Kimball CLP, CLS.
Technical Director / Sr. Developer | BigBlock Studios
._______________________________________________.
Bigblock Studios
http://www.bigblockstudios.ca Web site design & development.
27-1300 King Street East. Box 167 Oshawa, Ontario L1H8J4 Canada.
phone/fax: 905-426-5525
-
☆ A M B ☆
- 24,524 Posts
Gremlins
sudo is confusing that way. For a sudo user, all permission checks are bypassed completely. When making someone a sudo user fixes things, it's tough to know whether it's a cache problem or a permission problem.
I always install CacheClear, which makes it much easier to delete all files in the core/cache directory (especially if the core is moved). If CacheClear doesn't fix things, you know it's not a MODX cache issue, though it can still be a browser cache issue.
