Some field types would work well with auto saving functionality.

My example is a file field using the media module widget.

This widget provides its own buttons for uploading, removing, editing files.
It would be cool if we didn't have the editablefields save button and the node was automatically saved when one of those other operations is completed.

This feature would not really be useful for text fields etc though.

Basically I'm just talking out loud and if it is possible then great.

I can probably customise my own javascript solution for this for my current requirements.

Comments

mmilo’s picture

mmilo commented

Perhaps you could help out with #1172174: Make autosave optional and implement a "save button" views field ? :)

rooby’s picture

rooby commented

I would love to but I don't have the time sorry.

I also didn't end up doing my own custom javascript solution as mentioned in the original post as I ended up going with a different (not editablefield module) solution for editable fields that better suited my requirements.

gilmord’s picture

gilmord
Location 🇺🇦Ukraine
commented
Issue summary: View changes
Status: Active » Closed (outdated)

D7 reached its EOL back in January 2025, and there is no active release for D7 for this module anymore.
Development or support is not planned for D7. All D7-related issues are marked as outdated in a bunch.

Everyone can apply the patch above (not tested by the maintainers, tested by the community) to their D7 projects.
If the issue remains relevant for D10+ versions, merge requests with proposed solutions for a new module version (D10+) are welcome in a new follow-up issue.

Thanks!

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.