Project

General

Profile

Actions

Bug #8840

closed

Minor issue without visible effects: CB parameter sub-(pseudo)-fields have null type

Added by beat almost 3 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
21 January 2022
Due date:
% Done:

100%

Estimated time:

Description

This became visible in PHP 8.1 warnings. But it's much better to fix root cause than to retype null to string in all $field->type usages while $field->type was expected to be set (as string).

Treating this separately from PHP 8.1 adaptations.


Related issues 1 (0 open1 closed)

Related to CB - Feature proposal #8833: PHP 8.1 compatibilityClosedbeat18 January 2022

Actions
Actions #1

Updated by beat almost 3 years ago

Actions #2

Updated by beat almost 3 years ago

  • Status changed from Assigned to Resolved
  • % Done changed from 0 to 100

Fixed in MR !1761.

Actions #3

Updated by beat almost 3 years ago

Did an alternate fix in commit 206898a86e99889043df4164130d5d00a80bd033 of branch php81 for #8833 :

pseudoField->type = '';

That at least doesn't change fields ids, to preserve maximum B/C.

Actions #4

Updated by beat almost 3 years ago

  • Subject changed from Minor issue without visible effects: CB parameter sub-(pseudo)-fields are missing type=param to Minor issue without visible effects: CB parameter sub-(pseudo)-fields have null type
Actions #5

Updated by beat almost 3 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF