I am not sure if this is not implemented yet or a
limitation that is derived from FlexWiki. I guess it
may be disallowed to make sure the history of the page
is not lost, but I thought I would mention it anyway.
The limitation is derived from FlexWiki, which has no
ability to actually delete topics. FWP is designed to be
interoperable with FlexWiki webs, so exactly how to deal
with this is a bit problematic.
There are several options:
1) Always allow the user to delete the topic/namespace.
2) Never allow the user to delete the topic/namespace.
3) Allow the user to delete the topic/namespace, and add the
topic/namespace to a special "ignore" list so that if
something like fwsync downloads the namespace/topic in the
future, FWP won't report its presence.
4) Add the ignore functionality from 3 to fwsync instead, so
that future synchronizations won't download the
topic/namespace at all. Optionally, augment FWP so that it
automatically adds the topic/namespace to the fwsync ignore
list when deleting in FWP.
I'm leaning towards 4 at the moment.
Depending on the particular option selected, this could be a
significantly complicated augmentation, so don't expect me
to complete it in the near future. Still, I think it's a
reasonable feature to include at some point before too long.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think suggestion 4 makes sense. I think this information
about the ignore list should be saved in the wiki directory in
some configuration file. The FwSync should find this file and
work with the information in it.
If you visit the link below, you will find that the process for
deleting in this site is to change the topic contents
to "deleted". I am not sure what happens after that. But
using the topic contents to indentify that the topic is
deleted, may be a bit slow when populating something like
the topics list. But during FwSync and saving of the topics
we can make such check and accordingly add the topic to
FWP ignore list.
Logged In: YES
user_id=879696
The limitation is derived from FlexWiki, which has no
ability to actually delete topics. FWP is designed to be
interoperable with FlexWiki webs, so exactly how to deal
with this is a bit problematic.
There are several options:
1) Always allow the user to delete the topic/namespace.
2) Never allow the user to delete the topic/namespace.
3) Allow the user to delete the topic/namespace, and add the
topic/namespace to a special "ignore" list so that if
something like fwsync downloads the namespace/topic in the
future, FWP won't report its presence.
4) Add the ignore functionality from 3 to fwsync instead, so
that future synchronizations won't download the
topic/namespace at all. Optionally, augment FWP so that it
automatically adds the topic/namespace to the fwsync ignore
list when deleting in FWP.
I'm leaning towards 4 at the moment.
Depending on the particular option selected, this could be a
significantly complicated augmentation, so don't expect me
to complete it in the near future. Still, I think it's a
reasonable feature to include at some point before too long.
Logged In: YES
user_id=347585
I think suggestion 4 makes sense. I think this information
about the ignore list should be saved in the wiki directory in
some configuration file. The FwSync should find this file and
work with the information in it.
If you visit the link below, you will find that the process for
deleting in this site is to change the topic contents
to "deleted". I am not sure what happens after that. But
using the topic contents to indentify that the topic is
deleted, may be a bit slow when populating something like
the topics list. But during FwSync and saving of the topics
we can make such check and accordingly add the topic to
FWP ignore list.
http://www.flexwiki.com/default.aspx/FlexWiki.FormattingRules