rejetto forum

Software => HFS ~ HTTP File Server => Bug reports => Topic started by: maverick on February 24, 2009, 08:12:49 AM

Title: New Flag - build 226
Post by: maverick on February 24, 2009, 08:12:49 AM
Build 226 and default template ...

New flag doesn't show in filelist but shows up correctly on a file search.  The error is in the default template.  No problems in my custom template.
Title: Re: New Flag - build 226
Post by: rejetto on February 24, 2009, 12:27:19 PM
i tested by specifying 1440 minutes (1 day) and listed a real folder with the default template.
only the right files were marked, and they did.
so, no luck trying to reproduce it.
can someone confirm this bug?
Title: Re: New Flag - build 226
Post by: luca69 on February 24, 2009, 01:16:25 PM
Tested with default template and flag time of 2 minutes: it works fine
Title: Re: New Flag - build 226 and build 228
Post by: maverick on February 28, 2009, 08:58:23 AM
Quote
i tested by specifying 1440 minutes (1 day) and listed a real folder with the default template.
only the right files were marked, and they did.
so, no luck trying to reproduce it.
can someone confirm this bug?

New FlagBuild 226 and Build 228 with default template ...
New flag doesn't show in filelist but shows up correctly on a file search.  The error is in the default template.  No problems in my custom template.

Try this ...

1. Virtual Folder
    - virtual subfolder (filelist new flag ok)
       - real subfolder (filelist new flag not shown)

2. Search finds the new flag at all levels shown above

3. New Flag Setting used 120 minutes




Title: Re: New Flag - build 226
Post by: rejetto on February 28, 2009, 01:34:04 PM
tested, and it works here.
see my screenshot, A and B are virtual, temp is real.
flag time set to 14400 (10 days).

can you please try to reproduce the problem on a clean HFS ?
Title: Re: New Flag - build 226
Post by: maverick on February 28, 2009, 02:33:44 PM

Re-tested and got the same results.  Re-checked further and I found the problem to be a diff template that didn't affect my customized template but did affect the default template.  Resolved problem.