Wedge

I still think it would e better to flag the error, that way someone can deal with it; I wouldn't have figured it out for a while if I hadn't been specifically looking.

Yup, it should definitely be $critieria in both the call and the if before-hand. I'll commit it once I have some other stuff to commit, but need to head out now.

Awesome, thanks. I'll look at it first thing in the morning.

So, this was raised ages ago in the private area, and I want to bring it back for discussion. It is, after all, something of a mess.

First question: do we really need the facility for multiple smiley sets?

Second question: do we really need to ensure the same smileys are present in every set?

Third question, and this is one for the programmers rather than anyone else: can we safely ditch the predefined smileys shtick? Spoiler because it's long, messy and of little importance to most people, other than the UI aspect which I'll deal with afterwards.


I mentioned a UI problem. Adding a new smiley is incredibly unintuitive.[1]

So, if we don't have customised smileys, because internally it's *all* that customised gig, we get to massively streamline the UI. Depending on how the above other questions turn out.

Also: as far as I'm concerned you will have to use FTP/SFTP credentials to upload files. I really hope that's not a problem for anyone because I'm not prepared to budge on that; the whole point is to NOT have to change file permissions and thus encourage people to make things insecure by design.

Thoughts welcome.

1.

In fact, one of my side projects is a heavily modified SMF install (there's enough custom code that I don't want to have to keep patching to keep it level with Wedge, and I don't even see my keeping it beyond SMF 2.0). For reasons I won't get into, this project's smiley set was made out of a single sprite sheet, so I crudely replaced the code in SMF with that image and offsets and whatnot, and I showed the other folks involved on the project the UI, showing off the different smileys and all the codes attached to it - and the take-away comment was "I like the whole admin control. I wish SMF had such." - as in he thought I'd made the entire UI for customised smileys, solely because no-one had mentioned to him about enabling them.

I have no idea which tables need to be updated, or indeed whether anything actually needs to be done other than pruning logs.

On the one hand you could argue that the items should be deleted, on the other you could argue that all you really need do is ensure that the table joins don't flake out because there's no longer a matching relation to the members table, it would have the same practical effect as resetting the ids to 0.

Also, while we're on that note, do we need to add the facility to reassign owners of albums and so on? Are the old details recorded, e.g. email address? Same deal for items, on that same note.

So, I spent some time looking at what IPB does. I see it as the real competition to Wedge, not so much competing with SMF or the other free systems. I figure if it's what people are willing to pay for, I want to see what it demands.

I gotta say, I'm inclined to take the road they did - there's no calendar board, no linked topics or anything, you just have the calendar as an item that people can browse - and there's an RSS feed for it too.

They also provide abilities like restricting who can see individual events, plus a per-day view (as opposed to SMF/Wedge which currently only offer month/week views, because it can't handle times on events, there's no need for a per-day view), plus the ability to support multiple calendars rather than just one, though I'm honestly not sure how useful that part is.

It does make me seriously wonder how much of the calendar is worth salvaging.

Does this happen on local installs?

I seem to recall this being related to the attachment drag and drop plugin of Dragooon's, which also may or may not have been fixed in the intervening time.

fixLongWords got removed a fair while ago, it's done via CSS these days.