NewFeatures260

New and changed features in JForum 2.6.0

Libraries

• removed Apache Commons Codec, because Java 8 has Base64 built in
• updated Apache Commons FileUpload from 1.3.3 to 1.4
• updated Apache Commons Lang3 from 3.7 to 3.9
• updated Apache Commons Text from 1.2 to 1.6
• updated Apache Lucene from 3.6.2 to 8.1.1
• updated Apache Tika from 1.17 to 1.21
• updated c3p0 from 0.9.5.2 to 0.9.5.4
• updated FreeMarker from 2.3.27-incubating to 2.3.28
• updated Hsqldb driver from 2.4.0 to 2.4.1
• updated JavaMail from 1.6.0 to 1.6.2
• updated jQuery from 1.12.4 to 2.2.4
• updated Mysql Connector from 5.1.45 to 5.1.47
• updated Postgresql driver from 42.2.1.jre7 to 42.2.5
• updatd Quartz from 2.3.0 to 2.3.1
• updated SqlServer driver from 6.2.2.jre7 to 7.2.2.jre8
• updated slf4j from 1.7.25 to 1.7.26

---

New Features and fixes

• Java 8 is now required instead of Java 7
• Note that due to the Lucene library update, all posts must be reindexed. This will be done automatically when the web app is first started, but -depending on the number of posts- may take a while. Keep an eye on the jforum.log file for progress updates.
• Mobile pages: fixed bug [#88] where the wrong forum name was shown in the Recent Topics page; added the Hot Topics page; Google Analytics (if enabled) is now also used in the mobile pages; user rank is displayed better; pretty dates are used, if those are enabled using the dateTime.pretty property or configuration; PM pages (inbox and sent box) have pagination; posts require captchas (if captchas are enabled)
• Localizations: lots of improvements to various translations, particularly Italian, and a brand new Spanish localization [#94]
• switch Google Analytics from ga.js to analytics.js
• Social media sharing: added Whatsapp, Tumblr, Hackernews and Print, and fixed bugs with Twitter and XING
• [#78] properly handle missing server version information
• [#80] replaced links to various jforum.net pages with links to sourceforge.net wiki
• [#79] avoid stack overflow when loading templates that weren't cached
• [#77] PostgreSQL performance improvement for a few DB queries; this also fixes [#86]
• put a more meaningful message into the moderation log when a topic is deleted
• Feature: stop words for searching can now be configured in a language-specific way
• Bug fix: clicking the Twitter handle in the user profile now opens the Twitter page in a new window
• address potential XSS issues
• only show registration day, not registration time, on user profile; this also fixes [#83]
• [#84] Broken utf8 chars in form-urlencoded POST request
• [#85] Bug fix: Categories can't be added when using the EhCache caching engine
• [#87] Some minor cosmetic fixes
• [#89] Pagination for personal messages
• [#90] posts.new.delay is now applied to personal messages as well as posts
• [#92] Relative timestamps like GitHub or Facebook
• on topic pages, the user name is now a link to the user's profile
• Member list and moderation log are now only shown after login
• [#95] allow additional SMTP properties when sending mails
• Allow changing default Admin username during installation

---

New Configurations

Entry name	Default value	Description
lucene.analyzer.stopwords	en	Comma-separated list containing zero or more of: ar, br, cz, de, en, fr, bg, bn, ca, cjk, ckb, da, el, es, eu, fa, fi, ga, gl, hi, hu, hy, id, it, lt, lv, nl, no, pt, ro, ru, sv, th, tr. Include all languages for which there is content in the forums; that will prevent stop words in those languages from being indexed for searching. The index needs to be recreated for this to take effect. Default is "en" because that's how it worked before. If you have content predominantly from one language, you may want to adjust both the lucene.analyzerand lucene.analyzer.stopwordsproperties to reflect that language.
dateTime.pretty	false	Whether to show relative times like "1 hour ago", "1 day ago", "6 month ago" etc, or absolute times like "December 21, 2018". This replaces the dateTime.local property which is no longer supported.
mail.smtp.additional.properties	mail.mime.address.strict=false	A comma-separated list of additional SMTP properties to use when sending out mails. For example, adding mail.smtp.starttls.enable=true and mail.smtp.starttls.required=true would require TLS to be used.

Database Schema

No schema changes