AdeV

There is an SMF plug-in which makes it a bit easier to insert images inline, but in the meantime, Chris' method will work (and is, to my knowledge, the only way to host the images inside Mem AND show them inline).

I've been looking for a sensible alternative to Coppermine that we can use here, since Coppermine seems to be semi-abandoned these days (last update was 2024, and that was after a 6 year period with no updates...); but so far, I've yet to find anything which seems to be designed specifically to give the same sort of functionality that Flickr or Photobucket used to offer for free; and that plays well with forum software like SMF.

I did start to write my own, about a year ago... but time got away from me and now I've forgotten how to do it... but on the other hand, AI is way better now, so... don't hold your breath; but also, watch this space...

Quote from: Charles Lamont"... significant friction with users ..."

A quick look suggests SMF 2.1 is a considerable improvement, so when it happens it would behove 'us lot' to refrain from whingeing while we acclimatize.

hehe 

I'm ambivalent tbh. As I wrote elsewhere, I'm not exactly keen on SMF's interface at all: It does, however, have the distinct advantage of being free to use without restriction, quite modifiable, and reasonably robust.

Although I think email might be broken right now As soon as I've cleared my desk of urgent day job work, I'll need to take a closer look

Hi - sorry for the delay replying here.

Yeah, the listerengine.com domain (which I do not control) has gone dormant - the people who own it have failed to renew it (like they do every year), so now we're on the backup domain lister-engine.com (which I DO control).

This does mean that anyone who uses Coppermine will now have broken links.  Since that's a mega pain in the arse to fix, I'll do a DB script to do it for you, just as soon as I can find the time to do so.

Apologies!

Going forward, it would be better to use the lister-engine.com address, as that will ALWAYS point to the correct location. I'll check the Coppermine config to see if I need to change anything there.

As you may have read in the news recently, there's been a couple of nasty vulnerabilities discovered in the PHP programming language, which is used by millions of websites across the planet, including MEM (the forum software is implemented in PHP). Newer versions of PHP (8.5+) have already been fixed; but older versions will not be addressed.

The bad news is: We're running on an older version of PHP, one that won't be patched, and I can't upgrade to a newer one because SMF 2.0 doesn't support them. To do that, we'd also need to upgrade to SMF 2.1, which is a MAJOR job - and, I know from other forums that have made the switch, there are enough differences between 2.0 and 2.1 to cause significant friction with users (i.e. you lot  ).

The good(ish) news is: Because I recently moved us to a new server & a new containerised system (docker, for those who know what that is - if you don't, it's not vital to the news), so we're already partly protected. I've also just made some configuration changes that SHOULD make us pretty much secure. It's not 100% guaranteed... but fingers crossed: And even if they do get into the system, they're stuck in a container they can't get out of, which will significantly reduce any damage they could do.

With regards to the database - the DB is backed up nightly, with one backup retained for a week - so if anyone does notice anything funky, as long as it's reported quickly, we'll lose at most 1 day's worth of posts.

Unfortunately I'm severely time constrained right now, which means I don't know how much of a chance I'll get to do a trial migration to v2.1 + upgrade to latest PHP + patches; but I'll try to fit it in if I can. Then I'll need some volunteers to take a look at it/test it to make sure the new user interface isn't going to cause problems.  I'll post any news up here & in the chatterbox board.

So...

The bad news is: We're running on an older version of PHP, one that won't be patched, and I can't upgrade to a newer one because SMF 2.0 doesn't support them. To do that, we'd also need to upgrade to SMF 2.1, which is a MAJOR job - and, I know from other forums that have made the switch, there are enough differences between 2.0 and 2.1 to cause significant friction with users (i.e. you lot  ).

The better news is: Because I recently moved us to a new server & a new containerised system (docker, for those who know what that is - if you don't, it's not vital to the news), so we're already partly protected. I've also just made some configuration changes that SHOULD make us pretty much secure. It's not 100% guaranteed... but fingers crossed: And even if they do get into the system, they're stuck in a container they can't get out of, which will significantly reduce any damage they could do.

With regards to the database - the DB is backed up nightly, with one backup retained for a week - so if anyone does notice anything funky, as long as it's reported quickly, we'll lose at most 1 day's worth of posts.

Unfortunately I'm severely time constrained right now, which means I don't know how much of a chance I'll get to do a trial migration to v2.1 + upgrade to latest PHP + patches; but I'll try to fit it in if I can. Then I'll need some volunteers to take a look at it/test it to make sure the new user interface isn't going to cause problems.  I'll post any news up here & in the announcements page.