Ouch! So you definitely are familiar with this pain. I would like to say "come help! We need your skills", but I doubt you want to do more of your day job as hobby volunteer work. Death's Darling (aka ElizaWy) is making some pretty big strides on a replacement OGA framework (PHP, but not Drupal), so if you are interested, we'll meet up and talk about next steps. No pressure though.
What I meant was, the difficulty lies in the entanglement of outdated framework needing outdated PHP. There is nothing I am aware of about the server hardware/OS that prevents modern PHP versions from being used, but this statement...
"it probably wouldn't be too hard to replace Drupal's internal mail functionality with something more up-to-date without fully upgrading Drupal."
... is incorrect, unfortunately. Modern PHP breaks nearly every part of drupal 7 and the modules it uses. It is filled with deprecated functions and now-forbidden datatype uses. Replacing just the mail functionality would still leave every other part of the site busted. We can't tell the mail functionality to use PHP 7+, but tell everything else to keep using PHP 5. Which means all parts of the site have to be overhauled to work with modern PHP, or the whole site has to keep using outdated PHP.
That's probably in there as well. Upgrading PHP would enable TSL stuff, but it would also break EVERYTHING else until we get the rest of it updated. Also, yes we're aiming for an OGA that isn't neccessarily Drupal at all. More of a replacement + migrate data than an upgrade.
"...unless you're just using really outdated servers installations..."
Bingo. Well, maybe not outdated server hardware/OS, but the OGA framework is drupal 7. The current drupal version available is 10.2. There is no upgrade path from 7 to current, and certainly no simple update with the massive database and custom modules. TLS 1.3 didn't exist when drupal 7 was built, much less the consideration to incorporate it into drupal's emailing system.
Also, @dejonge2 there isn't really a reason you won't be able to post here again. You can log in with your username and the password you picked. You won't be able to change your password nor get any notifications via email because of the temporary email used, but that doesn't stop you from logging in now that you're registered.
Added a warning on the registration page. See image below. Verbiage suggestions welcome. Hopefully this will serve as a stop-gap for now. I can always rename your nick to the one you really wanted in the event it becomes unaccessible due to this issue.
EDIT: Issue is fixed, warning removed from registration page.
I figured it might be better to keep this in the same thread?
Correct. Thread necromancy is impossible here: if there is more content to share on a given topic, then the topic isn't actually dead. Sharing the new content isn't resurrecting it.
If a topic is locked, it's dead, but then resurrecting it by making another post isn't possible.
Who is "you" in this context? Who are you talking to? Where did they talk about NFTs?
No castles?! I could swear zabin did some LPC castle stuff. Maybe it's just not OGA-BY. I'll go find it.
"Mutagen Dusk"
Ouch! So you definitely are familiar with this pain. I would like to say "come help! We need your skills", but I doubt you want to do more of your day job as hobby volunteer work. Death's Darling (aka ElizaWy) is making some pretty big strides on a replacement OGA framework (PHP, but not Drupal), so if you are interested, we'll meet up and talk about next steps. No pressure though.
What I meant was, the difficulty lies in the entanglement of outdated framework needing outdated PHP. There is nothing I am aware of about the server hardware/OS that prevents modern PHP versions from being used, but this statement...
... is incorrect, unfortunately. Modern PHP breaks nearly every part of drupal 7 and the modules it uses. It is filled with deprecated functions and now-forbidden datatype uses. Replacing just the mail functionality would still leave every other part of the site busted. We can't tell the mail functionality to use PHP 7+, but tell everything else to keep using PHP 5. Which means all parts of the site have to be overhauled to work with modern PHP, or the whole site has to keep using outdated PHP.
That's probably in there as well. Upgrading PHP would enable TSL stuff, but it would also break EVERYTHING else until we get the rest of it updated. Also, yes we're aiming for an OGA that isn't neccessarily Drupal at all. More of a replacement + migrate data than an upgrade.
Bingo. Well, maybe not outdated server hardware/OS, but the OGA framework is drupal 7. The current drupal version available is 10.2. There is no upgrade path from 7 to current, and certainly no simple update with the massive database and custom modules. TLS 1.3 didn't exist when drupal 7 was built, much less the consideration to incorporate it into drupal's emailing system.
Also, @dejonge2 there isn't really a reason you won't be able to post here again. You can log in with your username and the password you picked. You won't be able to change your password nor get any notifications via email because of the temporary email used, but that doesn't stop you from logging in now that you're registered.
Added a warning on the registration page. See image below. Verbiage suggestions welcome. Hopefully this will serve as a stop-gap for now. I can always rename your nick to the one you really wanted in the event it becomes unaccessible due to this issue.EDIT: Issue is fixed, warning removed from registration page.
Correct. Thread necromancy is impossible here: if there is more content to share on a given topic, then the topic isn't actually dead. Sharing the new content isn't resurrecting it.
If a topic is locked, it's dead, but then resurrecting it by making another post isn't possible.
Thanks for the update!
Pages