Wanted to test this. Hadn't used this module before. I installed the alpha release, been clicking around for 10 minutes but haven't found a way to make a field editable yet. What gives?

Comments

cees.vanegmond’s picture

+1

tomlurge’s picture

me too, embarrassingly

spacereactor’s picture

First need to know where you want to field to display editable field.

For views, create view as normal and after click on the field that can be editable, under "Formatter" select "editable". Enable/disable "Click to edit" depend on your need.

For content display, goto the content type choose manage display, Look for the field that you want to display as editable field, select "FORMAT" and change to "editable". Edit the field with the icon button that look like a gear. Enable/disable "Click to edit" depend on your need.

!!Important, not all field is editable. example you nid is fix and can't edit. Either edit theme css or use css injector to edit the css for the editable display.

Hope this help, i also first time using editablefields. if i miss out anything others please input.

damiankloip’s picture

The editablefields project page explains how to get editable fields working. I got it working in a few seconds. Essentially it adds a new display formatter for fields...

LarsKramer’s picture

Category: bug » support
Status: Active » Fixed
yoroy’s picture

Category: support » bug
Status: Fixed » Active
Issue tags: +Usability
StatusFileSize
new128.89 KB

Not being able to find functionality is a definite UX bug, not a feature request. And this should be made more obvious in the UI itself. Documentation on another web site doesn't count as a fix imo.

Given the current situation it might be worthwhile to provide a more specific message after enabling the module:

LarsKramer’s picture

Assigned: Unassigned » LarsKramer

The idea of showing a short instructive message after enabling the module is good.
However, as explained in #3, if you only want to make a field editable in a view, the configuration is done in Views UI, not in the content type display tab. So just showing the message you propose might confuse people who only need it to work in Views. And providing help only in form of a long temporary mesage is not a good solution.

Therefore I think a better solution would be to include the instructions from the project page in the README file, and on a "Help" page (which in Drupal 7 can be reached directly from the module list).

I don't have much experience submitting patches, but I will give it a try, if you agree this is the way to do it.

LarsKramer’s picture

LarsKramer’s picture

I have made a proposal for some configuration instructions here: #1203004: Update Readme with some basic instructions for use
Before doing any work with help pages, let me know what you think. I think we could use more or less the same text on the help page.

kika’s picture

Look for the field that you want to display as editable field, select "FORMAT" and change to "editable"

Do you mean Drupal 7 / Views 3? Failing to see that "editable" setting. Using latest 7.x-1.x git branch

LarsKramer’s picture

StatusFileSize
new75.09 KB

You need the dev version of Views for Drupal 7 as mentioned in #1206656: Error on Node view page: Argument 1 passed to drupal_array_get_nested_value().

See the attached image for location of field Formatter select box in Views UI.

LarsKramer’s picture

Status: Active » Postponed

Setting this to postponed until #1203004: Update Readme with some basic instructions for use has been reviewed.

lokinder.chauhan’s picture

hello LarsKramer
thank for post.this save my time.

johnv’s picture

Status: Postponed » Active

Hi Lars,

I guess with the new README.txt, which is committed last february, this can be closed?

Taxoman’s picture

Status: Active » Fixed

Yes, looks like sufficient instructions are in the latest README.txt file now.

Automatically closed -- issue fixed for 2 weeks with no activity.