Skip to content

Fix/migration forms v3#100

Merged
TDannhauer merged 2 commits intoFRAMEWORK_6_0from
fix/migration_Forms_V3
May 7, 2026
Merged

Fix/migration forms v3#100
TDannhauer merged 2 commits intoFRAMEWORK_6_0from
fix/migration_Forms_V3

Conversation

@TDannhauer
Copy link
Copy Markdown
Contributor

Drop deprecated ->type access on form variables (V3 migration)

Summary

Horde\Form\V3\BaseVariable::__get('type') emits a WARN-level deprecation
("Variable property 'type' is deprecated, please remove '->type'") on every
access, because in V3 the variable IS its own type. With Turba (and any other
app rendering V3 variables) this floods the Horde log with dozens of warnings
per page render.

@TDannhauer TDannhauer requested a review from amulet1 May 7, 2026 15:43
@amulet1
Copy link
Copy Markdown
Member

amulet1 commented May 7, 2026

I added this deprecation message specifically for that reason - to alert about no longer needed ->type (and few other things).

We just have to be careful - we can not remove it from places which still may utilize mixture of old classes (e.g. classes that extend Horde_Form_Type) and new V3 classes. Ideally we have to first migrate any apps relying on Horde_Form_Type to V3-compatible classes.

@amulet1
Copy link
Copy Markdown
Member

amulet1 commented May 7, 2026

As long as ->type is dropped only for V3 types (which is the case here as far as I can see), we should be fine.

@amulet1
Copy link
Copy Markdown
Member

amulet1 commented May 7, 2026

Also see horde/Form/pull/24.

@TDannhauer TDannhauer merged commit c97c631 into FRAMEWORK_6_0 May 7, 2026
0 of 4 checks passed
@amulet1 amulet1 mentioned this pull request May 8, 2026
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.

2 participants