World: r3wp

I have downloaded Curecode source.

The func is defined in "db-abstract.r" and has the missing refinment 
!
So what ? Is just the installed file on the site not up to date ?

I'm not familiar with RSP, but it seems it's loaded one time then 
run with the webserver (not like cgi that are loaded on each call).

So maybe it just need to be restart to handle already corrected code 
!?

Thanks, DideC, I'll fix that tonight.

Just a note... I had to restart the server to get CC running... reloading 
config is not enough.

Also I'm missing basic instalation notes...
1. to add into httpd.conf:
	webapp [
		virtual-root "/curecode"
		root-dir %www/curecode-r091/ ;or different dir
	]
2. To get a known admin password, change in private/build-db.sql:
EE10C315EBA2C75B403EA99136F5B48D 
to

21232F297A57A5A743894A0E4A801FC3  ;(enbase/base checksum/method "admin" 
'md5 16) = so the known password will be 'admin' for admin account

3. to run private/install.r script

And there must be something more as registering new user gives error:
Error Code :  	500
Description : 	access error !

Cannot open /c/rebol/server/Cheyenne/www/curecode-r091/www/curecode-r091/nonenone/email-activation.tpl

Near : 	[template: read join locale/get-path %email-activation.tpl]
Where : 	send-confirmation

to get rid of the first none, it's resuired to add:
locales-dir %locales/

into webapp block... the second none is difficult. at least i really 
cannot find, how to set the 'lang in locales. The 'default-lang  
in 'webapp seems not to be working and in main httpd.conf as well. 
It must be a bug (or missing feature) in public version of the Cheyenne.

Admin install password is "nimda"

It requires also a valid SMTP server in %private/curecode.conf.

should be : locales-dir %private/locales/

Didec : the bug you've found is related to the Cheyenne instance 
version (0.9.17) CureCode's demo is running on. It's a typical case 
of global context word collision between several apps defining global 
functions using the same name. That's why I've sandboxed, by default, 
all RSP webapps in v0.9.19.

rebooting CureCode...

Is the reboot done ? I get "La connexion avec le serveur a été réinitialisée 
pendant le chargement de la page." while trying the confirmation 
link.

It's down currently, I'm trying to migrate the CureCode webapp to 
the main Cheyenne instance on the server, but it seems I've messed 
up something in the config file.

Ah, looks like it's missing a user right access in MySQL.

Up and working now.

Ah, important notice : URL has changed, it's now http://softinnov.org/curecode/

You may need to remove the :8000 part in the activation link.

OK. Trying...

hmm, failed to log on...

Works like a charm !

right, works now.

index.rsp doesn't work !

(Accueil link)

let me see that...

works here

right, works only when Projects selector is set to "all"

There's a bug in %index.rsp from a change I did last week in the 
statistics SQL code. Fixing...

Fixed

Should work ok now.

The "Attached Files" zone in ticket edition mode is not yet working 
so just ignore it.

ok. Must go. See later

If someone can do a step by step blow on installing curecode ( including 
what ever one has to do with mysql ) .. I will try and set it up 
as well .. I need a public bug tracking database too.

Several questions:


- what is meant by Severity field of values - text, block, feature? 
I do understand major, minor, trivial, etc., but not those mentioned 
...

- for better searches, I would expect field 'fields to be filled 
in with every field form contains. E.g. I want to filter using 'Built-in

- CureCode, if slightly refined, could serve as auto changelog generation 
system. But Carl (or responsible person) would have to fill-in 'built-in 
field. In the past, I e.g. proposed addition of small table called 
Releases to RAMBO for such purposes. It would contain named releases. 
Main base could have small helper, value 'next pre-filling 'buil-tin, 
once someone markes it as built. 'next would be related to the closest 
relese from the Releases table.

Severity:
- Text: typo error, wrong text,...(minor severity)
- Block: blocking issue or error (worst severity with Crash)

- Feature: not really a bug, more a new feature (it has been almost 
superceded by the new Type field)


Searches: the search feature currently only works on TEXT fields 
(missing 'comments field). Version, built-in and others are INTEGER 
fields storing ID they should be in the filter section. The filter 
section needs to be expanded.


Changelog: it seems to me more reliable and secure to just correctly 
fill-in the 'built-in field once built.

re Block - ah, I thought it is related to REBOL block! datatype :-)

I thought these were interesting priority codes http://simile.mit.edu/wiki/Priority_Codes

I think that explicit words are easier to remember than P1,P2,P3...

I mentioned it not so much for the codes, but the classes they use 
.. eg P9

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.