Docs /Tab-EE

Tab-EE Changelog

Tab-EE — Changelog

All notable changes to Tab-EE are recorded here. Versions follow the add-on's addon.setup.php version.

0.8.0

Added

  • Tab-EE works in a Grid on the Auto layout — Grid's default, where it previously did nothing at all. Auto is a table while it fits and stacks into rows, each with its own title bar, once it does not; ExpressionEngine decides as the window resizes. Tab-EE gives it one tab choice for the whole Grid and shows that choice in whichever form the Grid is in: the header-row menu (as in Horizontal) while it is a table, and a strip in every row's title bar once it stacks. Picking a tab in any row moves them all.

    One choice shown two ways, rather than per-row tabs, because the Grid can change form at any moment: per-row choices would have to be reconciled with a shared one every time the width crossed the line. It also hides the same columns in every row in both forms, so what ExpressionEngine measures does not depend on the form it is currently in. Like Horizontal it starts on All fields. Choosing a tab can narrow the table enough for ExpressionEngine to turn a stacked Grid back into a table — that is Auto doing its job, and the choice carries across.

Fixed

  • The tab strip no longer stretches across a stacked Grid row's title bar. ExpressionEngine gives every direct child of a stacked row's cells width:100% — an Auto Grid once it stacks, and any Grid in Live Preview — which pushed the first tab under the drag handle.

  • Renaming a tab no longer moves fields on the Tab-EE fields that reuse it. A tab's handle is what assignments point at, and it was being rebuilt from the tab's name on every save — so renaming "Metadata" to "Meta Info" on a source quietly sent every reusing field's Metadata fields to the default tab. The field's own screen hid this by remapping its dropdowns; the fields reusing the tabs were not on that screen to be remapped. Handles now travel with the names and are kept. Only a new tab takes its handle from its name, with a suffix if that handle is already taken (metadata_2).

  • Saving a Tab-EE field no longer wipes its assignments when the screen shows a notice instead of them. When another Tab-EE field shares the group, or the field is not in one yet, the settings screen shows a notice where the dropdowns go. Nothing was posted for them, and the save took that as "everything on the default tab". The same applied to a Grid column or Bloqs atom showing a notice. Stored assignments are now kept unless the dropdowns post.

  • A field group's tabs no longer disappear when a tabbed Grid, Bloqs block or Fluid item sits above them. The check for a second Tab-EE field in the same group counted any mounted strip on the form, so whichever of those rendered first made the group's own strip stand down and hide itself. It now counts only another field-group strip.

  • Cloning a Bloqs block gives the copy working tabs. Bloqs clones a block's markup, which brought along a strip that looked right but answered no clicks. The copied strip is now replaced with a live one. With nesting on, a child block's strip no longer stops its parent's from mounting.

  • Tabs in a Fluid item meet the line beneath them again. The Tab-EE field's own label was lifted out as a panel caption even inside a Fluid item, where it sat under the title bar and pushed the first field's top border — the line the tabs connect to — about 36px down. The label is no longer shown in a Fluid item.

  • A horizontal Grid whose headers cannot be matched to its columns is left alone. Tab-EE matches a header to its column by position; when the counts disagreed it still hid the cells but not the headers, so every heading after a hidden column sat over the wrong data. It now leaves that Grid untabbed and says why in the browser console.

  • A tinted Bloqs title bar follows a theme switch. The block's own background, under the tint, was read once when the page loaded, so switching between light and dark left the old theme's colour beneath the bar.

  • Removed a notice pointing at an Add-Ons settings page that has not existed since 0.3.0.

Changed

  • A Tab-EE column looks up its sibling columns once per Grid, not once per row (and a Bloqs atom once per block definition). A 50-row Grid ran about 100 identical queries.

0.7.0

