I think it's fixed. You can grab the source code from SVN to build it now, or wait for the upcoming 2.8.1 release - which should happen within the next few weeks.

I had taken a first stab at this (which you can find in SVN), but it doesn't yet do what I want it to do. So, more work is needed, which I may get around to in the next few weeks.

I see what you mean. This will be addressed in the next release.

This has been fixed in 2.8.0, BTW.

To my knowledge this hasn't been done. I'm guessing it would have something to do with https://api.slack.com/messaging/webhooks, which doesn't look too difficult. I'll look into that, but I can't make promises as to a possible timeline. Would you be willing to help with testing, if it ever came to that?

It's been a while since the last release, and we've been busy adding features and fixing bugs to make JForum even better than it already is. A servlet container that supports Servlet API 3.1 is now required, for example Tomcat 8. Some of the new and improved features are:

Registration can be restricted to particular email addresses or email addresses from particular domains, and then be auto-assigned to specific groups.

The authenticity of outgoing emails can now be verified via DKIM.

The registration pages and the password recovery pages are now mobile-friendly.

It's now possible to log in with the email address as well as username, as that is what users expect these days.

New default connection pool, potentially increasing performance with multiple concurrent users.

Numerous bug fixes and small improvements

A full list of new features is at https://sourceforge.net/p/jforum2/wiki2/NewFeatures280/, upgrade instructions are at https://sourceforge.net/p/jforum2/wiki2/UpgradingFrom270to280/ and you can download it from https://sourceforge.net/projects/jforum2/files/. The documentation is at https://sourceforge.net/p/jforum2/wiki2/Documentation/

All feedback is welcome.

You can grab the source code via SVN as described in https://sourceforge.net/p/jforum2/code/HEAD/tree/, and then do something like "mvn -DskipTests=true package" which will create a deployable war file.

I just committed that change. It'll be in the next release (which should be out in the next month or so), or you can get it today by building from source code.

It's software - just about everything is feasible

What I meant is I can add that to the codebase. I'll probably get around to it soon, likely by next week.

You mean something like http://cssdemos.tupence.co.uk/image-popup.htm? That might make for a useful addition.

The scaling down of attached images is deliberate, in order not to mess up the page layout in case of large images.

What would be good to have happen is that clicking on an image opens it in full size in a new tab. That would make the text easy to read - would that help you?

kjhf ajfh lkjsahdf sajh lasjhf aklhdf akllkafkljahdf l

kasjfkhas ajkshdg akjhdgs dkajhgsd kajshdg jakdd agds akgdsa

attachment