Hi I dunno if this is just a problem with me XD but I was wondering if we could change the "weighting" order so the highest number was higher up the section instead of lower.

Coz I would put it as the first cosplay I completed (Rinoa) was 1, 2nd (Temari) - 2 etc etc but then they were at the top and if I want them at the bottom (which I'm more used to) they have to be 9 and 10

But that means everytime I complete a cosplay if I want them at the most recent completed at the top that means I have to change every number so everything moves down.

Whereas if we had it so the weight number: 1 was at the bottom of the section then all we need to do is number the most recent cosplay we've finished instead of changing them all

Does this make sense? I'm not very good at explaining =[

An alternative I want to suggest is a drag/drop system or similar, so we can edit the order of cosplays without fiddling with numbers~
I kind of want to put mine in alphabetical order, so I would have to change the numbers everytime I added or completed a cosplay :/

I agree, I think they should be ordered with the smallest number at the bottom rather than at the top. I remember CosSpace did smallest number at the top and it was hell whenever I wanted a new costume because I'd have to move them all down.

This time I started with 999 and went downwards (because I doubt I'd have 999 costumes no matter how hard I try XD), but it'd still be preferable if the weighting system could be reversed.

I do love the fact we can order our costumes though, have been wanting this system for ages now, thank you! x)

If it's any help, costumes do not have to have unique weighting numbers. You can list more than one costume with the same number and they will be ordered by create date amongst their fellow numbered costumes.

They also don't have to be consecutive numbers, so you could give one costume a weighting of 20 and the next a weighting of 10. It just knows that 10 is smaller than 20 and you have room to play with

The reason 0 is the top of your list is so you don't have to re-order every time you add a costume. New costumes will go to the top by default as 0 is the base-line.

I like the thought of a drag/drop system a lot more XD

Also a new problem has arrived. I dunno if it's just me. But everytime I edit/add a new photo to a costume the weighting returns to 0 so I need to rearrange the weighting again @_@

is this happening to anyone else?

Amy's addressed the reason it starts at 0 - honestly it'll save you a lot more time then re-numbering *all* of them! It gives you the opportunity to have complete control, but for everyone else it means if they are happy having them in the order they add them to the site, they don't have to change a thing. In the future we'd love to implement a lot more edit in place/drag & drop functions on the site, not just for this bit here. For now though, this is a step towards that



I've just being testing this and can't get it to do what you say happens! Can you let me know the costume you're getting this on, and if it's affecting any others? Please keep in mind that if you change the status (from Planned, to In Progress for example) it'll reset to 0, as it's classed as being in a different list. Drop me a PM if it's easier, or if there's anyone else who's getting this please shout!

They're all in my "In Progress" section

I added my Vanessa straight into In Progress which as you said went to the top at 0 but when I changed her weighting she didn't appear at the "Most recently added costumes" on the front page so returned her to zero

Now so far everytime I've edited Freya, Lenne and Jessica Rabbit they've returned to 0 when I had them all in order of events, Originally the order of the top three was "Vanessa - Kurumu - Jessica Rabbit" but since I recently added a photo of Lenne she'd now top middle. And the same happened with Freya Crescent, Jessica Rabbit and Rinoa Heartilly :S

I've had this when I edited my Ada Wong and Yuna Cosplays; they re-set to 0 (not a major problem, just thought I'd mention it) x

Hey guys, thanks for the info - this should now be fixed, let me know if anyone has any further problems!