Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Thomas Beckert 193 posts 469 karma points
    Aug 30, 2016 @ 09:56
    Thomas Beckert
    0

    invalid date although it is valid

    Hi,

    we use umbraco 7.2.8 and the newsletter studio. As I want to schedule a sending, i get an error message, that the date is not valid.

    We use German as default language. Might this be the problem? German date format does not work either by the way.

    Any idea?

    enter image description here

  • Markus Johansson 1918 posts 5785 karma points MVP c-trib
    Aug 30, 2016 @ 14:50
    Markus Johansson
    0

    Hi!

    The date looks good to me, what version of Newsletter Studio are you running? I know that there was some issues with the date picker after a breaking change in the Umbraco core.

    Does the date validate correct in other parts of Umbraco? (ie. the publish dates etc on a node?)

    http://support.newsletterstudio.org/customer/en/portal/articles/1053104-change-log

  • Thomas Beckert 193 posts 469 karma points
    Aug 30, 2016 @ 14:54
    Thomas Beckert
    0

    Hi,

    yes, on the publish at date picker, it works fine. We run v2.1.0 of newsletter studio.

  • Markus Johansson 1918 posts 5785 karma points MVP c-trib
    Sep 02, 2016 @ 12:33
    Markus Johansson
    0

    Hi!

    I've tested this on multiple versions of Umbraco 7 and can't reproduce it. Just tested with v7.3 and v7.5 and it works.

    Would an Umbraco upgrade be an option for you?

    // m

  • Thomas Beckert 193 posts 469 karma points
    Sep 08, 2016 @ 14:54
    Thomas Beckert
    0

    Hi,

    I'll try to run an update this weekend. Let you know the result as soon as I figure out. :)

  • Thomas Beckert 193 posts 469 karma points
    Oct 05, 2016 @ 19:03
    Thomas Beckert
    0

    Hi, Markus,

    sorry for my late feedback. I couldn't run the update earlier.

    Here the result:

    Update 7.2.8 to 7.3.5 -> same error. Update 7.3.5 to 7.4.3 -> error vanished.

    So with version 7.4.3 everything is fine now. :)

    Thnx for your help.

    Best regards -

    Tom

  • Thomas Beckert 193 posts 469 karma points
    Oct 06, 2016 @ 06:20
    Thomas Beckert
    0

    Hi, Markus,

    me again. I just noticed that in the send-option, I cannot choose membergroups anymore. Is this a know bug?

  • Markus Johansson 1918 posts 5785 karma points MVP c-trib
    Oct 06, 2016 @ 07:20
    Markus Johansson
    0

    Hi!

    Thanks for sharing the result with your upgrade.

    No that should work! Do you see the options or are they gone? What happens? Are you on Umbraco 7.4.3 and Newsletter Studio 2.1.0?

    // m

  • Thomas Beckert 193 posts 469 karma points
    Oct 06, 2016 @ 07:25
    Thomas Beckert
    0

    The options are just gone. I can only check Newsletterstudio groups. I'm on 7.4.3 and Studio 2.1.5

  • Markus Johansson 1918 posts 5785 karma points MVP c-trib
    Oct 06, 2016 @ 07:41
    Markus Johansson
    0

    Sounds like something is wrong with the providers?

    Did you change anything in the /config/newsletterStudio.config?

    Do you see any errors in the log och trace log?

    If you made an upgrade chances are that you are on the "UmbracoLegacySubscriptionProvider"?

    <subscriptionProviders>
                <provider name="NewsletterStudioSubscriptionProvider" type="NewsletterStudio.Bll.Providers.NewsletterStudioSubscriptionProvider, NewsletterStudio" />
                <provider name="UmbracoLegacySubscriptionProvider" type="NewsletterStudio.Bll.Providers.UmbracoLegacySubscriptionProvider, NewsletterStudio" />
            </subscriptionProviders>
    

    You might need to change that to:

     <subscriptionProviders>
                    <provider name="NewsletterStudioSubscriptionProvider" type="NewsletterStudio.Bll.Providers.NewsletterStudioSubscriptionProvider, NewsletterStudio" />
                    <provider name="UmbracoNewSubscriptionProvider" type="NewsletterStudio.Bll.Providers.UmbracoNewSubscriptionProvider, NewsletterStudio" />
                </subscriptionProviders>
    

    Give that a try and let me know =D

    // m

  • Thomas Beckert 193 posts 469 karma points
    Oct 06, 2016 @ 07:53
    Thomas Beckert
    0

    I added the UmbracoLegacySubscriptionProvider and then, it works again. :)

  • Thomas Beckert 193 posts 469 karma points
    Oct 06, 2016 @ 07:58
    Thomas Beckert
    0

    I removed the Provider again and it still works, so I guess it was kind of cache issue. Thanks for your help again.

  • Markus Johansson 1918 posts 5785 karma points MVP c-trib
    Oct 06, 2016 @ 08:12
    Markus Johansson
    0

    Great!

    Question: Did you have the UmbracoNewSubscriptionProvider or was it only the NewsletterStudioSubscriptionProvider in the config?

    // m

  • Thomas Beckert 193 posts 469 karma points
    Oct 06, 2016 @ 08:14
    Thomas Beckert
    0

    This is the current code:

       <subscriptionProviders>
      <clear />
      <provider name="NewsletterStudioSubscriptionProvider" type="NewsletterStudio.Bll.Providers.NewsletterStudioSubscriptionProvider, NewsletterStudio" />
      <provider name="UmbracoNewSubscriptionProvider" type="NewsletterStudio.Bll.Providers.UmbracoNewSubscriptionProvider, NewsletterStudio" />      
    

  • Markus Johansson 1918 posts 5785 karma points MVP c-trib
    Oct 06, 2016 @ 08:16
    Markus Johansson
    0

    Thanks! I understnad!

    But did you have the UmbracoNewSubscriptionProvider there before you added the UmbracoLegacySubscriptionProvider?

    I'm trying to figure out if the UmbracoNewSubscriptionProvider has any issues?

    If you had that in your configuration and it did not work then I need to look at it but if you only had the UmbracoNewSubscriptionProvider in your config that explains why you did not see any member groups.

    // m

  • Thomas Beckert 193 posts 469 karma points
    Oct 06, 2016 @ 08:21
    Thomas Beckert
    0

    No, this code above was the code during it didn't worked. I added the Legacy Provider, refreshed, it worked, I removed the Legacy Provider, it still worked. So my guess was that cache issue.

Please Sign in or register to post replies

Write your reply to:

Draft