@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!
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...
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://...
We might want to talk about this issue at the dev meeting (if someone is available to speak to the issue and what needs to be done):
Support SVG in Image Library
https://github.com/...
I know it's a long and difficult job to make Backdrop known and for people to realize the power (and simplicity) of the product. And I think you do a great job.
What I like about Backdrop...
Posted1 day 23 hours ago by Dominique (In Info Veritas) on:
Comments
Here are some issues I would like to talk about or revisit (as time permits) during the Weekly Dev meeting or during the Design/UX meeting.
Better defaults position for breadcrumbs on installation of new sites.
https://github.com/backdrop/backdrop-issues/issues/4113
Config Recipes
* What can we do for the next release?
* How do we promote this? Is this a few feature (in theory, except for a bug it was there before)?
https://github.com/backdrop/backdrop-issues/issues/3763
Add a 'User: compare' visibility rule
Is this a good feature for core? Can we get it working for this release?
https://github.com/backdrop/backdrop-issues/issues/4029
This batch of issues
Add a new pageless node above the "Promoted Content" block on Home page
https://github.com/backdrop/backdrop-issues/issues/4849
Provide a new 'hidden-path' content type OOTB, and use it as a content block
https://github.com/backdrop/backdrop-issues/issues/4903
[UX] Change default home page from 'user' to 'node' - if user removes path to home
https://github.com/backdrop/backdrop-issues/issues/3343
A recent update with our long-standing symlink problem: Issue 3008
There's now a simpler alternate approach with less impact. Some core dev eyes are welcome.
The purpose is, to solve the initial problem soon. If people need more elaborated solutions for special cases, this could be a follow-up.