Added

  • Tab-EE now works in a Grid set to the horizontal layout. It previously did nothing there, and not for want of space: a horizontal Grid is a real table with one shared header row, so per-row tabs are impossible — twenty rows each showing different columns under one fixed heading. ExpressionEngine also omits the per-row tools bar in that layout, so the strip had nowhere to mount.

    Horizontal therefore gets a different model rather than a smaller one: one tab choice for the whole Grid, hiding a column's heading and its cell in every row together, so everything stays lined up. The strip becomes a single icon at the right end of the header row; clicking it opens a menu of the tabs.

    It starts on All fields, so adding a Tab-EE column to a populated Grid changes nothing until somebody picks a tab. The icon shows when a filter is active, and the header row honours the Title bar colour setting the same way a row's bar does.

    The vertical layout is untouched — it keeps its per-row strip, where each row remembers its own tab. 'Auto' layout is still unsupported: it reflows to stacked rows at narrow widths, where the per-row bar reappears, so it needs its own decision about switching models mid-resize.

Fixed

  • Assigning fields to tabs no longer needs an extra save in Bloqs. Adding a Tab-EE atom to a block definition that already had atoms showed "no saved columns to assign yet" and asked you to save a Grid field — wrong noun and wrong advice — while the same thing in a Grid or a field group listed its neighbours straight away.

    Two causes. The "add an atom" template that every new atom is cloned from carries no settings, so it reported itself as a plain Grid, searched exp_grid_columns with a Bloqs field id and found nothing; the block definition in the request now identifies the host when the settings cannot. And sibling atoms were looked up via the atom's own id, which a new atom does not have yet — they now come from the block definition, which is known before the atom exists.

  • A new field created from a group's page knows which group it is in. ExpressionEngine links to that screen two ways, and only one puts the group in the path; the other passes it as a query parameter, which Tab-EE ignored. A new field on that route listed no neighbours and claimed it was "not in a field group yet".

0.6.3

Fixed

  • Updating now clears up the junk field definitions 0.6.1 left behind. 0.6.2 stopped new ones appearing, but a site that saved a Grid field or a block definition while 0.6.1 was installed already has the rows in its database, and they keep producing the deprecation warnings and the Bloqs fatal until they are removed by hand.

    The update deletes any Grid column or Bloqs atom that has neither a name nor a type, along with the col_id_<n> column Grid added to the field's data table for it, and any Bloqs atom data pointing at the definition. Both fields are required by Grid's own validation and col_type names the fieldtype the column is, so a row missing both cannot function however it was created — while a row missing only one of them is left alone. What was removed is written to the developer log, with the settings each row carried, so the change is reviewable rather than silent.

0.6.2

Fixed

  • A phantom column could break saving a Grid field or a Bloqs block definition, with a wall of "Undefined array key col_name / col_type" warnings and, in Bloqs, a fatal: Call to a member function validateSettings() on null.

    0.6.1 stopped hiding the tabs textarea with display: none, so that ExpressionEngine would stop disabling it and tabs would save. That fixed one problem and created a worse one: Grid and Bloqs keep their "add a column/atom" template on the same form, inside data-group="always-hidden" — EE's own marker for markup that must never be submitted. A control in there that suddenly posts materialises a column row carrying settings but no name or type, and both Grid and Bloqs walk every posted row looking up its fieldtype.

    Tab-EE's controls are now disabled if they sit inside that container and enabled everywhere else, decided at submit. Keyed on EE's marker rather than on visibility: a real column whose panel is merely collapsed is hidden too, and disabling that would trade one silent data loss for another.

0.6.1

Fixed

  • Tabs and field assignments would not save on a field's settings screen. You could add tabs, assign fields, save — and come back to an empty form.

    The cause was Tab-EE's own: the chip editor hid the textarea that carries the tabs with display: none, and ExpressionEngine's settings screen, which disables the controls in its fieldtype panes and then re-enables the ones in force, skips a control that is not laid out. It stayed disabled, and a disabled control is not submitted at all.

    That alone lost the tabs. It also lost the ASSIGNMENTS, which were submitted perfectly well: with no tabs in the request, the save correctly read "this form did not render Tab-EE's controls" and preserved what was stored — discarding what had just been sent alongside.

    The textarea is now clipped rather than removed from layout, so it stays a real enabled control. Two guards sit behind that: it is re-enabled on submit whatever else happens, and a save that receives assignments now honours them even when the tabs are missing.

