Viewing 1 replies (of 1 total)
  • Steven

    (@shazahm1hotmailcom)

    It appears to be either the linkedin or wp stats causing the redirect to the 404 because one of them are stripping either/both the #/?. New iterations if ezTOC support unicode in the anchors ID which is permitted in the HTML5 spec which I think is causes one or both to act in unintended ways. The next update, I’ll force remove those characters.

    You can test this theory ahead of any releases by either removing the ? marks from the headings (temporarily) and/or deactivating the linkd/wp stats.

Viewing 1 replies (of 1 total)
  • The topic ‘404 errors on all ToC’ is closed to new replies.