I like the neatness of the first screenshot that @jenlampton proposed on #1321 (comment).
Placing the same warning message twice on the search settings form:
and then again on the confirm page:
looks really too excessive.
I do understand the initial concern for some people who could press the button without realizing the consequences. However, in fact the consequences are not so scary, because (1) no data is lost anyway and then (2) those who pressed the button will see the warning on the confirm page anyway.
Making the button outstanding with the scary text in red color was sufficient enough, so if possible please remove the description text.
Recent comments
Hi patch-works I did something similar with Drupal 7: a block with aniversaries of historical dates. You can see it at https://lassalle-kreis.de/ down in the blue footer, the middle column...
How to get a list of upcoming birthdays?
@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