Re: Removal of Content Lock module from Drupal
Ben Cooksley <[email protected]>
| Newsgroups | gmane.comp.kde.events |
|---|---|
| Message-ID | <CA+XidOFaTtJthMUXxfW10QaBJBZcHnGdktQ47sccAcTxBOjE1Q__18015.3365292185$1574927584$gmane$org@mail.gmail.com> |
On Thu, Nov 28, 2019 at 8:47 PM Paul Brown <[email protected]> wrote: > > On jueves, 28 de noviembre de 2019 6:09:15 (CET) Ben Cooksley wrote: > > Hi Promo and Akademy Teams, > > > > In the past few days the Drupal developers who maintain the Content > > Lock module for Drupal decided that they would cease supporting their > > module on the 7.x series of Drupal. > > > > Unfortunately this means we're no longer able to continue using this > > module, as we won't receive security updates and other critical fixes > > to the code. > > > > I've therefore gone ahead now and removed the module from both the Dot > > and Akademy sites. We will likely need to look into upgrading both of > > them to Drupal 8.x in the coming year, as this (modules ceasing > > support for 7.x) is something which is likely to become more > > commonplace as Drupal 9 approaches. > > > > Apologies for the inconvenience. > > What does the Lock module do, Ben? Lock an article when someone is working on > it? That is correct - it is designed to prevent two people editing the same content at once. > > Cheers > > Paul > -- > Promotion & Communication > > www: http://kde.org > Mastodon: https://mastodon.technology/@kde > Facebook: https://www.facebook.com/kde/ > Twitter: https://twitter.com/kdecommunity > LinkedIn: https://www.linkedin.com/company/kde > > Regards, Ben