(Don't know if this is a feature request or a bug)
When deploying using custom base URL, there is no error handling. The user can enter whatever string they want, but strange errors will occur if the string does not follow a certain pattern.
The pattern I realized works looks like this:
the string needs to start with https://
the string needs to end with /
If these steps aren't followed, the url can look like this:
In this case I had only written "/hem" as my custom base URL, which Noodl let me do. This caused the crazy url in the picture and that certain pictures did not build properly. It seemed as if a new /hem// was added every time i refreshed the page.
Noodl might be doing checks for .se or .com url's and that this bug only appeared because I'm using a .io url.
It would be helpful to have error messages in the custom base URL text field that make sure the two steps above are followed.
(I'm using URL path type Hash if that makes a difference)
(Don't know if this is a feature request or a bug)
When deploying using custom base URL, there is no error handling. The user can enter whatever string they want, but strange errors will occur if the string does not follow a certain pattern.
The pattern I realized works looks like this:
If these steps aren't followed, the url can look like this:
In this case I had only written "/hem" as my custom base URL, which Noodl let me do. This caused the crazy url in the picture and that certain pictures did not build properly. It seemed as if a new /hem// was added every time i refreshed the page.
Noodl might be doing checks for .se or .com url's and that this bug only appeared because I'm using a .io url.
It would be helpful to have error messages in the custom base URL text field that make sure the two steps above are followed.
(I'm using URL path type Hash if that makes a difference)