Project

General

Profile

Actions

Bug #63938

closed

Error message in RTE, if I want to insert a Custom Item

Added by Harald no-lastname-given almost 10 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
RTE (rtehtmlarea + ckeditor)
Target version:
-
Start date:
2014-12-16
Due date:
% Done:

100%

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

Description

Hello Developers!

After I changed TYPO3 6.2.9 to 7.0.2, I get an error message in RTE, if I want to insert a Custom Item. A screenshot I still attached.
In TYPO3 6.2.9, it works perfectly!

Unfortunately, I do not know to which person and in which category I shall allocate this error - I am sorry

The error message:


Uncaught TYPO3 Exception
#1294585070: No module "rtehtmlarea_wizard_user" could be found. (More information)

UnexpectedValueException thrown in file
C:\typo3\htdocs\typo3-7-servus\typo3\mod.php in line 46.


Thx

Harald


Files

NoModule.png (11.6 KB) NoModule.png Harald no-lastname-given, 2014-12-16 18:00
first.png (6.63 KB) first.png Harald no-lastname-given, 2014-12-18 10:00
second.png (12.5 KB) second.png Harald no-lastname-given, 2014-12-18 10:00
configuration-module.png (48.3 KB) configuration-module.png Harald no-lastname-given, 2014-12-18 10:00
Actions #1

Updated by Stanislas Rolland almost 10 years ago

  • Category set to RTE (rtehtmlarea + ckeditor)
Actions #2

Updated by Stanislas Rolland almost 10 years ago

Something wrong in this installation. Please clear all caches using the Install tool.

Actions #3

Updated by Harald no-lastname-given almost 10 years ago

Thank you, but that was the first thing I did. It did not help.
I can not understand why it works without problems in TYPO3 6.2.9 unfortunately. In the new features of TYPO3 7, I could see no evidence. It's all about the user item. All other functions are working properly?

This is a shame

Actions #4

Updated by Stanislas Rolland almost 10 years ago

The module was moved from rtehtmlarea/mod5 to rtehtmlarea/Modules and was renamed from rtehtmlarea_wizard_user to rtehtmlarea_wizard_user_elements. So it is not normal that a script would be requesting module rtehtmlarea_wizard_user.

Please check the value of $GLOBALS['TBE_MODULES']['_PATHS']['rtehtmlarea_wizard_user_elements'] in the Configuration module.

If it is not there, please try to un-install and re-install rtehtmlarea.

Updated by Harald no-lastname-given almost 10 years ago

Now I have played all scenarios:

rte de-installed and re-installed, RTE set to typical etc.

New TYPO3 7.0.2 installation - without further extensions (also with the TYPO3 7 developing version tested).

The only optional RTE configuration according to this example.
http://docs.typo3.org/typo3cms/extensions/rtehtmlarea/Configuration/PageTsconfig/userCategory/Index.html

The value in the configuration checks (Sreenshot). This is also fine
$ GLOBALS ['TBE_MODULES'] ['_ PATHS'] ['rtehtmlarea_wizard_user_elements']

When I call the user element is all the same:

You can call the element. The description is displayed. But as soon as one clicks on it, the error message comes.

Now I do not know anymore

Actions #6

Updated by Gerrit Code Review almost 10 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 http://review.typo3.org/35568

Actions #7

Updated by Stanislas Rolland almost 10 years ago

Please test this change: http://review.typo3.org/35568

Actions #8

Updated by Harald no-lastname-given almost 10 years ago

SUPER - Everything works fine again!

Exactly what I thought. I never found it ....

Thx

Harald

Actions #9

Updated by Gerrit Code Review almost 10 years ago

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

Actions #10

Updated by Stanislas Rolland almost 10 years ago

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

Updated by Benni Mack about 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF