World: r3wp

Doc, I still have issues with the cookies created from Curecode. 
Essentially, when I leave the browser open and the session expires, 
the next time I try to use curecode, it loads up the error page. 
I just manually delete the cookie and I'm good and I have extended 
the timeout as well which helps. I was wondering in the httpd.cfg 
file if there is any value for curecode's timeout that will make 
it endless (perhaps "none" ? ). Thanks. It is a very usefule app.

There is no endless timeout value. Such feature would blow up the 
server's RAM sooner or later.

the next time I try to use curecode, it loads up the error page.

 Could you be more specific? On what page do you let the browser open? 
 What do you do when you resume your work after the session expires 
 (on what link/button do you click)?

I'll have to verify when it happens again but I think it's the "Sorry. 
this page cannot be displayed." And any link clicked will cause this 
to come up.  Doc, this is not super important because changing the 
timeout helps. I'll wait until it happens again and give you better 
details. How's that  sound?

Besides, no one else seems to have this issue so it could very well 
be something on my side.

Thanks, that would help, as I tried several times to reproduce your 
issue without success. By the way, what browser (and version) are 
you using?

Do you have a browser plugin or any other tool installed that could 
remove or alter in any way your browser cookies?

I use FF 5.0 (just upgraded this morning though. Previously it was 
4.0.1). As far as cookie altering tools, not that I know of, though 
I was wondering if AVG could be doing something. Anyway, I just cost 
you a few lost Red minutes. I'll wait until it happens again.
Thanks.

No problem, I am used to multiplex different tasks. ;-)

At some point recently, Chrome started saving the username and password 
in CureCode. Don't know whether this was a CC or Chrome change, but 
it's welcome either way.

I guess it's a Chrome change, last update on CureCode site was in 
January.

Doc, it says in the trace.log that there is an SQL error:


** User Error : ERROR 1064 : You have an error in your SQL syntax; 
check the manual that corresponds to your MySQL server version for 
the right syntax to use near '' at line 6 
	** Where: none 
	** Near:  [do-sql/flat 'r3bugs [{

I will have a look, but it has probably been fixed since v0.9.8.

well, it worked before, but I'm curious about the near '<unknown 
char>' bit

if there are no dangers in upgrading curecode, I may do that instead.

trying 0.9.12 and getting this crash:


        URL  = /bugs/
        File = /home/henrikmk/serve/www/bugs/head.rsp

        ** Script Error : Invalid path value: locals 
        ** Where: repend 
        ** Near:  [request/config/locals/instance 
%title.inc

This is with the latest cheyenne release 0.9.20.

Have you followed the migration process? There's a migration script 
in the archive, probably in the /private folder.

It's the %private/upgrade-096-0910.r script.

I see, will try.

There doesn't seem to be such a script. There is however an install.r 
script.

About your error, the newest CureCode versions require the definition 
of a LOCALS block in the webapp:

	locals [
		name		"REBOL3 Tracker"
		instance	%rebol3/
		short		"r3"
	]

private$ ls

ChangeLog.txt     build-db.sql   generate-load.r  helper.r   instances
access-control.r  db-abstract.r  generate-test.r  install.r

I see, thanks.

ok, it looks like I'm going to need that upgrade script. where can 
I find it? it's not included in the distribution.

http://curecode.org/dl/upgrade-096-0910.zip


I am not sure it applies to 0.9.8, you'll need to check if the new 
SQL  tables are already there or not.

Be sure to backup your database before using it.

ok, thanks.

now I get an invalid port spec:

** Access Error : Invalid port spec: mysql://<removed>
        ** Where: do-sql
        ** Near:  [do-sql/flat 'bugs any [

You should check that <removed> part for an invalid definition.

It should be something like this:

mysql://user:[pass-:-localhost]/bugs


I also tried it in a different console and it only appears if the 
mysql-protocol is not loaded.

There is no reference to mysql-protocol.r anywhere in the source 
code. Could that be it?

In 0.9.8 there is a reference to mysql-protocol.r in app-init.r, 
but it's gone in 0.9.12.

Ah probably, now CureCode expects that the %mysql-protocol.r be loaded 
externally. The best way to do that is to instruct Cheyenne to load 
it directly by declaring it in the GLOBALS section of the config 
file, like this:

	worker-libs [
		%<path-to-mysql-protocol-folder>/mysql-protocol.r
	]

I see.

Btw, all these setup steps are handled by the %private/install.r 
when doing a new installation.

actually no, I already read through the install.r file and there 
is no reference to anything but SQL queries and a message which contains 
a description of the webapp, but not worker-libs.

You're right, it is missing, I'm adding it right now.

Another crash in index.rsp:

sess: session/content

	if all [
		not sess/login?
		none? validate/full [action word! *]
		'identify = request/content/action
	][

SESS appears to be NONE.

Have you restarted Cheyenne fully after the changes in httpd.cfg?

I kill the old session with kill -9 and start the new after that

You should stop Cheyenne completly, remove the %.rsp-sessions file 
found in Cheyenne working folder, then restart it.

ls -lR | grep sessions

reveals no such file

Try with ls -laR | grep sessions while Cheyenne is fully stopped.

It's a file starting with a dot (= hidden file), so -lR is not enough 
to list it. Also, it exists only when Cheyenne is not running.

where is the worker-libs block supposed to be located?

GLOBALS section of %httpd.cfg

that seemed to be it. now I'm back to this morning's crash when clicking 
bug entries in the database.

ok, missing table...

The upgrading script should have created all required tables.