Updated by lillenon Friday, October 14th 2005.
EZ publish is an Open Source Enterprise Content Management System and development framework. With advanced functionality for content management (CMS), e-commerce, intranets and much more, you can build your dynamic internet solutions fast and reliable. It has the flexibility for making about any web solution with general libraries and functionality, but still it is a ready CMS and e-commerce solution you can set up without any php programming knowledge. eZ publish is dual licenced between GPL and the eZ publish professional licence, which means you can use it for free under GPL for your website or you can build commercial software with the professional licence. eZ publish is build after the eZ software philosophy: Open software that has an open and dynamic architecture, and follow general open standards. Usability for the target user is a top priority and the software is developed following strict academic processes ensuring a high quality and ease of use.
Licence : GPL Version : 3.7 [Stable]
Platforms : Linux, Windows, FreeBSD etc
Requirements : PHP, Apache, MySQL
Download [ 3.7 ] : http://ez.no/ez_publish/download
PHP4 - Server-side, cross-platform, HTML embedded scripting language.Updated by FastRunneron Monday, October 31st 2005.
PHP is a server-side, cross-platform, HTML embedded scripting language. It is a tool that lets you create dynamic web pages. PHP-enabled web pages are treated just like regular HTML pages and you can create and edit them the same way you normally create regular HTML pages.
Licence : GPL
Version : 4.4.1 [Stable]
Download [ 4.4.1 ] : http://www.php.net/downloads.php
Apache Server - Number One HTTP Server.Updated by FastRunneron Friday, October 14th 2005.
Apache has been the most popular web server on the Internet since April of 1996. The Apache project is an effort to develop and maintain an open-source HTTP server for various modern desktop and server operating systems, such as UNIX and Windows NT. The goal of this project is to provide a secure, efficient and extensible server which provides HTTP services in sync with the current HTTP standards.
Licence : BSD type
Version : 2.0.55 [Stable]
Download [ 2.0.55 ] : http://httpd.apache.org/download.cgi
MySQL - SQL (Structured Query Language) database server.Updated by FastRunneron Tuesday, November 22nd 2005.
The MySQL database server is the world's most popular open source database. Its architecture makes it extremely fast and easy to customize. Extensive reuse of code within the software and a minimalistic approach to producing functionally-rich features has resulted in a database management system unmatched in speed, compactness, stability and ease of deployment. The unique separation of the core server from the storage engine makes it possible to run with strict transaction control or with ultra-fast transactionless disk access, whichever is most appropriate for the situation.
Licence : GPL
Version : 4.0.26 [Stable] 5.0.16 [Development]
Download [ 4.0.26 ] : http://dev.mysql.com/downloads/mysql/4.0.html
More info...
1. www.icewalkers.com
2. www.opensourcecms.com
Thursday, December 22, 2005
Troubleshooting the Dreamweaver MX MySQL Connection
In the guide we look at how to troubleshoot the Dreamweaver MX MySQL Connection. Before we look at troubleshooting the connection, we`ll first look at how the Connection actually works.
How the Dreamweaver MX MySQL Connection Works
To connect to a MySQL database, Dreamweaver MX uploads a hidden file to your server. This code runs on the server, and gets the information about your MySQL database.
Because this code is actually run on your server, rather than your local PC, it will work even if your MySQL server (or hosts) is setup to disallow outside connections.
Once the hidden file has collected information about the MySQL Database Structure and the info it contains, it relays back to Dreamweaver MX. This is why Dreamweaver MX connects to the server when you use the DMX recordset creator for example.
What can go Wrong ?
There are usually only two things that normaly go wrong:
1) Dreamweaver MX uploads its hidden files to the root directory of your web site. If the permissions are set up incorrectly on this directory, then Dreamweaver MX won`t be able to upload the hidden file it uses to connect to the database.
2) Dreamweaver MX can upload the hidden file it needs to connect to the database, but when it goes to read back from the file, it looks in the wrong place on the server.
We`ll now look at how to fix these two problems.
Problem 1 - Dreamweaver MX can`t upload its hidden file
This can be diagnosed by looking at the FTP Log in Dreamweaver MX. To view the FTP Log, you need to open the Results panel, and then select the tab labeledFTP Log.
This log lists all the FTP operations that occur, including the Dreamweaver MX hidden files to connect to the database. If Dreamweaver MX cannot write the files it needs it will tell you here. You then need to change the permissions on your web directory to allow the user who`s FTP details you entered in the Site Definition can upload.
Problem 2 - Dreamweaver MX can upload its hidden file, but can`t read it back
This again can sometimes be diagnosed from the Dreamweaver MX FTP Log, as mentioned for Problem 1. You also need to edit your site definition and check the paths in the Sections shown below:
Local Info Section
Edit the Site Definition for your site, click on the Advanced Tab, and select Local Info from the Category Menu.
Check the path for the HTTP Address. This should be the web path to the root of your web site for example:
http://www.dreamweavermxsupport.com/
Next, you need to check the Testing Server section, which is shown below:
Testing Server Section
First, you need to check that Server Model is set to PHP MySQL.
Next, check the address for the FTP Host is correct.
The next setting, Host Directory, is very important, and is the server path to the root of the web site on the server. For example, on some servers when you log in you are placed in your user directory. In this example to get to the root of the website, we use the server path /web/. If when you log in, you are placed straight in the root of the web directory, then you can leave this box empty.
Next, check your login and password details are correct, and that the user has permission to write to the root of the web site.
Lastly, check the URL Prefix. Again this should be the Web Path to the root of your web site eg
http://www.dreamweavermxsupport.com/
If you entered a path in the Host Directory, this can be appended to the end of the URL Prefix by Dreamweaver MX. This is incorrect, and if it has done this, you need to change it so it points to the root of your web site again.
Check the Dreamweaver MX Database Connection
Open your Dreamweaver MX Database Connection, by clicking the yellow cylinder next to the Database connection name on the Databases tab which is in the Application Panel.
Database Connection Dialog Box
For the MySQL Server, remember that Dreamweaver MX communicates with the Database through a hidden file on the server. This means that for the MySQL server you need to enter localhost rather than the web address of the server, as that`s the context the hidden code is run under.
Finally, Check the User Name and Password are correct, and valid to connect to the MySQL server as a local user. Also check the Database name is correct.
Click the Test button, and your connection should be successful.
Error 401 - Authorisation Error
Another error you may get is a 401 - Authorisation Error, which occurs if your web site is password protected, using an .htaccess file. This means that when Dreamweaver MX uploads its hidden files to get the database information and then tries to read it back, it can`t, because it can`t supply the password so is denied access to the files.
This only occurs if your main website directory is protected, and so by default, every directory underneath is also protected.
This problem is easy to solve. Create a plain text file called .htaccess. Add the following:
satisfy any
allow from all
Save the file, and then upload it into the hidden directory _mmServerScripts which is in the web root directory of your website. This file turns off protection for this directory only, allowing Dreamweaver MX to read the files correctly and will allow you to connect to the database.
PHP download Museum
If you are looking for older php versions that maybe compatible with older versions for Dreamweaver MX or the EZ Publish use this link:
Here is the Museum of PHP Dowloads
url: http://ftp.emini.dk/pub/php/museum/win32/
NOTE:
1. eZ publish 3.6.x and lower do not run on PHP 4.4. eZ publish versions 3.7.x and newer will run only on PHP 4.4. see this link: http://ez.no/download
2. Neither Dreamweaver MX nor Dreamweaver MX 2004 are compatible with PHP version 4.1.0 due to a bug in mysql_pconnect(). With Dreamweaver MX, you can use PHP 4.0.6 and earlier, or PHP 4.1.1 and later. With Dreamweaver MX 2004, you can use PHP 4.1.1 and higher, 4.2.x and 4.3.x, running on Apache 1.3. Dreamweaver MX 2004 does not support PHP 4.0.6 and earlier because this version of Dreamweaver has updated the variable syntax to the PHP 4.1 standards ($_GET vs. $HTTP_GET_VARS). Please refer to Application server and web server test pages (TechNote tn_16399) to learn how to check your version of PHP using the phpinfo() function. see this link: http://www.macromedia.com/cfusion/knowledgebase/index.cfm?id=tn_16515
Here is the Museum of PHP Dowloads
url: http://ftp.emini.dk/pub/php/museum/win32/
Log-on Links
1. InterAkt (Dyanmic Extensions for DWMX) http://www.interaktonline.com
2. DMX Zone http://www.dmxzone.com
3.
2. DMX Zone http://www.dmxzone.com
3.
Configuring Apache 2 and PHP 4 for Windows
url reference: http://www.dmxzone.com/ShowDetail.asp?NewsId=6452
This tutorial is designed to help you set up a server environment for using PHP with Dreamweaver on a Windows platform. The tutorial recommends using the Apache Web Server, Windows Installer Version, and zipped source code for PHP.
(March 25, 2004)
Properties
| |||||||||||||||
Configuring Apache and PHP for Windows
I use the Apache web server for my PHP web development, even though I develop on Windows using Dreamweaver. I use Apache for a number of reasons.
- I also do ASP development, and find it easier to reserve IIS for ASP alone.
- Apache is easier to configure to work with PHP.
A number of books I have read give different advice on how to configure these systems. All I can do is show you which method works best for me.
Installing Apache
I use the Microsoft Windows Installer version of Apache. Visit the Apache Web Site at www.apache.org. Follow the links to the download page. The current MSI file is
apache_2.0.49-win32-x86-no_ssl.msi
If you intend to continue to use IIS, as I do, you will need to stop IIS before proceeding with the installation. After stopping IIS, locate the msi file and double-click on it. Since you are only using a development server, you can just insert dummy data at every occasion that Apache asks.
I recommend accepting the All Users, Port 80 option. If we want to use another port, we can set this up later, in the configuration file.
For development purposes, Typical installation should be satisfactory.
If you wish to install to a different folder, now is your opportunity.
Finally, you are asked to click install. You can now find Apache , as a Windows service, in the Control Panel, under Administrative Tools > Services.
Configuring Apache will be analogous, whatever platform you are on. These instructions will be for a Windows environment. The only changes you will need will be to account for the different way file paths are described on Linux, Mac and Windows.
On all platforms, Apache is configured by a file called httpd.conf. Open this file up in a text editor. (I often need multiple text files, so I use NoteTab in preference to NotePad. NoteTab is free, and is available from www.notetab.com. On Linux (I’m using Mandrake 9.1); I use Quanta, which also permits multiple files open.).
Find the line referring to Listen.
Listen 80
If you are running 2 web servers, change this line to
Listen 8080
If left at 80, you will access the web server at http://localhost. Otherwise, it will be at http://localhost:8080.
Whenever you make a change to this httpd.conf file, you must restart Apache , for it to recognise the changes.
Find the document root statement.
DocumentRoot "C:/Program Files/Apache Group/Apache2/htdocs"
Check it describes the actual position of the web server root. Unix type document roots do not need to be in quotes, but Windows paths work better in quotes. Don’t ask me why! Notice also that the Windows backslashes are rendered as forward slashes.
As with IIS , you could simply place your sites as subfolders of the web root. Thus, C:\Program Files\Apache Group\Apache2\htdocs\mysite would be served as http://localhost/mysite.
As with IIS , it is usually more convenient to have the folders elsewhere. In Apache , this is referred to as an alias.
Search httpd.conf for the word alias. You will see a couple of aliases set by default. The script gives other examples, in the commented lines (any line beginning # is a comment line, and ignored at execution).
Here is a typical alias off my machine.
# permission for malinbooks folder
Alias /malinbooks "C:/webs/malinbooks"
Options Indexes MultiViews
AllowOverride None
Order allow,deny
Allow from all
I have added a comment for each alias to make it easy to find. The Alias command defines the nature of the alias. This is saying that C:\webs\malinbooks will be served as http://localhost/malinbooks. The information in the Directory tags sets the permissions.
We can enter
# permission for phpbattybooks folder
Alias /phpbattybooks "C:/webs/phpbattybooks"
Options Indexes MultiViews
AllowOverride None
Order allow,deny
Allow from all
As usual, after any changes, save httpd.conf, and restart Apache .
Installing PHP
I have attempted this, in a number of ways, and have become convinced that it is easiest to download the whole package zipped, rather than use the Windows Installer.
PHP is obtained from www.php.net, where you will find detailed instructions on installation, which is not difficult.
Under Windows, follow these instructions.
- Stop Apache
- Download zip file, rather than win installer. Php-4.3.1-Win32.zip
- Extract contents to C:\php
- Copy php.ini-dist to your Windows directory – Windows in XP, WINNT in 2000. Rename it as php.ini
- Copy php4ts.dll from C:\php to C:\Windows\System32
- Edit php.ini in a text editor, as shown in the next few lines
- Find the line extension_dir = ./
- Amend to extension_dir = "C:\php"
- Find line doc_root = ./
- Amend line to doc_root = "C:\Program Files\Apache Group\Apache2\htdocs"
- Find line session.save_path = ./tmp
- Amend line to session.save_path = "C:\tmp"
- Make sure that the folder "C:\tmp" exists, or use another folder in the php.ini file.
- Save and close php.ini
- Open httpd.conf in text editor
- Look for lines beginning LoadModule
- Add these lines
LoadModule php4_module “C:/php/sapi/php4apache2.dll”
AddType application/x-httpd-php .php
- Save file
- Start Apache
The next job is to test that php is working. Create a file in a text editor, or Dreamweaver. Fill it with this code:
phpinfo();
?>
Save the file into the root of the Apache web server, as phpinfo.php. Call the file up in your browser, e.g. as http://localhost:8080/phpinfo.php When you do this, you should see a page of information about PHP. This will show that your installation is working. If you do not get such a page, check all the steps above very carefully.
You should now have a good working development server on your Windows machine.
Happy Developing,
Paul Taylor
Running MySQL as a Service Under Windows NT
Paul DuBois
paul@kitebird.com
Document revision: 1.01
Last update: 2003-01-23
Introduction
When you maintain a MySQL installation, normally you want the MySQL server to run all the time. You can start the server by invoking it yourself, but if the machine restarts, MySQL availability is interrupted until you remember to start the server again. Under operating systems that allow you to modify the system startup procedure, you can include a step that launches your MySQL server. That way, the server runs without intervention on your part even in the event of an unattended machine restart. You can achieve this under Windows NT by installing MySQL as a service that is set to run automatically. NT's service management facilities also allow you to control the service manually if necessary--for example, to stop the service to perform administrative tasks with the server down, then start it again afterward.
The discussion in this article uses "Windows NT" as a generic term that also applies to other NT-based systems, such as Windows 2000 and XP. It does not apply to versions of Windows that do not support services, such as Windows 95, 98, or Me.
If MySQL is not already installed on your system, you can download it from the MySQL AB web site:
http://www.mysql.com/Some of the commands described below require you to invoke a server from the command line (the DOS prompt in a console window). The servers are found in the bin directory of your MySQL installation. (By default, the MySQL installation procedure places MySQL in the C:\mysql directory, but you can choose another location if you like.) The following instructions make little assumption about the installation location, other than that the bin directory of your MySQL installation is named in your PATH variable setting. If your PATH variable isn't set to include this directory, you'll need to invoke a MySQL server either by changing directory into the bin directory first or by specifying the server's full pathname, such as C:\mysql\bin\mysqld-nt for the mysqld-nt server.
Installing MySQL as a Service
To install a MySQL server as a service under Windows NT, invoke it with the --install option from the command line. For example, to install mysqld-nt this way, use the following commands:
C:\> mysqld-nt --installThe first command installs the server and sets it to run at the next system restart and each restart thereafter. However, it does not cause the service to start immediately. The NET START command accomplishes that without a machine restart. The argument to NET START is the service name, which is "MySql" no matter which of the MySQL servers you install. (The service name is not case sensitive, so you can specify it in any lettercase.)
C:\> NET START MySql
When you install a MySQL server as a service from the command line, normally only the --install option is used. You cannot specify runtime options on the commmand line because you don't invoke the server directly from the DOS prompt. To specify options that the server should use each time it runs thereafter, you must place them in an option file instead. Suppose you want the server to start as though you'd given the --flush and --log=query-log options on the command line. To achieve the same effect using an option file, add the options, one per line, to the [mysqld] group in the file:
[mysqld]When it starts up, the server looks for option files in several locations. The two most common are the my.ini file in the Windows system directory, and C:\my.cnf. You can put the startup options in either file (creating it as a plain text file if it doesn't exist). There are several example option files that you can look at in the top-level directory of your MySQL installation.
flush
log=query-log
Controlling the MySQL Service
A MySQL server that has been installed as an automatic service is run by NT's service management facilities each time the machine starts up. Those facilities also allow you to start or stop the server manually or to check its status. These operations are available both at the command line and through the graphical interface provided by the Services Manager.
Controlling the Service From the Command Line
To start or stop the MySQL service from the command line, use these commands:
C:\> NET START MySqlTo check the server's current status, use the following command. If the server is running, the service name "MySql" will appear in the list of services displayed by the command:
C:\> NET STOP MySql
C:\> NET STARTAnother way to stop the server that does not involve NT's service management commands is to use mysqladmin:
C:\> mysqladmin -p -u root shutdown
Controlling the Service Using the Services Manager
To control the server using a graphical interface, launch the Services Manager. You can find this as the Services item in the Control Panel or in the Administrative Tools item in the Control Panel. The Services Manager displays information like that shown in Figure 1. (Your particular version may have a somewhat different appearance.)
Figure 1. The Services Manager
The MySQL service line will contain the word Started if the server is running, and also includes the service startup mode. The mode is either Automatic (service runs automatically as part of the system startup procedure), Manual (service is started manually), or Disabled (service does not run at all).
To control the MySQL service, select the MySQL line from the service list on the left side of the Services window, then click the appropriate button:
- To stop a running service, select the MySQL line and click the Stop button.
- To start the service, select the line and click the Start button.
If you perform service operations from the command line while the Services Manager is running, it will not notice the effect of those operations. For example, if you install or remove the MySQL service by invoking a server with the --install or --remove options, Services Manager doesn't update its service list. Similarly, if you run commands such as NET START or NET STOP at the DOS prompt, Services Manager doesn't notice changes to the service status. To avoid confusion, close Services Manager before performing service operations from the command line, then reopen it. That way, information that the Services Manager displays will be up-to-date.
Removing the MySQL Service
If you decide you no longer want to run MySQL as a service, remove it by invoking the server with the --remove option. However, before you do this, you should stop the server if it's currently running. For example, if you installed mysqld-nt, stop it and remove it like this:
C:\> NET STOP MySqlYou should also remove the service if you want to switch servers, because you can't install a second server as a service without first removing the existing one. Suppose you're using mysqld-nt and want to switch to mysqld-max-nt, which includes support for additional features. Run the following commands to stop and remove the service, install the new server, and restart the service:
C:\> mysqld-nt --remove
C:\> NET STOP MySqlThe preceding instructions actually are a bit overspecific. It doesn't really matter which server you use to remove the service. You can invoke any of them with the --remove option, no matter which server is installed. For example, if you have installed mysqld-nt, you can remove it using mysqld.
C:\> mysqld-nt --remove
C:\> mysqld-max-nt --install
C:\> NET START MySql
Acknowledgment
The original version of this article was written for NuSphere Corporation. The current version is an updated revision of the original.
Reference url: http://www.kitebird.com/articles/nt-serv.html
Subscribe to:
Posts (Atom)