GITHUB . COM {}

Detected CMS Systems:

Wordpress (2 occurrences)

Analyzed Page
Matching Content Categories
CMS
Monthly Traffic Estimate
How Does Github.com Make Money
How Much Does Github.com Make
Wordpress Themes And Plugins
Keywords
Topics
Payment Methods
Questions
Schema
External Links
Analytics And Tracking
Libraries
Hosting Providers

We are analyzing https://github.com/squidfunk/mkdocs-material/issues/5949.

Title:
Regression with nav item direct linking to blog post in 4.40.3 · Issue #5949 · squidfunk/mkdocs-material
Description:
Context In a recent change, directly linking to a blog post from the nav exhibits strange behavior. The nav link works, but that specific blog post is missing the metadata sidebar and it is excluded from the blog index. Bug description O...
Website Age:
17 years and 8 months (reg. 2007-10-09).

Matching Content Categories {📚}

Social Networks
Video & Online Content
Transportation

Content Management System {📝}

What CMS is github.com built with?

Github.com utilizes WORDPRESS.

Traffic Estimate {📈}

What is the average monthly size of github.com audience?

🚀🌠 Tremendous Traffic: 10M - 20M visitors per month

Based on our best estimate, this website will receive around 10,653,586 visitors per month in the current month.

check SE Ranking
check Ahrefs
check Similarweb
check Ubersuggest
check Semrush

How Does Github.com Make Money? {💸}

Subscription Packages {💳}

We've located a dedicated page on github.com that might include details about subscription plans or recurring payments. We identified it based on the word pricing in one of its internal links. Below, you'll find additional estimates for its monthly recurring revenues.

How Much Does Github.com Make? {💰}

Subscription Packages {💳}

Prices on github.com are in US Dollars ($). They range from $4.00/month to $21.00/month.
We estimate that the site has approximately 5,316,011 paying customers.
The estimated monthly recurring revenue (MRR) is $22,327,244.
The estimated annual recurring revenues (ARR) are $267,926,929.

Wordpress Themes and Plugins {🎨}

What WordPress theme does this site use?

It is strange but we were not able to detect any theme on the page.

What WordPress plugins does this website use?

It is strange but we were not able to detect any plugins on the page.

Keywords {🔍}

nav, squidfunk, blog, issue, navigation, posts, post, bug, commented, works, metadata, excluded, mkdocsmkdocs, mission, mkdocs, owner, problem, set, perpil, link, site, entry, working, resolved, blocked, sign, item, behavior, linked, note, edited, edits, plugins, pages, mentioned, page, open, projects, linking, missing, file, author, reporting, reproduction, click, attached, removed, version, plugin, work,

Topics {✒️}

possibly related issues personal information regression squidfunk edits owner open projects bug resolved issue reproduce mkdocs serve squidfunk closed post called entry community edition blog bug reporting guidelines mission nav item click continue reading mission-statement/ validation blog nav item related links reporting specific blog entry specific blog post blog plugin rely upstream issue issue mentioned mission blog post projects milestone bug description explicit titles set comment metadata assignees 'blog/posts/mission mkdocs-material-9 nav link works discussions code docs directly linking author days ago limitations mentioned bug archive_url_format bug report post titles blog entry 3-blog-entry open blog post mentioned pr behavior intentional undefined behavior blog index blog entrypoint blog plugin blog/index 'nav' configuration

Payment Methods {📊}

Braintree

Questions {❓}

Already have an account?
Is this change in behavior intentional?
What was the last version working?

Schema {🗺️}

