World: r3wp

I'm upgrading CureCode to the latest version to fix this issue. Emails 
will be sent through the builtin MTA, fixing the instability caused 
by the SMTP scheme when a connection error occurs.

Entering in maintenance mode on CureCode server, current user sessions 
will be closed for the upgrade. If you're editing a ticket please 
save your changes now and logout from CureCode. I'll do the server 
upgrade in ~10mn.

Restarting server...

server up again, testing if everything is working ok....

forgot to add new options in config file...restarting

Seems to work ok now.

CureCode v0.9.10 changelog :

	o FEAT: Ticket's attached files management added.
	

 o FIX: Default query parameters corruption for anonymous users fixed.

 o FIX: Issue #1371 regarding policy for ticket deletion by owner.
	o FIX: Dimissed ticket can't be changed by the owner anymore.

 o FIX: Ordering not working properly for all filters and columns.
	o FIX: Minor missing translations for french catalog.

	o LOOK: Added Henrik's 33% fix for page header.

 o LOOK: "Example code" field now use PRE tag for better rendering 
 of source code.

is CC available for download?

Older versions are available here: http://curecode.org

Latest version: I need to build a package first, can be done rapidly, 
but no install script yet available, you'll have to figure it out.

Regarding the new attached files feature: adding or deleting files 
doesn't generate any new entry in the ticket's log. As attached files 
management is done asynchronously, it doesn't require posting the 
ticket's form to commit changes. So, the policy for logging attached 
files actions is not clearly defined yet. Your feeback about this 
topic is welcome.

For Chrome users, you might need to SHIFT-reload on CC's first shown 
page to get the lastest CSS file version.

Been doing usual user-type things on new CC.  Looks good!

why not put it on googlecode so we can access latest as we please 
8-) even better github, guthub is amazing 8-)

Thanks Sunanda. I'm currently testing emails sending.

Will: I'm already using my business SVN repository. Managing a new 
public repository would be currently too time-consuming for me. I 
prefer for now making snapshot archives for download. Once CC will 
be a bit more mature (having an install script for example), I'll 
probably move it on a public one.

Graham, please retry to reset your password, if you can't get access 
to your account, let me know.

Worked.  Thanks.

CureCode v0.9.10 source code released, see http://curecode.org/
New installation script included.

Thanks Doc 8-)

The password reset link doesn't change each time you reset the password.

You mean the key part? The key is per user account, not per email 
sent.

Do you think that's it's not enough secure?

Everyother system I've used which has reset the password has used 
a different link each time.

Can we have it so that the userid and password prepopulate?

I don't think CC remembers my project even though I set the R3 as 
default project.

Also, I use http://supergenpass.com/to remember my password ... 
but this seems to work oddly if at all on the CC site ...

It wouldn't matter if I could prepopulate the userid and password 
...

If I input a search item, then to clear the search item I have to 
clear it, and hit enter to resubmit with a blank search field?

Is there a filter to on searches to only show active issues?

Active issues: no such filter yet, I miss it too.

Looking at your preferences saving issue...

Can't see anything wrong with your prefs data nor in the prefs saving 
code. Your current default project is "All Projects", selecting R3 
project in the droplist, then going to Profile and hitting "Set default..." 
button should work, can you try it again?

Password remembering: Chrome's password system seems to have difficulties 
too. I don't have any clue about what the cause is, maybe BrianH 
would, as he had investigate such issues deeper.

Search item: any filter will remain active until you change its parameter 
or select another one.

Reset password link: CC's reset password link can only be compromised 
if someone get access to your email account or if he's able to sniff 
your web traffic. I'm not sure that the risk of someone taking control 
of your CC account and mixing up your posted tickets, or spamming 
comments is severe enough to raise the security protections higher. 
I usually apply protecting measures proportionnally to the level 
of risks involved. If you can convince me that the current level 
of protection used in CC is not high enough, I will raise it.

Doc, well, when I tried to log in for the first time I get the "Sorry. 
this page cannot be displayed.." error.  After fooing around with 
it for a while I thought perhaps the curecode code had to be located 
inside the root-dir. I originally had it on another drive. Well, 
that seemed to fix it. Thanks.

fooing = fooling

Such error message means that a REBOL error! has been raised in a 
RSP script or in %app-init.r. The error is then logged in %trace.log 
for you to review. I should make a customized error page by the way.

Doc, yes,  I realized that it was representative of an error after 
trying to create a test page to read a mysql db using your mysql 
library (just to test my mysql install). I wsa wondering though whether 
it's true that all the scripts have to be located within the root-dir? 
 That is, in my case, I had the curecode folder on a different drive.adn 
referenced that via the "root-dir" in the curecode web-app section. 
Well, actually, that was generated bu the "install.r" script. Just 
curious.
Thanks.

Webapp's root-dir must point to the folder where CureCode application 
is located. The install script doesn't move anything nor creates 
any file, it just builds the bugs database and prints out a webapp 
definiton based on the location of the CureCode folder, and answers 
you give.

Yes, I see that. What I was referring to was whether or not Cheyenne 
can see outside of  host's root-dir. BTW, the whole thing (Cheyenne 
and Curecode) work great.

Cheyenne can see what REBOL can see, there's currenlty no specific 
limitations in Cheyenne. However, it would be safer to limit accessible 
folders using the SECURE sandboxing system.

OK, thanks. Great stuff.

Would be better to create a R3 GUI project  now ... or filter them 
off and import them later on?

Doc, you might want to add a feature to curecode so that a user has 
a default project so we don't need to choose it everytime.

There is already ...

Really? I'll recheck as I must have missed it.

Ahhh there is.  I haven't been in my profie for so long.

Just wondering if  others are experiencing this behavior and/or this 
is a Cheyenne issue. After so many hours I have to restart the Cheyenne 
services in order for curecode to work. Cheyenne is working in that 
I can go to any other page.