We have moved to GitHub Issues
Created by Funka! 14 Sep 2012, 18:18:38 Updated by Funka! 22 Nov 2013, 22:45:40
Is duplicated by: U4-2574
Relates to: U4-2593
Relates to: U4-2587
Relates to: U4-3631
Sometimes content nodes are used as "data" sub-nodes, not actual pages with actual public URLs. In fact, trying to preview or surf to any node that does not have a template will just result in a 404.
My recommendation to reduce confusion for the editors/end-users is to hide or grey-out the Preview button and the "Link to Document" hyperlink when it is should already be known ahead of time by the back-office that trying to do this will just result in an error!
Attached is a screenshot showing one idea of how this might look (with my mouse hovering over the greyed-out preview button so you can see the title/tooltip). In this example, we only have a "Staff" page and template, but use sub-nodes for each staff member which are all shown on one single page. (And thus don't have their own pages or templates.)
I'd probably also recommend totally hiding the empty "Choose..." select box for the template when there aren't any to choose from, and instead just show the note you see that I added saying "No templates defined." Thank you for this consideration!
Grabbed by top table
Seems that there's still a link created on 4.11.8 but the preview button has been disabled though.
In 6.0.5 the preview button does not appear to be disabled and a link to the node is created even though it has not assigned template.
Think this should be reopened perhaps?
I'm the guy who created this feature request, and although the preview button did get disabled, there was always the linked URL which still causes confusion for our clients which I had hoped would be maybe a greyed-out path, not something the client can click on. (See the attached screenshot showing my idea on this.) Would love to re-open this since it perhaps was only ever half completed? (Still better than nothing, though!)
Confirmed that the preview button has regressed in 6.1.1 as well. (And besides, I'm still hoping for the "Link to document" to NOT actually link to document!)
I see this was closed again. Does that mean we will see this fixed in 6.1.2?
Also, is my request to have the hyperlink removed from the "Link to document" denied? (The other half of my original request.) People still click it and get 404's and then call me up to complain, and I have to keep explaining this to them. It seems like bad user-experience to knowingly generate links that can do nothing other than lead to an error page.
Just FYI, still regressed/not working in 6.1.3. Changing from "Fixed" back to "Open".
If not going to fix, let's just say "Won't Fix" instead of fixed?
It was fixed for 4.10.0. I see there's been some kind of a regression though, for which I opened issue U4-2587.
@Funka: FYI issues with a "Due in version" that should stay closed if the version is released. I'll be looking at a way to lock issues like that. Just create a new issue that relates to this one and we're all good. As for the link to the document, please create a new feature request for this.
Totally understand about issues here with a set "Due in Version". Regarding creating a new issue for the "Hide Link to Document" I will do that too. However, if you'll note, that was always the intention of this issue (please note the title does say exactly this, and is mentioned in description and mockup screenshot.) It's just it never got completed 100% of the way in my opinion, only 50%. In any case, thanks for looking into this and taking care of it!
Type: Feature (request)
Backwards Compatible: True
Affected versions: 4.10.0
Due in version: 4.10.0