Downloading SMF

Started by Norv, July 11, 2009, 03:59:43 PM

Previous topic - Next topic

Norv

Experiment:
I would like to download SMF 1.1.7, and the upgrade of 1.1.7 to 1.1.8, and from 1.1.8 to 1.1.9.
Looking at the menu, I go first at "Download", from all the options there. I find the latest versions, which is okay of course. I download the small update to 1.1.9.
Then, I look at the menu on the left, for older versions. From all the entries, I see nothing closer to what I wish than "Archived releases". So I go to archived releases, but I find only 1.0.x there. I mean, the first are 1.0.17. I go to the 42th page (the last) and I find still 1.0.beta5. *headscratch*. Where is 1.1.7?
I look again at the menu on top of the page, because clearly the left navigation doesn't seem helpful at all. I see nothing where it could be, but I know the upgrade package must be somewhere (I have seen it in the past), so I try them all. At "Support" perhaps? Mhm, no. At "customize"? I don't see why the older SMF versions would be at "Customize", but I try. Oh, at "Customize" there is the "Upgrades Site" in the navigation menu on the left! (why isn't it at Downloads?)
I find 1.1.7 to 1.1.8.
Now, where is 1.1.7?...

------

Please consider to make the patches available along with SMF versions (that is, "upgrades site" available from the downloads page).
Also, is there a rule or anything that may help one find the last five versions? Except... downloading one random package and editing the name of the download?
[EDIT:] If there is such a huge un-categorized list with "Archived releases", can't it be at least ordered? I fully expected it to be ordered... so that one looking at the first and the last can  understand what is there.
[EDIT2:] By the way, I found  1.1.7. By editing the name directly in the download link for another package. The point of the experiment however, is that this is not user-friendly at all. As said before, if 1.1.7 is an archived release, there should be at least an ordered list there, so that one can search for it with some chance to find it quite normally. It is expected to not have more than that, after all it's an old version now, but an ordered huge list should be okay.
To-do lists are for deferral. The more things you write down the later they're done... until you have 100s of lists of things you don't do.

File a security report | Developers' Blog | Bug Tracker


Also known as Norv on D* | Norv N. on G+ | Norv on Github

青山 素子

First, why are you looking for such an old version and the package manager updates? You should really start with the most recent version of SMF unless you have some very special need.

Second, we know the archive is a mess and are working on a plan to make it better. Right now, we're pouring effort into our 2.0 software, so it's not a primary project right now. However, be assured, we will work on it.

I don't think we've ever really had a place for the package manager updates for SMF in our downloads area, just the manual upgrade and update archives. The admin area in SMF handles the notifications and simple installs easy enough it's not really something to have special need of.
Motoko-chan
Director, Simple Machines

Note: Unless otherwise stated, my posts are not representative of any official position or opinion of Simple Machines.


Norv

Quote from: Motoko-chan on July 11, 2009, 09:35:32 PM
First, why are you looking for such an old version and the package manager updates? You should really start with the most recent version of SMF unless you have some very special need.
Well, I was making some tests lately about SMF latest versions behaviors and their upgrading under less optimal conditions. As not all questions issued at support have straightforward answers, or not that I know of. But the problem I am raising here is not about my needs. I can deal with that.
However, there are other needs of users, that I've noticed, needs that are rare, yes, but exist every once in the while. For example, there are still users with SMF 1.1.2 or 1.1. RC_something or even less. There are cases of any version, including recent like 1.1.5 or 1.1.7, who's SMF installation does not work anymore (hacked, partially deleted, something) and who only have a data-only backup to restore somewhere. Now, I know today that a 1.1.5 or 1.1.7 database can be restored in a 1.1.9 structure, and work flawlessly. But even that, I received confirmation only recently. Then again, this is not about me. There are users out there who do know a few things about SMF or software, but don't know when SMF database structure changed, and whether it did in a relevant way for their restoring problem. For many of them, I think, there's an obvious solution: install a fresh SMF of the same version, restore the database, upgrade SMF (files and database). But "install a fresh SMF of the same version" requires a trip to the archive.
Now, again, I am not saying this is a common need. I think it's a rare need. However, it happens. The archive is in place for something, and if anything, it should allow one to find an old version, when such situations or others occur.
I'm not saying it should allow it with many features, categorized by language/type/subtype or whatnot. But simply allow it in a way a computer user would expect.
I submit that an unordered list of 42 pages is very unexpected. We're spoiled. We cannot imagine that there is no way of knowing where the record is.

For example:
Page 1 has 1.0.17 and page 42 has 1.0.beta5. From this, I understand that there are only 1.0.x versions here. (I honestly believed that, for the last month or so).
Randomly clicking in the middle however, I find that page 26 has 1.1.4 ! Well... then perhaps 1.1.7 is here somewhere. But is it before, from 1.0.17 to 1.1.4, or after, from 1.1.4 to 1.0.beta5 ?
I'd go for "after". Let's see what page 27 says: smf_1.1.3_slovak. Lose.
Okay, page 25 be it: 1.1.4 still. Okay, page 24: 1.0.13. Lose!

...Please let me put it this way: an element of the interface must not trick the user. To the user, a (huge) list makes sense if they can browse through it going closer to the goal. Otherwise, why is it there?
They don't all have to be perfectly handy. But the list serves no purpose, if its content is not ordered in a comprehensible manner.

Quote from: Motoko-chan on July 11, 2009, 09:35:32 PM
Second, we know the archive is a mess and are working on a plan to make it better. Right now, we're pouring effort into our 2.0 software, so it's not a primary project right now. However, be assured, we will work on it.
Sure, I understand that. Just please allow me to make it clear that I was not talking about significant changes. The point about the archive is that it is really not useful at all unless ordered. No more, but I'm afraid no less either. Am I missing something obvious here?
To-do lists are for deferral. The more things you write down the later they're done... until you have 100s of lists of things you don't do.

File a security report | Developers' Blog | Bug Tracker


Also known as Norv on D* | Norv N. on G+ | Norv on Github

karlbenson

The archived releases page isn't the best organised :P

The trick would be to find any version, then simply modify the url for the version you want ;)

Thantos

IIRC the package manger files are in the mod site area (kinda) not on the archive page.  IE: http://custom.simplemachines.org/mods/downloads/smf_1-1-2_patch.tar.gz

Advertisement: