You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
BugEither a bug report, or a bug fix. Let's hope for the latter!FeedbackWaiting on the submitter for answersSymbologyRelated to vector layer symbology or renderers
Author Name: Patrick Dunford (@enzedrailmaps)
Original Redmine Issue: 17707
Affected QGIS version: master
Redmine category:symbology
This seems to be an enduring problem or not well documented in Qgis that I can ever remember but it seems to have been working properly in earlier masters and stopped working again in later ones.
I have found almost consistently except for this rare period when it actually worked that every time I set up a new installation of Qgis and load the styles into Style Manager that my styles which have a custom SVG symbol have the symbols missing and I have to every single time go through and add these symbols back to the styles manually.
With a style file like the attached loading it in master 313ec55 will find all the custom SVGs and load them straight off from the xml file, the later masters e.g. the current one will not.
Just to make it even more complex I have some layers with rule based styles, these will not remember the custom SVGs so every time I open a project for the first time after installing Qgis I have to go through and set all these by hand as well.
Given there is a path stored to the SVG file inside the XML file for each style it can't be that hard surely?
Please check if this issue is still valid on QGIS 3.4.5 or 3.6.
status_id was changed from Open to Feedback
qgib
added
Feedback
Waiting on the submitter for answers
Bug
Either a bug report, or a bug fix. Let's hope for the latter!
Symbology
Related to vector layer symbology or renderers
labels
May 25, 2019
@enzedrailmaps path must be absolute or relative to "/usr/share/qgis/svg/" (or whatever is the folder where the QGIS installer places the SVG symbols in your system).
The QGIS project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale".
If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue.
In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue.
If there is no further activity on this issue, it will be closed in a week.
BugEither a bug report, or a bug fix. Let's hope for the latter!FeedbackWaiting on the submitter for answersSymbologyRelated to vector layer symbology or renderers
Author Name: Patrick Dunford (@enzedrailmaps)
Original Redmine Issue: 17707
Affected QGIS version: master
Redmine category:symbology
This seems to be an enduring problem or not well documented in Qgis that I can ever remember but it seems to have been working properly in earlier masters and stopped working again in later ones.
I have found almost consistently except for this rare period when it actually worked that every time I set up a new installation of Qgis and load the styles into Style Manager that my styles which have a custom SVG symbol have the symbols missing and I have to every single time go through and add these symbols back to the styles manually.
With a style file like the attached loading it in master 313ec55 will find all the custom SVGs and load them straight off from the xml file, the later masters e.g. the current one will not.
Just to make it even more complex I have some layers with rule based styles, these will not remember the custom SVGs so every time I open a project for the first time after installing Qgis I have to go through and set all these by hand as well.
Given there is a path stored to the SVG file inside the XML file for each style it can't be that hard surely?
The text was updated successfully, but these errors were encountered: