option to hide current value (only show edit box) or make them editable on click

Yes, I think that showing the 'current value' should be an option, not the default way to show it. The current value is visible in the edit field anyway.

I agree. For now, I'm using -

.views-row-edit-static {
display:none;
}

in my theme, but I don't really wanna do that. Please give an option. Thanks.

+1

btopro please use the follow button located in the top-right corner of every thread to subscribe to issues rather than commenting please.

Attached is a patch that tries to sort this.

I am unsure if the approach I am taking will work for every single field, but so far my few tests went fine. Probably @joachim can shed some light on that.

Looks ok, though I prefer to avoid settings or variables that are negatives, as then you have to mentally parse a double negative when making sense of a FALSE value.

@joachim not sure I followed? You mean to have a setting to rather show the value than to suppress it? I just followed the same approach as the other hide settings in the module.

@hanoii I agree; it's following the convention provided by the description suppression field setting listed just above it. Behavior makes sense to me.

Is there anything going on with this issue? I have a view from my D6 site that uses Editable Views that did not have the current value; only the edit box. I need to see if I can get this to work.

I've applied patch #5, I don't see any issues thus far. Exactly what I was looking for. I change the default suppress value to TRUE as it seems redundant so I want the exception to be FALSE.

I have also tried the patch and it provides the expected functionality and doesn't seem to cause any problems.

The attached patch is mostly a re-roll of #5. It also adds this option to the Title edit field.

I also don't see an issue double negative since it is consistent with the other options.

I'd love to see this patch get in. The 18 exceptions are all Undefined index: suppress_value. Seems like that's probably a simple fix (I know in a template that error means you're missing an if (isset (...) but I'm not enough of a module developer to figure out what's needed.

re-queued for testing ...

Attached patch updates #12 to test to see if "suppress_value" exists on handler options array, and if not, outputs the value (equivalent to suppress_value === FALSE). If the options array does contain this key, it handles it.

Patch from #20 applies and works great!

@hanoii thank you for #5; @robertwb thank you for #20. I am using #20, it applied cleanly, it works great, and I think it is needed for many use-cases because it is a powerful way to reduce clutter on a large editable view.

Setting RTBC.

+++ b/handlers/editableviews_handler_field_field_edit.inc
@@ -62,6 +63,13 @@ class editableviews_handler_field_field_edit extends views_handler_field_field {
+      '#description' => t('If selected, the value on field is hidden.'),

This needs a reword. Other than that, looks good. Thanks for the reviews!

patch works great for me as well

Updated checkbox's description (as mentioned in #24) to help commit it sooner..

Sorry.. ignore my previous one.. (I forgot to change the description in the 2nd case)

This patch works for me. :)

Great Patch please commit it.

Yes patch works great, please commit

Confirmed, patch from #28 applies and functionality works as expected.

bump

#28 is rocks!

hurray! 28 works