Bug 444728 - Saved Searches are not listed in the page footer
Summary: Saved Searches are not listed in the page footer
Status: RESOLVED FIXED
Alias: None
Product: bugs.kde.org
Classification: Websites
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Unspecified
: NOR normal
Target Milestone: ---
Assignee: KDE sysadmins
URL:
Keywords:
: 444759 444900 (view as bug list)
Depends on:
Blocks:
 
Reported: 2021-10-31 16:47 UTC by gjditchfield
Modified: 2021-11-05 09:52 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description gjditchfield 2021-10-31 16:47:07 UTC 
SUMMARY
I have several saved searches, which used to be listed in the home page footer.  The new layout doesn't list them.  They are still available through Preferences > Saved Searches, but that is not as convenient.  (Note also the "Show in Footer" column of Saved Searches, which is meaningless at the moment.)
Comment 1 D. Debnath 2021-11-01 08:34:49 UTC 
It has been fixed. Please refresh your force refresh your browser with Ctrl + Shift + R
Comment 2 Albert Astals Cid 2021-11-01 08:39:37 UTC 
*** Bug 444759 has been marked as a duplicate of this bug. ***
Comment 3 Albert Astals Cid 2021-11-01 08:40:22 UTC 
(In reply to D. Debnath from comment #1)
> It has been fixed. Please refresh your force refresh your browser with Ctrl
> + Shift + R

That's kind of a not great solution, we're going to get one bug report per person that doesn't see them, can't we actually fix this without user interaction?
Comment 4 D. Debnath 2021-11-01 08:44:48 UTC 
(In reply to Albert Astals Cid from comment #3)

> That's kind of a not great solution, we're going to get one bug report per
> person that doesn't see them, can't we actually fix this without user
> interaction?

Unfortunately, this is how browsers cache website resources. I'm not sure what can be done about this other than just telling the people reporting the bugs that it has been fixed.

Also, can you confirm that you can see your saved searches at the bottom of the page now?
Comment 5 Albert Astals Cid 2021-11-01 08:56:38 UTC 
(In reply to D. Debnath from comment #4)
> (In reply to Albert Astals Cid from comment #3)
> 
> > That's kind of a not great solution, we're going to get one bug report per
> > person that doesn't see them, can't we actually fix this without user
> > interaction?
> 
> Unfortunately, this is how browsers cache website resources. I'm not sure
> what can be done about this other than just telling the people reporting the
> bugs that it has been fixed.

I have not much idea about webdev, but i can't see a world in which this is not fixable somehow. Searching for "how to force browser to reload cached css/js files" returns some ways to do that, now sure how easy that is to implement in bugzilla internals.

> Also, can you confirm that you can see your saved searches at the bottom of
> the page now?

Yes, that is fine.
Comment 6 D. Debnath 2021-11-03 19:02:47 UTC 
*** Bug 444900 has been marked as a duplicate of this bug. ***
Comment 7 D. Debnath 2021-11-05 09:52:54 UTC 
(In reply to Albert Astals Cid from comment #5)
> (In reply to D. Debnath from comment #4)
> > (In reply to Albert Astals Cid from comment #3)
> I have not much idea about webdev, but i can't see a world in which this is
> not fixable somehow. Searching for "how to force browser to reload cached
> css/js files" returns some ways to do that, now sure how easy that is to
> implement in bugzilla internals.
Thanks to this hint by this comment: https://www.reddit.com/r/kde/comments/qmex5t/kde_bugtracking_page_was_revamped/hje0rpl/ the cache will be forcefully refreshed after the next merge :)