0.6.0

Added

  • A tabbed field group now draws a panel. A Grid row and a Fluid item arrive with a title bar and a bordered body; a field group had neither, so the tabs floated above loose fields and looked attached to nothing. The fields a strip governs are now enclosed in a box with the tabs on its bar, matched to a Grid's proportions.

    The box is painted onto the fields rather than wrapped around them. The fields a strip governs are frequently not next to each other — a channel's non-group fields interleave with its group's — so a wrapper would have to reorder the form or enclose fields that are not on the tab. Where a run is interrupted the panel segments, which is the honest answer: a field that is not on the tab is not in the box.

    The field's own label becomes the panel's caption, and its caret collapses the whole panel. A Panel title setting overrides that caption.

  • A title bar colour. Any Tab-EE instance can tint the bar its tabs sit on — a Grid row, a Bloqs block, a Fluid item or a field-group panel. Empty means the default, which is unchanged.

    The active tab keeps the body's colour rather than taking the tint: that contrast is what makes a folder tab read as joined to the content below, and a tinted bar strengthens it. Label colour is derived from the tint, so a dark colour gets light labels without anyone having to think about it.

Fixed

  • The active tab could be left white on a dark form (or black on a light one). Its colour is sampled from whatever it sits on, and that was read once at mount — before the theme's styling had landed, or before a theme switch had swapped the stylesheet. It is now re-read until the change settles.

  • Editing tabs on a channel field's settings screen did nothing. The textarea that carries them is disabled on that screen, so it never posted, and the save correctly read "not on this form" and kept what was already stored.

  • Dark-theme borders lifted from #2c2c2c to #3a3a3a.

0.5.0

Added

  • Pro Variables support. Pro Variables ships with ExpressionEngine and puts every variable in a group on a single form — the same shape Tab-EE already tabs elsewhere. A Tab-EE variable now tabs the other variables in its group.

    Add it the way you add any variable: Variables → New, type Tab-EE. You may have to enable it first — Pro Variables ships with only Textarea switched on, under its own Settings → Variable types, and a type that is not enabled is not offered.

    It also works inside a Pro Variables grid, tabbing that grid's columns once per row, exactly as in a channel Grid. That needs no separate setup: a Pro Variables grid is ExpressionEngine's own Grid under a different content type.

Fixed

  • Grid column lookups are scoped by the grid's content type. exp_grid_columns holds the columns of every Grid on a site and the ids restart per type, so a Pro Variables grid whose id matched a channel Grid's field id would inherit that Grid's Tab-EE column as a rival and refuse to be configured — naming a column its author could not see and had no way to remove.

Note

Tabs on grid columns require the Grid's vertical layout, in Pro Variables exactly as in a channel. A horizontal table shares one header row, so hiding columns per row would stop the cells lining up with their headings. Tabs on the variables in a group have no such requirement.

0.4.0

