@PrabuEla
This is for the Drupal 7 version of the module on PHP 8.2
Collins405 → created an issue.
I am sad to report that due to the uncertanties around Drupal 7 (Classic) - I have now commissioned a full rebuild of our saas platform in React and other technologies to move away from Drupal. This is taking 12 months and $250,000 to do.
Looking at how this was handled, I cannot afford to take the same risks by rebuilding in a later version of Drupal and having a similar problem down the road.
This means I am retracting my offer of $10,000 a year to support this initiative, and I will be taking my 2500+ Drupal 7 sites away by the end of the year (in time for the EOL).
Thank you to everyone who tried supporting this, I am sad to let Drupal go, but also 4 months into the new build, already seeing a plethora of benefits to moving to a new system and architecture. I didn't want to have to spend this money just to end up with essentially the same service just on a new platform, but I wasn't left with many choices.
Yes, but things like jQuery and Ckeditor can be solved with relatively trivial updates to core or contrib - theres no need to force people to rebuild their entire sites just to upgrade them.
I for one am devastated by the loss of Drupal Classic and what it has already done to Drupal as a whole. I think its a huge mistake on the Drupals part, and will see the platform used less and less until it only gets used by die hard fans or hobbyists, and we lose our community entirely.
I am already seeing the majority of developers I know leave Drupal in favour of other platforms that don't force their hand and require them to make major updates to platforms just to maintain current functionality.
With Drupal classic, there's no one forcing anyone to use bleeding edge PHP, although you can if you want. Symfony isn't forcing their lifecycle down either because it's not included with Drupal classic.
This right here sums up everything wrong with Symphony Drupal, and every reason why Drupal Classic is amazing as a bit of open source software that can stand on its own.
I think the issue here is the Drupal Association is assuming we're all on small to medium sites that can be upgraded / rebuilt in the new version with relative ease.
I have 10 servers, with 10 multisite installs, each with 500+ customers on - all utlizing a custom CRM and Business management system with D7 at its core. We're talking 100+ custom modules, over $250 million worth of financial records, customer data, reporting history etc that cannot be simply migrated/rebuilt without millions of dollars of work.
I feel completely shafted by this decision, and would financially support a "Drupal Classic", or "Drupal Lite".
Drupal 7 is still a fantastic platform to build apps on. I like to strip out all contrib modules using the minimal profile and build custom code on top. It dramatically speeds up development having all user auth etc ready to go, and make a pretty good boilerplate for many projects.
This is great news.
Was there any discussion about renaming D7 to Drupal Classic and allowing the community to keep it alive indefinitely?
Please can this be committed? I have to patch after every update!
Hey all, have there been any updates on this?