First of all, I love the Domain Access module. Thanks for all the effort.

After upgrading to 7.x-3.10 I keep getting the following error after enabling/disabling a module:

Notice: Undefined index: path in domain_nav_menu() (regel 51 van drupal\sites\all\modules\domain\domain_nav\domain_nav.module).

I currently have the following Domain Access modules installed:

  • Domain Access
  • Domain Configuration
  • Domain Content
  • Domain Navigation
  • Domain Settings
  • Domain Views

I'm not using any other node access modules.

PHP version: 5.4.3
Database: MySQL 5.5.24

Any ideas on what might be causing this issue? I didn't have this issue in the 7.x-3.9 version.

Thanks in advance.

CommentFileSizeAuthor
#8 domain_init_check-2012410-8.patch813 bytesYaron Tal
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Bob_Vdl’s picture

The error shows up every time I save a configuration, instead of just on the modules screen.

agentrickard’s picture

I'll have to take a look.

Funksmaname’s picture

I have the same problem - very interested in this...
It doesn't seem to be causing problems as far as I can see - just appears 4 times on cron run.

thanks!

agentrickard’s picture

The error suggests that hook_domain_load() is not being called properly. I cannot reproduce the error, so anyone who can provide steps to replicate would be a hero.

I suppose it is possible that the change to domain_api() in the 3.10 release causes this issue for older sites.

Funksmaname’s picture

fyi, mine is not an 'old' site - it's in recent dev so using latest dev versions of modules...

agentrickard’s picture

Status: Active » Postponed (maintainer needs more info)

Steps to reproduce, please.

rancidl’s picture

*Subscribing
Same issue here too, can't find help online, unsure if it's a major issue or a small notice than can be hidden/prevented by isset or something similar.

Yaron Tal’s picture

Issue summary: View changes
Status: Postponed (maintainer needs more info) » Needs review
FileSize
813 bytes

This happened to me when installing from an install profile and having domain_nav as a dependency. Looks like it also happens when you forget to put the domain bootstrap in your settings.php.

The solution for me was to do an extra check if the $_domain variable is properly loaded as is also done in domain_init() in the domain module.

Yaron Tal’s picture

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

patch was created on latest dev

ExTexan’s picture

Is that patch really the correct approach?

In my case, it seems that the modules are installed correctly, including the domain bootstrap in my settings.php, so if there really is a problem somewhere, wouldn't that patch just hide it?

agentrickard’s picture

Status: Needs review » Needs work

Well, hiding the error is kind of the point, here. We should probably log an error, however, rather than silently suppressing.