We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Are you experiencing an issue with...
🪲 Description
Since deploying #2441 to production, the 'path' field expects the content not to have a URL base set, but we use one everywhere else:
this doesn't work:
you have to do this to get a preview to render:
This was difficult to pick up on staging because there is no base set.
The text was updated successfully, but these errors were encountered:
Ah, hmm. I mentioned this change in the PR. Local dev looks like production. I didn't realize staging looked so different.
To be honest, I feel like the long URLs everywhere have to go. They make the page look incredibly busy:
I suppose you copied and pasted the example URL into the Path box and expected it to render. Is that right?
If so, I wonder if this can be made clearer. I have an idea about a possible solution.
Reverting the behavior is a possibility too.
Sorry, something went wrong.
Fix for confusing path behavior in modal
301a8fe
Proposed quick and dirty fix for #2495.
After discussing offline we decided to hold off on changing this given the changes in #2496 will wipe out this part of the workflow.
No branches or pull requests
Are you experiencing an issue with...
🪲 Description
Since deploying #2441 to production, the 'path' field expects the content not to have a URL base set, but we use one everywhere else:
this doesn't work:
you have to do this to get a preview to render:
This was difficult to pick up on staging because there is no base set.
The text was updated successfully, but these errors were encountered: