Bug #65792
No identifying value for object of class "" found.
| Status: | Resolved | Start date: | 2015-03-17 | |
|---|---|---|---|---|
| Priority: | Must have | Due date: | ||
| Assigned To: | Alex Kellner | % Done: | 100% |
|
| Category: | - | |||
| Target version: | - | |||
| TYPO3 Version: | 6.2 | Has patch: | Yes | |
| PHP Version: |
Description
After Upgrade from TYPO3 v6.2.10 to v6.2.11 with Powermail v2.2.0 I get an:
"No identifying value for object of class "" found."
in one powermail form (it's a selectable field with a list of years, see screenshot).
Reverting to TYPO3 v6.2.10 solves the problem temporarly.
Screen Shot 2015-03-17 at 5.45.41 PM.png (39.3 kB)
SelectFieldViewHelper.patch
(1.7 kB)
Related issues
History
#1 Updated by Alex Kellner 5 months ago
- Status changed from New to Needs Feedback
- Assigned To set to Sandro Barbieri
Hi,
did you clean the caches in Install Tool after upgrading?
Alex
#2 Updated by Joerg W 5 months ago
I have done the same upgrade and got exactly the same error message with plugin version 2.1.17.
In the log I get:
Core: Error handler (FE): PHP Warning: get_class() expects parameter 1 to be object, array given in /home_pr1/g/o/gospelchor-winterthur.ch/typo3/typo3_src-6.2.11/typo3/sysext/fluid/Classes/ViewHelpers/Form/SelectViewHelper.php line 174
#3 Updated by Christoph Lehmann 5 months ago
Same error here. I cleared all caches.
diff typo3_src-6.2.10/typo3/sysext/fluid/Classes/ViewHelpers/Form/SelectViewHelper.php typo3_src-6.2.11/typo3/sysext/fluid/Classes/ViewHelpers/Form/SelectViewHelper.php
158c158
< if (is_object($value)) {
---
> if (is_object($value) || is_array($value)) {
#4 Updated by Claus Fassing 5 months ago
I fix this for me by setting optionValueField to "value" in Select.html
<vh:Form.SelectField
options="{field.modifiedSettings}"
optionValueField="value"
property="{field.marker}"
class="powermail_field powermail_select {vh:Validation.ErrorClass(field:field, class:'powermail_field_error')}"
id="powermail_field_{field.marker}"
additionalAttributes="{vh:Validation.ValidationDataAttribute(field:field)}"
multiple="{field.multiselectForField}"
value="{vh:Misc.PrefillField(field:field, mail:mail)}"
/>
For me this looks more to be a bug of the SelectViewHelper as of Powermail.
I don't remember that the optionValueField attribute is a mandatory field.
#5 Updated by Claus Fassing 5 months ago
Thanks for the diff Christoph.
Looks like options can pass as array now but without a handle for the key assignment.
#6 Updated by Christoph Lehmann 5 months ago
works - thanks!
#7 Updated by André Wuttig 5 months ago
- File SelectFieldViewHelper.patch added
Here is my patch which changes the SelectFieldViewHelper to work under 6.2.11 I don´t know if it is the best solutation. Your way is also nice.
#8 Updated by Urs Braem 5 months ago
Same here. I was unable to apply the Patch by André, as I didn't even find the Select*Field*ViewHelper.
Changing
if (is_object($value) || is_array($value)) { back to if (is_object($value))worked
#10 Updated by Marcus Schwemer 5 months ago
This should be change in the Core, since 6.2.11 introduces a breaking change.
Even post-verifies on gerrit of ACME-members state that it breaks: https://review.typo3.org/#/c/36909/
#11 Updated by Michael Schwarzenberger 5 months ago
I have the same prolem with 6.2.11 and powermail.
Afert change back to
if (is_object($value))
it is work for me, but the conditions and form work very slow.
Micha
#12 Updated by Gerrit Code Review 5 months ago
- Status changed from Needs Feedback to Under Review
Patch set 1 for branch TYPO3_6-2 of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at http://review.typo3.org/37959
#13 Updated by Alex Kellner 5 months ago
- Assigned To changed from Sandro Barbieri to Alex Kellner
- % Done changed from 0 to 60
- Has patch changed from No to Yes
Thx for all that spent time into that issue.
I also reviewed it and came to the solution that this is related to core.
I hope that TYPO3 6.2.12 will include this patch: https://review.typo3.org/#/c/37959/2
Sorry for this discomfort.
I will let this ticket open for all people who are searching for a solution.
#14 Updated by Stefan Neufeind 4 months ago
Core has merged the patch meanwhile. Just had to try it myself with a pre-6.2.12, which solved the problem. So as soon as 6.2.12 ships, we're fine :-)
#15 Updated by Alex Kellner 4 months ago
- Status changed from Under Review to Resolved
- % Done changed from 60 to 100
TYPO3 6.2.12 is available now.
This fixes this issue.
Thx to all reporter