Sql dump off the assets table joined
good before upgrade : only 6 occurences for com_zoo ACL
Bad after upgrade 1 : 82 occurences found for com_zoo
bad after upgrade 2 : 84 occurences found for com_zoo when try to modify them via BO
modify Administrator ACL on SYSTEM > CONFIGURATION > ZOO > ACL.
Assets table looks like :
wz1mj_assets_good_beforeupgrade.txt
Administrator ACL are blocked as "refused" on SYSTEM > CONFIGURATION > ZOO > ACL.
Assets table looks like :
wz1mj_assets_broken_after_uprage1.txt
I add ASSETS TABLE file before the joomla 3.7.4 upgrade and ASSETS TABLE file after the joomla 3.7.4 upgrade.
After the upgrade :
wz1mj_assets_broken_after_uprage1.txt
Before the upgrade :
Priority | Urgent | ⇒ | Medium |
Status | New | ⇒ | Information Required |
One of the asset handling changes in J3.7.4+ is that empty assets will not be saved
so actually the asset entries should now be less than before ...
we adjusted our initial asset creation in our component (flexicontent component) to account for this
because we were creating a small number of empty assets ...
about zoo component:
Administrator ACL are blocked as "refused" on SYSTEM > CONFIGURATION > ZOO > ACL.
the problem is that you have about 20 or 30 of assets for 'com_zoo' component !!!
(i mean of the component itself !, i do not speak of its categories or its fields, etc)
i am not sure how this happened, but once you have 2 assets for a component and you click to save component configuration, then you will get 1 new asset every time (if i remember correctly)
The multiple assets can manifest the behaviour that all non-super user groups (e.g. administrator usergroup) will show as having all permissions refused !
e.g. make full site backup and do execute an SQL query to delete the assets
and then hopefully next time you save component only 1 component asset
and any further saves will not create any more duplicate component assets
in any case report to the authors that multiple assets of the component itself are created ...
i do not know who should be responsible for checking for duplicate assets,
but it is good if the component checks ... and account for this case, and deletes all duplicate assets and then creates a single one ...
thank you for your answer, I will follow your instructions.
Closed_By | franz-wohlkoenig | ⇒ | joomla-cms-bot |
Status | Information Required | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2017-08-25 12:53:16 |
Closed_By | ⇒ | franz-wohlkoenig |
Set to "closed" on behalf of @franz-wohlkoenig by The JTracker Application at issues.joomla.org/joomla-cms/17690
closed as stated above; it can always reopened.
have you asked Devs. of com_zoo?
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/17690.