Drupal 7.12, last development release of link.

Sometimes, when I save a node, I get the error:

Notice: unserialize() [function.unserialize]: Error at offset 0 of 8 bytes in _link_load() (line 328 of /var/www/sites/all/modules/link/link.module)

www.centrovolantini.it/1234567?authid=S36rGUbuQyQF

after the error the url is duplicate in the url titl (which was void) and the url is stripped by the ?authid=S36rGUbuQyQF

Comments

dimon00’s picture

dimon00 commented

I believe it is related to the fivestar module.

It seems it occur after I change a vote using the fivestar edit-while-viewing widget.

Edit: it happens even without fivestar. The occurrences are less frequent but the problem is still there. :(

dqd’s picture

dqd
Location London | N.Y.C | Paris | Hamburg | Berlin
commented
Priority: Major » Normal
Status: Active » Postponed (maintainer needs more info)

dimon00,

please provide links, screenshots or markup outputted at this point and maybe also screenshots of your link settings. Since there are about 10 formatters to choose from in the field edit form, we have to dip deeper to find the error.

One possible problem could be the added update: in a switch/case: function with a patch committed lately, if I remember correctly. Not sure yet ... was a fast idea. Can you please check the dev commit list for that to find the issue? But beware its just a thought on this, since it sounds familiar to me a little bit.

Finally what I sad above would help it, when it turns out that it is something else.

jantoine’s picture

jantoine commented

This issue appears to be related to incorrect default values being set for fields during an upgrade from D6 to D7. Editing and saving the field appears to fix the issue.

@dimon00

Please confirm you were seeing this issue on an site that was upgraded to D7.

dimon00’s picture

dimon00 commented

@AntoineSolutions

No. The website was never upgrade from D6 to D7.

I executed several upgrades from minor release of D7.

jantoine’s picture

jantoine commented

Hmm... Does re-saving the field fix the issue? If it does, perhaps there was an a change in how defaults were stored in the DB at some point, either with this module or with core fields? If re-saving the field does not fix the error, than I am wrong in assuming that only mis-configured defaults are the cause of the error.

dimon00’s picture

dimon00 commented

Of late I'm not getting the error anymore.
But I had to change the link field in a text field in my main node type.

I still have a link field in another node type and I still believe it doesn't interact very well with the fivestar module.

The problem is definitely in the database. Sometimes I'm getting the node unpublished or one of my field unset... quiet annoying. :(

jkingsnorth’s picture

jkingsnorth commented
Issue summary: View changes
Status: Postponed (maintainer needs more info) » Closed (fixed)

Sounds like the error was fixed, or fixed itself. The issue can be reopened if anyone else comes across it. Closing since it is an old issue.

zythyr’s picture

zythyr commented

I am having this issue when migrating from D6 to D7. I am unsure if this issue is due to Link module or Migrate. I have posted details on Migrate issue page prior to encountering this issue page: https://www.drupal.org/node/2898474#comment-12191176

Comment #3 fixed the issue for me, however, the solution seems tedious since it requires manually finding those fields and re-saving them.