Foundation docs site returning 404 errors

[rickcurran]

Hi,
It looks like there is an issue with the Foundation docs site, it's giving a 404 error when you try to access any content pages within it:

https://get.foundation/sites/docs/

Thanks,

Rick

[wallbe99]

I am having the same issue.

[Jonnie2417]

The links seem to be correct on the homepage but wrong on the subpages

[phpfui]

I just found this as well. Apparently the links are no longer including the full path. They all start with /, so are not relative. If they were relative to the current page, it would probably all work.

Here is the workaround for now:

Add /sites/docs/ in front of the page.

For example, if you navigate to Button Group from the menu, you end up at https://get.foundation/button-group with a 404 error. You need to add /sites/docs/ before button-group like this: https://get.foundation/sites/docs/button-group

Not sure why this changed. Could be a regeneration issue. Will investigate and see if I can see a commit that went wrong. Hopefully @joeworkman can fix this shortly.

[phpfui]

I suspect this is a generation issue. I can not find any recent commits that would account for this new behavior. It is probably related to a NodeJS or configuration issue that added the absolute paths.

It looks like the site source uses relative links (which should work) here: https://github.com/foundation/foundation-sites/blob/develop/docs/partials/component-list.html

But the generated HTML uses absolute paths (starting with a /). I also noticed that the site supports no extension, or a .html or .htm extension.

Hopes this helps.

[semyl]

Looks like it has been 6 days since this was reported, and it is still an issue. Big turn-off for trying to get info from Foundation docs.

[rickcurran]

@joeworkman Any chance you could take a look at this please?

[frequency-studio]

Still not fixed. Does anyone have a backup copy of the docs that we can upload somewhere? Or are we doomed to using Archive / Wayback Machine until this project finally disappears for good : ( https://web.archive.org/web/20230524083334/https://get.foundation/sites/docs/xy-grid.html

[rickcurran]

@frequency-studio The source for the docs are all here on Github anyway: https://github.com/foundation/foundation-docs

(@joeworkman @zurbrandon @zurbchris Sorry, I'm trying to bump some eyes on this issue please, not sure who else to tag who is able to resolve this?)

[phpfui]

Add /sites/docs/ in front of the page you want for now. All the docs in the repo directly as well.

[guillermolavagnino]

Until they fix it can be accessed by html files, examples:

https://get.foundation/sites/docs/accessibility.html
.....
https://get.foundation/sites/docs/javascript.html
.....
https://get.foundation/sites/docs/grid.html
......

and so on

If you don't find a file, you can track it with Google, for example search:

foundation global styles

Result:
https://get.foundation/sites/docs/global.html

[rickcurran]

@joeworkman @zurbchris @zurbrandon @DanielRuf Can someone please take a look at this issue with the side menu navigations of the Docs pages not working correctly please? It's been two weeks now that it's been broken and there are several issues and discussions threads for the same thing.

I'm not sure what the issue is exactly and what needs to be done to resolve it (looks like some kind of hosting / routing issue) but if I can help in any way please let me know.

This reflects poorly on Foundation as a project when the basic ability to look at the documentation isn't working.

[DanielRuf]

I'm not part of the project anymore and do not have any access to the mentioned documentation and GitHub repos.

If the code is from one of the GitHub repos, then there probably was a change, which caused this.

[joeworkman]

Sorry for the delay guys. I just wrapped up a big launch until yesterday and I have had to put the blinders on to get it all done.

This is very strange. I am not sure how this happened because I have not changed the docs site for a while. I will look into it now.

[joeworkman]

OMG! So it's all fixed now. But let me tell you the story of the past 12 hours....

The build has worked and had not changed for like 7 months. However, the links were broken on server hosted by Netlify. Foundation required a pretty old version of node. Netlify suggested that I update node. Well in order to do that, I needed to completely overhaul the dependencies and run a million tests to ensure that we could run on a newer version of node.

So win No. 1 today is that we have now have Foundation 6.8.0. This version now requires node 16 but will also run great under node 18 and 20. This is a pretty awesome win if you ask me.

With all of that published, I was feeling pretty good with myself and published the new build to Netlify. No dice. 😭

After probing and looking around, Pretty URLs was enabled on the site. This completely modifies your URLs to your pages. I turned off that checkmark and it was magically fixed! They must have recently launched this feature and turned it on by default.

It could have been a 30sec fix had I known. But now we have F6.8, so let's call it a good day. 😎

[rickcurran]

@joeworkman Ack! That sounds like a bit of a task – thank you for sorting all of that out! I'll need to check out F6.8, I've been running everything with node 14 :) Thanks again for dealing with that!

[rickcurran]

@joeworkman Is it possible to use the Zurb template install option with 6.8? As per these installation instructions:

https://get.foundation/sites/docs/installation.html#experienced-template-installation

[joeworkman]

I have not updated the zurb template yet. What does that do for you that the sites template doesn't? I will not be maintaining panini if that is why. It has been replaced by proton.

[rickcurran]

@joeworkman Yep, it was really all the other things that the Zurb template provides src / dist compiling of CSS and JS files, I do also use Panini but I'm not strongly tied to that, but I do have a workflow that is based around how that template works, albeit with a few modifications to the gulpfile.babel.js. To update it do you think it would be matter of updating the shared dependencies that the sites template uses, and then figure out the updates for the remaining ones to get it to work under newer versions of node?

I'm aware the set up I use is a little fragile due to relying on node 14 to work, thankfully it keeps working but it's better to try and update it if possible, so I'd be keen to take a look at updating the Zurb template if I can figure it out. Let me know if you have any pointers / advice! Thanks!