OK. This may be an artifact of bad data in your database, but only if you're
working with an existing DB built with FW 1.8. I'm assuming you're working
with a fresh copy. Unless I hear from you otherwise, I'll see if I can repro
this against a clean install of 2.0.0.72. I hope to get to this (and the
other bug you reported) today, but it may be later this week, as I've got a
bit of travel coming up.
i have already an existing DB with 2.0.0.52 and it's the same DB i've used
for 2.0.0.72... okay... i will try to start from scratch (clean) with
2.0.0.72... uninstalling everything and not to modify anything... hope to
get it work...
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Flexwiki-users mailing list
Flexwiki-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flexwiki-users