Added

  • Bloqs support. A Tab-EE atom tabs the other atoms in its block, with the strip in the block's own header and each block remembering its own tab.

    Bloqs draws no rule under its title bar, and a folder tab works by connecting to one. Rather than give this one host a different-looking control, Tab-EE supplies the rule itself — as its own full-width element, added only to blocks that have a strip, so an ordinary block is untouched. Bloqs' own header spans less than the block's width, so a border on it would visibly stop short.

  • Fluid support. A Tab-EE field inside a Fluid field-group item tabs that group's fields, scoped to the item — so the same group added twice gives two independent strips.

    A plain single-field Fluid item has no siblings to tab, so nothing renders there.

  • A default tab. Every field now belongs to exactly one tab. Fields you do not assign go to a default tab — named "Content" unless you change it — instead of appearing on every tab, which read as duplication.

    It is derived rather than stored: it appears only while something is in it and disappears once everything has been assigned. A field added long after the tabs were set up therefore lands somewhere visible rather than nowhere.

  • One Tab-EE per container. Two in the same group, Grid, block or item would each hide the fields belonging to the other's tabs. The settings screen now names the existing one, and a second instance stands down and hides itself.

  • A release build. ./build-release.sh produces a zip mirroring an EE web root, so extracting it puts both the add-on and its runtime in place.

Changed

  • The strip collapses to a dropdown at tablet width, not only when it runs out of room. 767px is ExpressionEngine's own control-panel breakpoint, so Tab-EE reorganises at the same width as the interface around it.

  • The add-on icon now ships. It was present but named icon_1.svg; ExpressionEngine matches icon.svg or icon.png exactly and otherwise falls back to a generic icon with no warning.

Fixed

  • Tab handles are no longer re-derived from tab names in the browser. Renaming a tab keeps its handle, so regenerating one produced a handle nothing was assigned to and silently dropped every assignment on that tab.

  • Saving a field from a form that never rendered Tab-EE's controls no longer wipes its tabs and assignments.

  • The chip editor now appears when configuring a Grid column. Grid renames the input, so the editor never initialised there and you got a plain textarea.

  • Assets are versioned by modification time. ExpressionEngine does not version third-party theme assets, so a browser could keep serving the script it had cached from before an update.

  • The per-atom tab selectors work in Bloqs' block editor. Bloqs renders a second, hidden Tab-EE pane for the atom you have not added yet; that pane has no atoms of its own, and its editor was reaching across into the saved atom's selectors and emptying them. Saving in that state stored empty assignments, so this could lose a block's configuration.

  • A renamed default tab shows its own name in the assignment dropdowns. Grid and Bloqs rename the field's inputs, so the name was read as missing and the built-in "Content" was shown in its place.

0.3.0

Changed

  • Tab-EE is configured entirely on the field. The control panel section and the cp_js_end extension are gone; you add a Tab-EE field where the tabs should appear and configure them there.

    ExpressionEngine offers an add-on no render hook on the field-group screen, no update event on a channel field and no insert event on a field group — so configuring from the outside meant decorating screens Tab-EE does not own. A fieldtype owns its own settings form.

  • Grid tabs are configured on the Grid, as a Tab-EE column, rather than in a separate screen listing Grid fields.

Added

  • Reusable tabs. A Tab-EE field can take its tabs from another rather than defining its own. It is a live reference: rename a tab on the source and every field using it follows. Definition only mode makes a field a source that never renders a strip.

    Which fields sit on which tab is always local and never inherited — field ids mean nothing in another group. A reference may only be one level deep, and a reference to a field that no longer exists resolves to no tabs, leaving everything visible rather than hiding anything.

  • Field group support. A Tab-EE field tabs the other fields in its group on the publish form.

Removed

  • The exp_tab_ee_configs table is no longer used. It is left in place on update rather than dropped, because its rows are the only record of how a Grid was tabbed before this version and they cannot be migrated automatically — a column must exist before it can be assigned to a tab. It is dropped on uninstall.

0.2.0

Added

  • The Tab-EE fieldtype and its settings screen: tab chips with inline editing, drag-to-reorder and a live count of the fields on each tab, above a compact row per field with its tab.

0.1.0

Added

  • Per-row field tabs for native ExpressionEngine Grid, configured from a Tab-EE control panel section. Each row keeps its own tab; the strip becomes a dropdown when the row cannot hold it.

    Vertical layout only. Per-row state in a horizontal table would leave rows showing different columns while the headers stayed fixed, so the cells would stop lining up with their headings.