The templates and template parts which contain hard coded links prefixed https://s.b/wp55/thisis/ are acceptable when used in a local development environment but not at all acceptable in a live site. The browser attempts to find s.b and takes an awfully long time. Alternatively, in my local development environment, I may not notice the switch.
Given that this is an experimental theme, and I expect to make many changes to template parts with navigation blocks, it would make sense to automatically adjust any URL starting https://s.b/thisis/ to the siteurl(). This may result in a 404, but that’s OK.
Requirement
- Dynamically adjust the URL prefix for certain hardcoded navigation links
- Change the prefix to siteurl() - or network_url() - whichever is necessary for WordPress Multi Site
Proposed solution
- As already implemented for Fizzie and SB
- But with improvements to cater for Gutenberg’s improvements to the Navigation link’s Server Side Rendering.
The templates and template parts which contain hard coded links prefixed
https://s.b/wp55/thisis/are acceptable when used in a local development environment but not at all acceptable in a live site. The browser attempts to finds.band takes an awfully long time. Alternatively, in my local development environment, I may not notice the switch.Given that this is an experimental theme, and I expect to make many changes to template parts with navigation blocks, it would make sense to automatically adjust any URL starting
https://s.b/thisis/to the siteurl(). This may result in a 404, but that’s OK.Requirement
Proposed solution