Closed ftorres16 closed 3 years ago
Hello @ftorres16
Thanks for using our template, you can see the latest build of our theme is performing well on search https://themes.gohugo.io//theme/parsa-hugo/
I think you messed with your baseURL, that's why this is happening to you.
Hello @somratpro
Thanks for your reply.
I double checked and the baseurl
field in config.toml
and it matches the URL of my blog with the same formatting as in example site.
I also inspected the search form in the HTML for the example you provided and compared it to my own. They match perfectly, aside from the URL in "action".
I inspected the requests on my browser and my blog is sending the request to https://<blog>.com/search?s=test
(same as on your demo).
However, on my blog I get a 302
response with the header location /search/
that takes me back to an empty search page.
I also noticed that /search/?s=<search_term>
works fine on my website, but not /search?s=<search_term>
.
I figured it could be because my folder structure was content/search/_index.md
and the example site had content/search.md
, but I made the change and it is still not working.
Well, can you share your repository with me?
I sent you an invite
try to add /
at the end of your baseURL. baseurl = "https://lapolino.com/"
When I do that and search I get two //
after .com
but none between the search
and the ?s=<term>
. So instead of an empty search page I get 404
Ok, then remove it. and I give an update to the theme, try it now
It worked, thanks!
So a star to the repository would be fantastic.
Hi,
I am using the parsa-hugo theme for a personal blog, and I am using the latest version from the master branch on Gihub.
I have noticed that the search bar doesn't seem to be working for me on the production version of my blog (it works fine on
hugo server
).When I type a search term on the search bar and hit enter it redirects me to https:///search/ so no results are found.
I have found that when I do it with the local server the URL is instead http://localhost:1313/search/?s=, which works just fine.
What is more, if I manually tipe the
?s=<search_term>
on the live version I can see the search results just fine.I am not sure how to continue debugging this issue, or if it is related to parsa-hugo or my own build/deploy process.