I am using Domain in conjunction with Acidfree, a image gallery module which depends ONLY on Taxonomy and Image (and that is Image core only). Albums are a nodetype, and can easily be published to the single domain X. A nice Acidfree feature is mass import of image archives. When doing a mass import, the form is complemented with the Domain's "Publish To:" information: setting it to domain X and uploading imagefile.tar.bz, images are correctly untarred and inserted into album, but they always get assigned to domain #0, irrespective of "Publish To:" settings. Is there anything that can be done around that? In my "node settings" everithing is unchecked (including Album and Image node types).

Comments

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented
Status: Active » Postponed (maintainer needs more info)

This would require some testing about how AcidFree is handling the form input.

Does AcidFree create individual nodes from the elements of the tarball? If so, it is likely that the node creation process is ignoring the extra form data.

skizzo’s picture

skizzo commented

yes. Each single picture results in few files (thumbnail, original...) and exactly one node of type "image".
I tried to upload from X.mydomain.com but resulting image nodes are still (re)assigned to domain #0.
However if I go node/add/image (i.e. add a single image) then the "Publish To: X" field is honored.
The problem happens only with /node/nnn/import (i.e. add images batch to album node nnn)
To begin with, I carried out all these tests as User #1

agentrickard’s picture

agentrickard
he/him
Primary language English
Location Georgia (US)
commented
Title: Assignment to domain for uploaded file » AcidFree does not respect all hook_form_alter() implementations
Project: Domain » Acidfree Albums
Version: 5.x-1.0 » 5.x-1.x-dev
Status: Postponed (maintainer needs more info) » Active

This is, IMO, a bug in AcidFree. The nodes are getting assigned to domain #0 because no other options are available at the code level.

AcidFree is auto-processing some node forms to save this data, and the implementation of domain_form_alter() is not being respected.

It appears, from looking at the code, that AcidFree is throwing away data inserted by contributed modules -- this would include any Node Access module (like OG or DA).

The simple fix may be a patch to _acidfree_set_node_defaults(&$node) to pick up either a) the current domain (from the $_domain global), or b) the Domain settings for the parent node. Option b is probably best.

I am moving this to the AcidFree queue.

mwheinz’s picture

mwheinz commented
Status: Active » Closed (won't fix)