The page group has not been completely generated since the last time it was changed. Note that a partial generation may well in fact have changed every file which needs to be changed, so that generating the page group after you receive this message will not result in any file changes.

see also:

web generation: button: generating the whole page group introduction: generating part of a page group

Texts can contain embedded text blocks, which can themselves contain other embedded text blocks. If a text block tries to call itself (either directly or as the result of an earlier text replacement) this could cause an endless loop.

see also:

text blocks: 'embedded' text blocks

An endless loop was detected while processing a replacement code.

This would be caused, for example, if the field 'page title 1' contained the text #TITLE1#.

It would also be caused if the field 'page title 1' contained the text #TITLE2# and the field 'page title 2' contained the text #TITLE1#.

see also:

templates and text replacement

The number of main pages generated for a page group depends on the elements. You are trying to view a page number which doesn't exist.

see also:

data structure: how many main pages?

When fast find is used in a global find/replace action, the system attempts to build an SQL instruction which will only find records containing the text being searched for; this is considerably faster than the alternative, which is a serial read of the database. In certain circumstances this would require an SQL instruction which would be too complex, and fast find cannot be used.

This may also happen when the text being searched for contains characters which have a special meaning in SQL, such as hash (#) and asterisk ( * ). Either change your search text to avoid using these characters, or do not use fast find.

Tip: It is often more efficient to use fast find with a less specific search string than to read serially through the database to find exactly what you want.

The number of main pages generated for a page group depends on the elements. You are trying to generate a page number which doesn't exist.

see also:

data structure: how many main pages? screen: web page groups: field: page number to view/generate

An element or page group which is linked to from another element (using 'link destination' in the element subscreen) cannot normally be deleted, nor can such an element be moved to another page group. It is, however, possible to allow these actions in the company screen, in which case a warning will be given. If code generation is attempted using the linking element, a warning will be given and the code #DESTINATION_URL# will be replaced by an empty string.

see also:

templates and text replacement: system-wide text replacement codes

An address is being calculated for a file in another page group, and its value depends on whether the files are to be used locally or on the web server(s).

E.g. suppose two web sites, site1 and site2 are maintained on the same local machine, and the generated files are placed in C:\web sites\site1\ and C:\web sites\site2\ respectively. The two sites are hosted on different servers: http://www.site1.com/ and http://www.site2.com/. If a file in site1 contains a link to page page1.html in site2, the generated code for the URL will depend on whether the file(s) are to be used locally or on a remote location: ../site2/page1.html or http://www.site2.com/page1.html.

Choose No if both the file being generated and the file it will link to are to be used locally.

Choose Yes if either file is to be stored on a remote machine.

Tip: Ideally, the directory structures on the local and remote machines should be identical, relative file names will always be used and this question will never be asked. If this is not possible, it is often useful to use local file names while a web site is being tested off-line, then to re-generate the page groups, using remote names, before uploading the files to the web site.

see also:

web generation: absolute and relative addresses

A record can not be imported if a record already exists with the same record code for the same company. You must first delete or rename any such records.

see also:

list of actions: import from import/export file (.ipd) introduction: record numbers and codes

As record numbers are unique throughout the system for a given type of data (e.g. there can never be two web page elements with the same element number, even in different web page groups belonging to different companies), a record can not be imported if its record number already exists.

It is, however, possible to import the record with a new record number. If this is done, all imported records will afterwards be checked for use of the old record number, and updated where necessary. This is a fairly lengthy process, and interrupting it may cause links within and between the imported records to no longer work.

Tip: rather than importing records with a new record number, it is often faster to copy the existing records to new ones, then delete the originals, so that their record numbers are no longer in use.

see also:

list of actions: import from import/export file (.ipd) introduction: record numbers and codes

After records have been copied or imported with new record numbers, they will be checked for (internal) use of the old record number, and updated where necessary. E.g. if a web page group is copied, any elements which link to other elements in the same page group using their element numbers (as opposed to referencing the next, previous etc. element), will have to be updated.

This is a fairly lengthy process, and interrupting it may cause links within and between the copied or imported records to no longer work.

Tip: rather than importing records with a new record number, it is often faster to copy the existing records to new ones, then delete the originals, so that their record numbers are no longer in use.

see also:

list of actions: import from import/export file (.ipd) introduction: record numbers and codes

After records have been copied or imported with new record numbers, they will be checked for (internal) use of the old record number, and updated where necessary. E.g. if a web page group is copied, any elements which link to other elements in the same page group using their element numbers (as opposed to referencing the next, previous etc. element), will have to be updated.

This is a fairly lengthy process, and takes even longer if all text fields have to be checked for embedded numeric key references (e.g. #wPAGE_URL:nnn#, #ELEMENT_URL:nnn# and #TEXT:nnn#, where nnn is numeric). If you're sure you aren't using any of these (or don't mind updating them manually) you can speed up the key reference update procedure considerably by answering No here.

Note that the link destinations of web page elements (set at: control panel > web pages > web page groups > elements > link destination) are always updated.

see also:

list of actions: import from import/export file (.ipd) introduction: record numbers and codes subscreen: web page elements

When the main local location of a page group (i.e. the location where the generated files will be put) is changed, it is possible to update the relative paths for (image) files so that the generated files will contain links back to the current locations.

E.g. suppose the location is C:\web sites\site1 and the site's images are stored at C:\web sites\site1\images. The relative location for images is then images. If the main location is changed to C:\web sites\site2, the image location can be updated to ..\site1\images, so that generated files link back to the original location, or left as images, in which case the files will link to the new location C:\web sites\site2\images.

see also:

web generation: absolute and relative addresses screen: web page groups: field: always use local / remote filenames

An element or page group which is linked to from another element (using 'link destination' in the element subscreen) cannot normally be deleted, nor can such an element be moved to another page group. It is, however, possible to allow these actions in the company screen, in which case a warning will be given. If code generation is attempted using the linking element, a warning will be given and the code #DESTINATION_URL# will be replaced by an empty string.

see also:

templates and text replacement: system-wide text replacement codes

An endless loop was detected while processing a replacement code.

This would be caused, for example, if the field 'page title 1' contained the text #TITLE1#.

It would also be caused if the field 'page title 1' contained the text #TITLE2# and the field 'page title 2' contained the text #TITLE1#.

see also:

templates and text replacement

A possible endless loop was detected while processing an embedded replacement code.

This would be caused, for example, if the field 'page title 1' of page group xxx contained the text #wPAGE_TITLE1:yyy#, and the field 'page title 1' of page group yyy contained the text #wPAGE_TITLE1:xxx#.

see also:

templates and text replacement: system-wide text replacement codes

During output file generation, either the file already existed, or it was successfully created (in which case it will have a file size of 0 bytes), but the system was then unable to write data to the file.

This may be caused by the presence in the content to be written of something which Windows doesn't like; certain exotic Ascii characters can have this effect.

To view the content which is to be written without actually writing it to disk, use the button 'preview generated text' (  ).

This error can also occur when a page or element is previewed in a browser window, in which case the file will be called '~temp.html'.

see also:

web generation: previewing generated code

An attempt to determine an address (normally during output file generation) by combining an absolute and a relative address failed, because the resulting address would require a higher directory than the top directory of the absolute address used. This is usually because the relative address contains too many ../ strings.

e.g. this would happen if an attempt is made to combine the relative address ../../index.html with the absolute address C:\web sites.

see also:

web generation: how addresses are determined

An attempt to determine an address (normally during output file generation) by combining an absolute and a relative address failed, because the resulting address would require a higher directory than the top directory of the absolute address used. This is usually because the relative address contains too many ../ strings.

e.g. this would happen if an attempt is made to combine the relative address ../../index.html with the absolute address C:\web sites.

see also:

web generation: how addresses are determined