We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Noticed while working on #2433, the cross-references for the OMERO properties are currently broken. Looking at the historical releases, this regression seems to have introduced during the migration to readthedocs. For instance, compare the omero.ldap.base markup in https://docs.openmicroscopy.org/omero/5.6.4/sysadmins/server-ldap.html vs https://omero.readthedocs.io/en/v5.6.5/sysadmins/server-ldap.html.
omero.ldap.base
The relevant logic is in
omero-documentation/omero/conf.py
Lines 407 to 411 in 72fa9fe
There are a few factors that might have caused this regression but the two obvious ones coming to mind are:
1- change in newer Sphinx major version (5.6.4 was built with Sphinx 3 vs Sphinx 5 for 5.6.5) 2- self-hosted vs readthedocs infrastructure.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Noticed while working on #2433, the cross-references for the OMERO properties are currently broken. Looking at the historical releases, this regression seems to have introduced during the migration to readthedocs.
For instance, compare the
omero.ldap.base
markup in https://docs.openmicroscopy.org/omero/5.6.4/sysadmins/server-ldap.html vs https://omero.readthedocs.io/en/v5.6.5/sysadmins/server-ldap.html.The relevant logic is in
omero-documentation/omero/conf.py
Lines 407 to 411 in 72fa9fe
There are a few factors that might have caused this regression but the two obvious ones coming to mind are:
1- change in newer Sphinx major version (5.6.4 was built with Sphinx 3 vs Sphinx 5 for 5.6.5)
2- self-hosted vs readthedocs infrastructure.
The text was updated successfully, but these errors were encountered: