FLEXIContent - v2.0.0 - final for J2.5 released (r1648)

Hello there, I donwlaoded and installed the last version. All is well. Therefore I encounter the following little bugs. Images talk better than lon explinations

1. Can't find this variable in language FC file in english to translate in french language file. What can I do for this problem


2. Same thing in message text


3. Why is a content in content liste view greyed and non editable after having modified it from frontend


Thanks in advance for your help.

.
See previous page . . .

ggppdk wrote: Please replace # symbol to ; (semicolon) in admin\language\en-GB.com_flexicontent.ini before comments at lines 1207, 1211, and 1214.

.

Sorry, this hasn't fixed anything for me. Still with the same bugs.

Need help.

Thks

Hi,
I've the same problem written before:

1) When someone try to modify an item and he isn't a superadministrator appear this error: FLEXI_NO_ACCESS and nothing else happend.

2) The superadministrator cannot modify the items if someone else tried to open it. A lock appear and the item's name become gray.

3) When the user (manager for example) logout, in the superadministrator panel disappear the lock but the item's name remains gray. If I try to check the checkbox and use the "modify" button on top of the page the error is: "This item is currently edited by another administrator". But this isn't true.

Use joomla tools unlock

Issue 2 and 3 resolved.

And for the first one?

1) When someone try to modify an item and he isn't a superadministrator appear this error: FLEXI_NO_ACCESS and nothing else happend.

A big thankyou.

Did you use flexi access ?
Verify your authorisation

This is my configuration in flexycontent permissions for the users group who cannot modify items.
This users group can create but cannot modify items because appears this error: "FLEXI_NO_ACCESS".

Configuration - Not Allowed
Component access - Allowed
Can create content - Allowed
Can delete content - Allowed
Can edit content - Allowed
Can edit own content - Allowed
Can edit state of content - Allowed
Can manage fields - Not Allowed
Can view fields - Not Allowed
Can manage tags - Not Allowed
Can Archives - Allowed
Can manage stats - Allowed
Can manage templates - Not Allowed
Can use version - Allowed
Can use tags - Allowed
Can manage articles - Allowed
Can copy articles - Allowed
Can order articles - Allowed
Can set article params - Allowed
Can display all items - Allowed
Can manage types - Not Allowed
Can create type - Not Allowed
Can delete type - Not Allowed
Can edit type - Not Allowed
Can edit state of type - Not Allowed
Can manage categories - Not Allowed
View All Categories - Not Allowed
View categories tree - Not Allowed
Can create category - Not Allowed
Can delete category - Not Allowed
Can edit category - Not Allowed
Can edit state of category - Not Allowed
Use multiple Categories - Allowed
Delete own category - Not Allowed
Can manage files - Allowed
Upload file - Allowed
View All files - Allowed

I was trying to implement cascade behavior for category filters, and i ended up checking all the (FC v2.0) category model for ACL and other issues, because if i found some ACL bugs and other issues in the category model:

1 - one bug allowed viewing of a category when a user did have the required access level to view it.
2 - one minor bug, the alpha-index was showing letters from all items of the category and not only the ones that the user had access to
3 - then also implemented ability for alpha-index to display items according to current filtering (this is a new feature for filters, and now i have added it to alpha-index too)
4 - added support for core filters: createdby / modifiedby / item type / item state / tags, these were missing in FC v2.0
5 - Fixed access level not checked properly for fields used as filters (meaning if a user cannot see a field then he/she should be able to use it as filter)
6 - Added support for "My Items"
7 - Added support for "Author Items" (ALL or in specific category), NOTE this if for frontend Display, NO support for backend AUTHOR management yet like in v1.5.6
8 - Fixed redirection to login page, (default component name has changed in J1.6+ it is now com_users and not com_user)
9 - Added better messages for wrong access
10 - Added sql error reporting via joomla messages to track down any SQL query errors (bugs)
11 - Fixed wrongly checked access level for subcategories, that caused allowed inclusion of subcategories that user did have access to view, and similar -minor importance- bugs for the reported number of assigned subcats and their assigned items (remember we have these numbers next to subcategory names), as the reported number of subcats and assigned items included all, (of course if show unauthorised global parameter is enabled then all must be shown)
12 - ? i think i checked everything

-- I will also check item model tomorrow, also now, i think i am able to fix category tree creation according to access level of the categories (we have an open bug).

-- Also we (me and enjoyman) have tracked down and fixed the weird bug that made the creation of the new search-index not to stop.

About what you report for items, i will check,
but do the users have edit capability in the main category of the item?

Regards

Hi,
In all the category and subcategory, for this users group, I have this configurations:

Can create - Allowed
Can delete - Allowed
Can edit - Allowed
Can modify state - Allowed
Can edit own items - Allowed