Currently the editor is always active, and as soon as you've made a change it gets saved, which isn't particularly a good workflow for most users. It would be better if you could enable editing mode via a simple 'squarespace-esque' interface, and then choose whether or not to save or discard all changes that where made at the end.

I will likely submit a patch for this at some stage as well as this is a requirement for myself.

Comments

perandre’s picture

It would be good to be able choose betweeen the way it is today, and what Deciphered suggests; both are useful.

iler’s picture

I agree that there should be option to use the way it now behaves or with this toggle editing & save button functionality.

iler’s picture

Just to make my opinion clear this is what I meant:

  • There should be option for using this save + undo button functionality.
  • But at the same time there should be possibility to use this autosave functionality because this is the way the Aloha Editor library is meant to be working.

So I think there should be option in the modules settings to choose which behavior you want to use.

iler’s picture

Project: AlohaEditor » Aloha Editor (obsolete)
Version: » 7.x-1.x-dev

Moving to Aloha project.

iler’s picture

Assigned: Unassigned » deciphered

Any progress with this one?

deciphered’s picture

Haven't had a chance to start yet iler, my need for this is for a personal project for my work, so it's lower priority than paying clients and we have just been hit with quite a few new projects which means priority has dropped.

However, there is no question I will be making this happen, I just can't confirm when.

It really isn't a hard thing to implement though, it's simply a case of storing the modified value in Drupal.settings somewhere and then triggering the AJAX callback on a button press. Ultimately I would like one button per page, but that's probably something that could be configurable.

Cheers,
Deciphered.

R.J. Steinert’s picture

Here's a related issue in the Aloha issue queue on GitHub https://github.com/alohaeditor/Aloha-Editor/issues/43 that gives some advice on how best to accomplish this. I'm new to this module so if someone wants to throw out a really rough patch, I can probably work it into shape.

sprice’s picture

One button per page? Why not just put it on the ribbon, or make it behave like the ribbon. Is that possible?

deciphered’s picture

I personally like the idea of one button per page, but I definitely think it should be optional, there should be multiple approaches the user can choose between. I'm getting close to this requirement in a project and will look at it soon.

R.J. Steinert’s picture

Drupal 7 had an "edit mode" for a little while.

#473268: D7UX: Put edit links on everything

But I think if there isn't some indication that something CAN be edited, then the user won't think, "oh, I'll click the edit button" and users don't necessarily need to edit 30 things on a page all at once (this is also a performance problem). Personally I think the edit button, save button, and other related actions (ie. there should be a hook in the save mechanism so we can do things like allow users to enter a revision message).

denjell’s picture

i agree. most of my users on the beta weren't even aware they could edit. dotted lines and yellowish background are not obvious enough. the autosave is nice, but accidents happen...

rootwork’s picture

+1 on both of these as options

I like the default behavior and could see it being really useful, but agree that in a lot of situations it can be confusing.

wim leers’s picture

Version: 7.x-1.x-dev » 7.x-2.x-dev
Assigned: deciphered » wim leers
Status: Active » Fixed

In the 2.x version of this module, Aloha Editor now works on the back-end, out-of-the-box (i.e. you don't have to download Aloha Editor separately anymore). Please *do* follow the included installation instructions.

The Edit module provides the functionality described in this issue.

If you want to use Aloha Editor on the front-end as well, please see #1782332: Upgrade the Edit module so that it leverages the Aloha module.

Status: Fixed » Closed (fixed)

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