UBB.threads PHP Forum Software Community Forums Active Threads

Has anyone here actually sold a Forum or have knowledge of what's involved?

Wondering how the transfer is actually done where both sides interests and $$ are protected.

No, we currently have no plans on updating the built in MD5 lines to process passwords with password_hash and password_verify. Keeping assets updated for PHP compatibility has been our main goal with current rounds of updates.

If we do update the mechanism in the future users would have to request a new password before being able to login with the forgot password system as you cannot decode an MD5 hash to update it to another hashing scheme.

re ubbt 8.1.0
1. error reporting has been cleaned up for php 8.5
2. smarty is updated from 4 to 5.8
3. will look at that and have it fixed for the ubbt 8.1 release. most of the dev is done using chrome, firefox and ofc edge. thank you for catching and reporting the strays from safari
4. hmm. wasnt aware that perl (cgi) was still being used outside of the forwarders for ubb from early 2000s. i'll take a look into this, as its something i also use on a few personal sites XD thank you
5. hot patches dont usually update the credits or general readme text files. but 8.1 will be a full update, and these docs will reflect its changes.
6 & 7 looking into these now. thank you! expect fixes for ubbt 8.1

ubbt 8.1 is fully checked to work on php 8.5 (php8 and newer)

A few more items from running 8.0.1 on PHP 8.4, in case they help 8.1.0:

1. libs/ubbthreads.inc.php line 917 passes E_STRICT to error_reporting(). E_STRICT is deprecated in PHP 8.4, so it logs a deprecation on every request — about 99.7% of our forum's log lines. Removing E_STRICT from that line fixes it. That runtime error_reporting() call also overrides php.ini/.user.ini, so we can't quiet it from config.
2. The bundled Smarty predates PHP 8.1's nullable-parameter rule (deprecations in smarty_resource.php, smarty_internal_data.php, Smarty.class.php). A Smarty refresh would clear them.
3. iOS Safari: the head emits a viewport without shrink-to-fit=no, and a second viewport from a theme competes with it, so tables shrink after rotating. One viewport tag with shrink-to-fit=no fixes it.
4. ultimatebb.cgi (legacy stub) prints "HTTP/1.1 301" — under CGI it needs "Status: 301", so old links get a 500.
5. credits.md still says 8.0.0 after the 8.0.1 patch.
6. Control Panel > Paths & Database can't save new DB credentials once the old ones stop working (the save needs a live connection), and fails silently.
7. ubbthreads.php?ubb=grabnext returns 200 even with junk parameters, giving search engines one extra URL per post.

Thanks!

Hi all,

We run UBB.threads 8.0.1 on PHP 8.4 and are planning around 8.1.0. A few questions for the developers:

1. Database outages: can the "unable to connect to the database" page be customized, and could it send an HTTP 503 with Retry-After so search engines treat an outage as temporary?
2. SEO: are a <link rel="canonical"> tag and schema.org DiscussionForumPosting markup on topic pages planned?
3. PHP 8.2+: are the utf8_encode() calls and the "passing null to parameter" deprecation warnings addressed in 8.1.0?

Any rough idea of 8.1.0 timing would help too.

Thanks!

Hi all,

We're running UBB.threads 8.0.1 on PHP 8.4. Looking at the stock code, member passwords are stored as md5() (and older DES crypt() hashes are still accepted at login).

Two questions for the developers:

1. Does the upcoming 8.1.0 release move password storage to PHP's password_hash() / password_verify()?
2. If so, will existing md5/crypt hashes be upgraded automatically when a member logs in (password_needs_rehash), so nobody is forced to reset?

If this is already on the roadmap, a rough idea of the 8.1.0 timing would help us plan. Happy to test a beta if that's useful.

Thanks!

FYI, I discovered Cloudflare "Turnstile", which allows you to protect any page on your site (you don't need have your domain on Cloudflare). You just need to have a Cloudflare account and a key. It is a bit of code and setup, but it's working great in my testing - the site still gets hits from bots, but they are stopped immediately rather than triggering full forum pages which was causing excessive load.

I am so sorry to report that I am running UBBT 8.0.1 and PHP 8.3.33 and the control panel member management area is blank and the tabs do not work. Tested on both Chrome and Firefox. Is anyone else having issues with these settings. Should I ask admin to downgrade PHP to 8.3.31 instead of 8.3.33? Everything worked fine a couple of weeks ago, if that helps. Thanks for any assistance.

New issue: My member management screen is giving a white screen, not allowing me to pick a tab.

I'm running the PATCHED version 8.0.1 on PHP Version 8.3.33.

I pay $30 per month to support a very important forum re verbal abuse. I need to approve a member.

I have the white screen in Control Panel and no tab action.

I also cannot find the template described by phoenix011235.
/templates/default/admin/membermanage.tmpl
I am a web developer and this is a bit frustrating
Phoenix suggested:
Change:
$config[BASE_URL]
to:
$config['BASE_URL']

Or can you tell me how to fix? I have no control over the PHP version, apparently.
Thanks very much,
Kind Regards.

Is this on 8.0.1?