DiscussionForumPosting:
      context:https://schema.org
      headline:Regression with nav item direct linking to blog post in 4.40.3
      articleBody:### Context In a recent change, directly linking to a blog post from the nav exhibits strange behavior. The nav link works, but that specific blog post is missing the metadata sidebar and it is excluded from the blog index. ### Bug description On my [site](https://speedrun.nobackspacecrew.com/), I link to a specific blog entry under a nav entry called **Mission**. This normally works fine, but in insiders 9.2.7+4.40.3 I get an error: `A reference to 'blog/posts/mission.md' is included in the 'nav' configuration, but this file is excluded from the built site.` The nav link works, and it shows the blog entry, but it is missing the blog metadata like date and author. Other posts that aren't linked in the nav show up in the blog index, but the `mission.md` one is missing. ### Related links - [Reporting a bug](https://squidfunk.github.io/mkdocs-material/contributing/reporting-a-bug/) - #5904 ### Reproduction [9.2.7+insiders.4.40.3-blog-entry-in-nav-not-working.zip](https://github.com/squidfunk/mkdocs-material/files/12505125/9.2.7%2Binsiders.4.40.3-blog-entry-in-nav-not-working.zip) ### Steps to reproduce 1. mkdocs serve 2. See the error `A reference to 'blog/posts/mission.md' is included in the 'nav' configuration, but this file is excluded from the built site.` 3. Click the `Mission` nav item, note it does not have metadata 4. Click the `Blog` nav item, note there is no entry for the mission blog post. 5. Click `continue reading` and note the post called Entry has metadata. ### Browser _No response_ ### Before submitting - [X] I have read and followed the [bug reporting guidelines](https://squidfunk.github.io/mkdocs-material/contributing/reporting-a-bug/). - [X] I have attached links to [the documentation](https://squidfunk.github.io/mkdocs-material), and possibly related [issues](https://github.com/squidfunk/mkdocs-material/issues) and [discussions](https://github.com/squidfunk/mkdocs-material/discussions). - [X] I assure that I have [removed all customizations](https://squidfunk.github.io/mkdocs-material/contributing/reporting-a-bug/#remove-customizations) before submitting this bug report. - [X] I have attached a __.zip file__ with a [minimal reproduction](https://squidfunk.github.io/mkdocs-material/guides/creating-a-reproduction/).
      author:
         url:https://github.com/perpil
         type:Person
         name:perpil
      datePublished:2023-09-03T03:25:05.000Z
      interactionStatistic:
         type:InteractionCounter
         interactionType:https://schema.org/CommentAction
         userInteractionCount:8
      url:https://github.com/5949/mkdocs-material/issues/5949
      context:https://schema.org
      headline:Regression with nav item direct linking to blog post in 4.40.3
      articleBody:### Context In a recent change, directly linking to a blog post from the nav exhibits strange behavior. The nav link works, but that specific blog post is missing the metadata sidebar and it is excluded from the blog index. ### Bug description On my [site](https://speedrun.nobackspacecrew.com/), I link to a specific blog entry under a nav entry called **Mission**. This normally works fine, but in insiders 9.2.7+4.40.3 I get an error: `A reference to 'blog/posts/mission.md' is included in the 'nav' configuration, but this file is excluded from the built site.` The nav link works, and it shows the blog entry, but it is missing the blog metadata like date and author. Other posts that aren't linked in the nav show up in the blog index, but the `mission.md` one is missing. ### Related links - [Reporting a bug](https://squidfunk.github.io/mkdocs-material/contributing/reporting-a-bug/) - #5904 ### Reproduction [9.2.7+insiders.4.40.3-blog-entry-in-nav-not-working.zip](https://github.com/squidfunk/mkdocs-material/files/12505125/9.2.7%2Binsiders.4.40.3-blog-entry-in-nav-not-working.zip) ### Steps to reproduce 1. mkdocs serve 2. See the error `A reference to 'blog/posts/mission.md' is included in the 'nav' configuration, but this file is excluded from the built site.` 3. Click the `Mission` nav item, note it does not have metadata 4. Click the `Blog` nav item, note there is no entry for the mission blog post. 5. Click `continue reading` and note the post called Entry has metadata. ### Browser _No response_ ### Before submitting - [X] I have read and followed the [bug reporting guidelines](https://squidfunk.github.io/mkdocs-material/contributing/reporting-a-bug/). - [X] I have attached links to [the documentation](https://squidfunk.github.io/mkdocs-material), and possibly related [issues](https://github.com/squidfunk/mkdocs-material/issues) and [discussions](https://github.com/squidfunk/mkdocs-material/discussions). - [X] I assure that I have [removed all customizations](https://squidfunk.github.io/mkdocs-material/contributing/reporting-a-bug/#remove-customizations) before submitting this bug report. - [X] I have attached a __.zip file__ with a [minimal reproduction](https://squidfunk.github.io/mkdocs-material/guides/creating-a-reproduction/).
      author:
         url:https://github.com/perpil
         type:Person
         name:perpil
      datePublished:2023-09-03T03:25:05.000Z
      interactionStatistic:
         type:InteractionCounter
         interactionType:https://schema.org/CommentAction
         userInteractionCount:8
      url:https://github.com/5949/mkdocs-material/issues/5949
Person:
      url:https://github.com/perpil
      name:perpil
      url:https://github.com/perpil
      name:perpil
InteractionCounter:
      interactionType:https://schema.org/CommentAction
      userInteractionCount:8
      interactionType:https://schema.org/CommentAction
      userInteractionCount:8

External Links {🔗}(8)

Analytics and Tracking {📊}

Site Verification - Google

Libraries {📚}

Clipboard.js
D3.js
Lodash

Emails and Hosting {✉️}

Mail Servers:

aspmx.l.google.com
alt1.aspmx.l.google.com
alt2.aspmx.l.google.com
alt3.aspmx.l.google.com
alt4.aspmx.l.google.com

Name Servers:

dns1.p08.nsone.net
dns2.p08.nsone.net
dns3.p08.nsone.net
dns4.p08.nsone.net
ns-1283.awsdns-32.org
ns-1707.awsdns-21.co.uk
ns-421.awsdns-52.com
ns-520.awsdns-01.net

9.52s.