Problem with installing Collective Access

GP_mngr_CA

Being employed in the ICT, I still am a novice at Collective Access. Trying to install a developers-environment, I ran into a problem. Setting up this environment, I started with XAMP 1.7.4 for windows on a laptop with OS: Windows 7. At first I had trouble with Apache unable to run, because the default port (80) was occupied by a system service. Searching on the Internet, I found a solution for that, but on implementing that solution, I decided to reinstall XAMP first and after that I no longer needed to implement the solution. XAMP is running smoothly ever since; Apache using the default port (80).

Next I followed the installation-manual on http://wiki.collectiveaccess.org/index.php?title=Installation_(Providence)#column-one

Configuration of PHP.ini was setup with the following parameters: post_max_size = 128M upload_max_filesize = 128M memory_limit = 512M display_errors = On

An empty MySql database named ‘collaccess’ with user ‘AC_admin’ with full access rights was setup. The contents of the CollectiveAccess software distribution was copied to the root of the web server instance, that is C:\xampp\www.

Configuration of setup.php was setup with the following parameters: <?php define("CA_BASE_DIR",“C:/xampp/www"); define("CA_URL_ROOT","/www"); define("CA_SITE_HOSTNAME","www.ca_oertijdmuseum.org"); define("CA_APP_NAME","collectiveaccess_oertijdmuseum1"); define("CA_APP_DISPLAY_NAME","CollectiveAccess Oertijdmuseum"); define("CA_DB_HOST",'localhost'); define("CA_DB_USER",'AC_admin'); define("CA_DB_PASSWORD",'************'); define("CA_DB_TYPE", 'mysql'); date_default_timezone_set('Europe/Amsterdam'); define("CA_SMTP_SERVER", 'localhost'); define("CA_SMTP_PORT", 25); #define("CA_SMTP_AUTH", 'login'); #define("CA_SMTP_USER", 'my_smtp_username'); #define("CA_SMTP_PASSWORD", 'my_smtp_password');

Generic site admin email - used as the "from" address

define("CA_ADMIN_EMAIL", 'info@oertijdmuseum.nl'); / ?>

When I try to access the URL ‘http://www.ca_oertijdmuseum.org/’, I get ‘the webpage cannot be displayed’ or ‘object not found! Please contact your webmaster’ and

Error 404 localhost 4-6-2011 10:19:08 Apache/2.2.17 (Win32) mod_ssl/2.2.17 OpenSSL/0.9.8o PHP/5.3.4 mod_perl/2.0.4 Perl/v5.10.1

I also tried adjusting the global.conf in C:\xampp\www\app\conf

Configuration of global.conf was setup with the following parameters: app_name = <collectiveaccess_oertijdmuseum1> app_display_name = <CollectiveAccess Oertijdmuseum> window_title = <CA_Oertijdmuseum>

locale_default = en_US

ca_base_dir =< C:/xampp/www > ca_conf_dir =< C:/xampp/www/app/conf> ca_app_dir = <C:/xampp/www/app> ca_lib_dir = <C:/xampp/www/app/lib> ca_models_dir = <C:/xampp/www/app/models> site_protocol = <http> site_hostname = <localhost

site_host = <site_protocol>://<site_hostname>

ca_url_root = <CA_root>

ca_media_url_root = <ca_url_root>/media/<app_name>

ca_media_root_dir = <ca_base_dir>/media/<app_name>

db_host = <localhost> db_user = <AC_admin> db_password = <************> db_database = <collaccess> db_type = <mysql>

smtp_server = CA_SMTP_SERVER

#smtp_auth = CA_SMTP_AUTH #smtp_username = CA_SMTP_USER #smtp_password = CA_SMTP_PASSWORD

ca_admin_email = CA_ADMIN_EMAIL

password_email_from = <ca_admin_email>

But the problem remains. What am I missing? Who can put me on the right track?

Henri

gord.barker

It would seem that because you set the CA_URL_ROOT parameter

define("CA_URL_ROOT","/www");

the address of your collection is now

http://www.ca_oertijdmuseum.org/www

at least thats the way it works on my system (I am using localhost rather than a web address but it should be similar.

GP_mngr_CA

Hi,

I tried accessing the URL http://www.ca_oertijdmuseum.org/www, but that didn’t work. Since your reply suggests to leave CA_URL_ROOT parameter blank, I adjusted it from define("CA_URL_ROOT","/www"); into define("CA_URL_ROOT",""); and tried accessing http://www.ca_oertijdmuseum.org, but it didn’t work either. Any other suggestions?

Henri

gord.barker

My dns does not see www.c_oertijdmuseum.org as a legitimate site. Is this a registered DNS name and are you installing collective access on the machine that this address points to? Is this a local machine that is resolved using Hosts?

rbur

Henri ... Although I'm having my own issues installing in Win7, I do have 4 installs of Providence working on XP machines with xampp. Unless I am not understanding your description (entirley possible given my current level of frustration) I think you have slightly mis-configured the setup.php.

In my installations of xampp .... the providence files go into a folder in the htdocs folder of xampp. Thus it looks like c:/xampp/htdocs/ca.

In setup.php, it would be: define("CA_WEB_ROOT_DIR", "c:/xampp/htdocs"); define("CA_URL_ROOT", "/ca"); define("CA_SITE_HOSTNAME", "localhost");

I suggest leaving the HOSTNAME as localhost at least to get things working. Call it from the browser by using http://localhost/ca

On one of my XP machines, I have two working instances of providence ... one in /xampp/htdocs/ca and the other in /xampp/htdocs/ca_sandbox and it all works perfectly (with appropriate definitions in setup.php).

Hope this helps ... Ron..

GP_mngr_CA

Gord,

That your DNS does not see http://www.c_oertijdmuseum.org as a legitimate site seems logical. The installation is on a local machine which isn't even always turned on. I tried to install a development-environment, therefore the URL is not yet a registered DNS name.

Ron

I tried your suggestion putting the providence files into the htdocs folder and adjusting setup.php. It isn't working yet, but the error-message has changed into:

Parse error: syntax error, unexpected ':' in C:\xampp\htdocs\ca\setup.php on line 5

Therefore it seems you put me on the right track, although there probably is still some cofiguration-problem in setup.php

Henri

rbur

Henri, I just realized that I may have mislead you a teensy bit. The values I quoted are for a 0.6 version ... for version 1 the values in setup.php should be: define("CA_BASE_DIR", "c:/xampp/htdocs/ca"); define("CA_URL_ROOT", "/ca"); define("CA_SITE_HOSTNAME", "localhost");

note that the first variable is different between ver 0.6 and 1.0

sorry about that.

This works for me in ver 1.0 and I have my permissions problems sorted out I think.

If you want, I can email you my setup.php in case you have over tweaked it.

Ron...

seth

Hi Henri,

I guess the hostname www.c_oertijdmuseum.org resolves to an actual IP address?

The error message Parse error: syntax error, unexpected ':' in C:\xampp\htdocs\ca\setup.php on line 5 indicates that you added some invalid code to your setup.php file while editing it. Take a look at line 5 for something that does not belong. If you are stuck then send the setup.php file to info@collectiveaccess.org and we'll take a look.

seth

GP_mngr_CA

Ron,

So nice to hear that you have solved your permission problems.

I realised that you were talking about a slightly older version and already used the parameters as they are in in the setup.php of the version I am using (that is ver 1.0).

define("CA_BASE_DIR", "c:/xampp/htdocs/ca"); define("CA_URL_ROOT", "/ca"); define("CA_SITE_HOSTNAME", "localhost");

but then I still get the parse error:

syntax error, unexpected ':' in C:\xampp\htdocs\ca\setup.php on line 5

Then I tried a slightly different approach:

define("CA_BASE_DIR", "c:/xampp/htdocs/ca"); define("CA_URL_ROOT", "/ca"); define("CA_SITE_HOSTNAME", "www.ca_oertijdmuseum.org");

but the result remains the same, that is the parse error.

I still am stuck, therefore Seth, I am going to use your offer and send the setup.php to you.

Henri

seth

One of the quotes in your setup.php file (on line 7 of the file you sent me) wasn't really a quote. It was a unicode character that looks like a quote. I sent you a file with this problem fixed.

GP_mngr_CA

Everyone thanks a lot for the help so far. As Seth showed me it is not such a good idea to edit setup.php with notepad.

When I put the fixed file in place, on accessing http://localhost/ca I got a whole series of new errors:

Warning: Unterminated comment starting line 130 in C:\xampp\htdocs\ca\setup.php on line 130

Strict Standards: Declaration of ca_users::delete() should be compatible with that of BaseModel::delete() in C:\xampp\htdocs\ca\app\models\ca_users.php on line 2256

Strict Standards: Declaration of ca_attributes::doSearchIndexing() should be compatible with that of BaseModel::doSearchIndexing() in C:\xampp\htdocs\ca\app\models\ca_attributes.php on line 720

Strict Standards: Declaration of ca_attribute_values::doSearchIndexing() should be compatible with that of BaseModel::doSearchIndexing() in C:\xampp\htdocs\ca\app\models\ca_attribute_values.php on line 367

Strict Standards: Declaration of BaseModelWithAttributes::delete() should be compatible with that of BaseModel::delete() in C:\xampp\htdocs\ca\app\lib\core\BaseModelWithAttributes.php on line 44

Strict Standards: Declaration of ca_item_tags::getTags() should be compatible with that of BaseModel::getTags() in C:\xampp\htdocs\ca\app\models\ca_item_tags.php on line 306

I immediately downloaded a free PHP-editor and with that, was able to get rid of the first warning error (which is not such a big deal).

However the Strict Standards errors are something quite different. Anyone any idea where those come from and how to get rid of them?

Henri

svendecabooter

What version of PHP and CollectiveAccess are you running exactly? Those strict errors should probably be handled in the code (if they haven't yet, perhaps you don't run the latest code). As an intermediate solution to have them not shown, i think you should tweak your error_reporting settings in php.ini (http://www.php.net/manual/en/errorfunc.configuration.php#ini.error-reporting).

seth

There are a few strict standards with which we do not comply, and probably never will due to the way PHP inheritance works. The best thing to do is disable strict warnings in php.ini, as Sven suggests.

GP_mngr_CA

Sven, Seth,

Thanks for the suggestions. I am going to look into into it, after this weekend in Budapest.

Henri

GP_mngr_CA

Hello there Seth, Sven,

it's been a long time since I put on another post. This is due to a shift of project-focus by my employer. We have taken the Collective Access Project out off the Ice-box mid-december 2011. At that time we tried to solve the 'strict standard errors' with yours suggestion of tweeking error_reporting settings in php.ini. We didn't get far. Therefore we tried a different approach. We installed XAMPP on a WinXP-workstation and tried installing Providence 1.1. This went smoothly! Collective Access is running perfectly on that machine. Then I tried the same installation-method on the Win7-machine. Unexpectedly the same errors appeared. Therefore I compared the installed components on both machines. I discovered there was a version-difference in the XAMPP on the WinXP- and Win7-workstation: on the WinXP-machine XAMPP 1.7.2 was installed, on the Win7-machine there was XAMPP 1.7.4! After deinstalling the 1.7.4-version and installing the 1.7.2-version the installation of Providence 1.1 went as smoothly as on the WinXP-machine.

Conclusion: somehow the combination of Win7, XAMPP 1.7.4 and maybe I.E. 8.0.7600.16385 seems not so well!

Henri

Alexx

Hi Seth, I've encountered a similar Problem installing CA on my new Server (new Provider). I get a lot "Strict Standards: Declaration of ca_ ..." & "Warning: session_start(): Cannot send ..." after successful installing CA. After successfull CA install I cannot login. URL: https://acms21.com/catest/

I've contacted the provider and they told me, it probably has to do with my .htaccess in my root directory. I attached the Error files and my .htaccess.

Can you detect the problem? Thanks a lot for your help, it is not urgent though. Have a nice weekend, Alex

Alexx

sorry, post can be deleted

seth

So is this resolved?

Alexx

Hi Seth, no it is not, I just accidently added the second post, which cen be ignored/deleted. Thanx for your help! Alex

seth

Try turning off E_STRICT error reporting in your php.ini file. The stock setup.php tries to do this, but it's not always possible to override it without editing php.ini.