-
-
Notifications
You must be signed in to change notification settings - Fork 175
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
3.6 - plugins compatibility #3485
Comments
Komments and Commentions need to be added as well. |
Thanks, I added them to the list above. |
Image Clip also. |
@mynameisfreedom Thanks, added to list. |
These two as well: rasteiner/k3-pagesdisplay-section#9 |
@MaluNoPeleke Added to list. |
These have been fixed and Commentions and Komments have already updated branches for 3.6 (but not released yet officially). |
I've updated the list. |
my mailjet plugin as some views as well but can be considered low priority (if any): |
Added to list. |
I am still working on this: https://github.com/mauricerenck/kirby-podcaster
|
As someone who has just released a custom panel view plugin, is it going to break in 3.6? I'm assuming this is related to the new Fiber system? Edit: Maybe I should just go test it myself 😅 |
@afbora Is it feasible to have my plugin compatible with both 3.6 and older versions? Or is this a headache waiting to happen? |
@PaulMorel You can use releasement. For example: v0 is |
@PaulMorel I have just worked on an update for my Versions plugin, which also uses a view. You can actually both register the view in the frontend for older versions and register an area in the backend for 3.6+. 3.6 will ignore the view defined in the frontend and 3.5 and previous versions will ignore the area. Unless your code runs into other breaking changes, you can make an update to your plugin that supports both scenarios. |
image-clip (develop branch) works now with beta2 |
@mullema Great! I've updated the list. |
Hi there is work in progress for the |
Here is another one WIP that could need some support: https://github.com/flokosiol/kirby-translations/tree/kirby3 |
Thanks @lukasbestle, That's exactly what I ended up doing. Registering the area for 3.6+ worked fine and I had very little changes to do for it to still work in 3.5. |
Can you pease add this plugin to the list? |
@MaluNoPeleke I've added to the list. |
Markdown Field: fabianmichael/kirby-markdown-field#116 (issue refers to the |
Just for completeness, updating the info in the original post on top: Commentions is now 3.6-compatible in newly released versions on both the stable branch (v1.0.5) and the WIP v2.0 branch (v2.0-beta.4). |
Komments latest release (and main branch) is now 3.6 compatible and 3.5 "backward" compatible. |
Kirby Podcaster now works with 3.6 |
Can be removed as I cannot reproduce anymore after latest plugin update |
Trying to migrate my OAuth Plugin to 3.6. I hooked into the Vue Router to prevent a redirect to the install view so you can still login with a valid OAuth user even when there is no user created yet. // always route back to panel home when trying to access installation view
if (panel?.app?.$route?.path === "/installation") {
panel.app.$go("/");
}
// prevent routing to the installation view (e.g. like the login view does)
panel?.app?.$router?.beforeEach((to, _, next) => {
if (to.path !== "/installation") next();
}); https://github.com/thathoff/kirby-oauth/blob/kirby-3.6/src/index.js#L12 Any hints on how to accomplish this with Kirby 3.6? |
I always get a error 500 after installing it on Kirby 3.6 RC.3 without any additional information (debugging turned on). |
Would you be so nice and create an issue in the komments github repo? This is more in my focus, I will have a look at it. Maybe with some additional info about your setup. That would be nice. |
Done: mauricerenck/komments#24 |
https://github.com/sylvainjule/kirby-pagetable I've merged the 3.6 support into the latest release I'm looking into the bouncer plugin next week! |
Can you add this plugin and maybe offer support to make it compatible with Kirby 3.6 again? |
@MaluNoPeleke This plugin has nothing to do with the changes introduced in 3.6, it wasn't compatible with 3.5 either. Let's not mix things up. |
Oh, sorry, sure. |
Let's collect a list of plugins we know 3.6 will break (and where we could send PRs or give tips how to update):
Done
Migrate to 3.6 rasteiner/k3-trevor-view#16
https://github.com/medienbaecker/kirby-modules/releases/tag/2.2.1
Migrate to 3.6 lukasbestle/kirby-versions#6
Migrate to 3.6 sylvainjule/kirby-pagetable#69
Custom Panel view
feature/kirby-3-6
branch is compatible with 3.6: https://github.com/mauricerenck/komments/tree/feature/kirby-3-6develop
branch is compatible with 3.6: https://github.com/sebastiangreger/kirby3-commentions/tree/develophttps://github.com/chrisbeluga/kirby-navigation/releases/tag/2.1.0
Kirby 3.6.0-beta.1 compatibility rasteiner/k3-pagesdisplay-section#9
Kirby 3.6.0 compatibility texnixe/k3-filesdisplay-section#4
Migrate to 3.6 sylvainjule/kirby-backups#4
develop
branch: https://github.com/mullema/k3-image-clip/tree/developIncompatibility with Kirby 3.6 : Str::template() parameters deprecated mzur/kirby-uniform#219
https://github.com/amteich/kirby-helpsection/releases/tag/2.0.0
3.6 compatibility with improved code standarts gearsdigital/reporter-for-kirby#32
3.6 compatibility bnomei/kirby3-mailjet#8
Kirby 3.6 compatibility bvdputte/kirby-autopublish#8
2.0.0 is compatible with 3.6: https://github.com/steirico/kirby-plugin-custom-add-fields/releases/tag/v2.0.0
Hooks into
vue-router
and store modules heavilyBeta with 3.6 support: https://github.com/distantnative/retour-for-kirby/releases/tag/4.0.0-beta.1
[next| Compatibility with Kirby 3.6 fabianmichael/kirby-markdown-field#116 The next branch is compatible with 3.6 but still under development
Please feel free to edit this post, so we have the full list always on top.
The text was updated successfully, but these errors were encountered: