afbora / kirby-tabs-field Goto Github PK

The current tab's background retains a light gray background color, even if the tab bar is being shown inside a structure field or builder field. See image.

Hey, after updating kirby to 2.5.9 I get an error on structured field after change the language a few times. when I remove the Kirby-Tabs-Field completely from my kirby install the error doesn't ocurre . I guess it is related to this issue: getkirby-v2/panel#1123. Is this something we can fix in the field?

Thanks!

The plugin prevents Kirby from running. I was unable even to see any PHP errors. Happy to supply more detail if/when required.

The tabs plugin doesn't seem to be loading correctly in Kirby 2.2 -- it's just displaying as a checkbox field.

Some plugins/fields broke with the 2.2 update or started to collide with each other, but this was still happening after removing all other plugins and fields. Maybe something with the way custom fields' JS gets loaded in 2.2.x?

When a user submits a form with error, this plugin switches to the offending tab so they can see where their error is located.

Unfortunately, this behaviour doesn't happen within a structure field.

When reloading the panel, the last opened tab will reopen. Unfortunately the first field (title) will be focused. So you can edit the field by mistake. For example when using keyboard shortcuts.

To showcase it, I switched to the second tab, reloaded and typed "asdf":

Hi,

I'm getting HTTP ERROR 500 after copying the plugin to plugins/tabs/ when visiting the Panel. Now, when viewing the site, I got the error Class 'BaseField' not found. Using Kirby 2.5.8.

Any ideas on how to fix this? Thanks.

When adding or editing an entry on Kirby's structure field within any tab but the first one, the opening modal causes the first tab to be selected too (it gets the "current" css class added), so that at the end, both tabs are selected and open at the same time. Thus the content of both tabs shows up and the interface is broken.

First, great filed, just what I needed :)

I've got one little thing:

When I have a tab with a structured field and add or edit the field I end up at the first tab instead of staying on the active (third) tab where the structured field is.

It would be nice to stay on the active tab after adding structured fields or even after a general page save.

I've encountered an issue while using this plugin together the "visual markdown" plugin and a structure field.

I mention the author here, hoping he sees this issue:
@JonasDoebertin

The problem was introduced here: 0271092

The above commit changed the CSS by putting the inactive tabs on top of the active one (or under it, doesn't seem to matter).

The result is that for some reason, the Visual Markdown field, while sitting in a hidden tab, responds to the "drop" event of the structure field when i drag and drop the structure items.

Actually you can see the same problem without the tabs plugin by dragging a structure item into a visual markdown field directly. But having the two fields sitting on top of each other, with one being invisible, aggravates the problem because it's impossible to sort the structure items.

I really don't know if it's more an issue with the tabs plugin (leaving the tabs on top of each other) or the visual markdown plugin (accepting a drop event from a structure field and then crashing).

I'm posting this here because in past versions of this plugin the issue wasn't there and I thought it might be easier to fix here.

Thank you all!