Thread

This question may be related to a resolved thread.

I am still having this Tab Manager sorting issue. They seem to reorder in pretty much random ways no matter what I try.
The last comment on the above “related” thread (actually the same) is that the bug was fixed for the “next release.”

Which release is that? I am currently working with v2.1.0 Build 20100810

Tab Manager sorting bug is still alive and kicking in this version.

(And, yes, I know that the custom tabs will always follow the standard ones.)

Any possibility of a screen shot or two? The bug should have been fixed in the build you’re using now.

Any possibility of a screen shot or two? The bug should have been fixed in the build you’re using now.

Here’s a video (what could a screen shot show?)

http://queensvw.com/images/site/tab-manager-bug.mov

Please let me know what you advise. Making me crazy. Everytime I think I see the pattern, it changes. I just want to order these things.

Hi dashard,

If you set the desired order for everything in one shot and hit Submit, does that work properly?

Yes. Seems to. PLEASE don’t tell me that’s necessary, though. I thought there were bits and bytes and computing instructions under the hood of EE, not gerbils on a wheel.

I should absolutely be able to add a new tab, and mark it as #1 to move it to the top. Heck, I’ll even accept it coming in as #2 because of some calculation based on the existing #1. But for it to simply Quantum Leap to and fro is crazy!

Any ideas? Bug is definitely not fixed, unless (don’t say it!) you’re going to tell me that to reorder 1 tab I have to renumber ALL tabs. You’re NOT going to say that, are you?

Thanks, dashard, I’ll run this by the devs again. Thanks for your patience.

Hi dashard,

This should be working better in the next release; I don’t have an exact ETA on when that will be. Thanks for your patience.

This should be working better in the next release; I don’t have an exact ETA on when that will be. Thanks for your patience.

This one I can live with. Just get cracking on that date bug!

The next release doesn’t have the date bug issue you linked to. Again, we don’t have an ETA.