In my experience (just now today), Courier 2.7.x isn't yet compatible with Umbraco 4.8. We have several 4.8 sites, then installed Courier 2.7 today which we'd purchased the licenses for awhile back. Crashed in a couple ways, most notably a SQL Insert conflict error. Tried installing fresh on some 4.7.2 sites, no problem.
Haven't yet upgraded existing Courier-enabled sites to 4.8 to test, but definitely wait until some kind of installation bugs are worked out regarding these two.
I would love to see some stacktraces or exceptions thrown by umbraco / courier for these crashes as I have tested against 4.8 during its developement, and just now, after reading your comment also tried transfering a complete site from a 4.8 to another 4.8 site, without any issues or error messages.
So for me to be able to track these things down, I need to get some error info from sites in the wild experiencing this.
Here are the steps I followed testing Courier 2.7.1 (yesterday's build) against 4.7.2 and 4.8.0 brand-new Umbraco sites
install 2 new Umbraco sites (4.7.2), using SQL 2008 databases, via the IIS7 install web package command
upgrade 1 site to umbraco v 4.8.0 (Assembly version: 1.0.4583.15483) per instructions, leave the other 4.7.2
install Courier as "Install local package" from the 2.7.1 download (1st item shown) for each instance
4.7 site accepts the install with no error
4.8 site throws this SQL error (and I'd checked the umbracoApp table, no Courier stuff there of course since new Umbraco site)
Server Error in '/' Application.
The INSERT statement conflicted with the FOREIGN KEY constraint "FK_umbracoUser2app_umbracoApp". The conflict occurred in database "umbraco_deveric", table "dbo.umbracoApp", column 'appAlias'. The statement has been terminated.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.SqlClient.SqlException: The INSERT statement conflicted with the FOREIGN KEY constraint "FK_umbracoUser2app_umbracoApp". The conflict occurred in database "umbraco_deveric", table "dbo.umbracoApp", column 'appAlias'. The statement has been terminated.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Now I can't create locations at all (there is no create option), and I'm getting this error when I try to create a revision:
System.Exception: Database persistence could not be found, please ensure you have a valid connection string and a Umbraco.Courier.Persistence.* dll in your /bin at Umbraco.Courier.Core.PersistenceManager.GetPersistenceProvider(Guid id) at Umbraco.Courier.ItemProviders.DataTypeProvider.AvailableSystemItems() in c:\Program Files (x86)\teamcity\buildAgent\work\872c402d3442319c\Core\Umbraco.Courier.Providers\ItemProviders\DataTypeProvider.cs:line 34 at Umbraco.Courier.RepositoryProviders.Local.GetChildren(ItemIdentifier itemID) in c:\Program Files (x86)\teamcity\buildAgent\work\872c402d3442319c\Contrib\Providers\Umbraco.Courier.RepositoryProviders\Local\Local.cs:line 260 at Umbraco.Courier.RepositoryProviders.Local.GetRootItems(Guid providerID) in c:\Program Files (x86)\teamcity\buildAgent\work\872c402d3442319c\Contrib\Providers\Umbraco.Courier.RepositoryProviders\Local\Local.cs:line 277 at Umbraco.Courier.Core.Packaging.RevisionPackaging.AddToQueue(RevisionManifest manifest) at Umbraco.Courier.Core.Tasks.PackagingTask.Run() at Umbraco.Courier.Core.TaskManager.(IRevisionTask value) 8/2/2012 11:26:53 AM
Getting this error when I create a revision with umbraco 2.6 (also unable to create locations):
System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary. at Umbraco.Courier.Core.ItemProvider.get_DatabasePersistence() at Umbraco.Courier.ItemProviders.DataTypeProvider.AvailableSystemItems() in c:\Program Files (x86)\teamcity\buildAgent\work\b6e7862632b3bd64\Umbraco.Courier.Providers\ItemProviders\DataTypeProvider.cs:line 34 at Umbraco.Courier.Core.Packaging.RevisionPackaging.AddToQueue(RevisionManifest manifest) at Umbraco.Courier.Core.Tasks.PackagingTask.Run() at Umbraco.Courier.Core.TaskManager.(IRevisionTask value) 8/2/2012 11:43:48 AM
I'm now on version Courier_2.7_2.7.0.37.zip with Umbraco 4.8 RTM
I discovered I can actually create a location at the end of the installation, but I can't create any additional locations once I leave the install wizard.
When I create a revision, I am still getting the error:
System.Exception: Database persistence could not be found, please ensure you have a valid connection string and a Umbraco.Courier.Persistence.* dll in your /bin at Umbraco.Courier.Core.PersistenceManager.GetPersistenceProvider(Guid id)
The only persistence dll in my bin folder is Umbraco.Courier.Persistence.V4.NHibernate.dll
Courier 2.7.x and Umbraco 4.8
Has the latest build of Courier 2 been tested in Umbraco 4.8? Does it work?
In my experience (just now today), Courier 2.7.x isn't yet compatible with Umbraco 4.8. We have several 4.8 sites, then installed Courier 2.7 today which we'd purchased the licenses for awhile back. Crashed in a couple ways, most notably a SQL Insert conflict error. Tried installing fresh on some 4.7.2 sites, no problem.
Haven't yet upgraded existing Courier-enabled sites to 4.8 to test, but definitely wait until some kind of installation bugs are worked out regarding these two.
Hi Eric
I would love to see some stacktraces or exceptions thrown by umbraco / courier for these crashes as I have tested against 4.8 during its developement, and just now, after reading your comment also tried transfering a complete site from a 4.8 to another 4.8 site, without any issues or error messages.
So for me to be able to track these things down, I need to get some error info from sites in the wild experiencing this.
/per
Here are the steps I followed testing Courier 2.7.1 (yesterday's build) against 4.7.2 and 4.8.0 brand-new Umbraco sites
Server Error in '/' Application.
The INSERT statement conflicted with the FOREIGN KEY constraint "FK_umbracoUser2app_umbracoApp". The conflict occurred in database "umbraco_deveric", table "dbo.umbracoApp", column 'appAlias'.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.The statement has been terminated.
Exception Details: System.Data.SqlClient.SqlException: The INSERT statement conflicted with the FOREIGN KEY constraint "FK_umbracoUser2app_umbracoApp". The conflict occurred in database "umbraco_deveric", table "dbo.umbracoApp", column 'appAlias'.
The statement has been terminated.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.272
SEE: http://blog.mattbrailsford.com/2012/07/18/creating-custom-applications-and-trees-in-umbraco-4-8/ for an explanation of why this error is happening.
The easiest and least destructive fix is to add the row manually to the table
1) Run this SQL:
2) Uninstall Courier
3) Re-Install Courier
Now I can't create locations at all (there is no create option), and I'm getting this error when I try to create a revision:
I'm going to try Courier 2.6 instead.
Getting this error when I create a revision with umbraco 2.6 (also unable to create locations):
I'm now on version Courier_2.7_2.7.0.37.zip with Umbraco 4.8 RTM
I discovered I can actually create a location at the end of the installation, but I can't create any additional locations once I leave the install wizard.
When I create a revision, I am still getting the error:
The only persistence dll in my bin folder is Umbraco.Courier.Persistence.V4.NHibernate.dll
Deleting datalayer=SqlServer from my connection string seems to have fixed it:
<add key="umbracoDbDSN" value="datalayer=SqlServer;server=vdb01;database=umbraco47;uid=umbraco47user;password=****" />
found the answer here: http://our.umbraco.org/forum/umbraco-pro/courier/32557-Error-running-Courier-related-to-NHibernate
I am running Courier 2.7.1 on Umbraco 4.8.0 and have a couple of issues, but no Exceptions.
@mark
- So if media doesnt deploy to folder, where does it go? to the media root? is the folder present?
- @RenderPage(file.cshtml) isnt supported, courier doesn't parse all cshtml files for internal references
- what settings do you use for mntp, seems they've added new options which isnt support in courier yet
/Per
@Per
Media references in content as an Image was deployed to the root of the media, but Images referenced through a MNTP were not deployed.
The folders were not present in the destination media area.
The setting that was lost on my MNTP was "Start node ID". This property isn't updated if I change it to the root either.
UPDATE: The ids don't match from source to destination. So the start node id points to a different place!
I just tried again and the images picked on a new MNTP are not picked for deployment.
Mark.
is working on a reply...