I had created a custom SubscriptionProvider where I needed to implement
public override bool Unsubscribe(string email, string listItemId)
before I could build.
And I had created a custom SubscriptionForm but still used the default macro. The settings on the macro was overwritten when upgraded, but that was solved by just selecting the correct .cshtml after update.
That's true! There is a breaking change in 2.1.0 that is related to subscription providers.
The thing is that the Umbraco installation-pipeline (scripts) has its limits and the best way to stay safe is to rename the macro and the files after installation.
I just want to add to the discusssion that even with v2.1.1 (one i received from markus via email just to double confirm its indeed the latest version), near the end of a big batch of send the error is thrown as below. This occurs rather inconsistently; i.e. if i send to the same batch list the same email at another time I dont get this error and it completes without any errors.
I am not sure what can be done but this is extremely important with un-attended scheduled sends;
Example case:
at 2060 of 26889 mark:
Error message:
NewsletterStudio, SendNewsletterService: There is already an open DataReader associated with this Command which must be closed first. : at System.Data.SqlClient.SqlInternalConnectionTds.ValidateConnectionForExecute(SqlCommand command)
at System.Data.SqlClient.SqlCommand.ValidateCommand(String method, Boolean async)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
at System.Data.SqlClient.SqlCommand.ExecuteDbDataReader(CommandBehavior behavior)
at System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader()
at NewsletterStudio.Infrastucture.Data.PetaPoco.Database.
Just to clarify, this is on and off. I get an error in test1 (same email, same recipient lists; i.e no changes) and i dont get an error in test2 or test3.
It appears on test4, but i cant reproduce on test5,6,7..
The sending tests on real SMTP with average size of 25-30K recipient lists.
Environment:
Using MSSQL2008 R2 on Windows 2008 R2 x64
The dll is the 2.1.1 - one you send via e-mail just to double confirm.
Upgrade from 2.0.0 to 2.1.1
I'm having some issues when sending newsletters to 2k+ subscribers. I get this error:
I can see in the forum, that I'm not the first, and that there is a bug, that shoud be fixed in the latest version.
What should I do to upgrade from 2.0.0 to 2.1.1 + Just install the package, or should I do any other preparations ?
Can't seem to find a guide on how to upgrade
Hi!
Are you on version 2.0.0 right now an planing to upgrade?
There is an article about this in our support-forum:
http://support.newsletterstudio.org/customer/en/portal/articles/1460096-from-version-1-3-3-to-higher
Just run the new installer over the old installation and you should be good to go.
Cheers!
I was on a 2.0.0. Now I'm on 2.1.1 :-)
I had created a custom SubscriptionProvider where I needed to implement
before I could build.
And I had created a custom SubscriptionForm but still used the default macro. The settings on the macro was overwritten when upgraded, but that was solved by just selecting the correct .cshtml after update.
Hi!
That's true! There is a breaking change in 2.1.0 that is related to subscription providers.
The thing is that the Umbraco installation-pipeline (scripts) has its limits and the best way to stay safe is to rename the macro and the files after installation.
Hope that you got everything to work?
// m
I just want to add to the discusssion that even with v2.1.1 (one i received from markus via email just to double confirm its indeed the latest version), near the end of a big batch of send the error is thrown as below. This occurs rather inconsistently; i.e. if i send to the same batch list the same email at another time I dont get this error and it completes without any errors.
I am not sure what can be done but this is extremely important with un-attended scheduled sends;
Example case: at 2060 of 26889 mark:
Hi!
This is related to the PetaPoco-implementation used and we have not been able to reproduce this error again after our fixes.
We need to look into your exact environment to narrow down what the problem is. Could you send me a PM?
Cheers!
// m
Just to clarify, this is on and off. I get an error in test1 (same email, same recipient lists; i.e no changes) and i dont get an error in test2 or test3.
It appears on test4, but i cant reproduce on test5,6,7..
The sending tests on real SMTP with average size of 25-30K recipient lists.
Environment: Using MSSQL2008 R2 on Windows 2008 R2 x64 The dll is the 2.1.1 - one you send via e-mail just to double confirm.
is working on a reply...