Project

General

Profile

Actions

Bug #82969

closed

Javascript Error in Backend

Added by Markus Günther over 6 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Backend JavaScript
Target version:
-
Start date:
2017-11-10
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
7
PHP Version:
Tags:
Complexity:
Is Regression:
Sprint Focus:

Description

When you create an non admin backend user and don`t add access to modules. You get JS errors in the backend.

I know that it is not useful to have a user without that permissions. But the backend allow users to do this and then
it should not happen that you get such errors in your console.

At the moment it seems that all versions are effected.


Files


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #84335: LiveSearch: Cannot read property 'options' on undefinedClosed2018-03-16

Actions
Actions #1

Updated by Frank Nägler over 6 years ago

  • Category set to Backend JavaScript
  • Status changed from New to Needs Feedback

Hey Markus,
can you please add more info like the conrete error message or a console output?

Actions #2

Updated by Markus Günther over 6 years ago

Hi Frank,

it is a bit different on each TYPO3 version.

Steps to reproduce the failure:

  1. Create a new backend user
  2. Enter only a username and password because these are the only mandatory fields
  3. save and close
  4. Switch to the backend user and then you have the errors on all backends

In the current master you get an exception for the module, which is right. But also the JS error that the autocomplete has no options.
I would expect to have just the exception ;)

In TYPO3 version 7.6 you get JS errors because the backend is guessing that you have module available, but that is not the case and because
the fields are not mandatory this can happen to regular backend users.

I understand the problem is that you can get the access rights from a group or a single user.
But excerpt solving the JS issues it would be nice to prevent that you are able to create a user that has no module permissions.

Actions #3

Updated by Markus Günther over 6 years ago

Attached screenshot of TYPO3 version 7 LTS

Actions #4

Updated by Markus Günther over 6 years ago

Attached screenshot version 8.

For my local version 7.x instance I already adjusted the JS so that you don't get the errors anymore.
But my last patch is far in the past and I first need to go thru the contribution tutorial.

For patching it.

And I bet it did not change, that I first need to tackle master, then backport to version 8 and then 7. Although version 7 is not really a backport.

Actions #5

Updated by Markus Günther over 6 years ago

It turns out that after solving an autocomplete issue a new issue lead to another JS error.

In the issue https://forge.typo3.org/issues/83041 I describe that the Admin tools are visible to editors without permissions. And then we have module data in the menu but should not have
any module data. And then the request to the module fails with a code 500.

So this issue ends in another JS error for TYPO3 version 9.

Actions #6

Updated by Gerrit Code Review over 6 years ago

  • Status changed from Needs Feedback to Under Review

Patch set 1 for branch TYPO3_8-7 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/54692

Actions #7

Updated by Gerrit Code Review over 6 years ago

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/54694

Actions #8

Updated by Gerrit Code Review over 6 years ago

Patch set 2 for branch TYPO3_8-7 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/54692

Actions #9

Updated by Gerrit Code Review over 6 years ago

Patch set 1 for branch TYPO3_7-6 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/54696

Actions #10

Updated by Gerrit Code Review over 6 years ago

Patch set 3 for branch TYPO3_8-7 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/54692

Actions #11

Updated by Gerrit Code Review over 6 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/54694

Actions #12

Updated by Gerrit Code Review over 6 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/54694

Actions #13

Updated by Gerrit Code Review over 6 years ago

Patch set 1 for branch TYPO3_8-7 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/54710

Actions #14

Updated by Markus Günther over 6 years ago

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

Updated by Gerrit Code Review over 6 years ago

  • Status changed from Resolved to Under Review

Patch set 1 for branch TYPO3_7-6 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/54714

Actions #16

Updated by Gerrit Code Review over 6 years ago

Patch set 2 for branch TYPO3_7-6 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/54714

Actions #17

Updated by Gerrit Code Review over 6 years ago

Patch set 3 for branch TYPO3_7-6 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/54714

Actions #18

Updated by Gerrit Code Review about 6 years ago

Patch set 4 for branch TYPO3_7-6 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/54714

Actions #19

Updated by Markus Günther about 6 years ago

  • Status changed from Under Review to Resolved
Actions #20

Updated by Andreas Kienast about 6 years ago

  • Related to Bug #84335: LiveSearch: Cannot read property 'options' on undefined added
Actions #21

Updated by Benni Mack over 5 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF