Stop using the base tag
using the base tag should not be needed and it could create problems when using anchors, especially when they are used to refer to SVG image resources: https://developer.mozilla.org/en-US/docs/Web/SVG/Attribute/xlink:href
At the moment we successfully managed to use SilverStripe without the base tag but that involved extending the Page class with a onBeforeWrite event that appended the absolute path to the src="assets/..." uri generated by tinymce.
Sam Minnée commented
In SilverStripe 4 it's much less important to use the base tag, although we have not yet removed it from default templates or the CMS.
There is work in progress to remove the base tag from the CMS here https://github.com/silverstripe/silverstripe-admin/pull/341 - this might make it in a 4.x release.
Michal Kleiner commented
We're removing it from all our templates anyway, so seeing it gone would only benefit us.
Dominik Beerbohm commented
I'am absolutly against this.
I see how other "cms"-systems works where you have to manually update all database tables before you can move the site from development to live server ...
I never had problems with the base-tag. But what I can say ... some poor programmed bots have.
Colin Richardson commented
I'm out of votes but will comment to offer my support to this, especially as I ran into it this morning. The SVG itself can be dealt with but removing base tag would be a better solution long term.