Issue 73 in uguu: patching breaks "go up" links

0 views
Skip to first unread message

ug...@googlecode.com

unread,
Aug 30, 2010, 3:01:44 PM8/30/10
to ug...@googlegroups.com
Status: Accepted
Owner: ruslan.savchenko
Labels: Type-Defect Priority-Medium Component-Web

New issue 73 by ruslan.savchenko: patching breaks "go up" links
http://code.google.com/p/uguu/issues/detail?id=73

"go up" links can be broken and lead to different page of parent directory.
I assume something is wrong with patching

ug...@googlecode.com

unread,
Aug 30, 2010, 3:16:27 PM8/30/10
to ug...@googlegroups.com

Comment #1 on issue 73 by ruslan.savchenko: patching breaks "go up" links
http://code.google.com/p/uguu/issues/detail?id=73

more info: pathfile_id is a rubbish:

uguu=> select * from paths where tree_id = 13 and parent_id = 2 and
parentfile_id = 544;
tree_id | treepath_id | parent_id | parentfile_id |
path | items | size
---------+-------------+-----------+---------------+---------------------------+-------+------------
13 | 3730 | 2 | 544 | anime/Kannagi
=Ayako= | 13 | 2334016664
13 | 4596 | 2 | 544 | anime/Kanamemo
=polished= | 13 | 3910392927
(2 rows)

uguu=> select tree_id,treepath_id,pathfile_id,treedir_id,name from files
where tree_id = 13 and treepath_id = 2 and name in ('Kannagi
=Ayako=', 'Kanamemo =polished=');
tree_id | treepath_id | pathfile_id | treedir_id | name
---------+-------------+-------------+------------+---------------------
13 | 2 | 581 | 4596 | Kanamemo =polished=
13 | 2 | 582 | 3730 | Kannagi =Ayako=

ug...@googlecode.com

unread,
Aug 30, 2010, 3:20:34 PM8/30/10
to ug...@googlegroups.com

Comment #2 on issue 73 by ruslan.savchenko: patching breaks "go up" links
http://code.google.com/p/uguu/issues/detail?id=73

what i mean is "parentfile_id is a rubbish". This should be fixed.

ug...@googlecode.com

unread,
Sep 1, 2010, 1:11:25 PM9/1/10
to ug...@googlegroups.com
Updates:
Status: Fixed

Comment #3 on issue 73 by ruslan.savchenko: patching breaks "go up" links
http://code.google.com/p/uguu/issues/detail?id=73

fixed in revision 3d31206d43

Reply all
Reply to author
Forward
0 new messages