Quiet Save Still Spams WebChanges

I decided to spend some time attempting to add a TopicClassification to topics appearing in SelectOne in order to help the process of refactoring. After working through a few of the topics I noticed WebChanges was being spammed by my work although I was using the quiet save.

How can I rapidly class SelectOne topics using the BasicForm without making waves in WebChanges?

-- Contributors: TravisBarker - 29 Mar 2008

Discussion

If there is no easy solution I would propose a scheduled TWikiRefactorDay? where all normal dev is suspended for a day of spring cleaning, we can coordinate the refactoring process from the TWikiRefactorDay? topic and from TWikiIRC.

-- TravisBarker - 29 Mar 2008

A TWikiRefactorDay? is an interesting idea. Could be fun.

-- FranzJosefGigler - 29 Mar 2008

I guess one solution could be a an additional "!InvisibleSave" button that would be a QuietSave (no email sent) but also would read the file date, set the %TOPICINFO to it, save, and set back the file date to the saved date. Seems worth of a feature request. Or it could be a checkbox option on save

-- ColasNahaboo - 29 Mar 2008

I for sure do not want it to be possible for people to save topics without the topic to appear in the WebChanges.

Two reasons.

• On my Motorola site we are some that really want to see what is being changed no matter what the person saving may think about it.
• On my Motion (public site) that it the only way I with the help of all the good users can keep an eye out for spam and remove it. An invisible save would be a heaven for spammers.

We already have Save, Quiet Save, Save and Continue and we have a Force new revision checkmark. In my view already at the limit of what should be of user interface related to saving.

I think an occational "spamming" of a WebChanges view occuring in very rare situations is a better trade off than another "high on the NerdoMeter"/"spamming heaven feature".

Maybe someone can write a small script that an admin can run that puts the refactored topics low on the WebChanges list. That would be a better solution.

-- KennethLavrsen - 30 Mar 2008

On the other hand, why would we want to have important refactoring be hidden from WebChanges?

In the spirit of hope, progress, and that others join in - let the efforts be seen.

(Mind you, i do find it difficult to keep the technical discussions going when the Dev topics in Codev drop off WebChanges - but i see that as a sign then we should split the Codev web site, not that refactoring should be hidden)

-- SvenDowideit - 31 Mar 2008

here is what has me concerned... PleaseStopCategoryStaleDeleteMe does this mean BasicForm should be replaced with tags? Im starting to lean toward having TWikiRefactorDay?

-- TravisBarker - 31 Mar 2008