Skip to content
New issue

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

[BUG] Docs are not automatically building with newest MarkDown content #2114

Closed
ysuarez opened this issue May 25, 2022 · 2 comments
Closed
Labels
Type: bug identifies a problem in the software with clear steps to reproduce

Comments

@ysuarez
Copy link
Contributor

ysuarez commented May 25, 2022

What steps does it take to reproduce the issue?

Visit this official docs page and see that the changes from this merged PR are not reflected

Here is a link that displays errors in building docs.
https://github.com/Islandora/documentation/actions

  • When does this issue occur?

n/a

  • Which page does it occur on?

In a few official doc pages that should have newer content, for example https://islandora.github.io/documentation/installation/docker-maintain-drupal/

  • What happens?
    n/a

  • To whom does it occur (anonymous visitor, editor, administrator)?

All visitors to the official docs.

  • What did you expect to happen?

That the latest documentation commits would lead to new markdown content.

Which version of Islandora are you using?

Any related open or closed issues to this bug report?

Screenshots:

@ysuarez ysuarez added the Type: bug identifies a problem in the software with clear steps to reproduce label May 25, 2022
@rosiel
Copy link
Member

rosiel commented May 25, 2022

Found the source: mkdocs-material-insiders, our theme, requires pymdown-extensions>=9.4 , but pymdown-extensions dropped python 3.6 support back in 9.2. Our Travis environment runs on python3.6.7, which seems to be a default. We might be able to specify the python version in the Travis file to something more recent.

@rosiel
Copy link
Member

rosiel commented May 25, 2022

Resolved with #2115

@rosiel rosiel closed this as completed May 25, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: bug identifies a problem in the software with clear steps to reproduce
Projects
None yet
Development

No branches or pull requests

2 participants