I thing you just removed your right to create resource and users.
check rights.

Hi Babynus,

I checked my rights (I'm admin) but nothing seems to be false (in my point of view)

Is there another rights I need to check ? If yes, where are they ?

Thx

Access rights seem coorct.

Do you have screen custromization plugin ?
It is the only way I can see to set fileds as readonly.
Check customization for resource screen.

Yes, I have this plugin.

Int the screen "Contact", field is a user and is ressource are readonly, but not in the screen "Ressources".

And one ather thing : in a previous backup (2 days ago), I've exaxtly the same, but it works correctly :blink: : I dont't understand anymore...

I need to uncheck the readonly en the screen contact to have theses fields in read/write ?

I tried to modify the fields in the screen "Contact" withe phe plugin but it's not authorized : I can't uncheck the "Readonly" of the tree fields (Profil, is a ressource and is a user).

I confirm, it is side effect of screen customization.
When you customize "contact" sceen, it locks "isResource" and "isUser" for everyone.
We'll fix the issue. (Ticekt #3503)

Thanks for your help.

in the meantime, is there a way around the problem ?

Not really.
The solution would be to reset your customization, but you would loose data in new fields.

Hi,

To fix issue, you'll have to manually update file /model/custom/contact.php
to change lines 84 to 86 from

    "idProfile"=>"readonly",
    "isUser"=>"readonly",
    "isResource"=>"readonly",

to

    "idProfile"=>"",
    "isUser"=>"",
    "isResource"=>"",

We've added fix in V7.1.4 so than this issue does not occur again.

Hello Babynus,

The problem appear again with news version of ProjeQtor and the las version of the plugin ScreenCustomization 🙁

I applied the same solution you describe above and it corrects the problem 🙂

It looks like the correction you have implemented in the plugin doesn't follow the version upgrade of ProjeQtor (or new version of plugin) 🙁

Hi,

The fix was lost.
It's been re-applied on V7.4.0 (coming soon).
It consists in same replacement on model/ContactMain.php as on /model/custom/Contact.php

Thanks for pointing out the regression.