Navigation by url to my polymerCLI generated starter-kit works perfectly deployed locally by ">polymer serve", but navigation by url is broken when deployed to an https site.
Entire generated app untouched is on github at https://github.com/datafundamentals/polymer1-starter-debug
README describes exact details.
Entire built and deployed starter-kit untouched is at https://cliffdweller.work/view1 but emptying cache and hard reload may be necessary to display 404 if you nav by menu first.
Really hope that I just haven't skipped some docs somewhere but if so, I'm sure I'll get the flames I deserve. I've been scratching my head on how to even look it up?
The answer to this question was posted polymer error on reloading
There are two fixes required, both the use-hash-as-path property and the use of the #/ as a prefix, so a quick glance at this answer may not be sufficient.
Related
The bounty expires in 3 days. Answers to this question are eligible for a +100 reputation bounty.
SoftTimur wants to draw more attention to this question.
I have a website made by docusaurus 2.0.0-beta.18. I realize that, in production, when I click on items in the sidebar it first goes to https://example.com/docs/a-page. If I reload the page, the url becomes https://example.com/docs/a-page/. This problem does not exist in localhost.
I think a url should be consistent before and after reloading. And like StackOverflow, a good style is not having / in the end.
I searched issues of Docusaurus and it seems that trailingSlash would be the solution. So I added trailingSlash: false under module.exports in docusaurus.config.js.
Then, I deployed this change to my production server with docker and nignix. Loading most of the pages of the website returned a 404 error, while static contents could be loaded. Reloading nginx or recreating docker containers did not help.
So does anyone know if trailingSlash: false would solve this trailing slash problem? And is the 404 error due to trailingSlash?
while hosting react web page on GitHub pages it shows only white pages even though I used the instruction on the deployment of react page on Github.
I think it is due to the react-router-dom (Switch and route ) methods I used to redirect to its page. please give me a solution regarding this.
I tried to edit the package.json file but it not be solved and I also tried to push the file again to that repo branch
https://itsmenick.github.io/my-portfolio/ this is my url
I did all the changes regarding the deployment ie changes in script and all but still not reflected in this.
https://github.com/ItsMeNick/my-portfolio/ this is my github path to repository
Can anyone say what is the mistake ?
That is odd. and the development build works just fine? I noticed there is a cors error from you github page and this could be your issue.
Wanted to create a "tags page" that has all posts with a certain tag. I added it to the header of my website but I keep getting a 404 error. It looks like the tags page isn't building at all?
404 Error page:
https://tiffanychenster.github.io/personal-blog/tag/reviews/
Repo:
https://github.com/tiffanychenster/personal-blog
Confused as to why it works locally but not on Github pages. Thought it might be an error with my nav links but messed around with header.html a lot and got nowhere. Any help with creating the tag page on remote server would be much appreciated
GitHub Pages only allows you to run a number of whitelisted plugins, and jekyll-tagging is not one of them. This means the plugin won't run, the tag pages won't exist and you'll get a 404 response.
The suggested workaround if you want to continue using GitHub Pages and custom plugins is to build the site locally and commit the output. You could commit it to the same repo in a subfolder and then select that folder as your base in GitHub. Alternatively, you could keep the result in a separate repo (i.e. my-website and my-website-output). This way the source git history isn't tied to your output - as well as keeping each repo's file size down.
Another way altogether would be to create the tag pages without the plugin. It would be a bit more manual but not always unmaintainable depending on your use case.
Check out the ruby gem update_tags, which does what you're looking for and works in GitHub pages.
Here's some more context about how and why that gem works.
I am developing a react chrome extension.
I have a footer bar to navigate across my pages(components).
I am using react-router-dom to switch/route between pages.
My extension works perfectly when debugging but, after I build it (npm run build) and Load Unpacked at my extensions, the first page renders good but when I click my footer navigation buttons, my extension shows this message:
The webpage at chrome-extension://myextensionid/ might be temporarily down or it may have moved permanently to a new web
address. ERR_UNEXPECTED
Is it because I did not publish it yet, routing only works after I publish my extension?
Any ideas what can be wrong, can you please help me with this issue?