This needs changes in places that provide and consume FileItemActionPlugins:
Check for "KonqPopupMenu/Plugin" or "KFileItemAction/Plugin"
Offending providers:
Offending consumer:
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Open | None | T12171 Meta task: KService | ||
| Open | None | T12173 KService: provide solution to migrate away from KServiceTypeTrader/KMimeTypeTrader for loading plugins and parts | ||
| Open | alex | T12250 Port KFileItemActionPlugin usage to KPluginLoader |
Dolphin uses the KFileItemAction/Plugin service type to get the list of available plugins/services in the settings page. Not sure if that is considered a blocker, I'd say it is waiting for KF6 branching ;)
But I generally think the logic to enable/disable plugins should be provided by KIO (where that config is already read).
@nicolasfella In T12256 we agreed that removing the KonqPopupMenu/Plugin is currently a no-goal. Consequently the most of the offending providers are using the desktop files which is considered a valid usage. I would appreciate if you could share your thoughts on T12256#254055.
(I replied in T12256, the last comment here is no longer applicable, desktop files for plugins are being phased out)
Moving this to done then. The dolphin parts are only compatibility logic and the folderview usage has been ported.