When I'm creating a path alias for a content type, I often get tripped up by the really long list of field tokens. If the list were only to contain the field tokens that would actually work for this content type, the experience of using the token browser would increase.
Additionally, we'd avoid the confusing thing that happens when you select a token that does not work for that content type, and then wonder why the pattern isn't working properly.
Recent comments
@indigoxela - I agree, I mentioned the SVG topic specifically for the dev meeting. I think we'll definitely want Nate involved in that discussion. Good call!
Apr 18th Weekly Meetings
Hi colbyat, re display in the browser: the problem is that when a 500 occurs, this PHP process died before being able to render anything. So that won't work. Logging is possible, but...
Displaying 500 errors
SVG's are a great topic for the design meeting, but also for the dev meeting. Two currently active issues related to SVG overlap a bit when it comes to security aspects. https://...
Apr 18th Weekly Meetings