We are running a roundup based tracker on
issues.fresco.org.

When (trying to) edit a bug older then about 8 month I
get "Error: activity" whenever I try to change
something. The message gets appended and send out via
mail, even inspite of that error (with all changes
documented), all other changes get ignored.

When reloading the bug-page even the message is gone.
We are using roundup 0.6.0. Any ideas?

Logged In: YES 
user_id=6405

Could you please post the actual HTML error to roundup-devel, or maybe 
try attaching it to this bug? 

Logged In: NO 

OK, here is the bug I want to change:
http://issues.fresco.org/cgi-bin/roundup.cgi/Default/bug41

I assign it to tobias and add a message "Will look into
this" and then click on "Submit Changes".

The result is what you can see under:
http://www2.fresco.org/tmp/bug41.html

You can take a look at the issues.f.o URL to see how the bug
looks after a reload of the page...

Regards,
Tobias (tobias at fresco dot org)

Logged In: NO 

All our Roundup-related files are in CVS by the way and can
be viewed at:
http://src.fresco.org/viewcvs/web/hosts/issues/

Just in case you need to look something up;-)

tobias

Logged In: NO 

All our Roundup related files are in CVS and can be viewed at:
http://src.fresco.org/viewcvs/web/hosts/issues/

Just in case you need to look something up;-)

Logged In: YES 
user_id=6405

Hurm. The error message really isn't very useful, is it :) 
 
I suggest commenting out the exception handler in the editAction at 
lines 998 and 1004, and see what the actual traceback tells us... 
 

Logged In: YES 
user_id=6405

Oh, just to make it clear: commenting out that handler will just let the 
exception propogate up further to the "unexpected" error handlers, 
which give far more information. The change still won't have any effect, 
but at least we'll have a clue as to *why*. 
 
parsePropsFromForm really needs much more consistent error 
throwing/handling :( 
 

Logged In: NO 

Thanks for the tip with removing the exception handlers. The
traceback brought me onto the track of some buggy detector.

That assumed that the activity field will allways change and
wourldn't want to report that, so it just removed that field
without much ado, causing that exception to be thrown.

Thanks! I guess this bug can get closed now.

Tobias