Project

General

Profile

Actions

Bug #49424

closed

Saving content element in workspace change flexform data from typoscript_content plugin

Added by Karsten Nowak (undkonsorten) almost 11 years ago. Updated 8 months ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Workspaces
Target version:
-
Start date:
2013-06-25
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.1
PHP Version:
Tags:
Complexity:
hard
Is Regression:
No
Sprint Focus:

Description

I have an content element (typoscript_content) with flexform data in tt_content field "pi_flexform".
It save uid's from other content elements in this field. The data in pi_flexform was changed when i save it in workspace.
The right saved list (in LIVE mode) is here:

...
<value index="vDEF">57,47</value>
...

An simple list with uid. Here is the same list but saved in workspace mode:

...
<value index="vDEF">
   <numIndex index="0">57</numIndex>
   <numIndex index="1">47</numIndex>
</value>
...

TYPO3 6.1.1
workspaces 6.1.0

Actions #1

Updated by Michael Stucki over 10 years ago

  • Category changed from Bugs to Workspaces
Actions #2

Updated by Michael Stucki over 10 years ago

  • Project changed from 624 to TYPO3 Core
  • Category changed from Workspaces to Workspaces
Actions #3

Updated by Mathias Schreiber about 9 years ago

  • Target version set to 7.5
Actions #4

Updated by Oliver Hader over 8 years ago

  • Target version changed from 7.5 to 7 LTS
  • Complexity set to hard
  • Is Regression set to No

Needs to be checked, whether it's still the case in TYPO3 CMS 7

Actions #5

Updated by Mathias Schreiber over 8 years ago

  • Target version deleted (7 LTS)
Actions #6

Updated by Riccardo De Contardi 9 months ago

I tried to reproduce the issue on TYPO3 version 12 with the following test

Prerequisites

- TYPO3 12.4.2
- a "Draft" Workspace
- a Content Element with a flexform configuration (I used a custom CE created with b13/container)

Test procedure

1. I added to the flexform config of the CE the following lines:

                    <link>
                        <label>TEST LINK</label>
                        <config>
                            <type>group</type>
                            <internal_type>db</internal_type>
                            <allowed>pages</allowed>
                            <size>10</size>
                            <minitems>0</minitems>
                            <maxitems>10</maxitems>
                            <show_thumbs>1</show_thumbs>
                        </config>

                    </link>

2. on LIVE workspace, I created the CE with the flexform config and added to this "link field" a couple of pages, save
3. I checked on the DB the content of the pi_flexform field on the tt_content table for the CE:

<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<T3FlexForms>
    <data>
        <sheet index="general">
            <language index="lDEF">
                <field index="link">
                    <value index="vDEF">2,3</value>
                </field>
            </language>
        </sheet>
    </data>
</T3FlexForms>

4. I switched to "Draft" workspace
5. Edited the same CE and added another page, saved it
6. I checked the DB and a new content element has been added, linked to the original one (that's the version of the same CE inside the Draft workspace)
7. I checked the content of its pi_flexform field:

<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<T3FlexForms>
    <data>
        <sheet index="general">
            <language index="lDEF">
                <field index="link">
                    <value index="vDEF">2,3,4</value>
                </field>
            </language>
        </sheet>
    </data>
</T3FlexForms>

This both applies to the pages created inside the workspace or in the LIVE workspace.

Is the issue solved? Or is a different test necessary?

Actions #7

Updated by Karsten Nowak (undkonsorten) 9 months ago

After ten years I would say, looks good to me ;-). For me no further tests needed. Ticket can be closed.

Actions #8

Updated by Riccardo De Contardi 8 months ago

  • Status changed from New to Closed

Karsten Nowak Thank you for your reply, sorry for the long wait!
I close this issue for now as solved

If you think that this is the wrong decision or experience the issue again on recent TYPO3 versions (12 or 13) please open a fresh issue and reference this one.

Thank you

Actions

Also available in: Atom PDF