I finally got domain access to work. This is on server 2008 with iis 7.5 with dns pointing to a dedicated ip.
7.x.2 showed all content on all sites when logged in (even with different users and permissions).
7.x-3x-dev separates the content like it should. I just get the above error when i create exclusive content.

In both versions, creating separate domains is not a problem.
For this I thank you "agent Rickard".

Any help with the error would be greatly appreciated. Other than that I think it's working as designed.

MrPhilbert

Comments

MrPhilbert’s picture

I disabled the domain source module and the error went away. I'm not going to do any cross domain searching yet so it's cool for now.
This could very well be a permission or configuration option that I'm just spacing over. I'm still not sure what "domain_site" is referencing though.

I'll do some checking and ramble on some more.

agentrickard’s picture

Status: Active » Postponed (maintainer needs more info)

I cannot replicate this error.

agentrickard’s picture

Status: Postponed (maintainer needs more info) » Active

Finally found an instance of it.

agentrickard’s picture

Status: Active » Needs review
StatusFileSize
new815 bytes

And a patch (for 7.x.3).

MrPhilbert’s picture

Holly cow! English must be your second language as PHP is obviously your first.

agentrickard’s picture

Status: Needs review » Reviewed & tested by the community

I take it this fixes the issue, then?

These kinds of errors are easy once you can reliably reproduce them.

agentrickard’s picture

Status: Reviewed & tested by the community » Needs review

Needs this little bit as well.

  // Run through the nodes and ensure they have proper data.
  foreach ($node_ids as $nid => $value) {
    $lookup[$nid] = $domains;
    if (isset($records[$nid])) {
      $lookup[$nid] = $records[$nid];
    }
    // It is possible that no record exists here.
    if (!isset($lookup[$nid]['domain_site'])) {
      $lookup[$nid]['domain_site'] = FALSE;
    }
  }

Will review after lunch.

MrPhilbert’s picture

Sorry for the late reply.
I was doing some client work for pdf data collection till early this morning. I'll do the patch and test this weekend.
Thanks

agentrickard’s picture

StatusFileSize
new1.41 KB

Better patch.

agentrickard’s picture

StatusFileSize
new1.41 KB

And a patch against 7.x.2.

agentrickard’s picture

Status: Needs review » Reviewed & tested by the community
StatusFileSize
new1.63 KB

Interesting, sometimes $nodes is not an array, so we have to account for that.

Committed to 7.x.2.

agentrickard’s picture

Status: Reviewed & tested by the community » Fixed
StatusFileSize
new1.5 KB

Committed to 7.x.3.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

VanessaM’s picture

Version: 7.x-3.x-dev » 7.x-3.8

Hi,

I am getting this error in version 7.x-3.8.

Can you provide a patch for this version since the code in the last patch doesn't exists.

Thanks!

VanessaM’s picture

Title: Undefined index: domain_site in domain_source_lookup() (line 298 of....modules\domain\domain_source\domain_source.module). » Undefined index: domain_site in domain_source_lookup() (line 273 of....modules\domain\domain_source\domain_source.module).
Status: Closed (fixed) » Active

I am getting this error in version 7.x-3.8.

agentrickard’s picture

Status: Active » Postponed (maintainer needs more info)

Under what conditions is the error generated?

And, no re-rolling the patch makes no sense, because the code has already been released as part of the 3.8 release.

agentrickard’s picture

Status: Postponed (maintainer needs more info) » Closed (fixed)

This code was actually removed in a refactor.

Please open a new issue that describes the conditions under which this error occurs.