Log in
Forgot your password?
The Dublin Core metadata element set
is a standard for cross-domain information resource description.
|
||
| Element | Description | Value |
|---|---|---|
| Identifier | resource ID | http://old.zope.org/Members/hewei/PHParser |
| Title | resource name | PHParser/PHPGateway |
| Description | resource summary | Bridging the gap between Zope and PHP world! PHParser/PHPGateway aims to combine Zope and PHP together. It provides you a possibility to run PHP scripts under Zope and Plone. PHParser is a DTML-Document-like object. Its content when being published is first rendered by the DTML engine and then passed to PHP CGI. The result from PHP CGI will be finally displayed. PHPGateway is a Folder-like object. When its 'docroot' property is pointed to a real directory in the file system, the entire directory can be published by Zope, even as a virtual host. Especially, the .php files under that directory will be directly passed to PHP CGI without DTML rendering. For example, you can now make "phpMyAdmin":http://sourceforge.net/projects/phpmyadmin installed in the file system run on Zope only by adding just one PHPGateway object. **Major Enhancements:** * Using environment to interface to PHP. That will make it almost no difference than a PHP running under Apache in CGI mode. All GET and POST parameters will be correctly parsed and stored in appropreate variables regardless of how *register_globals*, *variables_order*, *magic_quotes_gpc* and any other directives are set in php.ini. * Cookies and sessions are supposed to work. * File uploading is also supported! * Passing REQUEST.other to PHP as a global variable $ZOPE_VARS. * The PHP script can use 'header()' function to modify the header information. * HTTP authentication is now working. **Known Limitations:** * Some user modifiable options are hard coded in source files. I'm looking for a better way for users to easily change these options without touching the source. * As PHP's include/require functions search scripts in the file system, those PHP scripts that use these functions may not work automatically in PHParser. Either refer to this "How-To":http:howto-include to modify your PHP scripts, or put all your scripts in a directory in the file system and use PHPGateway to run them. * Besides the $ZOPE_VARS passed, there isn't any easy way to access Zope objects within the PHP script being parsed. One possible way is to use XML-RPC, which is still under initial testing. * A complete change log can be found "here":http://www.zope.org/Members/hewei/PHParser/changes. * PHParser/PHPGateway basically work with Plone. But has not been thoroughly tested. **Untested Functionalities:** * Sessions. **Known Incompatibilities:** * Some server and environment variables might be different from older versions. Please be careful if your scripts depend on PHP_SELF, DOCUMENT_ROOT, SCRIPT_NAME, SCRIPT_FILENAME, REQUEST_URI, PATH_TRANSLATED or PATH_INFO. **Thanks to these Zope Products:** * The original "PHParser":/Members/mjablonski/PHParser by Maik Jablonski * "Zope File System":/Members/andym/ZFS * "ZShellScript":/Members/jerome_alet/ZShellScripts by Jérôme Alet * "PathHandler":/Members/NIP/PathHandler by NIP * "ZCGI":/Members/haqa/ZCGI by Haqa * "ExternalFile":/Members/arielpartners/ExternalFile by Ariel Partners LLC **Thanks to these Articles:** * "Http client to POST using multipart/form-data":http://aspn.activestate.com/ASPN/Cookbook/Python/Recipe/146306 by Wade Leftwich * "The CGI Specification":http://hoohoo.ncsa.uiuc.edu/cgi/interface.html **Resources:** * **Mailing List:** A PHParser mailing list is also available for me to announce new releases, for users to report bugs and for everyone that is interested in PHParser to exchange experiences and ideas. "Join":mailto:[email protected] the list. |
| Creator | resource creator | hewei |
| Date | default date | 2005-10-12 15:00:06 |
| Format | resource format | text/html |
| Type | resource type | Software Package |
| Subject | resource keywords | External Access |
| Contributors | resource collaborators | |
| Language | resource language | |
| Publisher | resource publisher | No publisher |
| Rights | resource copyright | |
|
||
| Element | Description | Value |
| CreationDate | date resource created | 2002-11-05 11:03:11 |
| ModificationDate | date resource last modified | 2005-10-12 15:00:06 |
| EffectiveDate | date resource becomes effective | 2005-10-12 15:00:06 |
| ExpirationDate | date resource expires | None |
Backlinks:
via
Google
/
Technorati
RDF:
view RDF data