Support » Plugin: All-in-One Event Calendar » Forced registration in version 2.6.2

  • There should have been a warning that upgrading from 2.6.1 to 2.6.2 would require a account to continue using your free plugin. It’s not mentioned in the Changelog but this is a significant change to how this plugin operates.

    Thankfully free accounts are available, but notice that this was now a requirement would have been appreciated. This caused a bit of stress this morning for a client that thought that they’d lost their Events after all the menu options went away.

Viewing 4 replies - 1 through 4 (of 4 total)
  • wr


    According to there are 3 pland, none of them show the cost as “free”… can you clarify how you create a free account to use this plugin? Others are saying you need to pay to get it working…

    After you install and activate the plugin, it will ask you to click on a “settings” link. However, that currently results in an error message, so instead, click on the new “Events” link in the Dashboard menu and then on “Activate” which will result in the screen with the form to sign up for the free account.

    Beside the problematic of just introducing this without announcement:

    I do not want to be forced to register somewhere to use a plugin for my WordPress projects. However, site editors are still able to edit and create events. So I’ll wait for two updates or so and will do a module research afterwards, if timely still handles this bug as a feature…

    So they still haven’t fixed this “feature”?
    Use rollback to go to the pre-2.6 version.

    Looks like they are actively preventing this. It worked a few months ago, but they removed all previous editions off Luckily I still have a copy for what it’s worth. As soon as I can get my clients off this plugin the better. They are deliberately forcing people to sign up using their own events as hostage…

    • This reply was modified 1 year, 1 month ago by gmariani405.
    • This reply was modified 1 year, 1 month ago by gmariani405. Reason: typo/update
Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Forced registration in version 2.6.2’ is closed to new replies.