Koozali.org formerly Contribs.org

Wordpress 3.3.1 upgrade

Wordpress 3.3.1 upgrade
« on: February 04, 2012, 09:35:42 PM »
I have added the PHP5 contrib and tried to follow the instructions but I still am getting this message:
Your server is running PHP version 4.3.9 but WordPress 3.3.1 requires at least 5.2.4.

What do I need to do or check?
Thanks

Offline mmccarn

  • *
  • 2,464
Re: Wordpress 3.3.1 upgrade
« Reply #1 on: February 06, 2012, 12:19:26 PM »
In order to use the PHP5 contrib, you also need to add an "addhandler" directive to httpd.conf - either using db commands (for ibays) or using custom templates (for apps): http://wiki.contribs.org/PHP5#Usage

Exactly what you need to do will depend on how you installed Wordpress.


Re: Wordpress 3.3.1 upgrade
« Reply #2 on: February 06, 2012, 12:54:32 PM »
I tried to follow that and did what it said but it is still not working.
Can you perhaps help me troubleshoot the problem.
thanks
Dan

Re: Wordpress 3.3.1 upgrade
« Reply #3 on: February 06, 2012, 07:19:47 PM »
Moved to contribs section of the Forums.
- chris
If it does not work out of the box, please fill in a Bug Report @ Bugzilla (http://bugs.contribs.org)  - check: http://wiki.contribs.org/Bugzilla_Help .  Thanks.

Offline mmccarn

  • *
  • 2,464
Re: Wordpress 3.3.1 upgrade
« Reply #4 on: February 07, 2012, 01:06:37 PM »
I tried to follow that and did what it said but it is still not working.
Can you perhaps help me troubleshoot the problem.
thanks
Dan

1. How did you install wordpress (from the [utl=http://wiki.contribs.org/Wordpress]Wordpress[/url] contrib, into an ibay, using SME Sitemaker, into a folder in Primary)?

2. What template fragments (if any) are already involved in your wordpress installation (this will depend on how you installed wordpress)?

Here is the process I follow when I'm trying to reverse-engineer a situation with a template or db setting affecting a website:

1) Edit /etc/httpd/conf/httpd.conf directly.
-> locate the area that needs to be changed
-> insert the required commands
-> restart the web server using
sv t httpd-e-smith
-> test

If I have broken something, I can "return to the beginning" using:
expand-template /etc/httpd/conf/httpd.conf; sv t httpd-e-smith

If I've fixed the problem, I identify the template fragment that generates the section I need to modify:
cd /etc/e-smith/templates/etc/httpd/conf/httpd.conf
grep -ril <some text near my change> *


I then examine the files listed to see if my change can be made using a db variable, or if I need a custom template fragment.

If nothing is returned, repeat the search in /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf.

If the edit you need to make is not affected by a db variable, you'll need to create a custom template fragment:
mkdir -p /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf
cd /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf
cp /etc/e-smith/templates/etc/httpd/conf/httpd.conf/<TheFileINeedToCustomize> .

(note the trailing space and dot at the end of the last line).

Now I can edit the "custom" template fragment I've created, and its contents will be used instead of the default template fragment I started from when the affected file (/etc/httpd/conf/httpd.conf) is generated using 'expand-template'.

After making my changes:
expand-template /etc/httpd/conf/httpd.conf; sv t httpd-e-smith

If my changes have broken something:
cd /etc/e-smith/templates-custom/etc/httpd/conf/httpd.conf
rm <TheFileINeedToCustomize>
expand-template /etc/httpd/conf/httpd.conf; sv t httpd-e-smith


If your wordpress is in an ibay the above process gets a bit trickier...


Offline mmccarn

  • *
  • 2,464
Re: Wordpress 3.3.1 upgrade
« Reply #5 on: February 07, 2012, 01:21:53 PM »
It's also useful to create a file to show you your PHP version information:
cd /path/to/wordpress
echo '<?php phpinfo(); ?>
' > pi.php


Now if you browse to http://wordpress.url/pi.php you should get a long listing of detailed information about the specific PHP that is invoked when running php from your wordpress folder.

I don't know if having phpinfo() sitting around is a security risk; remove the file when you're done troubleshooting.

Re: Wordpress 3.3.1 upgrade
« Reply #6 on: February 12, 2012, 03:49:25 PM »
fixed my problem.
Stupid me named the directory and file incorrectly.
Once named correctly all working fine.
Thanks for all the help.

Offline mmccarn

  • *
  • 2,464
Re: Wordpress 3.3.1 upgrade
« Reply #7 on: February 13, 2012, 01:11:49 PM »
...named the directory and file incorrectly.

I hate that!