I upgraded from dev version 7.x-1.6+67-dev to the latest stable release 1.7 and I've been running into a lot of issues.

First, after upgrading many of my variables were overridden (for example show_n variable) A block I had set up to show 15 images suddenly got bumped down to 6. I had to manually change it back

Next I noticed that every single content type on the server got a new field added to it called Flickr Date. I had to manually go through and delete it

Now I'm getting an error and a warning message on pages that contain a flickr image or slideshow. (Prior to the upgrade no warning or errors were shown). These messages are:

Warning: Automatic fallback to the cURL connection method kicked in to handle the request. Result code from the failing request: 200

Error message
Notice: Uninitialized string offset: 0 in flickr_img() (line 320 of /myDrupalSite/sites/all/modules/contrib/flickr/flickr.inc).

I'm not sure what happened but things are acting very strange now!

As a side note, I upgraded flickr on another server from a stable release 1.6 to 1.7 and although I didn't have issues with the new field appearing and the variables being wiped out, I am still now seeing the Warning and Error messages listed above. (Of course only on my apache server, not on my windows machine).

I'm really not sure what's going on, but I wanted to get some details out there in case you wanted a start looking into this. I think I may fully uninstall the new stable release and go back to the old dev version I was using.

Comments

ladybug_3777’s picture

ladybug_3777 commented

Providing some more info:

The cURL Warning only occurs the FIRST time I save a node that contains a photoset field. So I'm OK with that warning message as long as it's not there all the time. At first it seemed like it was happening every time, but I think that is because I was switching back and forth on some different servers. I'll test a little more to triple confirm. I went into a quick panic mode because a long weekend is coming up and suddenly these issues popped up. Slowing down and looking closer now.

**update**
I just noticed the new cURL settings in the advanced section of the flickr config page. Turning on cURL makes the warning message disappear.

HOWEVER, The image offset issue is the main issue now. That one is still hanging around.

ladybug_3777’s picture

ladybug_3777 commented

A little more info as I work on this problem...

I'm seeing different behavior on different servers for this offset error. Not sure yet if this is related but the server that is NOT throwing this error has php version 5.4.6. The version that is showing the error is php version 5.3.5

After searching a bit, I've found this in regards to differences in the offset handling for php

http://php.net/manual/en/migration54.incompatible.php

Non-numeric string offsets - e.g. $a['foo'] where $a is a string - now return false on isset() and true on empty(), and produce a E_WARNING if you try to use them. Offsets of types double, bool and null produce a E_NOTICE. Numeric strings (e.g. $a['2']) still work as before. Note that offsets like '12.3' and '5 foobar' are considered non-numeric and produce a E_WARNING, but are converted to 12 and 5 respectively, for backward compatibility reasons. Note: Following code returns different result. $str='abc';var_dump(isset($str['x'])); // false for PHP 5.4 or later, but true for 5.3 or less

ladybug_3777’s picture

ladybug_3777 commented

I'm going to set up a new issue dedicated to the offset issue since it will be looked at separately.

lolandese’s picture

lolandese commented

I upgraded from dev version 7.x-1.6+67-dev to the latest stable release 1.7 and I've been running into a lot of issues.

Update hooks are based on stable to stable upgrades. We only tested 7.x-1.6 to 7.x-1.7.

First, after upgrading many of my variables were overridden (for example show_n variable).

Only variable_set('flickr_block_' . $delta, ... can override existing variables. In combination with show_n this only exists in the function flickr_block_save() (obviously). No idea how this could slip through. Check your Flickr block settings and save them. I apologize for the inconvenience.

Next I noticed that every single content type on the server got a new field added to it called Flickr Date. I had to manually go through and delete it.

You could have avoided that. Read the INSTALL.txt of the Flickr Block module. Next time we will provide a separate UPGRADE.txt file.

Warning: Automatic fallback to the cURL connection method kicked in to handle the request. Result code from the failing request: 200

If one connection method (open socket) fails for whatever reason, cURL is used as fallback (if available). You just get notified that occurred. The warning is generated by the Flickr module that also provides the fallback.

I'm going to set up a new issue dedicated to the offset issue since it will be looked at separately.

Once opened, I'll look into it.

ladybug_3777’s picture

ladybug_3777 commented

Thanks! I kinda figured the upgrade from dev to a stable release was the cause for a lot of weirdness. I actually wasn't going to report it for that reason at first, but wanted to toss it out there just in case.

I totally missed the INSTALL.txt for Flickr Block. I had the module installed a while ago and didn't think to re-check it. Totally my fault.

I did finally see the cURL settings and sorted that out. Thanks!

The other actual issue is here: https://www.drupal.org/node/2493707

And finally, THANK YOU for being such a GREAT module owner. You always get back to people quickly with helpful information and I (and I'm sure others) really appreciate it!

lolandese’s picture

lolandese commented

Thanks for your feedback. I need to know what people struggle with to make improvements, e.g. providing an UPGRADE.txt file next time.

ladybug_3777’s picture

ladybug_3777 commented
Status: Active » Closed (works as designed)