Section extension: extending core sections doesn't work

[tobimori]

Description

This is what I tried:

index.php

App::plugin('tobimori/test', ['sections' => ['submissions' => ['extends' => 'pages']]]);

Submissions.vue:

<script>
export default { extends: "k-pages-section" };
</script>

Result shows the empty pages section but clearly shows that no props are delivered (headline missing)

Let me know if you need anything else

Your setup

Kirby Version 4.4.1

[afbora]

Same issue was posted 1 year ago in forum https://forum.getkirby.com/t/how-to-extend-a-section/30517 but no replies.

[afbora]

@distantnative After long hours I found a clue for you. When I remove the load() method of the mixins, extending works. I think when extends is present, the load method of the mixins disables or overrides the ModelsSection::load() method.

I can take care the issue if solution is easy to implement. Currently I have no idea.

[distantnative]

Ohhhhh, but great catch @afbora to find the source of this.

Maybe a workaround for now could be to not register the JS part as section but as component with k-THENAME-section. That should skip the mixing to be enforced which you wouldn't need when extending the modelssection anyway. Does that work?

For a real solution, maybe we need to consider not enforcing the section mixing but making it optional. Would be a breaking change for those plugins that then need to add it manually.

[afbora]

I couldn't figure out how to implement the workaround exactly. Also, doesn't k-models-section need to be defined to extend ModelsSection? As far as I can see, it isn't in https://github.com/getkirby/kirby/blob/4.5.0/panel/src/components/Sections/index.js

[distantnative]

One would directly extend the models section of choice, e.g. in Tobi's case k-pages-section.

[distantnative]

@tobimori Finally could test the workaround. For now, if you do

panel.plugin("test/test", {
	components: {
		"k-submissions-section": { extends: "k-pages-section" },
	},
});

instead of registering it via sections, it does work for me. Background is, that anything registered via sections gets another Vue mixin injected that overrides the load method (and thus no data, props...) is loaded from the backend. As you're extending the pages section, that already has its own load method defined, so you're absolutely fine without the mixing and can work around the bug this way.