Stuck in Post Installation when using ACL manager

Hi

I am installing FC 2.1.3 r1813, new installation on:

Joomla 2.5.16
ACL Manager 2.4.2
(K2 2.6.6)

I get stuck in the post installation; Initial permissions, I can click the link and the icon turns as marked.
Then clicking on REFRESH turns initial permissions back.

I can see in ACL manager that it is the two categories belonging to core content that is complaining.
I can click Fix Asset Issues and everything turns green in ACL Manager, but FC wont start anyway.

I have only one article in com_content, the rest is in K2. (intend to moce all content to FC manually).

Which is the best approach to get around this?
Does FC require that there is articles and categories belonging to J! core when installing?

please read faq ...
www.flexicontent.org/component/f ... ?Itemid=28
and i didn't think that k2 AND flexicontent was compatible in same site ..

Hello

FLEXIcontent has no conflict with K2, it can co-exist,

now about ACL manager

-- FLEXIcontent will set content categories to have parent asset id the:
FLEXIcontent component asset ID

the ACL manager used to reset the parent asset ID of all categories, but i think they fixed this incompatibility, you may send me a PM with admin login to review this

Regards

Hi

Thanks for your help.

I had it initially installed on localhost, but now installed on live site (same issue).
I have sent you a PM.

Thanks,
Sune

Hello

i logged onto your site and it completed successfully,

please don't fix category assets with ACL manager it resets them every time

it wrongly detects FLEXIcontent assets as being invalid

THANKS for your assistance!

Is this an ACL Manager bug, that is or should be reported to the ACL Manager devs?

Thanks again,
Sune

Hello

the ACL manager should not reset:

the category assets of the TOP-level categories if it detects that they point to the asset of the FLEXIContent Component

Hello,

seeing this issue myself for some time now, I contacted the ACL manager dev and got the following reply:

I think that is caused because Flexicontent is making use of the Joomla articles as base, but try to store the article assets as nested items of Flexicontent. This is not correct, as the parent of articles in the Joomla articles database table should always be stored with the Articles Manager in the assets table. This is why ACL Manager detects the issue.
This is not something I can solve, and should be addressed by the developers of Flexicontent.

For my part, I think I can live with these "errors", as until now they never caused real problems for me.

The only question is:
What if other assets have to be repaired by ACL manager?
In this case, I can only fix them together with the FC asset entries in one go, and I will have to restore the initial permissions by FC each time afterwards.

Hope this procedure will work reliable also in future versions - or there will be a better solution.

Regards

Hello

please forward this message to ACL manager

- when FLEXIcontent is installed,

FLEXIcontent manages the Joomla articles, and not the Joomla article manager so inheriting permission from com_content component, is inappropriate

so the top-level categories are made to point to FLEXIcontent component asset


thus ACL manager should not be "fixing" the top-level categories, simply because as said above FLEXIcontent is managing the content and not Joomla article manager,


it 10x simpler for ACL manager to detect that FLEXIcontent is installed and avoid "fixing" the top-level categories


it is possible to allow Joomla top-level categories to point to com_content component asset but the extra ACL permissions that FLEXIcontent adds will no longer be inherited,


but we will examine and implmenet a workaround in a future release but now:


it 10x simpler for ACL manager to detect that FLEXIcontent is installed and avoid "fixing" the top-level categories


Regards

Hi there,

I'm the developer of ACL Manager and replied this in my ticket system to HillWoody:

I'm sorry you are in the middle of two developers...

I will never built-in any specific 3rd party extension support in ACL Manager because an extension is not using the Joomla ACL correctly. So it is indeed simpler for Flexicontent if ACL Manager detects Flexicontent, but that is not the correct way to move forward.

Let me try to provide a bit more technical background:
1) Flexicontent is stores categories is the #__categories table. The "extension" column is filled with "com_content", so the Joomla article manager.
2) In this table a reference is made to the #__assets table, in the assets table you will find the categories listed as "com_content.category.81". This means that in this example this asset is related to a category with ID 81, that belongs to "com_content".
3) The parent ID of this asset entry should always point to the component where it belongs, so "com_content".
4) Flexicontent is changing this parent ID to their "com_flexicontent" entry in the assets table. This is not correct, and detected by ACL Manager.

I think Flexicontent can solve this in two ways:
1) Correctly use the Joomla ACL system and respect that an asset like "com_content.category.81" belongs to the extension "com_content"
2) Store categories under their own extension name, so in the categories table with "com_flexicontent" and the assets should be names like "com_flexicontent.category.81". In that way the parent ID of this asset should indeed point to "com_flexicontent".

As their developer already said:
"FLEXIcontent manages the Joomla articles, and not the Joomla article manager so inheriting permission from com_content component, is inappropriate"
Suggestion 2 is the way to move forward. If it should not inherit the com_content permissions, they should store the assets under their own component name as well.

So I'm confident that ACL Manager is behaving correctly and that Flexicontent needs changes on this area to solve this issue.

Hopefully this helps you and the Flexicontent developers further.