`mkdocs-glightbox` does not work properly with Material for MkDocs blogs

[lilacpixel]

When the mkdocs-glightbox plugin is paired with Material for MkDocs and its built-in blog plugin, the lightbox does not work as intended on blog archive pages. Images on single post pages are linked properly and can be clicked to expand, but the same images are missing the lightbox when viewed on the main post listing and archive pages.

Steps to reproduce:

1. Create a new MkDocs site and enable the Material for MkDocs theme, glightbox, and the blog plugin.

mkdocs.yml

site_name: MkDocs
theme:
  name: material
plugins:
  - blog
  - glightbox

2. Create a blog post and add an image.
3. Build site and open the main blog page. The image is missing its link and cannot be clicked to view in a lightbox.
4. Click on the blog post title to open the single post view. The image is properly linked and pops up the lightbox when clicked.

Previously reported to the mkdocs-material team here.

Thanks for taking a look! 😊

[jaywhj]

@lilacpixel

This was caused by mkdocs-glightbox not adapting the template, I've given the fix, submitted the PR and waiting for the author's merge!

Now you can install the fixed version first using the following command:

pip install mkdocs-glightbox@git+https://github.com/jaywhj/mkdocs-glightbox@8802eba

[chroberino]

When the mkdocs-glightbox plugin is paired with Material for MkDocs and its built-in blog plugin, the lightbox does not work as intended on blog archive pages. Images on single post pages are linked properly and can be clicked to expand, but the same images are missing the lightbox when viewed on the main post listing and archive pages.

I am experiencing the same issue. I have tested the changes from PR #69 and I can confirm that it solves this issue!

[jaywhj]

@lilacpixel @chroberino

Yes, this bug is fixed, mkdocs-glightbox there are other bugs that are fixed in my branch version, waiting for the author to merge this first before I can PR.

Additionally, you can try Material's next generation MaterialX, which offers continuous updates and maintenance, and the difference is described here: https://jaywhj.github.io/mkdocs-materialx/differences/