Editing Web Host Content
To edit Web Host pages, you will need to be familiar
with HTML, Javascript, CSS style sheets, and Collect!'s
Report Writer codes.
Collect!s web host pages are stored in two locations:
1. Index pages, include text files and
script files, are located in subfolders in each
database's HTML folder. For example, C:\CV11\demodb\html.
Files located in Operator ID folders for each user
level in the HTML folder are generated from
Web Host. These pages must be edited from
within the Web Host's
reports.
2. Reports that are used to display results of form
submits from the browser are in Collect!'s Report
Definition List accessed through the Print menu,
Customize Printing, Edit Report Templates
option when you are in Web Host mode.
To edit the *.s, *.CSS, *.gifs, and *.html index files,
make your changes in their current folder location.
To edit a generated web report, Collect!'s Report Writer
is used. When you are in Web Host mode, select Print
from the top menu bar, and then select Edit Reports from
the drop-down choices. The Report Definition List will
be displayed. Each report is named according to the
operator user level that uses it and its purpose.
You must be in Web Host mode to view
the list of Web Host reports.
To easily determine which page to edit, view the Report
Definition list right after you have generated a page
in the browser. The report that Collect! used to generate
the page should be highlighted. Make the changes as
needed and return to the HTTP Request Log screen before
going back into the browser to refresh or navigate.
The browser will perform unexpected results if
you generate a page from the browser while
the Web Host instance is not at the HTTP Request
Log screen. Always return to the HTTP Request
Log screen after editing reports. Then return
to the browser to test your changes.
Reports use the @include command which pulls template
information from text files. These *.txt files may be edited
in any raw text editor, such as Notepad, WordPad,
or Ultra Edit. When a change is completed, the Web Host
instance must be shut down and restarted because
include files are cached in RAM. Once a page with an @include
file has been generated, Collect! will not look for a change to the
file until you clear out the processes stored in memory.
See Also
- Web Host Introduction
- Web Host Topics
- Modifying the Web Host
- Report Topics Index
- How To Edit Reports Or Letters
|
Was this page helpful? Do you have any comments on this document? Can we make it better? If so how may we improve this page.
Please click this link to send us your comments: helpinfo@collect.org