Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rss feed for searches doesn't show up #455

Open
anarcat opened this issue May 13, 2014 · 3 comments
Open

rss feed for searches doesn't show up #455

anarcat opened this issue May 13, 2014 · 3 comments

Comments

@anarcat
Copy link
Contributor

anarcat commented May 13, 2014

https://example.net/bookie/anarcat/recent has a proper <link> tag for pointing at the RSS feed:

    <link id="rss_url" href="https://example.net/bookie/anarcat/rss" rel="alternate" title="
    Latest bookmarks from anarcat
" type="application/rss+xml" />

but https://example.net/bookieanarcat/recent/toread doesn't, for an obvious reason: that URL is wrong! this URL gets generated from https://example.net/bookie/anarcat/recent after typing "toread" then enter in the search box.

adding a slash to that URL fixes the problem.

i'm using Chromium Version 34.0.1847.132 Built on Debian 7.5, running on Debian jessie/sid (265804). i do not know which version of bookie my friend has installed for me.

@mitechie
Copy link
Member

Sorry, I've read this a few times but I'm a little bit confused. Can you duplicate this on the live site on bmark.us in some way I can easily link/see? I'm trying to determine if you're reporting an example of #148 where the url generated doesn't work in the sub directory path or if you're saying that the rss url requires a / at the end of it? I can't seem to duplicate the requirement for a / in the rss url to work.

@anarcat
Copy link
Contributor Author

anarcat commented May 20, 2014

i believe this is related to @jcharaoui's bug report and i can reproduce on his instance. so it's not that it needs a trailing slash, it's the subdirectory thing.

@mitechie
Copy link
Member

Ok, awesome. Well, not awesome, but known issue with work in progress. I'll leave this bug open, but since it's linked to #148, when we get that closed up we'll try to QA and verify that this is corrected.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants