I just tried to toy around with Articulate on Umbraco Cloud.
I went about things as follows:
Create an Umbraco Cloud Project
Create a local copy of that project using UaaS.cmd
Install Articulate from the package repository in the back-office of the local copy
Create some DocTypes and content
Commit everything in the .Web repo and push to Umbraco Cloud
Transfer the local content to live
On the local copy, the dropdown for the Theme of Articulate works fine:
On the Live instance, it does not:
Likewise, the pages for the Articulate blog render fine on the local copy but on the Live copy, I run into 'No template for this page' errors, even though the them files themselves are committed and pushed correctly... When I clone the project again, the themes are really there.
I do not believe this has anything to do with property value converters as the umbrage versions between the local and live copy are the same.
Interestingly, when I create a new Visual Studio solution using UaaS.cmd, and run that locally, the dropdown suddenly also became non-functional.
I experienced this issue because for some reason, the Articulate binaries were not transferred from my local copy to the live environment as outlined here.
Articulate on Umbraco Cloud: theming issue
I just tried to toy around with Articulate on Umbraco Cloud.
I went about things as follows:
UaaS.cmd
.Web
repo and push to Umbraco CloudOn the local copy, the dropdown for the Theme of Articulate works fine:
On the Live instance, it does not:
Likewise, the pages for the Articulate blog render fine on the local copy but on the Live copy, I run into 'No template for this page' errors, even though the them files themselves are committed and pushed correctly... When I clone the project again, the themes are really there.
I do not believe this has anything to do with property value converters as the umbrage versions between the local and live copy are the same.
Interestingly, when I create a new Visual Studio solution using
UaaS.cmd
, and run that locally, the dropdown suddenly also became non-functional.What could be happening?
I experienced this issue because for some reason, the Articulate binaries were not transferred from my local copy to the live environment as outlined here.
No issue with Articulate :)
is working on a reply...