I know this is a known request. Just posting it for the reminder and 'it's how it should be'.

Comments

Michsk’s picture

Michsk commented

...

Michsk’s picture

Michsk commented

Mikestefff: any time / plans to get this done?

mstef’s picture

mstef commented
Status: Active » Postponed

I'm working with the Drupal.org redesign team to get Homebox ready for the launch. There is a very long list of changes being made. Once all that architecture is set and finished, I'll be able to get to this. Sorry!

Michsk’s picture

Michsk commented

Ok but this is one of the drupal.org dashboard things. That saving is done automatically, no loading text, trobblers or other things, just autosave. So fixing this would already be a step ahead.

drumm’s picture

drumm
he/him
Location NY, US
commented
Assigned: Unassigned » drumm
Status: Postponed » Active
Issue tags: +drupal.org redesign
Michsk’s picture

Michsk commented

yes

drumm’s picture

drumm
he/him
Location NY, US
commented
Status: Active » Fixed

Committed my work for this. It is a page option since different types of pages and situations call for different save rules.

mstef’s picture

mstef commented

...different types of pages and situations call for different save rules.

??

drumm’s picture

drumm
he/him
Location NY, US
commented

Personal dashboard - good idea to always auto-save.
Group dashboard that a lot of people see - good idea to preview and save when done.

mstef’s picture

mstef commented

Do we have homeboxes where one setting persists for all yet (group)?

mstef’s picture

mstef commented

I was the one who stripped auto save. I personally don't like it. Ideally, it wouldn't just be an option per page, but for the user while viewing the home box - perhaps a checkbox or something.

itsnotme’s picture

itsnotme commented

Moved comment to a better fitting place :)

Michsk’s picture

Michsk commented

Mike: really autosave is the best option for this. I cant get it that you dont see it. You want to give the user a option to check if he wants to autosave or not? Then well also have to explain 1)what auto save is and 2)what it autosaves. This is really not a good idea.

Personal dashboards just need to autosave.

The group dashboards, sure, those will need some 'thinking' to get it working for a group.

Michsk’s picture

Michsk commented

Im going to install latest dev right now, time to test all the new development on this module.

Michsk’s picture

Michsk commented

This works good for personal dashboards. I can not test for groups, since i don't use groups.

My personal preference would be to make the ajax saving and getting quicker tough... When you now move a bock, drop it, and press F5 you get a error.

A HTTP-error 0 occured; /##/homebox/js/dashboard/save

Status: Fixed » Closed (fixed)

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

bryancasler’s picture

bryancasler commented

On my site I am having the same problems as #15

On drupal.org/dashboard I do not have these problems

mstef’s picture

mstef commented
Status: Closed (fixed) » Active
brianV’s picture

brianV commented
Version: 6.x-2.x-dev » 7.x-2.x-dev
Priority: Normal » Critical

Bumping this to 7.x-2.x-dev.

Any fix will be backported to 6.x-2.x-dev.

brianV’s picture

brianV commented

marked #961364: Saving partially broken in 6.x-2.x-dev ? as a duplicate.

brianV’s picture

brianV commented
Title: Auto save » Auto save and regular save broken in 7.x-2.x-dev and 6.x-2.x-dev
Assigned: drumm » Unassigned
brianV’s picture

brianV commented
Category: feature » bug

Also, this is a bug.

brianV’s picture

brianV commented
Title: Auto save and regular save broken in 7.x-2.x-dev and 6.x-2.x-dev » Auto save and regular save broken in 6.x-2.x-dev
Version: 7.x-2.x-dev » 6.x-3.x-dev

Autosave and regular save have now been fixed in 7.x-2.x-dev.

Can someone confirm this is still a problem in the current D6 version? I don't have a copy of that running to check against, but the code doesn't have the same bug that broke it in the D7 port.

brianV’s picture

brianV commented
Status: Active » Fixed

Actually, I am looking at what it was re-opened on for Drupal 6. The #15 issue happens simple when you change the page before an AJAX request completes. It in no way indicates that autosave is broken, it just means that not enough time was given.

Unfortunately, AJAX only moves at the speed of the connection between you and the server, so not much we can do about it.

Marking as fixed, re-open if autosave is still problematic

rhymeswithcamera’s picture

rhymeswithcamera commented

I just upgraded to 6.x-3.0-beta2 (from 6.x-2.1). I apologize for my ignorance, but how should the Auto Save feature be behaving? Should I still be seeing a "Save" button with the "Unsaved" text when changes are made? I was assuming that it would work similarly to drupal.org where the saving happens automagically. Is there a setting I need to set somewhere?

brianV’s picture

brianV commented

You will need to go to the edit' page for your homepage. There will be a checkbox there to enable autosave.

rhymeswithcamera’s picture

rhymeswithcamera commented

Hmm, okay. I have two Homeboxes and the Autosave feature is checked for both. By checking this feature, is it supposed to hide the Save button, etc.?

drumm’s picture

drumm
he/him
Location NY, US
commented

Yes, the idea is the save just works and doesn't need UI clutter.

(There could probably be better reporting of connectivity issues, but that's another issue.)

rhymeswithcamera’s picture

rhymeswithcamera commented

Thank you. I got it working. I had to disable the Autosave feature, save, and then enable it again for each Homebox. Now it's working as expected. A much cleaner UI experience.

jcl324’s picture

jcl324
he/him
Primary language English
Location Portland, OR
commented

I have enabled/disabled autosave several times, and the autosave still does not work. The save button does appear and does save when clicked. What else might I be missing to get autosave to work?

drumm’s picture

drumm
he/him
Location NY, US
commented

Sounds like some JS on the page, not necessarily from homebox, is failing and bringing all the other JS to a halt. Load the page with your browser's JS console on and find the source of the error.

drumm’s picture

drumm
he/him
Location NY, US
commented

Or your theme is causing some jQuery selector(s) to miss.

Michsk’s picture

Michsk commented

no, it's got to do with the load. I thought that there was some kind of timeout in the homebox module, but guess there's none.

k3vin’s picture

k3vin commented

In my case i had this issue because i overided some form-classes in my template.tpl.php. After removed the overide function homebox saved the block settings as it should.

thanks for the hint drumm.

pkkelly’s picture

pkkelly commented
Issue tags: -drupal.org redesign

Hi All

My issue is that the auto save is working when items are closed or added, but when items are moved to other columns the autosave is not being triggered.

Any pointers anyone?

I havent changed any form-classes in my template and have flushed all user settings and re-enabled the auto-save feature a few times now!

zazinteractive’s picture

zazinteractive commented

I got:

An HTTP error 0 occured at /homebox/js/dashboard/save

When I click on add block, close a block on dashboard and then click on the same block in the add block menu

brianV’s picture

brianV commented

That is not related. That error is generated when you try to perform an action (changing the page etc.) before an AJAX request is finished.

Status: Fixed » Closed (fixed)

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