I've tried installing the OpenChurch install profile on two servers, one Unix one Windows. On the windows server (Wamp) the profile stops at the Database Config Step - clicking save configuration simply causes the step to reload and no error messages are given. On the Unix Server it hangs halfway through the Module Install bit and I can't access the install system again without clearing caches replacing all the files.

Comments

drupalninja99’s picture

It's probably running out of memory would be my initial guess. I need to test on windows. How much memory does your php install have and can you try raising it?

rlmumford’s picture

Its been raised to 512MB (cos I was chasing another bug in something else.

drupalninja99’s picture

i am looking at another issue that is an error bc ctools needs to be moved up higher in the install profile bc context now bombs since ctools isnt installed. i will notify you once this is ready. i am having to migrate to google code for the project until i can figure out drupal git hosting.

drupalninja99’s picture

Status: Active » Needs review

I fixed an install profile issue with the order of the modules, try downloading a fresh copy: http://openchurchsite.com/download/32/42/openchurch.tar_.gz and let me know if it still fails.

filikin’s picture

Firstly great theme - it went on smoothly on my home site.
Then I tried to install it on the church's site - downloaded your latest version tonight.

The database install seems to stall after installing 44 tables.
I restarted and got the error:
user warning: 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 ') ORDER BY fit DESC LIMIT 0, 1' at line 1 query: SELECT * FROM menu_router WHERE path IN () ORDER BY fit DESC LIMIT 0, 1 in /usr/local/pem/vhosts/139611/webspace/httpdocs/includes/menu.inc on line 315.

the database is mysql 5

How do I get round this?

drupalninja99’s picture

I would make sure you have enough PHP memory, maybe it died in the middle. I will double check the latest install to make sure it works.

drupalninja99’s picture

Just tested the install profile again and it ran smoothly, so you are saying that the install profile stops mid-way and you look at the database and there's only 44 tables? I haven't seen that before.

On another note we will soon have OpenChurch on webenabled.com so that will be another option for installations.

filikin’s picture

what's enough memory? If I run phpinfo, it reports 128M, but the site where the install worked fine it reports only 100M

filikin’s picture

tried again this morning with a fresh database and it went in smoothly - no issues
thanks

drupalninja99’s picture

Status: Needs review » Fixed

changing to fixed

drupalninja99’s picture

Status: Fixed » Closed (fixed)

closing

rlmumford’s picture

Status: Closed (fixed) » Active

Sorry, gonna have to reopen this again - downloaded the 'stable' alpha release today but still bombs at the database config step. Just trying to track down whether it puts any tables in at all. Works fine on my local server.

rlmumford’s picture

I don't get any tables when i hit submit on the database config step. That said, It looks like at some point it made half of them (when I installed a while ago with a different prefix)

drupalninja99’s picture

You're going to need like 256MB of memory to install I'm sure. It's probably bombing out due to memory.

drupalninja99’s picture

Status: Active » Postponed (maintainer needs more info)

Are you still having this issue?

mikegirard’s picture

I am having the same problem. I get to the database configuration page and the page just reloads without an error message after I submit the database details. I am attempting to install this on my Macbook inside MAMP, where I am running PHP 5.3 with a 256MB memory limit.

mikegirard’s picture

I checked the error logs. For some reason, default.settings.php had been renamed default.settings.php(copy) (or something like that) and the install script was unable to locate default.settings.php. Once I renamed the file the installation went beautifully.

Should have check the error logs before posting. Sorry.

drupalninja99’s picture

You need 512MB to be safe

mikegirard’s picture

So far everything is working with considerably less. I'll keep that in mind, though, when I put it into production.

drupalninja99’s picture

Status: Postponed (maintainer needs more info) » Closed (works as designed)

OK closing.