Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I just upgraded to rc3 and got this error:
Recoverable fatal error: Object of class stdClass could not be converted to string in translation_supported_type() (line 474 of .../modules/translation/translation.module).
Steps done to solve:
1. Deleted /views directory and installed new rc3 version => error stays
2. Deleted /views directory and installed new dev version => error stays
3. Deleted /views directory and restored 7.x-3.0-rc1 => error gone ... all ok again
Hope this helps
Comment | File | Size | Author |
---|---|---|---|
#3 | editable_fields_gone.jpg | 128.71 KB | FreeFox |
#1 | 1344946-fix-entity-handlers.patch | 5.29 KB | dawehner |
Comments
Comment #1
dawehnerCan you please explain when this appears?
For example describe what kind of view you created, provide an export etc. http://drupal.org/node/571990 has some valuable suggestions about this.
Views calls this function just once:
but there is looks fine, but OH i see the problem.
Here is a patch which does quite a lot of things
* Adds support to get a certain part of an entity via get_value();
* Adds support to get part of the value via get_value(). Therefore also take sure to add the fields to the query.
* Fix the rest of the node handlers.
Okay here is a patch.
Comment #2
FreeFox CreditAttribution: FreeFox commentedWOW, quick service ;)
I have patched the dev version with your patch and ... problems gone ^^
Thanks very much dereine
Comment #3
FreeFox CreditAttribution: FreeFox commentedAfter upgrade to the dev version of NOV 18 the problem is back so I restored the older version with the patch.
However, I noticed one more thing: the module editable fields is not working anymore. If I make a field in a view editable, instead of showing the editable field I see this:
1!--form-item-field_summary--0-->
(To be clear: this error is with the previous dev version with the patch.)
Attached a screenshot to visualize this. If needed I can give you access to the site.
Thanks in advance
Comment #4
kamenrs CreditAttribution: kamenrs commentedI have exactly the same problem with Views-7.x-3.0-rc3
Comment #5
dawehner@freefox
Please post only one problem per issue, i will totally ignore your comment, sorry.
In general this might be first a problem of editable fields, then by views itself, so please create an issue in the editable fields issue queue.
Comment #6
dco CreditAttribution: dco commentedFor me and Views-7.x-3.0-rc3, the patch solved the problem.
Any idea of when the production version of views will be patched ?
Tx
David
Comment #7
dawehnerMh what do you mean with "production version of views will be patched"?
Comment #8
johnw3600 CreditAttribution: johnw3600 commentedHi Dereine,
I think that means 'will this appear as Views-7.x-3.0-rc4?'
Regards,
John
Comment #9
dawehnerWell it means: Please test the patch and once it's tested it will be part of the next release, but if noone tested it, it might have to wait a bit more.
Comment #10
FreeFox CreditAttribution: FreeFox commentedTested on 3 sites and working fine.
Comment #11
dazz CreditAttribution: dazz commentedTested it on latest 7.x-3.x-dev and seems to work fine
Comment #12
dawehnerSo some people tested this patch. Thanks for doing it!
Committed to 7.x-3.x
Comment #14
igalarza CreditAttribution: igalarza commentedI've experimented this bug with the 7.x-3.0 release. This version is not patched? It works fine with devel version. Regards