Project

General

Profile

Actions

Bug #83005

closed

Problems with Workspace and News

Added by Erich Manser over 6 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Could have
Assignee:
-
Category:
Workspaces
Target version:
-
Start date:
2017-11-15
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
8
PHP Version:
7.0
Tags:
Complexity:
medium
Is Regression:
Sprint Focus:

Description

When I create a page with a normal content element text & images and save the page in a live workspace and then change into a preparation workspace and edit and save the same element everything is fine.
When I create a news element in live workspace and then switch to preparation workspace try to do some changes and save the record I get the error messages:

2: SQL error: 'Incorrect integer value: '' for column 'relatedpublications' at row 1' (tx_news_domain_model_news:NEW5a0c49ebcadee280211182)
1: [newlog()] Could not be edited in offline workspace in the branch where found (failure state: 'Online record was not in versionized branch!'). Auto-creation of version failed!

In this case there is no record created for the news.
If I create a new news element in the preparation workspace without an existing element in live workspace, everything is fine. Both records live and preparation are created and have the correct data.
So when creating the record first in live workspace and then creating a workspace copy of this record the error message turns up. The field relatedpublications is configured like:

    'relatedpublications' => [
        'exclude' => 1,
        'l10n_mode' => '',
        'l10n_display' => 'hideDiff',
        'label' => 'LLL:EXT:mediawall/Resources/Private/Language/locallang_db.xlf:news.relatedpublications',
        'config' => [
            'type' => 'inline',
            'foreign_table' => 'tx_news_domain_model_news',
            'MM_match_fields' => [
                'fieldname' => 'relatedpublications',
            ],
            'foreign_record_defaults' => [
                'hidden' => '0',
                'is_downloadable_news' => '1',
            ],
            'maxitems' => 100,
            'MM' => 'tx_news_domain_model_news_relatedmediawallitem_mm',
            'appearance' => [
                'showSynchronizationLink' => 1,
                'showAllLocalizationLink' => 1,
                'showPossibleLocalizationRecords' => 1,
                'showRemovedLocalizationRecords' => 1,
                'expandSingle' => 1,
                'collapseAll' => 1,
                'newRecordLinkTitle' => 'LLL:EXT:mediawall/Resources/Private/Language/locallang_db.xlf:news.create_new_relatedpublications',
                'enabledControls' => [
                    'info' => true,
                    'new' => true,
                    'dragdrop' => true,
                    'sort' => true,
                    'hide' => true,
                    'delete' => true,
                    'localize' => true,
                ],
            ],
            'behaviour' => [
                'localizationMode' => 'select',
                'localizeChildrenAtParentLocalization' => true,
            ],
            'mediawallitem' => true,
        ],
    ],

This seems correct to me.

In /CMS/Core/DataHanling/DataHandler.php function copyRecord_raw() in line 3762 the field value of relatedpublications is set to an empty string (“”) which in further case produces the errors above.

But when I debug the same with a default content element as text & media the same line has an empty string for the field media which is equal in type as relatedpublication and does not produce an error.


Related issues 1 (1 open0 closed)

Related to TYPO3 Core - Bug #78921: Copying records fails with SQL error without any messageNew2016-12-08

Actions
Actions #1

Updated by Oliver Hader over 6 years ago

  • Category changed from Backend User Interface to Workspaces
  • Status changed from New to Needs Feedback

What's are the exact version numbers of TYPO3 CMS and ext:news you're using? Thanks in advance for your feedback!

Actions #2

Updated by Riccardo De Contardi about 6 years ago

  • Related to Bug #78921: Copying records fails with SQL error without any message added
Actions #3

Updated by Riccardo De Contardi about 6 years ago

  • Status changed from Needs Feedback to Closed

No feedback since the last 90 days => closing this issue.

If you think that this is the wrong decision and have more information about how to reproduce your problem, please reopen it or open a new issue with a reference to this one. Thank you.

Actions

Also available in: Atom PDF