More File Manager problems: empty "File" listing page
Posted: Fri Nov 09, 2007 8:58 pm
CMSMS 1.2
FileManager 0.2.0
something has broken in this version of either CMSMS or FileManager but I'm having all sorts of issues.
First of all, when I open a page in editor and select some text and then click on "Insert/Edit Link" I am taken to the Link window, when I then click on "Browse" I'm taken to the Resources Browser where the default view is of the File Resource Type. but the problem is this page is empty even though I have 30 or more files in the /uploads/File directory. What gives with this?.
When I change my User Preferences to TinyMCE editor, all my files in File show up. So it sure seems like FCKEditor X is screwed up somewhere... or maybe I'm screwed up somewhere, but something ain't right.
I'm also noticing that uploads are now being given 777 permissions which is crazy. umask is set to 022 and testing reveals
read,write
read
read
config.php has this set...$config['default_upload_permission'] = '664';
So how I can end up with uploaded files with permissions of 777 is beyond me. Anyone have any ideas?
Something is really amiss with this version.
FileManager 0.2.0
something has broken in this version of either CMSMS or FileManager but I'm having all sorts of issues.
First of all, when I open a page in editor and select some text and then click on "Insert/Edit Link" I am taken to the Link window, when I then click on "Browse" I'm taken to the Resources Browser where the default view is of the File Resource Type. but the problem is this page is empty even though I have 30 or more files in the /uploads/File directory. What gives with this?.
When I change my User Preferences to TinyMCE editor, all my files in File show up. So it sure seems like FCKEditor X is screwed up somewhere... or maybe I'm screwed up somewhere, but something ain't right.
I'm also noticing that uploads are now being given 777 permissions which is crazy. umask is set to 022 and testing reveals
read,write
read
read
config.php has this set...$config['default_upload_permission'] = '664';
So how I can end up with uploaded files with permissions of 777 is beyond me. Anyone have any ideas?
Something is really amiss with this version.