By making the following changes you allow the actual tabs themselves to be above(before) or below(after) the panel content. Without this change if the code has the order of
instead of the more common
the script will not work. The reason for this is two .next usages that are based on the assumption that it will be written in that order. The correction goes based off the classes and still works with multiple tabs on 1 page. This allows for tabs above, below, left, and right.
This should now account for tabs out of order and tabs with panels in them. Without this out of order panels won't work and panels in a tab will get messed up when switching back to normal mode.
Sorry about doing so many commits stupid copy paste didn't work right. The last commit has the patch for allowing for panels within tab content as well as the fix for the tabs below content
By making the following changes you allow the actual tabs themselves to be above(before) or below(after) the panel content. Without this change if the code has the order of
instead of the more common the script will not work. The reason for this is two .next usages that are based on the assumption that it will be written in that order. The correction goes based off the classes and still works with multiple tabs on 1 page. This allows for tabs above, below, left, and right.
This should now account for tabs out of order and tabs with panels in them. Without this out of order panels won't work and panels in a tab will get messed up when switching back to normal mode.
Sorry about doing so many commits stupid copy paste didn't work right. The last commit has the patch for allowing for panels within tab content as well as the fix for the tabs below content
Please squash all the commits together, and then rebase.