Hi,

I get this error all the time.

I can't seem to figure out what changed recently.

Thanks

Comments

agentrickard’s picture

Status: Active » Postponed (maintainer needs more info)

More detail, please. This is neither replicable nor actionable. The domain_user property is loaded in hook_boot().

VanessaM’s picture

ok, I found a pattern to reproduce:

I created/edited an image style--> ran cron --> after cron finished I went back into the image style window and I get the errors.

agentrickard’s picture

Status: Postponed (maintainer needs more info) » Needs review
StatusFileSize
new487 bytes

It's odd. Something is firing very early in the process. You can, in this instance, safely ignore these errors, but we can also account for them. In this case, the warnings should be harmless.

Here's a patch.

agentrickard’s picture

Status: Needs review » Fixed

Committed.

   d497a98..fdb493c  7.x-3.x -> 7.x-3.x
VanessaM’s picture

I am still getting errors after installing the patch....

agentrickard’s picture

Please report the error in the body of a comment, not the issue title.

I simply don't believe this report to be possible. Look at the code and make sure the patch applied.

agentrickard’s picture

Status: Fixed » Active

Bah. That patch is inside an else.

In future, please don't put issue details in the title. I missed the line number because of it.

agentrickard’s picture

Version: 7.x-3.8 » 7.x-3.x-dev
Status: Active » Needs review
StatusFileSize
new978 bytes

Note that the other patch was already committed. So this patch will apply to 7.x-3.x-dev or to 7.x-3.9.

VanessaM’s picture

thank you so much! it works like a charm.
In the future I will put the error in the body too.

agentrickard’s picture

Status: Needs review » Reviewed & tested by the community

Thanks for the quick review. I'm just a little grump this week.

agentrickard’s picture

Status: Reviewed & tested by the community » Fixed

Fixed.

   06eb8a7..11597a9  7.x-3.x -> 7.x-3.x
Nephele’s picture

FYI, at least in my case these errors were appearing in cron runs. drupal_cron_run() changes the user to anonymous:

  // Force the current user to anonymous to ensure consistent permissions on
  // cron runs.
  $original_user = $GLOBALS['user'];
  $GLOBALS['user'] = drupal_anonymous_user();

This is presumably bypassing any processing you normally do in hook_boot().

agentrickard’s picture

Thanks. That makes sense.

Status: Fixed » Closed (fixed)

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