Error page

[finanalyst]

a) there is an Errors page in the 'more' drop down on the navigation bar

• the intention is to encourage community members to find the errors and eliminate them
• errors can occur when links (eg. external web pages) are no longer active
• they also exist because links to internal targets are misspelt in some way

This is an addition of mine to the work I did when developing Collection. I thought it would be useful in general.

Should I leave it in?

b) Other test results could be added to the errors page. Any suggestions?

c) There is a problem with the test as some valid links seem - I think - to be triggered. This may be due to the work to add extra functionality, so I need to look at it.

[coke]

My preference is to leave this only in debug builds and remove it from the prod site.

[finanalyst]

removing this issue. Link-Error-Test plugin is broken and needs work. This is not urgent

[finanalyst]

Reopening this issue. Link-error-test plugin partially repaired. Still has problems.

This is related to the issue for testing for bad links

Error report has been attached to more->anomalous links. It is picking up some 404 on remote sites, and a domain not recognised.

Some local errors are being incorrectly flagged as internal errors.

Quite a few missing files, so not all secondaries are being generated.

[coke]

There are a LOT of colors on this error page, and I find this jarring. My naïve suggestion is to replace the colored nested lists with headers per page and a table of issues on that page (or perhaps a single table where page is the first column).

[coke]

That said, any style changes can happen later, and I'm OK with closing this as completed and opening separate tickets for the remote link section, and for the UI if others agree.

[finanalyst]

I'm happy for the colours and UX to change in any way. The styling is all in Website/plugins/link-error-test/ so its just a SCSS change.

[finanalyst]

There are many link errors. However, I think the majority are now content errors. a) I have looked carefully at the ID generation in Pod::To::HTML when X<> markup is used. index-entries seem to be a major source of problems. b) Some X<> markup has been removed from pod6 sources since the official docs were last generated. This may have been related to the issue where links were causing the title to be above the window. Eg a callsame reference in 101-basics refers to functions#index-entry-dispatch-callsame. The anchor in the html on docs.raku.org should have been generated by an X<> mark up. That markup has been removed in Language/101-basics.pod6

I need some help removing the errors in the content files.

[coke]

We should disable the error page for the initial go live, but it's not urgent. Any other issues can be handled post go-live.

[finanalyst]

disabled for Go-Live. But it should be available for developer views, when we get those

[finanalyst]

@coke I have been looking at the index-entry failures. They are soft failures because the web page is opened, but the correct place on the page is not found.

I need a discussion with someone to go forward on this. There are several possibilities

• there is a simple fix and I cant see it
• there have been different ways to generate the ids for headers over time, leading to inconsistent links.
  • a =head1 X<callsame|Subroutines; callsame> markup will have an id #callsame because it is a header, but it will also have #index-entry-Subroutines_callsame-callsame because of the X.
  • it will not have #index-entry-callsame but this is sometimes what is referenced.
• a solution might be to have multiple <a for each type of id.

Alternatively, the Rakudoc sources could be edited.

I'm loosing the plot a bit.

[finanalyst]

@coke @2colours @cfa I think finally I have a handle on all the index-entry- links.

• there is an error page in new-raku It can be reached via more->About
• I have changed the format of the output, so less garish colours and simpler to understand
• There may still be some systematic errors, but I'd need help to identify errors that were not in the old site but are in the new site.
• I have changed the internal linking algorithm in Composite pages to the Documentable version, so links to /routine/cmp that are hard-coded in order/cmp will now work

These changes needed work on Raku::Pod::Render. I haven't uploaded the new version of RPR to fez. I have all the tests working now, but I want to do some more checks.