Not able to upload images when domain access module enabled

It looks like it could be related to this bug: #216086: Non-admin can't upload images using XP publisher. Has the user who is trying to upload the images got the "administer images" permission?

Yes. I am actually attempting to test functionality with drupal account #1. Who has all access permissions. I can't figure out what the problem is.

--
J.

Is there any information in the drupal logs?

One other thing, which you've probably already tested: can you create images in the normal way using the web browser (Create content->Image)?

main page of my log window....
php Mar 27 2009 - 11:39pm mysqli_real_escape_string() expects parameter 1 ... Anonymous
form Mar 27 2009 - 11:38pm Illegal choice 0 in Publish to element. Jimmy
form Mar 27 2009 - 11:38pm Illegal choice 0 in Publish to element. Jimmy
form Mar 27 2009 - 11:38pm Illegal choice 0 in Publish to element. Jimmy
php Mar 27 2009 - 11:38pm mysqli_real_escape_string() expects parameter 1 ... Anonymous
image_pub Mar 27 2009 - 11:38pm Album added with title test album Jimmy
php Mar 27 2009 - 11:37pm mysqli_real_escape_string() expects parameter 1 ... Anonymous
image_pub Mar 27 2009 - 11:37pm Session opened for Jimmy Jimmy
user Mar 27 2009 - 11:37pm Session opened for Jimmy. Jimmy
php Mar 27 2009 - 11:37pm Missing argument 3 for form_builder(), called in ... Anonymous

----
Type form
Date Friday, 27 March 2009 - 11:38pm
User Jimmy
Location http://xxx.com/publish_xp
Referrer
Message Illegal choice 0 in Publish to element.
Severity error
Hostname xx.xxx.xxx.xxx
Operations

--

seems to be a form error. I attempted to publish 3 images... and received 3 "Illegal choice 0 in Publish to element."

---

Thanks for working with me to trouble shoot this. It is very much appreciated.
--
J.

... oh and yes. I have tested creating image via node/add/image.
--
J.

Thanks for the log. I'm not quite sure what to make of, but prompted by the problems you're reporting, I've fixed the bug #216086: Non-admin can't upload images using XP publisher and made a new release of the module 6.x-1.0-beta2. It would be great if you could try this out to see if it fixes things for you. Please let me know if it works or not. If not, could you tell me if there is anything in the drupal logs (the one at admin/reports/dblog).

The updated version didn't work. I did playing around and figured out what the conflict is.
The conflict is the domain access module. I am not sure if other content access modules don't play nice with this, but can confirm that turn DA off does cause this module to quit working.

Thanks for following up on this.

Just to be clear, I assume you mean that turning the DA module ON causes image_pub to stop working.

It would be great if you could let me know whether you think that this is a bug in image_pub or a configuration issue or bug in domain access. If we can't resolve the issue easily or quickly, I will put some information in the README.

Yes, I turned on DA and it stopped working... turned DA off, tested and was successful in uploading pics via xp publishing.

The next step in troubleshooting IMHO is to test this module with other access modules to see if its an access issue in the module. I have a test install I put up to isolate this module (and images) on my server to be sure its wasn't php or apache configs. after installing drupal 6.10 and enabling just images and related modules, it worked. since I just have images and image publish installed, I'll grab a couple of access modules that are popular out there install them and see what happens.

Is anyone else out there using this successfully in conjunction with an access module?
I'll post my results here. thx, egfrith for the support on this.

thx.
J.

The 5.x version of the module works with taxonomy_access and both the XP and gallery remote upload methods, though I haven't yet tested the 6.x version.

Trying out other access modules might give some information, but I wonder if the various access modules are doing quite different things, perhaps limiting the approach?

I suppose my own approach (if I had time right now!) would be to try to debug the particular interaction by inserting watchdog or drupal_set_message statements to report on relevant variables at critical points of the code of both the DA and image_pub modules. Yes, this is crude, and one day I will learn how to use a php debugger!

The other thing that might be worth trying is to use the gallery_remote software, just in case it's only the XP part of the module that's broken, though I would guess that the problem is common to both.

The gallery remote is also reporting the same errors on the drupal logs. That filters out issues with the xp_publish component. I also did a test with taxonomy access and content access. Both worked. : ( This issue seems to be limited to just DA.

This is good to know. I'm changing the title to reflect this and, for my own sanity, changing the priority to normal, as although I would like to get this fixed one way or another, I don't think it is a problem that will affect a large percentage of image_pub users.

I agree. DA is getting more popular but not a big need to many users. Can we arrange some sort of bounty. I am not a developer and would love to get this up and running if your asking price is reasonable.

thx for the support to date.

--
J.

CorpX: I really appreciate your suggestion of offering a bounty, but after some consideration, I've decided that now wouldn't be the right time for me to accept - I have a number of other projects I really need to get on with as well as the day job and the rest of life... and I don't need the money. However, if you would like to advertise the bounty more widely, I would certainly look carefully at any patches that were submitted to image_pub.

The other thing that occurs to me is that perhaps the reason that things aren't working for you is not just the domain_access and image_pub modules, but also the precise configuration of your server. I wonder if it would be most fruitful to hire a contractor and give them access to your server - but this is just a suggestion.