Hi Walt
Sorry, I missed that you did not understand Namespace hierarchy yet. I use a
directory called "Namespaces". In this directory I have other directories
one each for each namespace I use: "OdsWiki", "PluginLib", etc. In that
regard it is flat. It is possible to nest these if there is a natural
heirarchy, especially if you are using Windows Groups for access control
(this is a new feature of 2.0). However the namespace listing in
flexwiki.config will flatten them - all namespaces are equal except where
access controls are in place.
John Davidson
On Wed, Jul 30, 2008 at 7:55 PM, Walt Crosby <
[EMAIL PROTECTED]> wrote:
> John:
>
> OK -- so Namespaces are essentially flat now, rather than somewhat
> hierarchical using the format that I had. So what about the Topics under my
> old dotted name structures -- are these hierarchical? Or am I just going to
> end up with one big directory with a huge number of files in a flat
> namespace? Is this why people are going to the SQL Namespaces?
>
> Walt
>
> ------------------------------
> *From:* John Davidson [mailto:[EMAIL PROTECTED]
> *Sent:* Wednesday, July 30, 2008 7:49 PM
>
> *To:* [EMAIL PROTECTED]; FlexWiki Users Mailing List
> *Subject:* Re: [Flexwiki-users] Upgraded to 2.0 -- now having problems
> with Namespaces
>
> Hi Walt,
> Fortunately (or maybe by design) the links you have will continue to work
> so long as you keep the namespace exactly the same as the part of the dotted
> structure prior to the dot and make sure the topics have the topic name as
> the part of the dotted structure following the dot.
>
> As to how to accomplish the renaming of the files from the dotted structure
> to an undotted name, that may be more of a problem. The rename command will
> not take a wildcard that will easily allow you to do this from the command
> line. The easiest way would be to use a word processor to create a batch
> file full of rename commands to do this for you. You would start to build
> the rename batch file by doing a command like
>
> dir /B /ON /N > dir.txt
>
> which would give you a listing of the original file names which you would
> need to transform into a command (1 for each file)
>
> ren oldnamespace.topic(10-20-2005).wiki Topic(10-20-2005).wiki
>
> Anybody else have any other ideas, as this is still a lot of work?
>
> John Davidson
>
>
>
> On Wed, Jul 30, 2008 at 7:07 PM, Walt Crosby <
> [EMAIL PROTECTED]> wrote:
>
>> John:
>>
>> Thanks for the quick response. I've been following this stuff pretty
>> closely for a couple of years, and I can't remember anything that says these
>> name structures were outlawed. When you say make these topics under the
>> primary namespace -- Does that mean these are just new pages?
>>
>> I went with Dotted Structure namespaces, because it seemed to make sense
>> as a way to delineate these things, particularly if you have multiple
>> organizations. How would I now make these topics without losing all of my
>> links that are already pointing at these namespaces?
>>
>> Is there any documentation on how to do this?
>>
>> Walt
>>
>> ------------------------------
>> *From:* John Davidson [mailto:[EMAIL PROTECTED]
>> *Sent:* Wednesday, July 30, 2008 6:48 PM
>> *To:* [EMAIL PROTECTED]; FlexWiki Users Mailing List
>> *Subject:* Re: [Flexwiki-users] Upgraded to 2.0 -- now having problems
>> with Namespaces
>>
>> Hi Walt,
>> I think that 1.8 (or maybe earlier) eliminated the use of topic name
>> formats such as yours. Dots are no longer allowed in topic names. This was
>> necessary for a number of reasons, among those hierarchical organization.
>> What I think you will need to do is create a namespace called
>> 'EverydayWireless' and then move the topics 'TechnologyPages' and
>> 'Marketing' into that namespace.
>>
>> Does this answer your question?
>>
>> John Davidson
>>
>> On Wed, Jul 30, 2008 at 6:06 PM, Walt Crosby <
>> [EMAIL PROTECTED]> wrote:
>>
>>> Guys -- I just recently upgraded to FlexWiki 2.0.0.246 from a pre-1.8
>>> version.
>>>
>>> My old Namespaces had name formats like EverydayWireless.TechnologyPages
>>> or EverydayWireless.Marketing. I copied them from the old directory to the
>>> new Namespaces directory and edited the SML file -- and I am able to view
>>> the pages very easily.
>>>
>>> However, when I go to Edit, I get an error like the following. I've
>>> taken a look at the code, and I realize it is because of the dotted
>>> structures I use. What am I supposed to use to make this error go away, and
>>> the Editing portion of the system to work. From my reading of the code, it
>>> has something to do with taking the "." out of the Namespace. But does that
>>> mean I have to move the files into a true hierarchy?
>>>
>>> I've looked around, and I can't seem to find anything that indicates
>>> whether I was supposed to move these into some other hierarchy...
>>>
>>> Walt Crosby
>>> CTO
>>> Everyday Wireless, Inc.
>>> Server Error in '/EWWiki' Application.
>>> ------------------------------
>>> *An illegal local name was specified: the namespace separator is not
>>> allowed as part of a local name.* *Description: *An unhandled exception
>>> occurred during the execution of the current web request. Please review the
>>> stack trace for more information about the error and where it originated in
>>> the code.
>>>
>>> *Exception Details: *System.ArgumentException: An illegal local name was
>>> specified: the namespace separator is not allowed as part of a local name.
>>>
>>> *Source Error:*
>>>
>>> The source code that generated this unhandled exception can only be
>>> shown when compiled in debug mode. To enable this, please follow one of the
>>> below steps, then request the URL:
>>>
>>> 1. Add a "Debug=true" directive at the top of the file that generated the
>>> error. Example:
>>>
>>> <%@ Page Language="C#" Debug="true" %>
>>>
>>> or:
>>>
>>> 2) Add the following section to the configuration file of your
>>> application:
>>>
>>> <configuration>
>>> <system.web>
>>> <compilation debug="true"/>
>>> </system.web>
>>> </configuration>
>>>
>>> Note that this second technique will cause all files within a given
>>> application to be compiled in debug mode. The first technique will cause
>>> only that particular file to be compiled in debug mode.
>>>
>>> Important: Running applications in debug mode does incur a
>>> memory/performance overhead. You should make sure that an application has
>>> debugging disabled before deploying into production scenario.
>>> *Stack Trace:*
>>>
>>> [ArgumentException: An illegal local name was specified: the namespace
>>> separator is not allowed as part of a local name.]
>>> FlexWiki.TopicName..ctor(String localName, String ns) in
>>> c:\Builds\ccnet\server\flexwikicore-20\Working\build\EngineSource\TopicName.cs:65
>>> FlexWiki.QualifiedTopicRevision..ctor(String topic, String ns) in
>>> c:\Builds\ccnet\server\flexwikicore-20\Working\build\EngineSource\QualifiedTopicRevision.cs:50
>>> FlexWiki.Web.PageUtilities.GetTopicRevision(Federation federation) in
>>> c:\Builds\ccnet\server\flexwikicore-20\Working\build\FlexWiki.Web\PageUtilities.cs:81
>>> FlexWiki.Web.PageUtilities.InsertStylesheetReferences(Federation
>>> federation, FlexWikiWebApplication wikiApplication) in
>>> c:\Builds\ccnet\server\flexwikicore-20\Working\build\FlexWiki.Web\PageUtilities.cs:143
>>> FlexWiki.Web.BasePage.InsertStylesheetReferences() in
>>> c:\Builds\ccnet\server\flexwikicore-20\Working\build\FlexWiki.Web\BasePage.cs:527
>>> ASP.wikiedit_aspx.__Render__control1(HtmlTextWriter __w, Control
>>> parameterContainer) +72
>>> System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer,
>>> ICollection children) +98
>>> System.Web.UI.Control.RenderChildren(HtmlTextWriter writer) +20
>>> System.Web.UI.Page.Render(HtmlTextWriter writer) +26
>>> System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer,
>>> ControlAdapter adapter) +25
>>> System.Web.UI.Control.RenderControl(HtmlTextWriter writer,
>>> ControlAdapter adapter) +121
>>> System.Web.UI.Control.RenderControl(HtmlTextWriter writer) +22
>>> System.Web.UI.Page.ProcessRequestMain(Boolean
>>> includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2558
>>>
>>>
>>> -------------------------------------------------------------------------
>>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>>> challenge
>>> Build the coolest Linux based applications with Moblin SDK & win great
>>> prizes
>>> Grand prize is a trip for two to an Open Source event anywhere in the
>>> world
>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>>> _______________________________________________
>>> Flexwiki-users mailing list
>>> Flexwiki-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/flexwiki-users
>>>
>>>
>>
>> -------------------------------------------------------------------------
>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>> challenge
>> Build the coolest Linux based applications with Moblin SDK & win great
>> prizes
>> Grand prize is a trip for two to an Open Source event anywhere in the
>> world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> Flexwiki-users mailing list
>> Flexwiki-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/flexwiki-users
>>
>>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Flexwiki-users mailing list
> Flexwiki-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flexwiki-users
>
>
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Flexwiki-users mailing list
Flexwiki-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flexwiki-users
