Upon upgrading from 7.x-1.0-alpha2 to -alpha3 I now receive multiple link_sanitize errors on the frontpage and on individual nodes using the link field. A selection of the messages follows:
Notice: Undefined index: enable_tokens in _link_sanitize() (line 355 of /home/mysite/public_html/sites/all/modules/link/link.module).
Notice: Undefined index: display in _link_sanitize() (line 388 of /home/mysite/public_html/sites/all/modules/link/link.module).
Notice: Undefined index: title in _link_sanitize() (line 394 of /home/mysite/public_html/sites/all/modules/link/link.module).
Notice: Undefined index: title in _link_sanitize() (line 406 of /home/mysite/public_html/sites/all/modules/link/link.module).
Notice: Undefined index: enable_tokens in _link_sanitize() (line 406 of /home/mysite/public_html/sites/all/modules/link/link.module).
Notice: Undefined index: attributes in _link_sanitize() (line 425 of /home/mysite/public_html/sites/all/modules/link/link.module).
I notice something like this problem appeared earlier in 7.x-dev, but reportedly was solved. (http://drupal.org/node/948628)
I did try updating php upon upgrade, but received a no pending upgrades message.
Any suggestions on how to deal with this?
Thank you.
Comments
Comment #1
jcfiala commentedHm. That is weird.
There weren't any changes in update.php, no. Try going through the settings for the field and set it up again. I'm sorry - this is still very much alpha software, and I'm more interested in getting the software to do what it's supposed to do and not as much watching for problems with breaking compatibility.
Actually, before that, try clearing cache if you haven't already.
Comment #2
femrich commentedClearing the cache seems to have made the messages disappear, thanks. Unfortunately, now I get this:
Notice: Object of class stdClass could not be converted to int in _menu_router_build() (line 3464 of /home/mysite/public_html/includes/menu.inc).This does not look like an issue with link field to me: It looks like perhaps with core menu to me, (though a quick search turned up nothing so far). Does it look like a core menu issue to you?
Thanks.
Comment #3
jcfiala commentedHm. Odd.
I don't have a copy of 7 I can really dig into here. Try clearing the cache a second time - it may help, I couldn't say. core menu could cover a lot of things, and theoretically the problem could still be in link, although I'm not sure how.
Comment #4
tim.plunkettBetween Alpha2 and Alpha3, link_field_info() was now has ['settings']['attributes'] = array(). Views chokes on this, because it calls filter_xss_admin() on each of the children of ['settings'].
Comment #5
jcfiala commentedWell, I think that's an error on View's side than an error on mine, although I'm willing to see documentation that we're not allowed to have arrays in settings there.
Comment #6
queryblitz commentedConfirming: clearing the cache fixes it.
Comment #7
femrich commentedClearing the cache did work for me to remove the initial error, but not the subsequent error. Still have not found the source of that error message, and could not say it is necessarily a link issue.
Comment #8
jcfiala commentedFair enough, femrich - let me know what you discover.
For the moment I'll park this issue at postponed (maintainer needs more info).
If you've just found this thread and you're having the issue in the issue body, the solution seems to be to clear all caches.
Comment #9
femrich commentedFound a thread addressing the menu router problem here (http://drupal.org/node/972536). This indicates the issue there may be related to interactions between core and nodequeue (though no clear solutions yet). It may be a coincidence that the problem appeared while I was working on the other Link Module issue, particularly since none of the other folks reporting the initial problem here reported the follow-up menu router issue.
Comment #10
jkingsnorth commentedThis issue was fixed, the caches needed to be cleared.
The subsequent issue does not seem to be part of the Link module. Closing this since it is an old issue.