Bug #31572

TypoScript FORM-Object produces Exception

Added by Andreas Bouche almost 8 years ago. Updated about 1 year ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Form Framework
Target version:
-
Start date:
2011-11-04
Due date:
% Done:

100%

TYPO3 Version:
4.6
PHP Version:
Tags:
Complexity:
easy
Is Regression:
Sprint Focus:

Description

After the fix of issue #31120 tx_form_Controller_Form throws an Exception when rendered via TypoScript:

Catchable Fatal Error: Argument 2 passed to tx_form_Controller_Form::cObjGetSingleExt() must be an array, null given, called in [..]typo3/sysext/cms/tslib/class.tslib_content.php on line 594 and defined in [...]typo3/sysext/form/Classes/Controller/Form.php line 102

When invoked via TS, the Variable $mergedTypoScript is NULL and thus the internal Rendering of COBJ_ARRAY fails (Form.php, line 129)

My solution for this was to simply use $typoScript instead of $mergedTyposcript when $mergedTyposcript is NULL. A Patchset with my fix will be submitted shortly.


Related issues

Related to TYPO3 Core - Bug #50274: Problem with Form extension and standard search Closed 2013-07-22
Follows TYPO3 Core - Bug #31120: Add default csc-mailform DIV wrap Closed 2011-10-19

Associated revisions

Revision dd84d0b3 (diff)
Added by Andreas Bouche about 6 years ago

[BUGFIX] Exception using cObject FORM in TypoScript

Through a bug introduced by #31120, an Exception is thrown when a
TypoScript FORM object should be rendered.

Change-Id: Ie67484fd014620ea229a7bee8bfebd063a3b57ae
Fixes: #31572
Releases: 6.2, 6.1, 6.0, 4.7
Reviewed-on: https://review.typo3.org/6537
Reviewed-by: Ernesto Baschny
Tested-by: Ernesto Baschny
Reviewed-by: Stefan Neufeind
Tested-by: Stefan Neufeind

Revision ceba809c (diff)
Added by Andreas Bouche almost 6 years ago

[BUGFIX] Exception using cObject FORM in TypoScript

Through a bug introduced by #31120, an Exception is thrown when a
TypoScript FORM object should be rendered.

Fixes: #31572
Releases: 6.2, 6.1, 6.0, 4.7
Change-Id: Ie67484fd014620ea229a7bee8bfebd063a3b57ae
Reviewed-on: https://review.typo3.org/23719
Reviewed-by: Stefan Neufeind
Reviewed-by: Sebastian Michaelsen
Reviewed-by: Ernesto Baschny
Tested-by: Ernesto Baschny

Revision 648018ef (diff)
Added by Andreas Bouche almost 6 years ago

[BUGFIX] Exception using cObject FORM in TypoScript

Through a bug introduced by #31120, an Exception is thrown when a
TypoScript FORM object should be rendered.

Fixes: #31572
Releases: 6.2, 6.1, 6.0, 4.7
Change-Id: Ie67484fd014620ea229a7bee8bfebd063a3b57ae
Reviewed-on: https://review.typo3.org/23718
Reviewed-by: Stefan Neufeind
Reviewed-by: Sebastian Michaelsen
Reviewed-by: Ernesto Baschny
Tested-by: Ernesto Baschny

Revision d34bde3d (diff)
Added by Andreas Bouche almost 6 years ago

[BUGFIX] Exception using cObject FORM in TypoScript

Through a bug introduced by #31120, an Exception is thrown when a
TypoScript FORM object should be rendered.

Fixes: #31572
Releases: 6.2, 6.1, 6.0, 4.7
Change-Id: Ie67484fd014620ea229a7bee8bfebd063a3b57ae
Reviewed-on: https://review.typo3.org/23717
Reviewed-by: Stefan Neufeind
Reviewed-by: Sebastian Michaelsen
Reviewed-by: Ernesto Baschny
Tested-by: Ernesto Baschny

History

#1 Updated by Oliver Hader almost 8 years ago

  • Assignee deleted (Oliver Hader)

Please don't assign issues to people directly

#2 Updated by Oliver Hader almost 8 years ago

Can you provide your TypoScript setup (that one of the bodytext in the accordant form content element). Thus, it's easier to reproduce.

#3 Updated by Mr. Hudson almost 8 years ago

  • Status changed from New to Under Review

Patch set 1 of change Ie67484fd014620ea229a7bee8bfebd063a3b57ae has been pushed to the review server.
It is available at http://review.typo3.org/6537

#4 Updated by Andreas Bouche almost 8 years ago

I used the following TypoScript in the Form-Element and created a FORM-Object directly in TypoScript with the same setup:

enctype = multipart/form-data
method = post
prefix = tx_form
confirmation = 1
postProcessor {
    1 = mail
    1 {
        recipientEmail = 
        senderEmail = 
    }
}
10 = TEXTLINE
10 {
    name = Test
    label {
        value = Testlabel
    }
}

#5 Updated by Frederic Gaus almost 8 years ago

This error is easy to reproduce. Just add the following typoscript to a TYPO3 4.6.0 instance.

page.100 = FORM
page.100 {
    enctype = multipart/form-data
    method = post
    prefix = tx_form
    confirmation = 1
    postProcessor {
        1 = mail
        1 {
            recipientEmail = 
            senderEmail = 
        }
    }
    10 = TEXTLINE
    10 {
        name = Test
        label {
            value = Testlabel
        }
    }
}

#6 Updated by Mr. Hudson almost 8 years ago

Patch set 2 of change Ie67484fd014620ea229a7bee8bfebd063a3b57ae has been pushed to the review server.
It is available at http://review.typo3.org/6537

#7 Updated by Steffen Gebert almost 8 years ago

  • Target version set to 4.6.1

#8 Updated by Xavier Perseguers almost 8 years ago

  • Target version changed from 4.6.1 to 4.6.2

#9 Updated by Gerrit Code Review almost 8 years ago

Patch set 3 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/6537

#10 Updated by Xavier Perseguers over 7 years ago

  • Target version deleted (4.6.2)

#11 Updated by Joris Willems about 6 years ago

I am getting this error on typo3 6.1.4 when viewing a page with a searchform. When uninstalling the sysext form the page and searchform is fine.

#12 Updated by Gerrit Code Review about 6 years ago

Patch set 4 for branch master has been pushed to the review server.
It is available at https://review.typo3.org/6537

#13 Updated by Gerrit Code Review about 6 years ago

Patch set 1 for branch TYPO3_6-1 has been pushed to the review server.
It is available at https://review.typo3.org/23717

#14 Updated by Gerrit Code Review about 6 years ago

Patch set 1 for branch TYPO3_6-0 has been pushed to the review server.
It is available at https://review.typo3.org/23718

#15 Updated by Gerrit Code Review about 6 years ago

Patch set 1 for branch TYPO3_4-7 has been pushed to the review server.
It is available at https://review.typo3.org/23719

#16 Updated by Andreas Bouche about 6 years ago

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

#17 Updated by Benni Mack about 1 year ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF