Articulate Target Post Page showing 404 on Umbraco Cloud Live
Hi All,
Umbraco 8.5.3 - Cloud
Articulate - 4.1.1
One of my colleague had installed Articulate onto our cloud project, it works well on Dev, but it doesn't on Live, the Articulate list page loads alright, but the target blog post / article post are showing 404.
I've checked that all the views from Articulate and binaries are all deployed, content are also deployed from Dev to Live using Umbraco Deploy which is good.
But the target page is still on 404. Any idea?
It feels as if the custom routing for Articulate is not working at all for the blog post page and this is only happening on Umbraco Cloud Live
I've found out what's the issue, on LIVE, there's a culture and hostname settings on Homepage which comes with the live url domain and my Articulate Document Type sits outside this Homepage (or on the same level with Homepage) so it's in 404 all the time.
Upon moving it inside the Homepage, it all works accordingly.
Posting it here just in case other people is having the same issue
Articulate Target Post Page showing 404 on Umbraco Cloud Live
Hi All,
Umbraco 8.5.3 - Cloud
Articulate - 4.1.1
One of my colleague had installed Articulate onto our cloud project, it works well on Dev, but it doesn't on Live, the Articulate list page loads alright, but the target blog post / article post are showing 404.
I've checked that all the views from Articulate and binaries are all deployed, content are also deployed from Dev to Live using Umbraco Deploy which is good.
But the target page is still on 404. Any idea?
It feels as if the custom routing for Articulate is not working at all for the blog post page and this is only happening on Umbraco Cloud Live
Thanks
Anyone facing the same issues with cloud?
i've contacted the cloud support too but they can't seems to figure out what's wrong either.
Thanks
I've found out what's the issue, on LIVE, there's a culture and hostname settings on Homepage which comes with the live url domain and my Articulate Document Type sits outside this Homepage (or on the same level with Homepage) so it's in 404 all the time.
Upon moving it inside the Homepage, it all works accordingly.
Posting it here just in case other people is having the same issue
is working on a reply...