The stacked content backoffice previews I've created work fine when the document is published. However when I unpublish a document the previews no longer work. Instead I get the following error come up in the overlay on the right hand side:
Unhandled controller exception occurred System.UriFormatException: Invalid URI: The format of the URI could not be determined.
It's not mega urgent (plus I'm not 100% sure of what I'm looking at when I go to the appveyor link you've supplied), so I'll wait for the patch then try it out.
EDIT: Just downloaded the latest version on GitHub, did a rebuild and copied the dll across to my project. Problem Solved!
I've just got this same error for a site using v2.04 on Azure? Works fine locally, as soon as I push to azure it's throwing this error? Views/files are all present and it's an exact copy of the local version? Any ideas on where I should start debugging this?
Previews don't load when page is unpublished
Hi,
The stacked content backoffice previews I've created work fine when the document is published. However when I unpublish a document the previews no longer work. Instead I get the following error come up in the overlay on the right hand side:
Is anyone else able to replicate this issue?
Cheers, Gavin
Hiya Gavin, let us know which version of Stacked Content and Umbraco, and I'll try to take a look.
Thanks,
- Lee
Hi Lee,
Umbraco 7.12.3 and Stacked Content 2.0.3
Cheers, Gavin
Hi Gavin,
I've been able to reproduce the bug. I've raised a ticket on our GitHub repo here: https://github.com/umco/umbraco-stacked-content/issues/66
The bug was introduced in Stacked Content v2.0.2. I'm looking into a fix.
Thanks,
- Lee
Good news is that I've fixed the bug. I'll get around to releasing a patch version later this week. For now if you need a copy, it's available from here: https://ci.appveyor.com/project/UMCO/umbraco-stacked-content/build/artifacts
Awesome. Thank you for such a fast turnaround!
It's not mega urgent (plus I'm not 100% sure of what I'm looking at when I go to the appveyor link you've supplied), so I'll wait for the patch then try it out.
EDIT: Just downloaded the latest version on GitHub, did a rebuild and copied the dll across to my project. Problem Solved!
Cheers,
Gavin
I've just encountered this error, running Umbraco v7.14.0 and Stacked Content v2.0.3 (which is currently the latest on nuget)
@Lee do you know when v2.0.4 might get released?
Hey Chris, this completely fell off my radar. I'll aim to get a patch release out towards the end of this week.
Hi Chris,
Stacked Content v2.0.4 has been released: https://github.com/umco/umbraco-stacked-content/releases/tag/2.0.4
...and there's a patch release for Inner Content too: https://github.com/umco/umbraco-inner-content/releases/tag/2.0.4
Enjoy!
Cheers,
- Lee
Superb! Will update ASAP.
Awesome thanks Lee! Is there somewhere I can subscribe to release notifications?
Hey Chris, yes - you can subscribe to the Release notifications on the GitHub repo: https://github.com/umco/umbraco-stacked-content
I've just got this same error for a site using v2.04 on Azure? Works fine locally, as soon as I push to azure it's throwing this error? Views/files are all present and it's an exact copy of the local version? Any ideas on where I should start debugging this?
Hey Lee!
This is where it seems to be failing, when trying to create a new
Urifor thePublishedContentRequest...https://github.com/umco/umbraco-stacked-content/blob/2.0.4/src/Our.Umbraco.StackedContent/Web/Controllers/StackedContentApiController.cs#L46
Which suggests that the
pageUrlvariable doesn't contain an absolute URL.I'm not sure why that would be. (I don't know enough about Azure to make an educated guess, sorry).
Cheers,
- Lee
The only thing that springs to mind is the
/umbraco/web.routing/urlProviderModeoption in "/config/umbracoSettings.config".https://our.umbraco.com/Documentation/Reference/Routing/Request-Pipeline/outbound-pipeline-v7#url-provider-mode
Thanks bud. I'll have a dig around.
I'm wondering if this is something to do with the umbraco addTrailingSlash option in the umbracoSettings.
I've just pushed to staging and it works fine, my staging pushes to 3 other sites. First two work fine, last one has
The others are true.
So my issue was user error and down to one of my custom UrlProvider's looking for a value in the umbracoUrlAlias and changing the url 🤦🏻♂️🤦🏻♂️
No worries. Glad you figured it out! :-)
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.