Not compatible with composerkit

[FlorianBoe]

Hi Scott,
I had a look at your plugin today and evaluated it for a few projects. I find the plugin very useful, especially for projects with a lot of older content.

I’ve noticed that the plugin doesn’t work with a Composerkit project structure. This is because, in run-panel-scan, you launch a new Kirby instance that isn’t aware of the differently configured roots.

To allow use with a different Kirby project structure, additional configuration options would be required. Would you be interested in such an adjustment?

[scottboms]

If you have some suggestions to allow for this, I'm definitely open to incorporating that. Feel free to submit a PR.

[FlorianBoe]

I'll try to find some time for a PR.

[scottboms]

I've finished (I believe) adding Composer installation support but not sure if there's anything else that needs to be addressed based on this issue. Version 1.0.2 hopefully does the trick.

[FlorianBoe]

Hi Scott,
I see that you have added Composer support. However, the package isn't listed on Packagist yet.

The problem I described regarding the unresolved path for configuring the cache and content folders is also independent of this: It seems that the link scanner runs in a worker that doesn't have the same configuration options as the main Kirby instance.

The only solution I can think of is to pass on other paths via an option in the plugin, build a temporary app instance and read these options, then reuse them in the real worker kirby app instance.

But this feels a bit hacky...

[scottboms]

Should be all good with packagist now, but not sure what the right thing to do is about the other matter but will chew on a that a bit.