allow (write, delete) user = owner;
Note
Do not create a user with the username of owner
.
Ownership of web publishing documents can be assigned either through the Web Publishing|Index and Update Properties form or through Web Publisher. The Index and Update Properties form allows you to do a bulk assignment of ownership to a set of documents and Web Publisher performs individual assignments of file ownership to a user when the user publishes or uploads the file.
Only the owner can modify the access control (ACL) rules for a file. These rules define the actions users can perform on the file, such as moving, copying, renaming, or deleting it. An owner can reassign ownership of a file to another user, and if a file has no owner, anyone with a valid username can identify themselves as its owner. Because the username identified as the owner of a file can change, any access control that you place on a file should target the owner of a file rather than a specific username.
If the default access control (ACL) that governs your server is not restrictive or flexible enough for your web publishing needs, you can use the Server Preferences|Restrict Access function to create an ACL that is more appropriate for web publishing.
For example, you could create an ACL like this:
acl "uri=/publisher/";This ACL sets a restriction such that only the owner of a file within the additional document directory of
allow (read, execute, list, info) user = anyone;
allow (write, delete) user = owner;
/publisher
can modify or delete the file.
See Chapter 6, "Controlling access to your server" for more information about setting access control.
Note
If you expect web publishing users to publish documents to a directory, you
need to set the Unix file permissions to give them write access to that directory.
You should also disable write permissions for directories you do not want them
to publish to.
Indexing and updating properties
Before users can perform a search across a set of documents and directories, information about the documents and directories needs to be indexed into the web publishing database. The web publishing database is stored as a search collection and is created as part of the server installation process. Initially it contains no data and must be populated by indexing the documents in the document directories.
The Web Publisher window lists the files and folders that are in the document directory selected when a user starts up Web Publisher, but the data initially is not indexed (and therefore is not available for searching) and the files have no owners (so anyone can define their username as the owner of a file, and thereby be able to set the access control for a file).
You can use the Index and Update Properties form to perform bulk indexing of documents to create searchable web publishing data and you can also use it to do a bulk assignment of owner for the files included in the collection. You can restrict or expand the scope of documents and directories to be indexed, and you can index just the file properties, called metadata, or you can also index the documents' contents. If you choose to index the contents of the files, you can search on any word in the documents although publishing and uploading files with Web Publisher may be slightly slower.
*.html
to only index the content in documents with the .html
extension, or you could use this pattern (complete with parentheses) to index all HTML documents:
(*.htm|*.html)
You can define multiple wildcards in an expression. See Chapter 3,
"Managing your server" for details of the syntax for wildcard patterns.
A summary of the indexing operation is displayed in the web browser window. The information is also logged to a local log file.
Note
Once you have indexed documents into the web publishing collection, you
should not change any document directory's URL mapping or the collection's
entries will target the URL mapping to the wrong physical file location. If you
have to change a document directory, you need to reindex the documents in
the new location. You can use the Repair function to remove the indexed data
from the old directory mapping.
Changing the web publishing state
You can deactivate web publishing and you can turn it back on. If you turn off web publishing, you also turn off link management. Documents that are subsequently moved or renamed may have incorrect links, and the link status database may not be up to date. The solution is to use the Web Publishing|Link Management function to manually turn link management off and then turn it back on again. This starts the link management function up again with an empty link status database. See "Changing the link management state" for more details of link management.
Note
If you turn web publishing off, all agents for the server are also turned off and
clients cannot use Netscape Web Publisher to access agent services. When web
publishing is turned back on, agents that were turned off solely because web
publishing was turned off are turned back on. Agents that were disabled for
other reasons are still disabled.
To change the web publishing state:
Setting the web publishing language
You can change the web publishing language to any language supported by the user's installation, and these are listed for the server administrator in a drop-down list on the form.
Note
Be cautious when using this function. If you change the language of a
collection, the system deletes all the existing data in the collection.
Your changes are reflected in the language.conf
file, which is located in the server_root/plugins/search/admin
directory.
After you change the web publishing language, your server is automatically restarted to apply the change.
Maintaining web publishing data
Web Publisher maintains multiple sets of data about the documents that are in the web publishing collection. When all web publishing data is synchronized, each file in the chosen document directory has a record in the web publishing collection and every property record in the collection has a corresponding file in the document directory.
Although you can limit the scope of the Repair and Report functions to checking only the files in a particular document directory for collection records, every property record in the collection is checked for a corresponding source document regardless of which directory the file might be in.
Occasionally, these can become out of synch. You can obtain a report on the state of your web publishing files, and then repair one or more directories as needed. For example, if a document that was indexed into a collection is deleted, there is a record in the collection that no longer has any corresponding source document. Repairing removes the collection records for any such document.
You can perform these functions to maintain your web publishing data:
Changing the link management state
At times, you may not need automatic link checking and updating. At these times, you can turn link management off to conserve resources and to improve searching and indexing performance. When you turn link management off, Web Publisher stops doing automatic link checking and you cannot use the Check Links function from the Web Publisher Services page.
You can also use this form to selectively turn the automatic link update feature on and off. When automatic link updating is on, Web Publisher changes the outgoing and incoming links in a file to keep them up to date as files are moved and renamed in Web Publisher. Because this revises the modification date for any file that has updated links, this feature is off by default.
Note
The automatic link update feature only affects links outgoing to or incoming
from moved or renamed files. It does not affect HTML files that are being
uploaded or published. Provided that link management is on, the links in these
files are always updated as part of the upload or publish operation.
For further information about link management in Web Publisher, access the online Web Publisher User's Guide through the Help menu command in Web Publisher or the Help button on the search interface, the Agent Services page, or the Web Publisher Services page.
Setting the version control archive
Netscape Web Publisher includes a version control system for keeping track of files and documents as they are updated and changed. Web Publisher manages version control for you, allowing you to compare different versions of a file, providing version history for any file under version control, and automatically incrementing version numbers for files edited under version control.
For further information about version control in Web Publisher, access the online Web Publisher User's Guide through the Help menu command in Web Publisher or the Help button on the search interface, the Agent Services page, or the Web Publisher Services page.
Files under version control are stored in an archive directory. To specify which directory you want Web Publisher to use as the version control archive directory, follow these steps:
/plugins/content_mgr/archive
. Web Publisher uses this archive to store all files under version control.
Unlocking files
If a file that has been locked in Web Publisher is required for another user, you can unlock it. This is true for files that were locked manually by the client or automatically by Web Publisher as part of an edit or download operation.
For further information about locking and unlocking files in Web Publisher, access the online Web Publisher User's Guide through the Help menu command in Web Publisher or the Help button on the search interface, the Agent Services page, or the Web Publisher Services page.
Be cautious in using this function because by unlocking a file that was locked,
you are forcing the file to be available for editing by other users. This is
contrary to the intent of the lock owner, who may not know of the unlocking
operation.
To unlock a file:
After you unlock a file, your server is automatically restarted to incorporate the lock change.
Note
If you want to unlock a file that begins with a period, as in .jshrc
, you cannot use this form to perform the unlocking. You will have to log into Web Publisher as the user and unlock the file there.
Adding custom properties
As server administrator, you can add your own custom Web Publisher file properties. These properties are added to the default set of file properties stored in the web publishing collection. Server clients can view visible custom properties in Web Publisher and use them in their document searches.
For further information about viewing and modifying properties in Web Publisher, access the online Web Publisher User's Guide through the Help menu command in Web Publisher or the Help button on the search interface, the Agent Services page, or the Web Publisher Services page.
Note
If you want to add another custom property after creating the maximum
number of custom properties for a given type, you cannot remove an existing
custom property and "reuse" the property's slot in the collection by adding a
new custom property of the same type. For example, if you want to add a
numeric property after 5 have already been created, you cannot delete one of
the existing 5 numeric properties and add another numeric property in its
place. The only way to use the new property is to remove the entire collection
and recreate it with the new property.
To add a custom file property:
webpub.conf
file,
although larger sets of attributes impact the performance of your server.
Note
You cannot use the additional attributes in the existing web publishing collection. If you want to use the new attributes in the web publishing collection, you must use your file system to remove both the web_htm
and link_mgr
collection files from the search collections directory and then restart your server. See "Configuring manually" in Chapter 11, "Using search" for details on how to change the webpub.conf
file.
Managing properties
You can list all the file properties that are available for use. These include the default set plus any new custom properties you have created. You can remove or edit only those properties that you have created. These have active Remove and Edit links in the first two columns.
To manage file properties: