-
☆ A M B ☆
- 66 Posts
Update
Used my backups to downgrade back to 2.2.14 and everything is working the way it did before.
Will build up a new site from a fresh 2.3.1 install and copy over the content...
-
☆ A M B ☆
- 66 Posts
Still having this problem with context menu disappearing...
Check screenshot
How can I solve this?
this is the only thing showing in the error logs:
[2014-10-14 20:46:52] (ERROR @ /manager/index.php) Could not find action file at: /home1/thijsvan/public_html/best/manager/controllers/default/system/context
-
☆ A M B ☆
- 24,524 Posts
For 2.3.1, it's /manager/controllers/default/context/.
Have you cleared your browser cache and cookies for the domain? Sometimes an upgrade can cause a problem if the browser has cached the original .js files and doesn't even look at the new ones.
Hi,
I have tried all suggestions in this thread so far and still see no menu item for context. Requesting /manager/?a=context returns a white page with an access denied message.
An other MODX installation on the same server comes with context menu. The only difference between the two installations I can think of is: the MODX version of the initial installation. Now they both are on 2.3.3 though. So I suspect the problem has something to do with the installation's history...
Thijs Van Damme, do you have a solution to this?
Thx
When you upgraded, did you transfer the new files individually with FTP? That often results in missing or corrupted files. Also, the new files sometimes don't overwrite the old ones.
See if there is an index.class.php file in this directory:
manager/controllers/default/system/context/
If there is one, take a look at it an make sure it's not truncated.
UPDATE:
If I check Sudo User in the user settings (Manage > Users > ...) the menu entry for contexts shows up (Tools > Contexts). So I have to be a sudo user to manage contexts. Is this wanted by the MODX developers or is it a bug or bad configuration of my installations? Can someone please confirm to have access to manage contexts without being sudo user? Thx
What's the Policy for your user's User Group? Is it by chance Content Editor? That would explain the problem.
To see the Context menu item, you need view_context permission. To actually edit, create, save, or delete a context, you need the other context-related permissions.
You'll need to either edit the current policy to add those permissions, or change to a Policy that has them checked.
Hi BobRay, thanks for your reply.
It's the default admin user:
- User Group: Administrator
- Access Policy: Administrator
- Active Permissions: 172 of 172
The Contexts menu item only shows up if I check Sudo User...
-
☆ A M B ☆
- 24,524 Posts
Verified. Create a user, assign him to the Administrator group, and he doesn't get the Contexts menu item. This is in a build of yesterday's Develop branch, by the way.
No problem editing a context from the Tree.