mkdocs-material deployment with Groups plugin fails with Error: 'GroupPlugin' object has no attribute 'is_serve'

[shamoon]

mkdocs-material deployment with Groups plugin fails with Error: 'GroupPlugin' object has no attribute 'is_serve'

[jimporter]

@kamilkrzyskow mike's loading of the config is totally separate from the mkdocs build action that happens later (mike can't really control MkDoc's internal plugin lifecycle anyway). This way avoids any possible strangeness with nested startup events, and gives plugins a chance to clean themselves up during the mike "pre-build" phase.

[jimporter]

OK, if the mkdocs build happens later then it's all good, and sorry for jumping the gun. I'm still unsure whether or not running the on_config event for all plugins is really necessary during load, as it seems to me you only need to run the mike's plugin on_config event to get what you need. 🤔

Plugins can do arbitrary things to transform the config during on_config, so we probably want to do that. For example, someone could write a plugin that automatically fills in values for remote_branch and remote_name (or even fill in some special values for the mike plugin).

[kamilkrzyskow]

For continuity, since squidfunk/mkdocs-material@55fe1cc the Group plugin in mkdocs-material won't crash mike. However, running on_config without first running on_startup should still be addressed here.

mike/mike/mkdocs_utils.py

Lines 30 to 33 in 533e996

	def load_config(config_file=None, **kwargs):
	with _open_config(config_file) as f:
	cfg = mkdocs.config.load_config(f, **kwargs)
	return cfg['plugins'].run_event('config', cfg)

[shamoon]

Thanks for your continued dedication to the project!

[kamilkrzyskow]

But why are both startup and shutdown being run during load of the config @jimporter?
I feel like this will completely break the lifecycle of plugins that open a resource in startup then use it later in post_build and close the resource in shutdown.
I think any event triggers should be outside of the load_config utils function and should be exported into the driver itself to mimic the proper event lifecycle, but I'm just guessing.

[kamilkrzyskow]

Unless this is a patch just for the load function, and later on it runs the full lifecycle again. I didn't check how the driver works in it's entirety.

[kamilkrzyskow]

OK, if the mkdocs build happens later then it's all good, and sorry for jumping the gun.
I'm still unsure whether or not running the on_config event for all plugins is really necessary during load, as it seems to me you only need to run the mike's plugin on_config event to get what you need. 🤔