Forum Moderators: coopster & phranque

Message Too Old, No Replies

Collective v3 not configuring

Collective v3 not configuring

         

ittlecas

7:29 pm on Apr 30, 2001 (gmt 0)



Love the idea of the software but I cant seem to make it run right. After setting all rights to full for everybody (temporarily) I still cant make the configuration script run.

I'm running on a NT 4 box and using frontpage to edit permissions. The script execute is working but when I tell it to write the configuration file I get a return of:
There was a problem creating the configuration file:
/collective/data/collective_config.lib
Check to see that the permissions on the data directory are set to (755 or 750).
Also check the "data directory" line near the top of the main collective script to see that it points at the collective data directory.

Paths are all correct and all permissions are set ... what am I missing?

sugarkane

8:47 pm on Apr 30, 2001 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Hi ittlecas, welcome to WebmasterWorld!

What path do you have defined for the 'data' directory?

ittlecas

9:23 pm on Apr 30, 2001 (gmt 0)



Well its /collective/data, of course. But if you'd like to see the problem in action, I still have it posted at www.cne-c.com/collective/collective.cgi.

sugarkane

9:31 pm on Apr 30, 2001 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



I may be way off the mark here, but shouldn't it be set to something like c:\server_root\collective\data if it's on an NT box? I think it needs to be a full directory path for the actual location on the server.

littleman

9:59 pm on Apr 30, 2001 (gmt 0)



It also needs double slashes -> c:\\server_root\\collective\\data

ittlecas

3:22 am on May 1, 2001 (gmt 0)



Ok well .. it took me a while to get the info off of the webmaster and what not but you are right about the double slashes. I changed all the info to physical path with single slashes and not even the main page script would run. BUT with double slashes in all paths, I still get the error ...
There was a problem creating the configuration file:
x:\ftp\cnec\collective\data\collective_config.lib
Check to see that the permissions on the data directory are set to (755 or 750).
Also check the "data directory" line near the top of the main collective script to see that it points at the collective data directory.

littleman

3:31 am on May 1, 2001 (gmt 0)



You'll most likely have to do the double slash thing again. Don't worry about permissions on NT, it won't matter. Odds are you have to put the full path with the double slashes in the "data directory" as well.

ittlecas

6:37 pm on May 1, 2001 (gmt 0)



Ok, yea the double slashes are in all the paths and I just double checked the path with the webmaster. All locations are correct and have double slashes. Whats next on the checklist?

littleman

7:02 am on May 3, 2001 (gmt 0)



Ittlecas, so what is happening now when you script the script?

ittlecas

1:58 pm on May 3, 2001 (gmt 0)



Same thing as while back. I had changed all the forward slashed to double backslashes on the first run. When you made the last suggestion, I mearly double checked the paths and physical location. Everything looks correct but ... Here you can look at it

www.cne-c.com/collective/collective.txt

littleman

4:57 pm on May 3, 2001 (gmt 0)



okay, try to change -> require "common.lib";
to the full path -> require "x:\\ftp\\cnec\\collective\\common.lib";
And then let's go from there.

ittlecas

5:14 pm on May 3, 2001 (gmt 0)



Done but no affect.

littleman

8:21 am on May 4, 2001 (gmt 0)



Looks like your script is unable to write files. It might be that the server is set up to allow scripts to write to existing files but not create new ones. If that is the case you may try to make blank files with the respective names and drop them in where they belong.

ittlecas

7:03 pm on May 4, 2001 (gmt 0)



Hey a new error
Script Error
Couldn't load required libraries.
Check that they exist, permissions are set correctly and that they compile.
Reason: X:\ftp\cnec\collective\data\collective_config.lib did not return a true value at X:\ftp\cnec\collective\collective.cgi line 147.

Just thinking out loud ... what should a collective_config.lib file look like?

littleman

9:23 pm on May 4, 2001 (gmt 0)



Doesn't your path start with 'e' not 'x'?

ittlecas

10:37 pm on May 4, 2001 (gmt 0)



Yes, sorry, all paths really say E: in the scripts but I have been posting X: as the simbolic letter of a unknown drive letter. Didnt think the drive letter would be substantial to you / help-desk.

littleman

11:00 pm on May 4, 2001 (gmt 0)



<Plea to the WebmasterWorld community>
Can someone who has actually installed the Collective on a M$ box before step in.
</Plea to the WebmasterWorld community>
Ittlecas, don't you actually have the actual config file? Didn't you get it when you downloaded the zip?

NFFC

11:05 pm on May 4, 2001 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



>Can someone who has actually installed the Collective on a M$ box before step in.

<hand raised>
It was a long time ago, I'll go look and see if I can retrace the steps.
<\hand raised>

[added]
OK, this works for me [searchengineworld.co.uk].

General tip is that whenever it say's "most people won't need to change" consider yourself not to be "most people"

ittlecas

2:34 am on May 5, 2001 (gmt 0)



Hey, I have good news! ...mostly...
I didnt realize the config.lib file in the $main is the $data/collective_config.lib file but after littleman mentioned that I just put it in the data directory. I still cant overwrite the file with new config info from the program and it wont write server responces in the $temp dir but it will submit the data and give me a success/fail message. Must be a problem with the IIS (or me).

But I consider this a success all the same ... thanks for sticking it out with me littleman and also to nffc for the extra suggestions!!!

mike555

5:06 am on Aug 11, 2001 (gmt 0)



Where can I find this Collective v3 script?

sugarkane

8:42 pm on Aug 12, 2001 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



It should be on Search Engine World [searchengineworld.com] somewhere - try doing a site search there :)