I have the odd result, that after installing and activating this module on a view, all fields in the view disappear.
No idea what causes this.

Comments

joachim’s picture

joachim CreditAttribution: joachim commented
Status: Active » Postponed (maintainer needs more info)

Is it a view using the editable tables plugin? Did you add editable fields to it?

Yuri’s picture

Yuri CreditAttribution: Yuri commented

Ok I found out what happens...
The editable table only appears when *all* fields in the view are of the type "editable". It does not work, when a normal field is included.
Also, when a field is set in the views field configuration as having the formatter 'editable', this will also break the view, no matter if the field is an 'editable' type or not.
The result with a broken view, is that only the word 'array' is visible, the rest disappears.

joachim’s picture

joachim CreditAttribution: joachim commented

> The editable table only appears when *all* fields in the view are of the type "editable". It does not work, when a normal field is included.

That is definitely not the case -- I have views with normal fields in them.

> Also, when a field is set in the views field configuration as having the formatter 'editable', this will also break the view, no matter if the field is an 'editable' type or not.

What formatter editable?

ibuildit’s picture

ibuildit CreditAttribution: ibuildit commented

He means

drupal.org/project/editablefields

I can verify that he is correct

joachim’s picture

joachim CreditAttribution: joachim commented

This module is not compatible with that one.

vbard’s picture

vbard CreditAttribution: vbard commented

seems like VBO is not compatible with that module too. The same happens - "Array" is written and nothing more.

MrDaleSmith’s picture

MrDaleSmith CreditAttribution: MrDaleSmith commented
Issue summary: View changes

I'm setting up this module with a view that uses bulk operations: when the bulk operations are enabled, the view fails to render due to $elements['#children'] being set as an array rather than a string in drupal_render(). If I remove the VBO, the view renders correctly.

Could this be the same issue?

ETA: ah, missed that last comment. Not compatible with VBO then.

Yuri’s picture

Yuri CreditAttribution: Yuri commented

I think that it is of importance that the module editablefields drupal.org/project/editablefields and this module are compatible, because the sites that I make I often have to use them both, they complement each other in different ways. In websites where content is edited it often is needed to modify a single fields as well as multiple.

Any idea in what way they are not compatible, and which module is likely to make the changes?