Copied to clipboard

Flag this post as spam?

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


  • Simon Hebert 22 posts 92 karma points
    Apr 12, 2016 @ 12:48
    Simon Hebert
    0

    Specific Date Recurring Event

    Hi!

    We need to planning yearly recurring events like birthday that occur once a yeat at a specific date. It seem not possible to do this type of configuration for events.

    Do you think this is an option that it could be implement in a near futur release?

    We actually use these versions: EventCalendar v2.3.2 and Umbraco v7.3.7.

    Thanks.

    Simon

  • David Brendel 792 posts 2970 karma points MVP 3x c-trib
    Aug 10, 2016 @ 10:33
    David Brendel
    0

    Hi Simon,

    anniversaries were implemented with v3 of the package.

    Regards David

  • Simon Hebert 22 posts 92 karma points
    Aug 15, 2016 @ 13:49
    Simon Hebert
    0

    Hi David,

    Thank you for the work to implement this fonctionnality!

    I will try this feature.

    Simon

  • Simon Hebert 22 posts 92 karma points
    Aug 18, 2016 @ 21:22
    Simon Hebert
    0

    Hi David,

    What is the best method to upgrade an already installed version of the package (from 2.3.2 to 3.0.0) from a live website? Using the Umbraco Backoffice Package manager or by downloading the file manually and using local package file or another way?

    Also, on the package presentation page, it's writed:

    "Version 3.0.0-RC and above can be used for free on localhost with a trial licence. A license can be purchased via my website http://www.davidbrendel.de soon."

    What this mean, the package will no longer be free? And if so, we cannot buy license for now? If i upgrade to 3.0.0RC, is EventCalendar will work again in my production environnement?

    Thank you for clarifying all these questions before we proceed.

    Simon

  • David Brendel 792 posts 2970 karma points MVP 3x c-trib
    Aug 19, 2016 @ 08:21
    David Brendel
    0

    Hi Simon,

    v3 of the package is a rewrite of the package. The whole infrastructure has changed and also the methods used to handle all the data.

    So upgrading from v2 to v3 won't be easy. And is not done with just doing a package install.

    I don't recomment updating it on a live website! I should make this more clear in the package description. Also as the new versi

    Yes correct, the package will no longer be free and requires now a licence to work on a production environment. So installing it on production without licence won't work.

    I'm currently working hard on updating my package with the shop implementation to provide the possibility to buy the licences. Currently had some trouble with the shop system. :(

    Regards David

  • Simon Hebert 22 posts 92 karma points
    Aug 19, 2016 @ 12:26
    Simon Hebert
    0

    Hi David,

    In your reply, your third sentence is broken to : "Also as the new versi..." I'm interested to know the end :)

    Ok, so I understand that I need to wait to be able to buy a license before installing it in production.

    I understand also that the upgrade process is not automatic and easy. I need to do a complete reinstall of the package? What is the steps you recommend to do? Uninstalling the old version from Umbraco packages, and install the new version from scratch is ok?

    Or uninstalling the old version will leave some old files or database components that will cause problem with the new version?

    Thanks,

    Simon

  • David Brendel 792 posts 2970 karma points MVP 3x c-trib
    Aug 19, 2016 @ 14:01
    David Brendel
    0

    Hi Simon,

    the sentence should be "Also the new version has a new code base."

    Yes thats right. Currently it's not possible to buy one. But I hope I get everything working over the weekend and then also release the final version of v3.

    Yes I would suggest an unistall of the current package and then an install of the new one. The database tables that were created are not deleted during an uninstallation. Files should get deleted completly.

    But the database tables of the new version have changed. So besides having new table names they also have a different structure on some fields. Also there is no distinct table for recurring events anymore. So you have to manually migrate the old values to the new table structure.

    All these changes are not quite the best for an upgrade strategy but where necessary to provide more reliable codebase and the new features.

    Regards David

Please Sign in or register to post replies

Write your reply to:

Draft