Skip to content

Stop passing deprecated $message to V3 variables in Horde_Form::validate()#34

Open
TDannhauer wants to merge 1 commit into
FRAMEWORK_6_0from
fix/stabelize_FormV3_vs_Turba
Open

Stop passing deprecated $message to V3 variables in Horde_Form::validate()#34
TDannhauer wants to merge 1 commit into
FRAMEWORK_6_0from
fix/stabelize_FormV3_vs_Turba

Conversation

@TDannhauer
Copy link
Copy Markdown
Contributor

Summary

  • Fixes log spam when legacy Horde_Form validates forms that use V3 variables created by Horde_Form::createVariable().
  • Horde_Form::validate() no longer passes the deprecated second $message argument to V3 BaseVariable instances; it is still passed for legacy Horde_Form_Variable wrappers (e.g. app-specific types without a V3 class).
  • Aligns legacy form validation with Horde\Form\V3\BaseForm::validate(), which already calls $var->validate($vars) with a single argument.

Problem

Horde_Form::createVariable() now returns V3 variables (e.g. Horde\Form\V3\TextVariable) when a modern class exists. Legacy Horde_Form::validate() still called:

@TDannhauer TDannhauer requested a review from ralflang May 18, 2026 21:14
@TDannhauer
Copy link
Copy Markdown
Contributor Author

pls review whether this approach is viable @ralflang .

turba floods the logs with this issue

@amulet1
Copy link
Copy Markdown
Member

amulet1 commented May 19, 2026

We should really finish migration to V3 in other apps first.

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