I attached a flickr slideshow to a point feature in the map along with a video and a couple images, and get this error as an anon and auth user:
arning: Parameter 6 to emvideo_flickr_sets_video() expected to be a reference, value given in /var/lib/hudson/jobs/watershednow/workspace/drupal/sites/all/modules/contrib/emfield/emfield.module on line 650.
Here's the error I get upon saving (along with map of broken imgs) http://skitch.com/skjalf/d6h2i/map-point-feature-chrome
Here's the error that shows up for anon users on full node page display for point map features: http://skitch.com/skjalf/d6h5r/firefox-map-point-error
Comments
Comment #1
seanberto CreditAttribution: seanberto commentedI think this is fixed. Pushing back to retest.
Comment #2
skjalf CreditAttribution: skjalf commentedI no longer get the error, but flickr slideshows saved within map features do not show up on the full node page for the map feature. (No broken box, or anything, they just don't show up on the page at all.) I tested this a variety of different ways (map feature with multiple images, attachments, etc and one with only a flickr slideshow) but no matter what I do it won't appear.
When I go edit the map feature with the slideshow, I can see that it looks like it's working- it's scraped a Flickr photoset ID that it notes below the field. Here is a screenshot of the edit page to see what I mean: http://skitch.com/skjalf/d9b8e/flickr-slideshow-upload
Videos work fine when the url to a video is entered in this field.
Comment #3
seanberto CreditAttribution: seanberto commentedCould you try with this URL: http://www.flickr.com/photos/thinkshout/sets/72157625136420960/ It works for me. Is this possibly theme-specific?
Comment #4
skjalf CreditAttribution: skjalf commentedTested with the thinkshout slideshow and a couple of others across all themes in FF and Chrome as both anon and auth and they still do not show up for me. The edit screen looks like it's properly seeing the flickr slideshow, referencing the thinkshout set's id (like in the screenshot above).
Comment #5
seanberto CreditAttribution: seanberto commentedTested both on my local environment and a Linux server and can't replicate. Sarah P was able to do this last night too. Asking Robbie to test.
Comment #6
seanberto CreditAttribution: seanberto commentedRobbie can't replicate this issue either. :(
Sorry. Marking as won't fix.
Comment #7
skjalf CreditAttribution: skjalf commentedTo follow up, the reason for this error turned out to be an error on my server where something wonky happened to the sql db during an upgrade of my installation. Installed on a fresh server it worked fine.
(edited for clarity)