Hello everyone,
phpBB is cult and still unrivalled in many areas. In my opinion, the big problem is the editor. You can write long essays about how easy it is to use BBCode: many people don't want it any more.
I have already written elsewhere in the forum about how complex a good rich text editor is. In social media, it is essential that only predefined HTML can be used and that configured layout elements are used. This is why BBCode is not dead if the editor is replaced by WYSIWYG. It's the required backend validation. However, it must be mapped in the rich text editor.
In concrete terms, this means that all BBCodes, whether default or custom, must be mapped in the rich text editor in every situation and translated into BBCode when saved. There are certainly other options, but they mean a major reorganisation and do not allow users to continue using BBCode, which is certainly what some people want.
Another sticking point is that images cannot be inserted via copy&paste. Perhaps this can also be implemented in the existing editor.
In my opinion, the rich text editor should be developed as an extension in order to gain experience first. We can probably build on the existing plugin. If it is well received, the extension can be incorporated into the standard version.
I am currently familiarising myself with extension development. This takes some time, especially alongside my job. When I'm ready to dedicate myself to more complex extensions, I'll get back to you on the subject. I would be very happy if a small team could come together to work on the extension.
phpBB is cult and still unrivalled in many areas. In my opinion, the big problem is the editor. You can write long essays about how easy it is to use BBCode: many people don't want it any more.
I have already written elsewhere in the forum about how complex a good rich text editor is. In social media, it is essential that only predefined HTML can be used and that configured layout elements are used. This is why BBCode is not dead if the editor is replaced by WYSIWYG. It's the required backend validation. However, it must be mapped in the rich text editor.
In concrete terms, this means that all BBCodes, whether default or custom, must be mapped in the rich text editor in every situation and translated into BBCode when saved. There are certainly other options, but they mean a major reorganisation and do not allow users to continue using BBCode, which is certainly what some people want.
Another sticking point is that images cannot be inserted via copy&paste. Perhaps this can also be implemented in the existing editor.
In my opinion, the rich text editor should be developed as an extension in order to gain experience first. We can probably build on the existing plugin. If it is well received, the extension can be incorporated into the standard version.
I am currently familiarising myself with extension development. This takes some time, especially alongside my job. When I'm ready to dedicate myself to more complex extensions, I'll get back to you on the subject. I would be very happy if a small team could come together to work on the extension.
Statistics: Posted by harryk — Sat Mar 22, 2025 7:39 am
