內容 |
|
|
|
|
Actually, the software does scale the image down if it is too large, so no change is needed. Not sure what's going on with this server, but it seems JForum does the right thing.
|
|
|
Thanks for the patch, I've just committed it (minus a bug that caused an exception if the number of results on the last page wasn't the same as the number of topics per page).
|
|
|
The base problem seems to be that the first page shows all 35 results, when it should only be showing 15.
So yes, that looks like a bug. I'll put it on my list.
|
|
|
Thanks for the heads-up. Not sure what is going on with the server, we'll look into it. It's unlikely to be missing libraries, that's just one of the things that can go wrong.
But I agree that there's little point in requiring an image of a particular size - it should just be scaled down to a reasonable size. We'll make that change for the next release.
|
|
|
We've just released JForum 2.8.1, which contains a number of small fixes and improvements that we've made over the last 9 months.
Various font and background colors can be configured at runtime from the Configurations page. So if you ever disliked some particular color JForum used, chances are you can now change it without even the need of a restart.
More control over image attachments from the Configurations page
Optimize Recent Topics and Hot Topics for large installations. Large meaning at least 100.000 posts before it will make a difference.
Fixed an issue where the last visited time on the forum home page was not actually reflecting that, but the time of the last session start
Switch optional Google Analytics integration from analytics.js to gtag.js
Fixed a CSRF vulnerability
As always, many dependencies haven been updated to the latest versions.
A full list of new features is at https://sourceforge.net/p/jforum2/wiki2/NewFeatures281/, upgrade instructions are at https://sourceforge.net/p/jforum2/wiki2/UpgradingFrom280to281/ 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.
|
|
|
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.
|
|
|
|
|
|
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.
|
|
|