breautek commented on issue #1278:
URL: https://github.com/apache/cordova-docs/issues/1278#issuecomment-1374540306

   Interesting. I've done a bit further research and found several pages that 
did properly do a redirect, and some that didn't.
   
   It seems to be powered by 
https://github.com/apache/cordova-docs/blob/806350c7c1ab0a230919c598558cb35263020eb0/www/_layouts/docs.html#L176-L187
   
   It produces a link with the same URL but replacing the version with `latest` 
in the URL for the link. However, the build process actually builds a list of 
generated URLs called `all-pages`, which the above snippet seems to use to 
decide to fallback to the documentation root/index.
   
   So this indicates that I was in fact wrong and redirecting to the same 
documentation page of of a different version is the intended behaviour.
   
   It's been awhile since I built locally, but my last build does include some 
of the URLs that isn't working. Unfortunately I'm not in a position to attempt 
to build as jekyll seems to depend on Ruby2, which is basically EOL now and 
Ubuntu 22 doesn't have official support anymore. Trying to install Jekyll on 
Ruby3 has errors.
   
   I'll be curious to see if the generated `all-pages.yml` file contains or is 
missing some of those URLs that isn't redirecting to the same version, such as 
`/docs/en/latest/guide/platforms/android/index.html`. If it's missing that 
line, then we have to look at why the generated `all-pages.yml` file is missing 
that page, otherwise we need to look at why the template seems to think it's 
missing.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to