Skip to content
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

Kirby v4 compatibility #12

Merged
merged 2 commits into from
May 25, 2024
Merged

Kirby v4 compatibility #12

merged 2 commits into from
May 25, 2024

Conversation

mrflix
Copy link
Contributor

@mrflix mrflix commented Oct 26, 2022

This PR includes now 2 compatibility adjustments: for Kirby 3.8.0 and for Kirby 4 (alpha.6). I think the adjustments for Kirby 4 break the layouts for Kirby 3.8.0.

Kirby 4.0 alpha.6

Before:
Screenshot 2023-08-08 at 08 53 37

After:
Screenshot 2023-08-08 at 08 53 20

Changelog

  • move k-table class from <table> to new wrapping <div>
  • remove outdated --item-height variable
  • top align fields so that single-line fields look nicer next to multiline fields (writer, textarea)
  • remove border-radius from inputs inside multilist
  • remove gray outline

Kirby 3.8.0

I just found this broken multilist UI in a project using Kirby 3.8.0.:

Screenshot 2022-10-26 at 11 26 08

Turns out that Kirby refactored the structure UI, switching from k-structure-table to the generic k-table with the release of Kirby 3.7.

This pull request adjusts the class names to fix the UI. It also makes the plugin incompatible with Kirby versions before 3.7.

Screenshot 2022-10-26 at 13 35 39

- move k-table class from <table> to new wrapping <div>
- remove outdated --item-height variable
- top align fields so that single-line fields look nicer next to  multiline fields (writer, textarea)
- remove border-radius from inputs inside multilist
- remove gray outline
@mrflix mrflix changed the title Fix UI after Kirby 3.7 structure field switch to k-table Kirby v4 compatibility Aug 8, 2023
@sylvainjule sylvainjule merged commit 07f8697 into sylvainjule:master May 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants