Message |
|
JForum indeed doesn't have plugins or themes, so you would make any changes to the only available theme, which is called "default". When you run JForum, there is a top-level directory called "templates", in which you'll find the front-end code (HTML enriched with FreeMarker code to make it dynamic) and the images, JavaScript and CSS.
we would need to adapt a WYSIWYG text panel to that forum instead these one
You mean you want to use rich text editor like one of https://itsfoss.com/open-source-wysiwyg-editors/? That's possible in principle, although you'll want one that can output BBCode, since that's what JForum uses to format text. The template that contains the textarea for posts (which is where you would need to plug in the WYSIWYG editor) is called post_form.htm
So in that cas, can we take the code and try to adapt ir or it don't work in that way?
JForum is open source software, so you're free to modify it and run it with your modifications within the bounds of its license (which is quite permissive).
|
 |
|
172.28.200.26 is a private server on your network - so you have a sys admin to talk to 
|
 |
|
That's JForum logging output, which doesn't add anything to the exception you posted earlier. What you want is the JavaMail debug output.
|
 |
|
"Connection reset" frequently points to a networking issue rather than an application issue. You can add "mail.debug=true" to the mail properties on the Config page. After restarting the web app you should then see lots of debugging output in the logs; maybe that points to something.
|
 |
|
I haven't encountered problems running JForum on Java 11. If there were any, that would certainly be a bug that would likely be fixed soon. As to Jakarta 9, I have just done a quick test on Tomcat 10.1, and it seems to runs fine in Tomcat's webapps-javaee folder. Have you tried that? I'm not sure if other servlet containers have a similar facility. As to the underlying question: eventually we'll certainly require newer Java and JakartaEE versions, but given that it seems to run fine as is, it's not a high priority right now.
|
 |
|
You can try this jar file - it has the mail sending fixes.
|
 |
|
Turns out that there were not one, but two bugs in the mail sending code - which must have been there for ages, without anyone ever noticing them. Kudos for triggering them! 
|
 |
|
My reading of the situation was pretty much completely wrong, including the use of the "Allow HTML" setting. The relevant setting that goes with "notifyText" is actually "Include the message contents within the notification email". But that doesn't seem to have to do anything with the bug, which I suspect is caused by reusing the MimeMessage object. I need to look into avoiding that.
|
 |
|
That doesn't look like the right fix, but don't worry - I already have a fix, and just need to test it. Patience 
|
 |
|
Yes, that's exactly what it is.
|
 |
|
What I meant is: if at least one of them has HTML turned on, and at least one of them has it turned off. Yes, that code section may well be the problem. Config info is taken from the SystemGlobals.properties and jforum-custom.conf files. The DB table serves mainly as a backup of jforum-custom.conf.
|
 |
|
I think this can happen if some of the users have "Allow HTML" turned on in their profile, and some users do not.
|
 |
|
I'm not sure, as I don't use HTML emails, but I'll take a look.
|
 |
|
In the file templates/default/user_profile.htm, replace registrationDay with registrationDate - that will use the format you selected. Note that in the topic view, the format will still use the short version "Jul 6, 2011", because there space is at a premium. Attached is a new JForum jar file that has the fix for Oracle. If you replace the one you have with this one, it should work regardless of the cache setting. Let me know how it works out for you.
|
 |
|
jdev1 wrote:I found reason of my problem it's "topic.cache.enabled" in SystemGlobal.properties. When it's "true" it uses selectAllByForum with MAX.integer as argument that's why it was 2147483647 as value.
That addresses the symptom, not the problem. If I provide you with a version that includes the fix I posted above, would you be willing to test that?
|
 |
|