internal > Bug

Database error with sortorder after upgrading / #1370

Summary

open
Jul 12, 2006
2 hours ... 10 hours
Jul 12, 2006 / pixtur
Oct 16, 2006 / pixtur
 

Attached files

No files uploaded
Possible solutions:
  1. Clear all cookies after each upgrade (which would be a good idea but pixtur does not know how to do this)
  2. Check the order string for valid attributes (which would be a good idea as well, but pretty scarry to code)

Issue report

Minor
Not available
WinXP / Firefox 1.5
v0.061
check order string before sorting with mysql.

 

2 Comments

binder

Oct 14, 2006
another solution
upgrading should delete all stored "TUID"-fields. Therefore all users have to login and problem should be solved?

pixtur

Oct 16, 2006
Reply to another solution
Relogin will not cause a recompution of the TUID. This is not random and is computed from the nickname and password. In the person table its called identifier.

Cookies are stored without this identifier. Their names are automatically generated out of Page and Block id. They are not user specific (which is is probably not very clever).

Maybe this user authorisation stuff and storing of user-specific data should be refactored some day (like not using cookies but a XML field in the person table. The Block, List and Page-Settings could then be sent by Ajax Requests.

 

Comment / Update