[Fixed 1938+] RuntimeException due to ACL change item cats

Bonjour,
With Joomla3.3.4 and V22r1932
i still have a problem when i want to validate an article written as a "author".
It's like desscribe here : www.flexicontent.org/forum/index.php?f=2...b_v=viewtopic#p47307
I don't understand why and i don't know what to do ...
Thanks for your help

Hello

this maybe problematic in J3,

if so give to all your users groups "can change category assignments", effectively ignore this ACL permission

until this is tested and-or fixed in J3

Thanks but i'm really disapointed ...
What's the configuration to use a workflow of validation with this runtime exception ?
Help !!!

Hello

i don't understand you want to use this feature ?
note that this feature is new in v2.2.0


this ACL feature disables the category field, which causes J3 form validation to fail (should work properly in J2.5)



the workaround is to give to you user groups "Can change category assignments",
did you try the above ?

the error occurs in J3 if you submit the item form with category field empty or missing or disabled

I send you a pm !

I just discovered that if i save first ans close after, it's ok.
But if i use the button "save and close", i've got a bug !!

And i tried with english as administration language ...
I saw that the secondary category is "locked".
How can i change this configuration ?
Thanks

Bonjour,
J'ai essayé de voir ce que cela donnait sous joomla 3 sans flexicontent.
Bien sûr, je ne peux pas choisir deux catégories mais je n'ai pas de RuntimeException.
Là, je suis perdu et très désemparé.
Que peut-on faire ?
Merci de votre aide.

Hello

i logged on to your website,

you have not done/tried what i asked you

give the ACL permission:
"change main category assignments" to your usergroups,

giving it these ACL permissions to the top-level usergroups

– Enregistré
– Gestionnaire

should be enough

i changed this in your website:
[attachment=0:2h9cozh8]<!-- ia0 -->change_main_cat.png<!-- ia0 -->[/attachment:2h9cozh8]

and as we said above will test / verify this issue for next FLEXIcontent public package

Muchos gracias for your help
I'm gonna try to find a solution to activate a validation workflow with this configuration.
Best regards

Hello

in r1938
- this bug is fixed,
- and also by default these permissions are granted (set to allow)


so in r1938+ you can use this feature

but for r1932 just set these to allow ...

Works for this week-end.
I'll try it as soon as possible.
One more thanks
Best regards