[Due to Invalid assetsTABLE] Administrator cant edit his own content

Hi,
we got a problem with the administrators. They can add content, they can edit content from other users but they cant edit there own content.

We looked at the right for the administrator group and it looks good. (attached screenshot)

What can cause this problem?

Best regards
Patrick

We are using:
FLEXIcontent 3.0.8
Joomla 3.6.5

at first update to flexicontent 3.1.1 and restet

We upgraded to the latest version.
The problem is still there.

We go on with some tests after the upgrade.

We fount out:
If the administrator opens any article and saves it, then he can not open it afterwards.

Thanks
Patrick

Hello

after upgrading to FLEXIcontent v3.1.1

- Edit and save component configuration once
- then if problem persists, then edit and save the top level categories

Hi,
we tried both but it didn't help.

Today i got an email form an "Super User" and she also got this problem.

One is with my super user account and the second on ist also form an super user. The other super sees only one category. The actual subcategory is marked as locked.

Any other suggestions?

Kind regards
Patrick

Hello

The other super sees only one category. The actual subcategory is marked as locked.

There is a permission "edit categories assignments" did you check this ?

After you check the above

Send me a PM with 2 accounts

a super admin and the other of an "administrator" account
and also suggest an item to edit to view the issue

Hi,

i have sent you the website and the login data via pm.

Kind regards
Patrick

If you look into the item list with the administrator account, you will see some item you cant access.

Thats the item we edited with this admin account.

After "save & close" we where not able to edit them again.

Hello

The assets (ACL) DB table has invalid entries
(multiple ACL records exist for every content item) 1 seems to be created every time the item form is saved

same thing happens if we allow access to Joomla article manager and we save joomla article form

There is nothing to fix inside FLEXIcontent code (only maybe add some detection of such a case)

This situation was created because there are 2 root assets (named ROOT.1)

You can either try to fix it manually or better use the Joomla extension:
ACL Manager
to repair your assets table and remove invalid entries