Could not install addon package?

Previous topic

Install & configuration

Next topic

Author	Message
morten fjellman	Thursday 24 February 2005 5:59:11 am This is the error message I get: <b> The setup wizard was not able to complete the creation of your selected sites. The following errors were detected: * EZSW-051Could not install addon package named contact_us * EZSW-040Failed to initialize site package plain </b> I've tried to delete all the tables in the database as well as the directories in the VAR directory(only those that are made during the install), but the same error message keeps comming up. Any ideas? Fjellman
Łukasz Serwatka	Saturday 26 February 2005 10:01:41 am Your problem is similar to http://ez.no/community/forum/install_configuration/cant_insert_data What other errors did you have during installation? Personal website -> http://serwatka.net Blog (about eZ Publish) -> http://serwatka.net/blog
Rob Rob	Saturday 26 February 2005 3:30:59 pm Do you use version 3.5.1, I had the same problem, but after I switched back to 3.5 it worked fine. Enable debugging to find out which file is responsible for that error.

Author

Message

morten fjellman

Thursday 24 February 2005 5:59:11 am

This is the error message I get:

<b>
The setup wizard was not able to complete the creation of your selected sites.

The following errors were detected:

* EZSW-051Could not install addon package named contact_us
* EZSW-040Failed to initialize site package plain
</b>
I've tried to delete all the tables in the database as well as the directories in the VAR directory(only those that are made during the install), but the same error message keeps comming up.

Any ideas?

Fjellman

Łukasz Serwatka

Saturday 26 February 2005 10:01:41 am

Your problem is similar to
http://ez.no/community/forum/install_configuration/cant_insert_data

What other errors did you have during installation?

Personal website -> http://serwatka.net
Blog (about eZ Publish) -> http://serwatka.net/blog

Rob Rob

Saturday 26 February 2005 3:30:59 pm

Do you use version 3.5.1, I had the same problem, but after I switched back to 3.5 it worked fine.

Enable debugging to find out which file is responsible for that error.