Filling list value automatically in ca_objects_representations bundle

remco

We have source access checking ( setting perform_source_access_checking = 1 in app.conf) activated to restrict access to three different collections within the system.
For now everything works as expected. Users can be restricted to only see and/or edit specific items within the database.
This of course depends on filling the source_id for every item as needed.
The only issue I have is that when adding an image (for instance) using the ca_objects_representations bundle the source_id is not available in the bundle so it can not be set.
The user will have to access the full (object representation) record to set the source_id.

We can use only one possible source_id value for object representations, that would not be a big issue.
I am looking for one of two possible solutions that I can think of:

Automatically fill the souce_id value when adding an image in the ca_objects_representations bundle. Setting the value as the default value does not work. The value wille be preselected, but will only be stored after saving the full record.
Find a way to add the source_id to the fields that are editable in the ca_objects_representations bundle so it can be set by the user at the moment they are adding the image.

Is either of these solutions possible?

remco

I tried the prepopulate plugin but is seems that also needs the full record to be openend.

monica

The representation fields that are editable are a setting of the bundle in the UI. I would have however assumed that setting the list item as default would be enough. Have you checked the source_id bundle settings in representation editor to make sure it’s using the default if empty?
The prepopulate plugin would need to be set to trigger on save of ca_object, with the target as ca_object_representation.source_id

remco

Thanks Monica,

I have phpmyadmin open with the ca_object_representation table opened, sorted to have the latest entry on top.
I have the desired value set as default in list_items.
What I can see happening when I add an image in the object editor is a new record being created with source_id as NULL.
If I open the representation editor the desired value is prepopulated in source_id. If I press save here the value in the table is changed to the desired value.
So it appears the ca_objects_representations bundle in the object crates the new record after save in the object editor but does not set the default value for source_id.

I guess it would be hard/impossible to add source_id to the editable representation fields for the ca_objects_representations or would you know a way?

How would I set the trigger on save of ca_object as you suggest?

For the moment in prepopulate.conf I have:

enabled = 1

prepopulate_fields_on_save = 1
prepopulate_fields_on_edit = 1

prepopulate_rules = {
	source_id_rule = {
		table = ca_object_representations,

		mode = addIfEmpty,
		
		useFor = [edit, save],

		target = ca_object_representations.source_id,

		template = 444,
	},
}

monica

The prepopulate rule needs to be triggered on table = ca_objects

remco

Sorry, same results.
I have tried setting the default value in mysql too, but even that gave the same result.
The value is only saved after opening it in the representation editor.

remco

For item level access control it is possible to disable it for different types of items.
Would this work for object representations? Like:
ca_object_representations_dont_do_source_access_control = 1

remco

For the moment I sort of solved the problem by adding two triggers to the table ca_object_representations in phpmyadmin:
For new inserts:

`CREATE TRIGGER set_default_source_id
BEFORE INSERT ON ca_object_representations
FOR EACH ROW
BEGIN
    IF NEW.source_id IS NULL THEN
        SET NEW.source_id = 444;
    END IF;
END //

DELIMITER ;`

For handling updates:

`CREATE TRIGGER update_null_source_id
BEFORE UPDATE ON ca_object_representations
FOR EACH ROW
BEGIN
    IF NEW.source_id IS NULL THEN
        SET NEW.source_id = 444;
    END IF;
END //

DELIMITER ;`

It might not be the most elegant solution, but it seems to work.
Of course this solution can only be applied if you essentially do not want source access checking for object representations.

seth

We'd have to add an opt-out for source level ACL for representations. There's not other fix. Your trigger works, but it's assuming a lot. It'll break eventually.

remco

Since representations are probably the only record type that normally gets added without opening the editor (or quick add editor) that might be a good idea.
I assume others will use source access checking, and guess they will run into the same issue.

seth

Yes. The change will likely be in the 2.0.5 release which will happen in the next few days.

seth

There are new per-table options to disable source level access control in the dev/2.0 branch. This will be released as version 2.0.5 later today.