Basic administration
Site structure
Content loaders and presentations
Miscellaneous
Basic development
Plex/Websydian development
This indicates that WebsydianExpress™ was unable to resolve to the demosite.
Use the "User Management -> Users" menu item in the administration menu.
Use the search facility to find the user, who have been deactivated. Press "Update" on the entry in the grid.
On the detail page change the user status to "Active". Press "Update".
The user will now be able to access the site again.
This is a generic error shown to the user whenever a programming error or an error in the site definitions occur.
Of security reasons the user will not get any more specific information about the error.
To facilitate finding the reason for the error the Websydian Express runtime can throw a number of messages depending on the cause of the error. These errors can be found in the message log.
Use the menu item "Utilities->Message log" in the administration menu to check whether any messages has been thrown.
By pressing the Help icon for an message entry in the message log you will get a detailed description of the message and an explanation of what you should do to rectify the situation.
These descriptions are delivered as part of the runtime. In some cases we will have updated the explanation to make it more meaningful. If you receive an error stating the the page containing the description can't be found, or if you do not think the explanation is good enough you can check the list of the newest version of the error descriptions here.
If you have defined all the frames as children to the frameset site element check that the HTML template for the frameset defines the right number of frames.
E.g. if you have defined 4 frames for the frameset site element, the HTML template for the frameset should contain the following HTML code:
...
<FRAMESET ROWS="74,50,*,40" ...>
....
Please note that it is the ROWS attribute in the template that define the number of rows (in this case 4 rows).
This will happen with the Mozilla Firefox browser if the feature "Change images" in the Advanced JavaScript Options is disabled.
First, check whether any messages have be written to the message log.
If a message has been thrown, please see the help for this message for further information.
If no relevant messages can be found in the message log, there are two possible reasons for the problem.
Go to the "Site Structure -> Site Structure", select the menu item in the site structure tree. Press "View". In the section "Menu Site Element behavior in Site Tree" find the property "Frame" and check whether this is the frame that ought to be populated. If it is not use the update functionality to correct the frame name.
If this is the case no PageGenerator function will ever be called. This means that no errors has occurred - and because of this no messages has been written to the message log. On the other hand - as no PageGenerator has been called - no function has populated the frame.
Contact the responsible developer to make sure whether an actual call has been added to the action diagram - and that it has been added in the edit point "Call to first pagegenerator".
Sometimes a business process can return a page that contains the error message [Unable to open Document Template in function "..\html\MyTemplate.HTM" in function "MyFunction"].
See below for reasons to this error and how to resolve it.
This error comes in three different variations:
This will almost always be because the template has not been generated - or has not been moved to the correct folder.
This can typically happen if the PageGenerator does not inherit from PageGeneratorForProcess or if the PageGenerator also inherits from a WSYBASE/WSYUTIL pattern.
The reason is that the option "WSYD Read external path", which is set to "No" for the PageGeneratorForProcess, has been overwritten by "Yes" from another pattern.
This will typically occur if a suffix have been defined for the current presentation - but not all templates used by the process have been copied.
This will typically occur for templates used by either error pages or dynamically loaded drop down generators.
Generate the template if it has not already been.
Copy the template to the correct folder.
Ensure that the PageGenerator does inherit from PageGeneratorForProcess.
Set the option "WSYD Read external path" to "No" for the PageGenerator.
Copy the file to a file with the specified filename.