Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
shortcut.module
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
16 Apr 2014 at 17:13 UTC
Updated:
27 Feb 2015 at 20:54 UTC
Jump to comment: Most recent
Comments
Comment #1
Anonymous (not verified) commentedAfter playing around with this for a bit, I think the issue has more to it than described in the initial post. Failed saving after reordering seems to be a side effect. The reproduction steps are valid, but the reordering is unneeded.
Any link with an empty path "" or the frontpage path "<front>" causes the shortcut set overview page to fail when saving all links using the "Save changes" button.
In shortcut_valid_link() a comment states that empty and front page links are valid for shortcuts. But when saving the list page, Url::createFromPath() is called and tries to resolve the "empty" link which off course fails.
When using "<front>" as path, a similar issue occurs. It seems like the "<front>" link is not properly read from the database, and becomes an empty string when evaluating the shortcut. I'm not sure if this should be a seperate issue though.
Comment #2
wim leersThis is being fixed as part of #2242535: Saving a shortcut set with empty or <front> link fails with an error.
Comment #3
Anonymous (not verified) commented@Wim Leers: your link points to this page. Could you correct it?
Comment #4
wim leersHah, oops!
I meant to link to #2235457: Use link field for shortcut entity — sorry!
Comment #5
wim leersAt the very least, this is postponed on #2235457: Use link field for shortcut entity. Once that lands, we should verify that it's indeed fixed, and if so, close this issue.
Comment #6
Anonymous (not verified) commentedAdding an empty path is no long possible, since the validation stops that. Using now works as expected by linking to the homepage.
If someone can verify this, we can close the issue.
Comment #7
dawehnerQuickly manually tested it and it seemed alright for me. Awesome.