Can't access my CP from backend, only akeeba backup & logout

[girbitte]

Hi,

I really need some help. I can't access my controlpanel from my backend. I have added a picture so you can have a look. I'm using 1.6.3. The site have no other users than super user, and it worked fine before my vacation(couple of weeks ago). The frontend is working.

So far I have tried this with no luck:
1. I have enabled plg_user_joomla in my database, actually all my plg_ are enabled. And also my administrator modules are enabled.
2. I have emptied my sessions table, cleared my cache and my cookies in my browser, but still no luck.
3. I added public $root_user='myusername'; in my configuration.php file (http://www.compassdesigns.net/joomla-bl ... permission)

UPDATE:

Thanks for your reply,

1. The user is assigned super users user group.
2. I have tried IE, Firefox and chrome = same problem in all of them.

I've been able to access the module administration page by entering the URL to the page. The problem seems to be that some modules in the administrator page is not showing even though they're enabled. I have problems with following modules:
- admin menu
- toolbar

When the toolbar is missing I'm also unable to do any changes since the buttons for apply and save is not showing as they are a part of the toolbar.

I uploaded some print screens so you can see my administrator modules, and when I log in.

Same problem still.


Regards,
Birgitte

[jen4web]

It looks to me like someone gave you a login but did not configure the ACL correctly.

You need to go back to your Joomla developer and ask them to configure your account correctly so you can work on the site.

If you don't have a Joomla developer, you need your super user login -- be sure to use that, and all options should appear.

If you don't have a super user login, and you don't have a Joomla developer, you need a way to access the database so you can change the super user credentials and get into the site. Usually you access the database through the control panel for your web hosting.

Good luck,
Jen

[SOAMJENA]

I might take a look, if you can send me the login details.

[zanderp]

Hi Birgitte,

Is the Super User group assigned to the "special" access level? You can check this via the database table #__viewlevels.

Sander

[Pjries]

Unfortunately, noticing the same thing in Joomla 1.7.0 after clicking email link to update to backup version 3.3.3. Not a critical site for me, fortunately, but would be happy to help troubleshoot this with that site.

ETA: this could be a Firefox 6 thing.. or maybe just a Firefox thing which may mean an AJAX or Javascript issue? I logged into my site in IE 9 (I know, but for testing purposes) and the control panel is visible and I can get around fine in the back end. Works fine in Chrome, as well.

Perhaps try another browser to gain access?

[girbitte]

Hi Birgitte,

Is the Super User group assigned to the "special" access level? You can check this via the database table #__viewlevels.

Sander

After a lot of trying I finally figured out what the problem is (I'm not that skilled with databases)

This is how my viewlevels looked like in my database:

viewlevels.jpg

So I changed the rules of the super user to this:

new viewlevels.jpg

And now everything works!!! I'm so revealed!

What exactly does the different rules mean? Maybe I should give super user all the rules?

[zanderp]

Hi Birgitte,

So I was indeed right with the access viewing levels.

The backend is using modules like we're using on the frontend of our website. Like the menu, control panel icons & sliders etc... By default those module in the backend have viewing level 'Special'. So only the users, in the user groups assigned to the level 'Special' are able to see the modules.

In this case you were able to login in the backend but not able to view the backend modules because your user group was not assigned to the special level. By assigning the Super User group (id to the special view level via the database you were able to see the modules again.

Glad your issue is solved!

Cheers, Sander

[shmerke]

Thanks girbitte, I have the same problem and I change the rules as you say and it's works. Thanks a lot again.

[kkokoruz]

I struggled with understanding I had to assign my new group to special for quite a while. What I still can't figure out is how to restrict category access in the backend like I can in the front end.

I have usergroups assigned via category permissions to be able to create and edit only the content that resides in that category. I love it!

What I can't figure out is how to do this in the backend. I thought that my category permission settings would apply to the backend as well but sadly this does not seem to be the case. I was hoping to give my users the option from working from the backend for articles as well as giving them a little more access to the users section to use the mass mail so we could communicate with each other but right now if I give the usergroup access to the backend they can create or edit any article in any category, not just the ones assigned to them via the category permissions.

Is restricted category/article access even an option for Joomla backend? Please let me know.

Thank You

[jen4web]

It should also be working in the back end. Look closely at the list of articles generated in the Article Manager when that user is logged in. You may see all of the articles on the site listed, but the articles they can't edit will not have a link on them. Only editable articles have a link.

Your usergroup for editing this category's articles on the front end and back end should have the site login and admin login permissions enabled. Then you should be able to go to each category of content and enable or disable access. It should not make a difference if they're editing by front or back end, as those category permissions apply in both areas.

Jen

[kkokoruz]

Jen, your the best! Your right about the articles and the categories no longer being links. I adjusted the permissions of 'edit state' for one user group and that locked things down further.

Right now I think my only global setting is 'edit own'

I was very confused by the ability to still create an article and see all the categories listed but after some testing I realized that when set properly the articles are created but not published and cannot be published unless that user group has 'edit state' allowed.

Finding out that this is the way Joomla handles permissions, it leads me to ask is there a setting or extension that alerts an admin when there is new content submitted but not published. An alert when you log in or perhaps an email.

I really appreciate the help!

[deirdrema]

This is exctly the problem I am having. I had an email to backup which I did and then I got exactly what girbitte showed here.
Now how do I acces the database tables? Where do I find them?

[deirdrema]

Can I recommend to joomla! developers that a warning is flagged in the back-end if you change the acces level to remove Super User AND to not allow people to change the name of 'special' in the <User Manager: Edit Viewing Access Level> section.

Changing either of these is a nightmare to fix!!! I know because I had to do it without SQL installed in our db!

[theBirdandBee]

Hi all,

i had the same problem exept i probably messed up some more.
Since i'm new to this can someone please post picture of the _user_usergroup_map and user groups or additional tables to set it all back to original? i changed the view levels back to the example on this treat.

but i still i can't see my whole backend probably because another setting is wrong my admin id is the 42 one.

Can someone tell me where it is wrong so i can correct it and point me to a really easy user manager tutorial since i don't seem to get that.

Thank you in advance,
Debbie

[theBirdandBee]

I solved my issue: in this way Add a New Super Administrator User

http://docs.joomla.org/How_do_you_recov ... assword%3F

[garyjaybrooks]

I found this information from Elin so we all are aware.

6=manager 3=author 8 = super user

[tatoxxi]

Girbitte, your suggestion worked just great, thanks a lot . It was all about adding 8 to the rules at special.