View Issue Details

IDProjectCategoryView StatusLast Update
0008421mantisbtotherpublic2007-10-04 01:37
Reportervboctor Assigned Tovboctor  
PrioritynormalSeveritymajorReproducibilityhave not tried
Status closedResolutionfixed 
Product Versiongit trunk 
Target Version1.1.0rc1Fixed in Version1.1.0rc1 
Summary0008421: Recently visted is showing some serialized filter instead of bug ids
Description

It seems that recently visited is picking up the wrong token from the database. This happens on this bug tracker. Following is a sample recently visited output, this is shown once I login:

Recently Visited: a:40:{s:8:"_version";s:2:"v8";s:10:"_view_type";s:6:"simple";s:13:"show_category";
a:1:{i:0;s:1:"0";}s:13:"show_severity";a:1:{i:0;i:0;}s:11:"show_status";
a:1:{i:0;i:80;}s:8:"per_page";i:50;s:17:"highlight_changed";i:6;s:11:"reporter_id";
a:1:{i:0;i:0;}s:10:"handler_id";a:1:{i:0;i:0;}s:10:"project_id";a:1:{i:0;i:-3;}s:4:"sort";
s:12:"last_updated";s:3:"dir";s:4:"DESC";s:11:"start_month";i:9;s:9:"start_day";
i:1;s:10:"start_year";i:2007;s:9:"end_month";i:9;s:7:"end_day";i:29;s:8:"end_year";
i:2007;s:6:"search";s:0:"";s:11:"hide_status";a:1:{i:0;i:80;}s:16:"and_not_assigned";
b:0;s:15:"show_resolution";a:1:{i:0;i:0;}s:10:"show_build";a:1:{i:0;s:1:"0";}s:12:"show_version";
a:1:{i:0;s:1:"0";}s:17:"do_filter_by_date";b:0;s:16:"fixed_in_version";a:1:{i:0;s:1:"0";}s:14:"target_version";
a:1:{i:0;s:1:"0";}s:13:"show_priority";a:1:{i:0;i:0;}s:12:"user_monitor";
a:1:{i:0;i:0;}s:10:"view_state";i:0;s:13:"custom_fields";a:1:{i:1;
a:1:{i:0;s:1:"0";}}s:13:"sticky_issues";s:3:"off";s:17:"relationship_type";
i:-1;s:16:"relationship_bug";i:0;s:12:"show_profile";a:1:{i:0;i:0;}s:8:"platform";
a:1:{i:0;i:0;}s:2:"os";a:1:{i:0;i:0;}s:8:"os_build";a:1:{i:0;i:0;}s:10:"tag_string";
s:0:"";s:10:"tag_select";i:0;}

TagsNo tags attached.

Activities

vboctor

vboctor

2007-10-02 00:38

manager   ~0015789

  • The cause of the bug was that the token_update() didn't have a WHERE clause, hence, updating one token will update all the tokens in the table. Hence, "last visited" token got overwritten by the value of a filter token.

  • Did some misc. cleanup in token_api.