Yes - you read right! This is a MAJOR bug where newly created tables (and edited tables) are being given the wrong 'field' in the db entry. Stupid error which is remedied by just minusing 1 from the field erm... field in the db entry. Added to this error the display functions now no longer work as before as '0' field number wasn't being picked up by the 'is it sortable?' query.
Now all fixed although PLEASE bear in mind if you've created new tables using the new 4.7 version then you'll need to manually minus 1 from every field in your tablemanager db. For example:
a:2:{i:0;a:2:{s:4:"data";s:9:"Full Name";s:5:"field";s:1:"1";}i:1;a:3:{s:4:"data";s:3:"Age";s:5:"field";s:1:"2";s:4:"sort";s:3:"asc";}}
Will become:
a:2:{i:0;a:2:{s:4:"data";s:9:"Full Name";s:5:"field";s:1:"0";}i:1;a:3:{s:4:"data";s:3:"Age";s:5:"field";s:1:"1";s:4:"sort";s:3:"asc";}}
So, in that example 1 is now 0 - 2 is now down to 1...
And yes - if you've edited a header you'll definitely also have the same problem. I'm really sorry about this, I had it on a sheet of paper for something to remember about the new query which I was supposed to fix before the initial release and I erm... Lost the piece of paper and forgot...
Still fixed now...
Pobster
Comments
Comment #1
lanesharon commentedI am relatively new to Drupal. So, could you please tell me what modules this effects?
Comment #2
pobster commentedJust this one, nothing else. If you don't have it installed you've no need to worry. If you do have it installed and the thought of manually doing the above scares you a little you can always just reinstall the tablemanager.mysql file and start from the beginning again (ie. you'll have no tables, but everything should work after you've put your data back in)
Hope this clarifies
Pobster
Comment #3
pobster commentedTo be honest, if you DO have this module installed (the 4.7 version anyway) and you don't want to manually change your tablemanager database or start from the beginning again then just editing the table header (not the rows) SHOULD make your tables work again.
...If it doesn't (which is unlikely) then please let me know and I'll help you myself.
Pobster
Comment #4
pobster commentedOkay now this is IMPORTANT:
I've changed this 'fix' back to how it was previously and PLEASE IGNORE the request to change your databases to the old way of numbering the fields. It actually makes a whole lot more sense in the code to keep it how it was in the first place. I know this will be annoying if you have read this already and have done it to your db and I apologise... Sorry about that... It's just that doing it this way also solves another little issue I had with the 4.6 version and so I'd prefer to keep it this way.
Thanks
Pobster
Comment #5
pobster commentedOkay, as a follow up and to avoid anyone having to do anything technical I've now included a .install file with the tablemanager package. If you run http://www.yoursite.com/path_to_drupal/update.php and go through the update pages, tablemanager will now update your db and tables to how they should look now.
Thanks
Pobster
Comment #6
pobster commented