Project

General

Profile

Actions

Bug #41398

closed

Suggest wizards don't work if plugin is added through wizard icon

Added by Oliver Salzburg about 12 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2012-09-26
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.7
PHP Version:
5.3
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

When adding a new plugin to a page by using one of these icons:

In the resulting dialog, suggest wizards will not work.

However, once the content element is saved, the suggest wizard will work:

I noticed this in one of my own extensions, but am using EXT:news here for illustration.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #50549: The suggest search does not work in new unsaved content elements.Closed2013-07-30

Actions
Actions #1

Updated by Stefan Galinski about 12 years ago

  • Status changed from New to Needs Feedback

Hmm.. Just tested that with the current master and the content element "special menus" as well the powermail2 plugin. In both cases the suggest wizard worked instantly.

Actions #2

Updated by Oliver Salzburg about 12 years ago

I tried powermail2 on the same site where I initially experienced the issue and the outcome is exactly as described above.

However, I also tried to reproduce this on another installation. It works instantly over there.

So far, I am clueless about where to start digging for the cause. We'll see.

Actions #3

Updated by Oliver Salzburg about 12 years ago

One major difference I could see between the working and non-working sites is the uid and pid parameters send to the suggest receiver.

Not Working:
        {
          "name": "uid",
          "value": "NEW5064247dc6ec8" 
        },
        {
          "name": "pid",
          "value": "-1790" 
        },

Working:
        {
          "name": "uid",
          "value": "1946" 
        },
        {
          "name": "pid",
          "value": "642" 
        },

I went through different scenarios with this, but on the non-working site the pid will always be negative (until I save) and the uid will be a NEW.... placeholder.
However, on the working site, the uid and pid will have valid values right from the get-go.

Actions #4

Updated by Oliver Salzburg about 12 years ago

Seems like it actually doesn't work on either site.

I was just a little confused because the working site uses TemplaVoila. The TV page module (or our configuration of it) seems to instantly save CEs upon creation, while the default page module doesn't. When using the default page module on the working site, the behavior is faulty and as described in the original report.

Actions #5

Updated by Stefan Galinski about 12 years ago

  • Status changed from Needs Feedback to Accepted

Now I could reproduce the issue. It just affects plugins and their flexform fields!

Actions #6

Updated by Oliver Salzburg about 12 years ago

Stefan Galinski wrote:

Hmm.. Just tested that with the current master and the content element "special menus" as well the powermail2 plugin. In both cases the suggest wizard worked instantly.

Ok, I've just made a new, fresh installation of 4.7.4 from the blank package, and I get the same problem.

Before saving:

After saving:

So, is this fixed in master?

Actions #7

Updated by Stefan Galinski about 12 years ago

So, is this fixed in master?

Please look at my comment above yours. It's not fixed in master and it seems to be a flexform issue with the suggest wizard.

Actions #8

Updated by Henrik Ziegenhain about 12 years ago

I can confirm it for 4.6.15 & 4.7.7

When I insert the Plugin via "Insert general Plugin" and then select the plugin. The CE gets saved and the suggest wizard for Flexforms is working.
When inserting the plugin directly as mentioned above I first need to save the CE manually to get the suggest wizard working.

Actions #9

Updated by Alexander Stehlik about 10 years ago

This one should be fixed with #50549.

Actions #10

Updated by Georg Ringer almost 10 years ago

  • Status changed from Accepted to Resolved
  • Is Regression set to No

resolved with the mentioned issue

Actions #11

Updated by Benni Mack about 6 years ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF