System requirements

By ezpdo4php on March 3rd, 2005
Table of Contents

Check readiness

EZPDO has a simple script to check if your system is ready for EZPDO. After you extract the package, on command line, simply type 

  cd /path/ezpdo/is/extracted/into
  cd scripts
  php check.sh

PHP 5.0.4 or up

EZPDO requires PHP 5.0.4 or up1) with extensions tokenizer, xml, sipmlexml, sqlite, and mysql (optional) enabled. Except mysql (optional), all the extensions are enabled by default in PHP 5.

Set up PHP5 fast

To quickly set up a Web server with PHP5 support, you might want to try XAMPP from www.apachefriends.org.

Notes on libraries

EZPDO has been made a self-contained package. You can now simply download the EZPDO package, unzip and you are good to go! Read on only if you want to use PEAR DB or libraries out of the package.

PEAR DB

The default database library is ADODb. Unless you prefer PEAR DB to ADODb, you do not need to install any PEAR package.

In case you would like to use PEAR DB instead of ADODb, please follow the PEAR installation instructions. For a system with PEAR set up already, this could be as simple as 

  pear install DB

or if DB already installed 

  pear upgrade DB

Make sure you are using version 1.7.2 or up. In config.xml, you need to set option db_lib to peardb. 

  <!-- The database abstraction library you want to use: default to adodb-->
  <!-- Currently available options: adodb, peardb -->
  <db_lib>peardb</db_lib>

ADODb and SimpleTest

The EZPDO distribution comes with ADODb and SimpleTest. The default location is libs/adodb and libs/simpletest under your EZPDO install directory. In case you want to use the libraries installed in different locations, you can define the following constants before including EZPDO runtime API (ezpdo_runtime.php) 

  define('EP_LIBS_ADODB','/path/to/my/adodb/install'); 
  define('EP_LIBS_SIMPLETEST', '/path/to/my/simpletest/install');

Acknowledgement

A special word of gratitude and appreciation is extended to the hardworking authors of the libraries.

1) We may consider providing backward compatibility to PHP4 only if there is a serious need.

21 user comments

  1. Paul H on April 16th, 2005:

    I’d love to use EZPDO for my PHP applications, but so many web hosts are still stuck with PHP4. In fact, both the web hosts I have accounts with are running PHP4 on their servers and I don’t imagine they’ll be upgrading to PHP5 anytime soon. So I’m going to just try getting EZPDO to run in PHP4. Hopefully it won’t be too difficult…

  2. ezpdo4php on April 16th, 2005:

    Paul, we totally agree and thanks for bring this up again. We have also received a few requests for backward compatibility. See http://www.ezpdo.net/bugs/?do=details&id=13 for example. We are thinking about tackling this issue, but serious effort will have to be deferred after the first release scheduled for late this month, which is for php5 only. We’d be happy if you or anyone else could start to investigate and sort out potential issues. Let us know what you find out and feel free to contact us if you need our help. Thanks. -oak

  3. Todd Nine on June 26th, 2005:

    I checked out the latest source from the CVS repository and looked into this. The easy part is creating functions for PHP 4 that are in PHP 5. However, every single class will require the access modifiers removed. This will require either a completely separate branch with parallel development, or special builds. The framework will still work, but this would break all the encapsulation that has been carefully crafted in this framework.

  4. ezpdo4php on June 26th, 2005:

    Todd, thanks for looking into it. We very much felt the same way. The big leap in the object model from PHP4 to 5 is a hugh hurdle to overcome. Although we have not totally given up on pursuing backward compatibility, we have started to look for experts who have more experience than us in porting PHP5 programs to PHP4.

  5. Cherouvim on August 15th, 2005:

    EZPDO rocks! But until my host(s) support php5 I’ll still have to do $row[0], $row[1] and $row[2] .

  6. ezpdorocks on August 15th, 2005:

    i for one would strongly suggest ezpdo not to supprt php4 at all. partly because it is going to be too difficult as it has used so many php5 features. the world of php evolves. quickly imho. people who get used to php5’s wonderful object features may never look back. at least for their new projects. stop supporting php4 is an effort for us all to move forward.

  7. EZPDO » EZPDO 1.0.3 available on August 16th, 2005:

    […] Bug fix (81): EZPDO assumed the tokenizer extension is always in place. Turned out not always true. Now additional checking is added in both epScanner and the readiness checking script (/scripts/check.sh). Thanks to an anonymous user for reporting this issue. […]

  8. RCR on August 27th, 2005:

    check.sh has an error. The signature of is_file_in_inc_dir should take one argument $file. It takes none.

  9. ezpdo4php on August 27th, 2005:

    rcr, thanks for reporting the problem. now fixed and checked in.

  10. TW on September 25th, 2005:

    The is_file_in_inc_dir() issue has not been fixed in the latest stable release.

  11. ezpdo4php on September 25th, 2005:

    it should have been fixed in the latest nightly.

  12. webbles on November 3rd, 2005:

    Just to let you know but it looks like you need MySQL 4.1. I tried to run the test scripts with MySQL 4.0 and I would get SQL errors. Upon upgrading to MySQL 4.1, the errors went away.

  13. Jason. on November 11th, 2005:

    Your check.sh script is broken in 1.0.3, the “stable” release. Should I be concerned about the rest of the library if the check.sh script is broken?

  14. ezpdo4php on November 11th, 2005:

    jason, you might want to try check.sh in the latest release candidate. we merged in some fixes lately. The rest of package should not be affected by the script. -oak

    p.s. could you please tell us what was broken in the script? thanks.

  15. Nick on November 19th, 2005:

    Typo:

    pear upgade DB

    Should be “pear upgrade DB”.

  16. Johan on December 17th, 2005:

    There’s another bug in the 1.0.3 stable check.sh script:

    function is_file_in_inc_dir() {

    should be

    function is_file_in_inc_dir($file) {

  17. Sdav on February 5th, 2006:

    Mysql is not enable by default in php5, actually it is not even in the php package is on pecl now.

  18. Headhunter on March 22nd, 2006:

    Hello, PHP also needs the SPL plugin.

  19. ezpdo4php on March 22nd, 2006:

    The PHP manual seems to say that

    This extension is available and compiled by default in PHP 5.

  20. Minh Nguyen on July 6th, 2006:

    I also agree. There is no need to develop a version for PHP4. People who are on hosts who only support PHP4 should threaten their hosts to leave. If the host still doesn’t comply… they should simply leave. There are too many good hosts out there that support PHP5.

  21. Malachias on July 21st, 2006:

    I don’t think at all that the hosting of PHP5 is a problem for anyone concerned with PHP and in that case you can easily switch - that’s correct. The main issue is that a lot of guys - like me - are working for companies where there’s a huge load of different unconnected PHP(4)-stuff and as long as it’s up and running everyone’s happy.

    But no one who’s sane will ever consider a switch to php5 as long as it doesn’t seem too urgent and the old shit is still in use. I pushed my employer into at least supporting php5 with a special extension and that’s where we are - .php is still php4 but at least I can use php5-code with .php5 … that’s not too bad if you’re really into changing all fucking includes and filenames from bla.php to bla.php5 etc …

Post your comments

XHTML: tags you can use <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>

Couldn't find your convert utility. Check that you have ImageMagick installed.