ProsePoint Express: hosted newspaper website content management software

Error at step 6.4 - Just when it's starting to get good

9 replies [Last post]
tdkolton
User offline. Last seen 2 years 45 weeks ago. Offline
Joined: 14/03/2009
Posts:

After carefully following the installation instructions, I went to step 6.4 to display the initial administration page.  I received the following errors, all seemingly related to themes:


Warning: array_keys() [function.array-keys]: The first argument should be an array in /home/tdkolton/public_html/aboutTown/includes/theme.maintenance.inc on line 227

Warning: Invalid argument supplied for foreach() in /home/tdkolton/public_html/aboutTown/includes/theme.maintenance.inc on line 227

Fatal error: Call to undefined function phptemplate_get_ie_styles() in /home/tdkolton/public_html/aboutTown/themes/garland/maintenance-page.tpl.php on line 23

I tried reinstalling.  No dice.  Any idea?

 

Paul Gillingwater
Paul Gillingwater's picture
User offline. Last seen 1 year 14 weeks ago. Offline
Joined: 05/03/2009
Posts:
Which version of PHP are you using?
What is your environment? Can you try this with XAMPP? See if it reproduces the problem.
__________________

Follow me on http://www.twitter.com/ahbleza

tdkolton
User offline. Last seen 2 years 45 weeks ago. Offline
Joined: 14/03/2009
Posts:
I am running it on a hosted

I am running it on a hosted shared Linux server.  Therefore, I cannot get to the root directory and am somewhat limited with what I can do by the Cpanel interface.  However, I was able to install Drupal 6.10 on another directory with no problem.

The PHP is set to: system default.  When I select PHP4, I get this error.  When I set it to PHP5, I initially received a different error, including a 500 Server error, but now it is the same error as PHP4.  I've reset my selection to "system default."

 

Paul Gillingwater
Paul Gillingwater's picture
User offline. Last seen 1 year 14 weeks ago. Offline
Joined: 05/03/2009
Posts:
PHP 5.2
The system won't work with PHP4. It definitely needs PHP5.2 or later, as per here: http://www.prosepoint.org/docs/php-requirements.html It may be that the cpanel is not switching your environment correctly to PHP5. Can you print out the PHP version you have, e.g., run something like this: < ? phpinfo(); ? > then post the results.
__________________

Follow me on http://www.twitter.com/ahbleza

tdkolton
User offline. Last seen 2 years 45 weeks ago. Offline
Joined: 14/03/2009
Posts:
I've changed the default to

I've changed the default to PHP5.  I can't tell which version it's running, but I have to assume it is a more recent version (my host is HostGator, and they're pretty good at keeping things up-to-date.

I'm not too knowledgeable about the apache handler, but my system says the following:

Handler Extension(s) System Apache Handlers cgi-script .cgi .pl .plx .ppl .perl server-parsed .shtml

There is nothing here about PHP.  Is that part of the problem?

I'm also curious why I am receiving a fatal error "Call to undefined function phptemplate_get_ie_styles()"

beng
User offline. Last seen 6 days 16 hours ago. Offline
Joined: 27/02/2009
Posts:
Please verify PHP 5.x

Hi,

Please confirm absolutely that your account is running PHP 5.x.

To do this, create a file info.php in your web space with the following line:

<?php phpinfo(); ?>

and then visit it from your web browser. There should be a version number in the resulting page output.

Once you can confirm it's PHP 5.x, if there are still issues, please let us know.

tdkolton
User offline. Last seen 2 years 45 weeks ago. Offline
Joined: 14/03/2009
Posts:
I cannot explainto you why
but I reinstalled the system for a third time and it is now working.  I'm confused, but happy, and grateful to those who tried to help.
rafialikhan
rafialikhan's picture
User offline. Last seen 2 years 31 weeks ago. Offline
Joined: 29/06/2009
Posts:
Takes a while to setup Prosepoint

My system requirements add up to what prosepoint needs to run and i already run several drupal 6.1x base application on it. Php 5 and XAMPP  Vista machine with 4 GB memory - all good

Im installing ProsePoint 0.22 directly - fresh install
When i try to install PP, I kept getting the timed out error while trying to install the profile every time and max_execution_time is already set at 360 sec. Since the document on priosepoint maybe a bit out dated i couldnt see any helpful troubleshooting tips. Then i change the max_execution_time to 1200 and then i finally managed to get the DB Configuration page. Its been a good 10 mins since i entered my details and waiting for it to come back with the next screen, i hope and pray that it does come back and may just be my system hogging my ram somewhere and not the typical installation time that prosepoint takes.

Your setup is something that a lot of people would love to have and build on top of, and in the era of video tutorials, it would be great if you have a 10 mins video tutorial on installation (installation being the number one pain point and requests to solve on the forum as well)

rafialikhan
rafialikhan's picture
User offline. Last seen 2 years 31 weeks ago. Offline
Joined: 29/06/2009
Posts:
Got everything installed - but apache crashes

Finally got prosepoint setup all the way till the last step. Unfortunately, the system crashes apache everytime i try to run the home page of my new setup site. I chose minimal option and not the demo option.

Installations and trouble shooting shouldnt be this painful.

beng
User offline. Last seen 6 days 16 hours ago. Offline
Joined: 27/02/2009
Posts:
...

Hi,

On some Windows platforms, max_execution_time has to be set to about 10 minutes. There is a part of PHP which is much slower on Windows (but I don't know why and it's outside my control).

When you say it 'crashes' apache, what symptoms do you see? Any error messages?

Also, during installation, did you see any warning or error messages?

You might want to reinstall from scratch, but with max_execution_time at about 10 mins (more is okay) from the very beginning.

If you have already done a two stage installation because max_execution_time was too short initially, you may have a corrupted database.