Definition of a Web-Site
phpGUI Start-Page
How to Use phpGUI
zworks Start-Page



Symbolic Name:

Any mnemonic name. May contain spaces and Umlauts.

FTP-Server-URL:

The internet-name of the site (URL). May be an IP-address or a www-name. The webmaster / provider must have installed a FTP-access.

Login-Name:

Username for the FTP-login.

Login-Pass:

Password for the FTP-login.

Remote Path:

In case the HTML- PHP-files do not reside in the root-directory of the webspace you may specify a subdirectory here.

Local Project-Dir:

The local directory, where all the HTML- /PHP- and other stuff is stored. It is important when uploading a file and is used to determine the target-directory of a file on the remote server.

This determination is done by 'subtracting' the Local Project Dir from the path of the upload-file (from the left side). The remainder of that subtraction is used as target-path relativ to the root of the webspace (which is normally '/'). All directories in the remainder-path are created automatically on the server, if not existent.

The Project-Directory must be organized hierarchically, that means all other directories pertaining to the site must be subdirectories to the Project-Directory as well.

HTTP-Dir:

This depends on how your webspace-provider has organized your webspace. Neccessary only if your webspace-provider gives you different addresses for the webspace and for FTP-access. In other words: If the Document Root of your domain is specified as a subdirectory to your webspace (which is what the FTP sees), then you must specify that subdirectory as HTTP-Dir.

Having the Document Root beneath the FTP-directory makes sense for security purposes: You may store (e.g.) password-files in the FTP-directory, where browsers and other html-based clients have no access to (while your php-scripts do have).

Content-Subdirectory:

If you intend to use the IMaGen-application (Internet-Magazine-Generator) then you must specify a subdirectory (beneath the 'Local Project Dir'), where the 'content' of your magazine shall be stored. If not existent, it will be created automatically.

If you write an article within IMaGen, the article-file is stored in a subdirectory under the content-subdirectory, using a path built from the rubrics in which the article is composed.

Example:
Let your local project directory by 'c:\data\webmag1\'; you write an article as part of the 'Sports'-chapter, in the 'Football'-section and, further detailed, in the 'Young Talents'-subsection. Then your article will be stored in 
 'c:\data\webmag1\Sports\Football\Young Talents\<article-name>.art'
The article-name is built from its time-stamp, with the file extension of 'art'.

Keep in mind, that - different from usual behaviour in phpGUI - the uploaded article will NOT replicate its local path on the server, instead the article will be stored in a MySQL-database (table-name 'Artikel').

Used Languages:

In case your online magazine is written in different laguages then you may specify these languages here. Simpley enter the languages, as a 'word-list': one after the other, separated by spaces (no colons, no dashes. Only one (or more) spaces).

There is no rule how the language be named, the only requirement is sequence: Once you have decided for - lets say - 'english dutch french' you must not change it to 'dutch english french'. Yet you may add another language.

When composing an article, the editor (you) must select the proper language from the list (if you have more than 1 language), because there is no automatic language recognition.

Languages are given numbers internally (IDs), and each article carries its language-ID in its header record.

MySQL-Database Server-URL:
Login-Name:
Password:

Not used at that time.



phpGUI-Startpage How to use phpGUI zworks-Startpage