home   services   products   downloads   contact   Nederlands 
 

webphlex: known problems in version 1.0.3
 

ref.no. found in version screen(s) description fixed in version
7 1.0.1 web page groups Link to element or detail page does not qualify linking page group as parent of target page group. When an element in page group A links to an element or detail page in page group B (rather than to page group B as a whole), page group A is not recognised as the parent of page group B, and will not appear in the site navigation for that page group.
Workaround: Create an element in page group A which links to page group B as a whole; this element can be made invisible by setting the indicators "visible on page?" and "visible in element list?" off.
not yet fixed
8 1.0.3 web page groups Indicator 'use default element template?' sometimes incorrectly set when creating new element records for files. When creating new element records for selected files (page 'tools'), based on an existing element, the indicator 'use default element template?' is always set on in the new elements if a default element template exists for the page group, even when the creation is based on an element with this indicator set off.
Workaround: Create elements, and correct indicator afterwards. N.B. the correction can be done in one element, and the change copied to the others using the button 'copy details from this record to other record(s)'.
[1.0.4]
9 1.0.3 web page groups Previous/next addresses in detail page sometimes incorrect when element not visible on main page. When an element is not visible on the main page (i.e. the indicator 'visible on page?' is set off), but a detail page is being generated (i.e. the indicator 'generate detail page?' is set on), the previous/next element addresses in the detail page are sometimes generated incorrectly.
Workaround: Do not generate detail pages for elements which are not visible on the main page.
[1.0.4]
10 1.0.3 clean up / compact database Option 'look for problems?' causes error messages. Using the option 'look for problems?' causes error messages of the form "Record from table data_class cannot be read for key 'XXX'."
Workaround: Ignore these error messages.
not yet fixed
11 1.0.3 web page groups First element cannot be created for empty page group. When a page group contains no elements, an attempt to create the first one causes error 792 "Attempting to write a record with a key value of zero - update cancelled".
Workaround: Copy one element from another page group, and change it.
[1.0.4]

 

Page last updated: 16-12-2007 15:35:11


Known problems in older versions:

ref.no. found in version screen(s) description fixed in version
1 1.0.0 web servers A relative address can be entered as the main URL for a web server. E.g. "www.iphlex.com" (without the "http://") is a valid Windows directory name, and is taken as a relative address. This can lead to unexpected results when page groups located on the server are referenced from page groups located elsewhere.
Solution: Only absolute addresses are accepted in this field.
Workaround: Only use absolute addresses (e.g. beginning with "http://", a drive letter or a computer name).
1.0.1
2 1.0.0 web page groups Certain fields are not put back to their original values by use of the 'Cancel changes' button. Concerns for example the indicators 'always use local / remote filenames'. 1.0.1
3 1.0.0 web page groups Right mouse click in selection windows gives error 2485. A right mouse click in the selection windows for elements and extra pages causes error 2485. This means that these records cannot be copied and pasted directly in the selection windows.
Workaround: Select an element or extra page using left mouse click, then use right-click in the subscreen to access record copy and paste.
1.0.1
4 1.0.0 web page groups Replacement code #ELEMENT_URL:xxx# does not always work correctly. When replacement code #ELEMENT_URL:xxx# is used on a detail page or an extra page, and references an element on the corresponding main page, the URL generated will point to the detail or extra page itself rather than to the main page (e.g. "#999" instead of "index.html#999"). Parameter ABS also does not work correctly with this replacement code in this situation. 1.0.2
5 1.0.1 web page groups "content/link" information in the element selection window sometimes incorrect. When an element is linked to another element, the "content/link" information in the element selection window sometimes incorrectly indicates a link to the target element's destination (e.g. the detail page) when the link is actually to the element's position on the main page.
This error may be ignored: It may be confusing, but has no further consequences.
1.0.2
6 1.0.1 web page groups Element linked to itself can cause program loop. When a page group element is linked (directly or indirectly) to itself, calling up the page group will cause the program to go into an endless loop. This will only happen if every element in the chain has another element as its link destination, and is linked to the destination of the target element rather than to its position on the main page.
Solution: The situation described causes an error message instead of a loop.
Workaround: Do not call up the page group in question. Once the data has been loaded into a new version of the system, the page group will be useable again.
1.0.2

 


iphlexwebphlex > known problems Copyright © 2006 iphlex systems