Solution: /dashboard/files/access not loading.
Permalink
I have been having a problem with a client of mine for about a day, really about 12hrs of spare time. Initially I performed a few searches to see if anyone else was experiencing this problem and/or had a solution aside from reinstalling. Anyway, enough rambling.
This problem arose after a client of mine requested to have an employee perform modifications to the site. As a logic measure I created a group and added the new user, however I saw no settings to control "File Manager" access, so I assumed all was well. It wasn't whenever the user attempted to add any media to the site via the file manager he received the infamous "unable to access the file manager" message.
i performed an upgrade from version 5.3.3.1 to version 5.4.0.5 in an attempt to have the fine grain control functionality. However as the title suggests, the path for this functionality was blank. After some investigation and probing, I discovered it is caused by an invalid entry in the `Pages` table.
WARNING : This fix involves making modifications the the database in use by Concrete5. Be sure to perform a backup before making any changes. I accept no responsibility or liability, this is merely an effort to share what I have found.
By running the query it was revealed that the entry which should point to the 'access.php' was missing. After running the query it however showed that the path itself was defined.
With a little analysis and deductive reasoning i figured out that i could simply insert a value into the `Pages` table with information similar to the existing '/dashboard/files/*' pages.
My advice is to simply take the `cID` from the second query, locate the entry in the `Pages` table with the corresponding `cID`, and edit it. If it doesn't exist, create a new entry.
All the fields in the 'files/access' entry can be the same as other 'dashboard/files/' pages, with the exception of the `cID` being equal to what was found in the `PagePaths` table, and `cFilename` = '/dashboard/files/access.php
'.
For surety you can run to locate the bad entry. Be sure to replace ? with the `cID` from the `PagePaths` query.
In my case the culprit was `cID`='21' & `cFilename` = '0'. The correct value should have been `cFilenam`= '/dashboard/files/access.php'.
I hope this helps anyone who was having this problem, and if it is in the wrong place or was previously posted, please feel free to let me know.
This problem arose after a client of mine requested to have an employee perform modifications to the site. As a logic measure I created a group and added the new user, however I saw no settings to control "File Manager" access, so I assumed all was well. It wasn't whenever the user attempted to add any media to the site via the file manager he received the infamous "unable to access the file manager" message.
i performed an upgrade from version 5.3.3.1 to version 5.4.0.5 in an attempt to have the fine grain control functionality. However as the title suggests, the path for this functionality was blank. After some investigation and probing, I discovered it is caused by an invalid entry in the `Pages` table.
WARNING : This fix involves making modifications the the database in use by Concrete5. Be sure to perform a backup before making any changes. I accept no responsibility or liability, this is merely an effort to share what I have found.
By running the query
'SELECT * FROM `Pages` WHERE `cFilename` LIKE '%files%'
'SELECT * FROM `PagePaths` WHERE `cPath` LIKE '%file%access%'
With a little analysis and deductive reasoning i figured out that i could simply insert a value into the `Pages` table with information similar to the existing '/dashboard/files/*' pages.
My advice is to simply take the `cID` from the second query, locate the entry in the `Pages` table with the corresponding `cID`, and edit it. If it doesn't exist, create a new entry.
All the fields in the 'files/access' entry can be the same as other 'dashboard/files/' pages, with the exception of the `cID` being equal to what was found in the `PagePaths` table, and `cFilename` = '/dashboard/files/access.php
'.
For surety you can run
SELECT * FROM `Pages` WHERE `cID` = ?
In my case the culprit was `cID`='21' & `cFilename` = '0'. The correct value should have been `cFilenam`= '/dashboard/files/access.php'.
I hope this helps anyone who was having this problem, and if it is in the wrong place or was previously posted, please feel free to let me know.
