Project

General

Profile

Actions

Bug #93645

closed

Workspace pagination empty and Javascript error: Uncaught (in promise) TypeError: t is undefined

Added by David Menzel about 3 years ago. Updated almost 3 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Workspaces
Target version:
-
Start date:
2021-03-04
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
10
PHP Version:
7.4
Tags:
workspace, module, javascript
Complexity:
Is Regression:
Yes
Sprint Focus:

Description

We just noticed an error in Workspaces.

1.) Choose a workspace, for example "Entwurfsmodus"
2.) select an (edited) page and switch into the workspace module
3.) console error: Uncaught (in promise) TypeError: t is undefined

If you use the pagination and you switch to page 2, the page is empty too. So this could be related.

Please see the attached images.

Noticed in TYPO3 10.4.13.


Files


Related issues 4 (1 open3 closed)

Related to TYPO3 Core - Bug #92846: Workspace: changes not always listed in workspace modulClosed2020-11-16

Actions
Related to TYPO3 Core - Bug #93915: Workspace "Uncaught (in promise) TypeError: a is null" when in workspace manager moduleClosed2021-04-13

Actions
Related to TYPO3 Core - Bug #94031: No publishing possible since TYPO3 10.4.15Closed2021-04-30

Actions
Related to TYPO3 Core - Bug #98129: Workspace pagination is brokenNew2022-08-12

Actions
Actions #1

Updated by David Menzel about 3 years ago

  • Related to Bug #92846: Workspace: changes not always listed in workspace modul added
Actions #2

Updated by David Menzel about 3 years ago

I also updated the reference index and only 2 issues were found.

[WARNING] 74515 records from 78 tables were checked/updated.
Updates: 2

The error still shows up in the console.

Actions #3

Updated by David Menzel about 3 years ago

same error in typo3/sysext/workspaces/Resources/Public/JavaScript/Backend.js with the Google Chrome message:

Uncaught (in promise) TypeError: Cannot read property 'expanded' of undefined
at Backend.renderWorkspaceInfos (VM194 Backend.js:13)
at VM194 Backend.js:13
renderWorkspaceInfos VM194 Backend.js:13
(anonymous)
VM194 Backend.js:13

Actions #4

Updated by Anatoli Zich about 3 years ago

Dave Zen wrote in #note-2:

I also updated the reference index and only 2 issues were found.

[WARNING] 74515 records from 78 tables were checked/updated.
Updates: 2

The error still shows up in the console.

I had the exact same issue too but i could fix it by updating the refindex.

Edit: That fixed only a few records. Not all.

I'd mark this as a regression

Actions #5

Updated by Anatoli Zich about 3 years ago

  • Is Regression set to Yes
Actions #6

Updated by Anatoli Zich about 3 years ago

So this is what i found so far:

- The error is still present on 10.4.14
- Downgrading to 10.4.12 fixes the problem
- The workspace module will show some items and then abort with the above mentioned message
- Clearing the refindex (truncate the table) fixes the problem
- rebuilding the refindex with "bin/typo3 referenceindex:update" reintroduces the error

I'm still figuring out which commit of v10.4.13 introduces this.

Actions #7

Updated by Anatoli Zich about 3 years ago

This is indeed a regression which came with 10.4.13. Reverting the following commit clears the problem: https://github.com/TYPO3/TYPO3.CMS/commit/385b3b7ae8

I found out that this error comes situational. It appears when:
... the workspace module pagination kicks in.
... the last element in the workspace list has IRRE elements and it's elements exceed the 30 items per page threshold.

I could reproduce it like this:
1. Have a workspace and switch to it
2. create 25 text elements (i know, this is stupendous) following this pattern: "test" followed by an incrementing digit. Thats actually important as ordering is an important factor in this case
3. create a file list with 6 items as IRRE Elements
4. Go to the workspace module
5. The file list should be at the bottom of the list.
6. Go to page 2 and the error appears

I also had this error in a case that involved IRRE subitems which i don't know how to reproduce right now but it also had something to do with exceeding 30 items on the page. It got thrown right on loading the first page of the workspace module (without having to switch the pagination page) and there was a multitude of content elements containing IRRE elements with subitems.

Actions #8

Updated by Gerrit Code Review about 3 years ago

  • Status changed from New to Under Review

Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/68519

Actions #9

Updated by Gerrit Code Review about 3 years ago

Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/68519

Actions #10

Updated by Gerrit Code Review about 3 years ago

Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/68519

Actions #11

Updated by Gerrit Code Review about 3 years ago

Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/68519

Actions #12

Updated by Gerrit Code Review about 3 years ago

Patch set 1 for branch 10.4 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/68575

Actions #13

Updated by Oliver Bartsch about 3 years ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100
Actions #14

Updated by Alexander Rotzsch about 3 years ago

Hi,

I successfully installed the patch with latest 10.4.14 and the console error changed to

Uncaught (in promise) TypeError: Cannot read property 'Workspaces_CollectionChildren' of null
at Backend.renderWorkspaceInfos (Backend.js?bust=1617885154:13)
at Backend.js?bust=1617885154:13

... and that means I still cannot send workspace-changes to the next stage or set it live. :-(

Actions #15

Updated by David Menzel about 3 years ago

  • Related to Bug #93915: Workspace "Uncaught (in promise) TypeError: a is null" when in workspace manager module added
Actions #16

Updated by Oliver Bartsch almost 3 years ago

  • Related to Bug #94031: No publishing possible since TYPO3 10.4.15 added
Actions #17

Updated by Benni Mack almost 3 years ago

  • Status changed from Resolved to Closed
Actions #18

Updated by Francois Suter over 1 year ago

  • Related to Bug #98129: Workspace pagination is broken added
Actions

Also available in: Atom PDF