Closed (fixed)
Project:
Link
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
2 Mar 2011 at 06:41 UTC
Updated:
1 Mar 2012 at 13:40 UTC
Jump to comment: Most recent file
I get this error after the update.
Notice: Array to string conversion in _link_sanitize() (line 447 of /home/htdocs/bamboo_apps/pub/sites/all/modules/link/link.module).
.
I have tried latest dev version, I have tried uninstall and database update but nothing helped to stop displaying this error! (Still trying different ways to find out a solution).
If any one could help, would be greatly appreciated.
Thanks in advance.
| Comment | File | Size | Author |
|---|---|---|---|
| #10 | link-issue-1078254-10-rel-attribute-converted-to-array.diff | 2.3 KB | alan d. |
| #1 | link-error.png | 25.93 KB | Bright Web Design |
Comments
Comment #1
Bright Web Design commentedI found the solution for the issue. It was because of the change in the structure of the latest updated version of the link module.
Please see the attached screen shot to understand what I say.
Now it's a headache for me to rewrite all the links I have made.
I hope this info will others who come up with same issue.
Best Wishes
Comment #2
modulist commented+1 subscribing. We're running into the same issue on two sites currently in development, with hundreds of nodes already imported into each one.
Comment #3
jcfiala commentedChanging the issue title - the problem isn't so much the Notice, as the fact that I moved things around and didn't produce a proper hook_update_N implementation to move the data.
Comment #4
jcfiala commentedThis shouldn't require changing the link data, just the field data. That being said, I've created an update hook in link.install and comitted it just now - sometime soon (tomorrow?) you should be able to pull down the 7.x-dev version and run that. Let me know how that works, please.
Comment #5
modulist commentedThanks for trying... I tried swapping out the 7.x.dev version and running update.php. I'm still getting an error, but on line 449 now:
Comment #6
jcfiala commentedWell, we need to change the Status if that didn't work. Hmm.
Comment #7
jcfiala commentedmodulist, can you get me what's in field_config and field_config_instance for the field in question? The status of the fields after you've run the update would be great, although if you can also let me know what were in these fields before an after the update that would be useful for seeing what's going on in your code.
Also, what are you doing when you get the error? Viewing the node? submitting the node?
Thanks.
(Anyone else having this same error, after pulling down the latest code and running the update, that would be useful as well to get your data.)
Comment #8
dqdsince this issue is almost half a year old I close it since somebody can reproduce the error in latest dev release ...
Comment #10
alan d. commentedI'm not fully sure if this is a upgrade issue. We are getting this on new sites that only runs on 7.x-1.0. Tracking down the error link, it is the rel attribute and a piece of code that is not working.
So in link_field_prepare_view() prior to _link_sanitize() we have an $item:
afterwards we have:
Internally, we have this:
which should be
This is not an issue on most sites as field_attach_prepare_view() will only be called once. On sites that have multiple calls (this is normal), the 'rel' is an array second time through and the warning is triggered.
Comment #11
alan d. commentedUpdating the title to the only issue that appears to remain.
Comment #12
dqdAlan D.,
this should be solved with this issue #1441702: Rel attribute should have an option to get automaticly turned on/off if link is internal/external
Comment #13
dqd