Current version: 2.0
These pages are currently being rewritten pending the release of NextPage 2.0
Some parts of this text may apply to previous versions of NextPage and not the current version.
.

Known Bugs

Does NextPage have any bugs?
Yes it does.Some of them havn't shown heir face yet. They'll end up on this page as soon as they have. Others have shown their face but haven't been fixed yet. Those bugs are addressed as 'Known Bugs' and are listed here:

  • project files are not deleted (projectman.pl)
    When a project is deleted the project file should be as well.  In the current situation you'll have to remove the file manually.

  • Error handling in project manager doesn't work properly (projectman.pl)
    The script doesn't (as it should)  throw an error message in case it's unable to create (the path to) a new project(file).  

  • Can't change user settings for current user (userman.pl)
    When you want to change any of the user settings, you need to be logged in as another user. In other words, when you are logged in as 'john' you can change user settings for 'jack' but not for 'john'.
    Would you try to change settings for 'john' anyway, you'll probably loose seetings for 'john'.

  • Can't generate all (edit.pl) [fixed]
    In order to use the generate all function in the source editor, (for some reason) a qualified source file needs to be loaded into the editor. So when you just modified a 'project file' or a 'template file', you need to load (open) any source file before you can have edit.pl generate all output files. 

  • Parent directory & parent/parent directory don't work as expected (windymap.pl)
    These functions (in the "browse-window") use JavaScript's history.go() function, which doesn't suit the task. Must be fixed within the perl code.

 


This page was generated using NextPage 2.0   Edit
Home  -  User's Guidel

Downloading NextPage

Pending NextPage 2.0
Last modified: Saturday, August 10 2002

SourceForge Logo