World: r3wp

I saw the classes but in CC (and in all other trackers I worked with) 
priority is not the key property driving the workflow, the most important 
one is : status. In CC/R3, P9 class would have the status "dismissed".

Anyway in CC, you can define your own list of priorities, statuses 
and severities if the default ones don't suit your needs.

Is CC for R3 closed for new users?

No, it's not and was never planned to be.

Looks like Paul had some difficulties registering or maybe hit a 
bug. In this last case, I'd like to see a detailed report (in this 
channel) from Paul.

Reports back "error account not yet activated".

I tried to register again and get this "Sorry, this page cannot be 
displayed. Try again or contact the web site administrator."

Steeve had similar problems - that is why we had to request that 
you add an account, Doc.

Error account no yet activated

 => check your junk folder in your mailbox for the confirmation email 
 (I need to investiguate on this one, could be caused by different 
 kind of issues)

Don't worry about getting me an account for curecode.  I'm not on 
the team that is working on R3.  Henrik was just trying to allow 
me to submit an enhancement throu there.

I'll check it - hold on.

nope nothing there related.

Sorry...

 message => trapped RSP script error, I'll look in the log file to 
 see what caused that.

Ok, so either your mail server didn't accepted emails from CureCode 
server, or there's a random bug on CureCode's email sending script.

Anyway thanks for the info Paul.

I don't know why my mail server would deny it.  I can try a different 
email account though.

Please do. I'll force activation on your first account.

Let me know when ready as it says that account exists.

Your first created account is active now.

Yep that worked.

You provided the same email address in the second attempt.

Yep.  No problem its working.

Doc, curecode site is nice and fast - good work!

I have lost some work on occasion due to the login timeout not being 
long enough. The post-only interaction model means that I can't go 
back to get my edits, so if I have to log in again my edits are lost 
for good.

I have taken to composing my comments and tickets offline as a result.

either have a longer timeout or implement ajax pings to keep session 
active

Brian, I agree that's an issue that needs to be solved. I thought 
about removing session timeout. Session would then end only when 
the browser is closed.

On second thought, that solution wouldn't be reliable enough on server 
side.

Not even that. It would be sufficient to do two things:

- Do a server-side redirect to a get page when you go into edit mode 
on a ticket or comment update.

- If doing a post and the session has timed out, create a new session 
and save the data to it temporarily and take the person to a login 
page. After the relogin, take them back to the page with their edits 
prefilled in. Then let them save (or perhaps save on the way).

Yes, that would be a good approach that could solve the issue at 
application level (not having to modify Cheyenne's session framework).

That is the method I used when I ran into this situation in the past 
with ASP.NET and ColdFusion sites - don't know the RSP version.

Seems doable in RSP.

I'll add that to the todo list for next release.

Thanks

Carl is having me review the submissions for him, so I have been 
using CureCode a lot lately.

Outside of work time, of course. (Hi Reichart!)

:-)

I'll give you admin rights then, so you can have more control on 
lists like Versions and Categories. My development version also allow 
admin users to force account activation easily from the users admin 
page.

Cool.

Brian, the new CC version has this new feature : "Ticket submitter 
can now delete his ticket." Do you agree with this feature for R3's 
CC?

Updating R3's CC to version 0.9.6...

yes, good feature. :-)

;-)

Upgrade done. Let me know if there's any regression.

Changelog : 0.9.6 - 21/01/2009

	o FEAT: Ticket submitter can now delete his ticket.
	o FEAT: Admin can now delete any ticket.
	o FEAT: Admin can now delete a user.
	o FEAT: Admin can now change user's role.
	o FEAT: Admin can now force validation of a new user's account.
	
	o FIX:	Tickets list loading twice on first visit issue fixed.
	

 o LOOK: Input fields and buttons border width reduced to 1 pixel.

After adding a ticket to CureCode I can no longer  get the ViewTickets 
page.
I just get  


Sorry, this page cannot be displayed. Try again or contact the web 
site administrator.

Go back to home page

Strange bug. I can see the new ticket : http://curecode.org/rebol3/ticket.rsp?id=573&cursor=1

Looking at the log files...

Try to log out, then log back in.

i logged out a few times, no difference.
Later i will try to restart my Seamonkey.