I get the following warning:

Strict warning: Only variables should be passed by reference in profile2_regpath_block_view() (line 39 of...

You can fix this by changing line 39 in profile2_regpath_blocks.module from:

if ($profile_type = reset(entity_load('profile2_type', array($profile_id)))) {

into:

$profile_entity = entity_load('profile2_type', array($profile_id));
  if ($profile_type = reset($profile_entity)) {
CommentFileSizeAuthor
#6 strict-warning_1833300_6.patch1.34 KBmsnassar
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

kingfisher64’s picture

kingfisher64 CreditAttribution: kingfisher64 commented
Version: 7.x-2.0-beta3 » 7.x-2.x-dev
Priority: Minor » Normal

Can anyone who knows how to commit this to the latest dev? It's pops up with php5.4 installed I believe.

Many thanks Marty for posting the solution

grasmash’s picture

grasmash CreditAttribution: grasmash commented
Status: Active » Fixed
kingfisher64’s picture

kingfisher64 CreditAttribution: kingfisher64 commented

Has the fix by Marty been put into the latest dev? I thought I had the latest dev which is dated 25th May and this fix was needed.

grasmash’s picture

grasmash CreditAttribution: grasmash commented

Yes, it was pushed to the latest dev, which was built last night.

Status: Fixed » Closed (fixed)

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

msnassar’s picture

msnassar CreditAttribution: msnassar commented
Title: Strict warning: passing variable by reference » another extra patch
Priority: Normal » Critical
Issue summary: View changes
Status: Closed (fixed) » Needs review
FileSize
strict-warning_1833300_6.patch1.34 KB

This also is needed for the last dev version (7.x-2.x-dev)...

JadH’s picture

JadH CreditAttribution: JadH commented

Hi,

I tried applying the patch
I got the below

patch unexpectedly ends in middle of line
Hunk #1 FAILED at 36.
1 out of 1 hunk FAILED -- saving rejects to file profile2_regpath_blocks.module.rej
matt.rad’s picture

matt.rad CreditAttribution: matt.rad commented
Status: Needs review » Reviewed & tested by the community

And chance of getting this fix rolled into the module? Works fine for me on two different production sites.