AssertionError:Tracking page size is not set

Created on 6 June 2023, over 1 year ago
Updated 18 June 2023, over 1 year ago

Problem/Motivation

Config import fails with search configurations when there is null value for Tracking page.

Steps to reproduce

Create a search component in cms and try to import the config on vanilla Drupal. AssertionError:Tracking page size is not set error stops you to import the configs due to null value for Tracking page.

Proposed resolution

I have added a patch for this. Needs review.

๐Ÿ› Bug report
Status

Postponed: needs info

Version

1.29

Component

General code

Created by

๐Ÿ‡ฎ๐Ÿ‡ณIndia Deepika Dhiman

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @Deepika Dhiman
  • Status changed to Postponed: needs info over 1 year ago
  • ๐Ÿ‡ฆ๐Ÿ‡นAustria drunken monkey Vienna, Austria

    Thanks for reporting this problem!
    However, why donโ€™t you just fix the config before importing to have a tracking page size? The error is there for a good reason, tracking will not work correctly without it. Disabling the error message and failing silently doesnโ€™t seem like a good idea, when just fixing the problem is so easy.

    PS: It seems you (like many others โ€“ it's really easy to misinterpret) are confused by the "Issue tags" field. As the guidelines โ†’ state, they aren't meant for free text tags related to the issue, but only for specific categorization purposes, usually by module maintainers.
    So, if you aren't sure your current usage is correct, please just leave the field empty.

Production build 0.71.5 2024