World: r3wp

debug/probe mold spec
 inserted on the first line...

no difference. it still reports tcp error. it must be coming some 
time before that function.

got debug/probe working now. it definitely stops at 'send-confirmation.

oh that's it. I just need to fill that function up with debug/probes 
and it works. :-) got a mail now.

graham or doc, could you please try registering at:

http://97.107.135.89/bugs/register.rsp

your account will be deleted after testing is done

Type the code your read in the following image

should be .. type in the code below or similar

I'm registered and in!

nice work .. hope you document all the fixes you had to make.

cool. now I need to access the admin account. only need the password.

yeah ... you only have the hash!

encode-pass: func [pass [string!]][
	enbase/base checksum/method pass 'md5 16
]

use that to create your new password and store that in the db

ie. store the result.

default admin account is : nimda

that's in comment somewhere (build.sql or install script)

Registering: ok
Email: ok
Login/logou: ok

this is sweet! complete user and project management.

v0.9.9 is a little bit better for management.

I'll make a package asap, so you can upgrade.

it's not in the sql script that I saw

yes, BTW, there are many places where the word REBOL3 is hardcoded 
in strings. I was wondering if it's a good idea to move that to the 
config? It seems obvious for customization.

also in the top table of the page, the one with three columns, I 
forced the width of each column to 33% to avoid the changing of the 
title to move the page name in the top middle of the page.

Since this works so well, I will reward graham and doc by keeping 
their accounts, so you don't have to register again. :-)

I would have said that CC's current install process is a real PIA 
;-)

I think we unearthed a lot of things that we otherwise would just 
bump into along the way, anyway. I'm still not safe on the email 
issue, as the debug lines are still present.

Ok, submitted a ticket!

That worked.

cool :-)

I'm working on an integrated client Mail Transfer Agent that will 
handle emails sending in Cheyenne without the need to install any 
third-party mail server. It should be ready in a couple of days.

nice

How will that work?

Transparently for the user. Internally, like a normal MTA, getting 
the right MX, queuing outgoing emails on disk, retry sending a few 
times if required, inform back user (and admin optinaly) by email 
if sending failed.

RSP users will just use SEND without any change. SEND will be patched, 
so SET-NET won't be required.

Obviously, emails will be sent in async mode by the UniServe layer.

what will you use for DNS?

OpenDNS?

I did this before ... http://www.rebol.org/view-script.r?script=email-check.r

only a couple of linest to make that into a mta :)

DNS server: the ones declared locally on the machine.

Yes, I've been inspired by your code when I started working on it.

I use something similar to provide mail support inside my application 
...

But I've reimplemented the dig:// scheme as an UniServe async protocol.

ahh... good idea

Looking forward to trying  it out

what is dig:// scheme?

DNS records querying

Doc - does Cheyenne already enable setting handlers for particular 
filetypes? I mean - equivalence to:

AddHandler rebol-cgi-dispatch .html
Action rebol-cgi-dispatch /cgi-bin/rebol-cgi-dispatch.cgi


For Cheyenne only users, it is not important, they can use RSP, but 
for those who want to have chance to migrate between Apache and Cheyenne 
in CGI mode, it might be usefull. I expect it not being a priority 
for you though ...

oh, wrong group .....

Would it be possible for a developer to have his reports automatically 
reviewed? There's a lot of extra clicking involved for me in my curecode 
since I submit reports to my own tracker.