[Jaap Visser]

merci de la confirmation que je ne suis pas le seul à réclamer
Personnellement je suis même "blacklister" par Le développeur CMSMS. et cela n'est pas grave puisque il y a une solution bien plus au point qui est fonctionnelle

Je peux comprendre que vous préfériez une version modifiée du CMSMS, maintenue par un développeur dédié, bien testé, prêt pour PHP 8.3.x et bien en avance sur la version officielle de l'équipe principale du CMSMS. Une version qui n'ignore pas les bugs et ne demande pas de désactiver les avertissements PHP comme s'il n'y avait pas de problèmes.

Voici une réaction en anglais pour Jo Morg: https://forum.cmsmadesimple.org/viewtopi...16#p350816


When you have anything more productive to contribute to the project please do

Here lies the problem, it is almost imposible to contribute. The only thing you can do is develop your own modules, themes, help in the forum or report bugs that get ignored most of the times so that is not a lot of fun.

For the CORE project there is no active roadmap, no infrastructure in place to see what is worked on, where the project is going, what the status is and where help is needed how you can add a patch or feature. Nobody has a fucking clue what the coreteam is doing simply because the svn branches are big mess, the team operates behind a big iron curtain and is not willing to involve the community in an open (source) setting.

You have been testing and been quite vocal about it and missed this issue, so I wonder: how much amount of testing would it be needed before we came across this issue anyway;


If you don’t spot that the content tag breaks your distribution when you assign it to a variable $content. Perhaps you should dig a bit deeper. Not only quick clicking around on a vanilla installation (like the core team seems to do) but some true intensive test work that involves production website(s) and/or real-life scenarios.


You have been away from the team, in spite of having been invited to return several times and declining the invitation... it is your prerogative to do so, but then do not assume to know everything there is to know about how we do our testing or any other of internal team processes;


Everybody knows the core team does not do much testing. Back in the day only Rolf was involved with beta testing. During a long CMSMS v 2.3 beta cycle I have never seen any core-team member doing any tests. Modules forked from Calguy still have the same bugs from 4 years ago that says it all.


The processes that are inplace are just smoke and mirrors: If you put enhough smoke you don’t see your own hands for your own eyes. You can be away for 10 years the history predicst the future the results can’t be ignored.. Du vieux vin dans un nouveau sac




Some of the "numerous problems had [that] been reported and not corrected" are not issues and have been put aside for a later discussion because those were not problems, were deprecation warnings that have a purpose and a meaning... you cried wolf too many times to be considered a serious player;


Turning off warnings so you don’t have to make any fixes is plain stupid. Soon or later you have to tackle the issue. When you don’t do that you forget about it or collect more technical dept end up in a maintenance nightmare.


I don’t know the exact moment when CG depracted multiple database Smarty template methods I gues it was 8 or 10 years ago. It is funny that ListIt (the module Jo maintains) is still using these legacy methods yeah Jo Morg is true Legacy player or should we call him a Retro Player:  He prefers software from the past and no breaking changes even when there better methods he ignores them. Or has it something todo with background noise and cancelling that out.