Maybe I’m overlooking something simple. Installed party_relationship in demo 7.0 database. Added relationship type plus reverse. But I can’t get the “+” button to work, adding new relationship records is disabled in party view and in party relationship view.
Tried the same in demo 6.8 and everything works as expected, i.e. I can add new relationships, delete existing ones etc…
At first glance, nothing has been changed in party_relationship in the last development cycle, so I’m probably missing something stupid…
Normall table_query models are readonly by default, so that was improved on the recent version to make explicit when no record rules are available. This allowed to remove the access rules for most of the table models.
The party relation is a table query that should not be readonly, and this is an exception so there is no possiblity to make a generic test to catch this error.
On the other hand, if we explicity give the permissions to the model, the client will allow the users to write without any issues. So once fixes there should be no issue and we won’t need any test to validate such setup.
For me it is not needed to just test an access configuration.
We normally do not test access rules configuration for modules as we know that the access rules work (there is a bunch of generic tests for access rules) and once they are setup they can not be broken.