Install issues about articulate HOT 12 CLOSED

You'll get that error for a lot of packages. I've tested numerous times and it completes. If you have errors in your log file, please post them.

from articulate.

Have tested again on UaaS as well and the installation worked. .. though there was a hiccup with UaaS which I've never seen before.

from articulate.

I have the following warnings:

2014-06-23 12:43:09,758 [26] WARN Umbraco.Core.PropertyEditors.LegacyPropertyEditorIdToAliasConverter - [Thread 19] A legacy GUID id was generated for property editor ArticulateThemePicker. This occurs when the legacy APIs are used and done to attempt to maintain backwards compatibility. Consider upgrading all code to use the new Services APIs instead to avoid any potential issues.
2014-06-23 12:43:10,408 [26] WARN Umbraco.Core.PropertyEditors.LegacyPropertyEditorIdToAliasConverter - [Thread 19] A legacy GUID id was generated for property editor Umbraco.ImageCropper. This occurs when the legacy APIs are used and done to attempt to maintain backwards compatibility. Consider upgrading all code to use the new Services APIs instead to avoid any potential issues.
2014-06-23 12:43:11,875 [26] WARN Umbraco.Core.Services.PackagingService - [Thread 19] Packager: Error handling allowed templates. Template with alias 'ArticulateList' could not be found.
2014-06-23 12:43:11,940 [26] WARN Umbraco.Core.Services.PackagingService - [Thread 19] Packager: Error handling default template. Default template with alias 'ArticulateList' could not be found.
2014-06-23 12:43:12,718 [26] WARN Umbraco.Core.Services.PackagingService - [Thread 19] Packager: Error handling allowed templates. Template with alias 'ArticulatePost' could not be found.
2014-06-23 12:43:12,780 [26] WARN Umbraco.Core.Services.PackagingService - [Thread 19] Packager: Error handling default template. Default template with alias 'ArticulatePost' could not be found.
2014-06-23 12:43:14,187 [26] WARN Umbraco.Core.PropertyEditors.LegacyPropertyEditorIdToAliasConverter - [Thread 19] A legacy GUID id was generated for property editor Articulate.MarkdownEditor. This occurs when the legacy APIs are used and done to attempt to maintain backwards compatibility. Consider upgrading all code to use the new Services APIs instead to avoid any potential issues.

from articulate.

Just repeated and i got further, but no js installed:

Could not find a part of the path 'C:...\App_Plugins\Articulate\Themes\VAPOR\Assets\js'.

from articulate.

That is very strange!

from articulate.

Hrm, actually that is because there is no JS in the Vapor theme, where do you get this error?

from articulate.

i'm on a different PC today, still initial install through WebMatrix.

Will try again later with no WebMatrix, see if it is any different. I'll keep you posted.

from articulate.

The JS error might just be a template problem, not sure. Try removing this line in the Master.cshtml of the Vapor theme:

//This loads all JS found in the current theme's js folder: /Assets/js
.RequiresThemedJsFolder(Model);

Since there is no js to load anyways for that theme.

from articulate.

Yup, i think that's the cause. If you remove that line you should be in business. I'll deploy a new package tonight/tomorrow.

from articulate.

Fixed in 22d6314

from articulate.

That's great - now working.

Quick question: should the templates be in the settings section of umbraco? i found them in the App_plugins..., but had expected them in settings.

from articulate.

@fergusdavidson Articulate is based on themes and they work based on theme folders, therefore the views cannot simply exist in the standard view folders because they need to exist in specific sub folders. We can create an Articulate theme file tree in the back office if people want to edit them in the back office.

from articulate.