Re: [Flexwiki-users] Moving on

> The toddler will be running around you craving your attention all the > time, the infant screaming because the diaper needs to be changed, and > the wife yells from the living room that she needs another beer so she > can watch the next episode of Dr. Phil. yeah.. we all go through it at > some s

Re: [Flexwiki-users] Moving on

> I am of course saddened along with everyone else to learn you are > leaving the project. Despite the feelings you've expressed, my initial > reaction to this news was that Flexwiki was basically at the end of its > development lifespan as a result of you leaving.  Hmm. Given that the coolest thi

[Flexwiki-users] Output Caching

OK, I just checked in my output caching code. By default, it's turned off, but if you uncomment the section in flexwiki.config and set it to an time interval (e.g. 00:10:00), it will enable the feature. The way it works is to cache (in the ASP.NET cache) the results of all calls to default.as

[Flexwiki-users] Moving on

It has been something like four years that I've been working on FlexWiki. Not very quickly at times, but I do at least try to put in around an hour every day. For quite a while now, that hour has become more a chore than something I look forward to. But I was committed to completing the tasks I sai

[Flexwiki-users] FlexWiki 2.0 Released

I just posted FlexWiki 2.0 RTW on SourceForge. Hooray! Here's the announcement: This is FlexWiki 2.0, Release To Web (RTW) version. It is identical to FlexWiki 2.0 RC1, and the recommended version for all FlexWiki users. This version sports many, many improvements and enhancements ov

Re: [Flexwiki-users] HTML to FlexWiki Syntax Conversion

I don't think we have anything official. I'm not aware of anything else, either. Technically, it would be pretty difficult to do this for the full breadth of HTML, as you can do things in HTML that you can't do in FlexWiki. If you had a small pile of limited HTML that was well-formed (or could

Re: [Flexwiki-users] FlexWiki 2.0: Should it RTW?

> I'll throw together a readme that mentions both the CPU/newsletter > potential > issue and upgrade steps. Here's the readme I wrote. It's pretty bare, but I think it gets the job done. Anyone have any comments? FlexWiki 2.0 Release To Web (RTW) README New Installation Instructions ==

Re: [Flexwiki-users] FlexWiki 2.0: Should it RTW?

> I am sorry for my tardiness with respect to giving you more > information. Things have been hectic here and my time at the office has > been limited. No apologies, please - if the pace of my work on this project has been any yardstick, we're lucky we get anything done at all. :) > With newsle

Re: [Flexwiki-users] FlexWiki 2.0: Should it RTW?

and see if i have any issues. Im still using mediawiki ( i hate php) and would gladly replace it. On Jan 7, 2008 3:18 PM, Craig Andera <[EMAIL PROTECTED]> wrote: Other than James' account of runaway CPU, which I'm still hoping to hear more about when he gets the time, I have

[Flexwiki-users] FlexWiki 2.0: Should it RTW?

Other than James' account of runaway CPU, which I'm still hoping to hear more about when he gets the time, I haven't heard anyone reporting positive or negative experiences with FlexWiki 2.0 RC1. I'm going to take that as a positive sign. J So what I want to know is, does anyone feel like there are

Re: [Flexwiki-users] FlexWiki 2.0 100% CPU

es James From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Craig Andera Sent: 21 December 2007 14:40 To: 'FlexWiki Users Mailing List' Subject: Re: [Flexwiki-users] FlexWiki 2.0 100% CPU Fair enough - we can hardly ask for more. If anyone encounters this problem,

Re: [Flexwiki-users] Having problems with Flex.csv

ers] Having problems with Flex.csv 1.8.0.1696. I haven't downloaded an update ever. Should I just go up to 2.0? Is there anything I have to do for conversion? Walt _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Craig Andera Sent: Friday, Decemb

Re: [Flexwiki-users] FlexWiki 2.0 100% CPU

27;ve flagged your message and will check out the newsletter configuration after the busy period has passed. Best wishes James From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Craig Andera Sent: 21 December 2007 11:56 To: 'FlexWiki Users Mailing List' Subject: Re: [

Re: [Flexwiki-users] Having problems with Flex.csv

What version are you running? FlexWiki 2.0 doesn't use that logfile any more, so I have to assume 1.8. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Walt Crosby Sent: Thursday, December 20, 2007 10:35 PM To: 'FlexWiki Users Mailing List' Subject: [Flexwiki-users] Having proble

Re: [Flexwiki-users] FlexWiki 2.0 100% CPU

- and also _ContentBaseDefinition. Does the newsletter code go through the cache? Best wishes James From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Craig Andera Sent: 20 December 2007 17:44 To: 'FlexWiki Users Mailing List' Subject: Re: [Flexw

Re: [Flexwiki-users] How flexible is FlexWiki?

> Just to understand this correctly - by coding you mean changing the > flexwiki source code? And therefore, loosing the ability to easily > upgrade to newer FlexWiki versions? Well, there's a plugin model, but I really don't know much about it, so I'm not sure whether it gives the ability to do

Re: [Flexwiki-users] How flexible is FlexWiki?

> Having read everything I was able to find on customizing borders on > www.flexwiki.com, I get the impression that changing borders is only > possible using Wiki syntax or Wikitalk generating Wiki syntax. Is this > so? Yes. > Given the strict specifications of the mentioned style guide, I'd ha

Re: [Flexwiki-users] FlexWiki 2.0 100% CPU

Reads against _ContentBaseDefinition.wiki are not unexpected - it's conceptually read multiple times per request just to check namespace permissions. I wouldn't be at all surprised to see a hundred conceptual reads against it just for one page to render. However, I added caching because of this ver

Re: [Flexwiki-users] FlexWiki 2.0 100% CPU

Do you have newsletters enabled? I don't have a specific scenario in mind, but that's the only thing that runs in the background, all the time. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of James Berry Sent: Thursday, December 20, 2007 10:57 AM To: 'FlexWiki Users Mailing List

Re: [Flexwiki-users] www.flexwiki.com back up

Thanks, David. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Ornstein Sent: Tuesday, December 18, 2007 12:08 AM To: FlexWiki Users Mailing List Subject: [Flexwiki-users] www.flexwiki.com back up The server was hung trying to shut down after installing some automated

Re: [Flexwiki-users] Offline wiki

ill look at integration with fwsync. John Davidson On Nov 30, 2007 11:25 AM, Craig Andera <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > wrote: I always thought that integrating fwsync with flexwikipad might be good. Short of that, fwsync with a GUI rather than command-line front end. T

Re: [Flexwiki-users] Plugin Licensing

As the author, you have the option to relicense or issue it under multiple licenses any time you want. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Davidson Sent: Thursday, December 13, 2007 10:39 AM To: FlexWiki Users Mailing List Subject: Re: [Flexwiki-users] Plugin Li

[Flexwiki-users] FW: Syntax highlighter for FlexWiki (via CraigBlog)

This was just sent to me. I don't have any plans to incorporate anything like this, but I said I'd make everyone else aware of it in case someone wants to investigate whether using it would be useful. -Original Message- Mail from CraigBlog: Sender: Gustavo Duarte

Re: [Flexwiki-users] Plugin Licensing

I'm not a lawyer, so take this with a grain of salt. Or maybe consider it all to be total BS. J One of the reasons FlexWiki chose the CPL is because it places fewer restrictions on derivative works, which a plugin may be considered to be. Based on my understanding, though, your contribution is

[Flexwiki-users] FlexWiki 2.0 Release Candidate 1 Available

I just posted the files for FlexWiki 2.0 Release Candidate 1. Woohoo! You can get it here . Here are the release notes: This is Release Candidate 1 of FlexWiki 2.0. Assuming we don't find any major bugs, this release will become the final FlexWiki 2.0 ver

[Flexwiki-users] LSASS Bug Fixed

I just checked in a change that I believe fixes the problem we were having with RC1 running up the CPU. All role-based security checks are now cached in the application cache (and therefore visible via the cache view admin pages). As a result, role-based checks seem to work like they should, and th

Re: [Flexwiki-users] Offline wiki

I always thought that integrating fwsync with flexwikipad might be good. Short of that, fwsync with a GUI rather than command-line front end. The code is already fairly well separated into a library and command-line portion with this stuff in mind. It would be up to someone else to do the work th

Re: [Flexwiki-users] www.flexwiki.com cutover Thursday

> Once I get a good build, I'll deploy the new bits, go back to role- > based security, and see if it's any better. Nope. Still broken. Looks like even the supposedly "fast" overload of IsInRole still sucks. There's one more approach I can try, but it will probably have to wait until next week. Me

Re: [Flexwiki-users] www.flexwiki.com cutover Thursday

> No, actually, it's not the build failing, it's that the build service > is completely down. Has been for a while. OK, that's fixed. Not sure what the deal was: seems like the SCM may have forgotten the account password. I reset it and also removed and re-added the build account from the "Log on

Re: [Flexwiki-users] www.flexwiki.com cutover Thursday

s to only occur under load, so I may have to test it "live", meaning www.flexwiki.com might have some problems when I start making changes. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Craig Andera Sent: Tuesday, November 27, 2007 6:39 AM To: 'FlexWiki Users M

Re: [Flexwiki-users] www.flexwiki.com cutover Thursday

to test it "live", meaning www.flexwiki.com might have some problems when I start making changes. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Craig Andera Sent: Tuesday, November 27, 2007 6:39 AM To: 'FlexWiki Users Mailing List' Subject: Re: [Flexwiki-u

Re: [Flexwiki-users] www.flexwiki.com cutover Thursday

BuitlInTopic then the > LockTopic.aspx page output would also be converted (though > LockTopic.aspx would remain as there is actual functionality, even > when page is not displayed). > > > [1] http://www.flexwiki.com/default.aspx/FlexWiki/RecentlyModified.html > > John Davidson

Re: [Flexwiki-users] www.flexwiki.com cutover Thursday

kTopic.aspx would remain as there is actual functionality, even > when page is not displayed). > > > [1] http://www.flexwiki.com/default.aspx/FlexWiki/RecentlyModified.html > > John Davidson > > On Nov 23, 2007 9:20 PM, Craig Andera <[EMAIL PROTECTED]> wrote: >

Re: [Flexwiki-users] www.flexwiki.com cutover Thursday

> I will also look at LastModified.aspx to see why it fails when > wikitalk does not ;) The one difference I can think of is that there's no RequestContext active in LastModified.aspx. RequestContext is used to do some per-request caching in the AuthorizationProvider. -

Re: [Flexwiki-users] www.flexwiki.com cutover Thursday

> I have discovered that each worker process has its own copy of the > cache and it will be slightly different in each copy, until that > process expires. Yeah, that's a major problem - it's the reason that FlexWiki can't be load balanced, in version 1.8 or 2.0, against either the filesystem or Sq

[Flexwiki-users] mailto bug

Try entering an email address of the following form: [EMAIL PROTECTED] You'll get completely messed up formatting as a result, or an error that indicates it's trying to interpret the address as a InterWiki link. WikiText of the form mailto:[EMAIL PROTECTED] is also messed up.

Re: [Flexwiki-users] Which is truly faster? Flat file or MSSQL Server

I don't think anyone has ever tested. I also suspect it depends on hardware, the size of your wiki, the load, and whether the SQL Server is local or remote. But I'm not even sure the question is meaningful. It's entirely possible that one is faster for some operations and the other is faster f

Re: [Flexwiki-users] www.flexwiki.com cutover Thursday

> Initial testing was done on FlexWiki and my site with Security on, but > I have confirmed same results on my site with security off, as well. > This may indicate an issue with the cache code. Is there an easy way > to disable the cache. Set the cache.disabled parameter in the namespace parameter

Re: [Flexwiki-users] www.flexwiki.com cutover Thursday

rver Error exception [HttpException (0x80004005): Request timed out.] Best wishes James From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Craig Andera Sent: 12 November 2007 21:09 To: 'FlexWiki Users Mailing List' Subject: Re: [Flexwiki-users] www.flexwiki.com cutover

Re: [Flexwiki-users] FlexWiki Style Feedback

> Craig told something about fw shipping with > 2 designs. What did I get wrong, how do the alternative styles work? Yeah, there are some switches in the flexwiki.config file (now editable via the /admin pages!). I've pasted in the relevant sections here [1]. I don't remember off the top of my hea

Re: [Flexwiki-users] FlexWiki Style Feedback

Can you elaborate on what about it makes it a bad choice for people? I think if it's just a matter of taste then that's one thing, But if there's something specifically unusable/broken about this one then we should consider changing it. Regardless, I do think we need to update the look somehow

Re: [Flexwiki-users] Proposed To Do List Management Feature

So I read over the proposal, but I'm not sure I can give good advice. For one thing, I'm not actually all that familiar with the web app, having spent most of my time with my head under the hood, so to speak. I will say that I think it's probably a bad idea to make WikiTalk read-write without a r

Re: [Flexwiki-users] www.flexwiki.com cutover Thursday

ing the > NoFollow notice (it has not been part of the test build). > > So if someone with access can do the replacement for us I would be > appreciative. > > John Davidson > > On Nov 12, 2007 4:09 PM, Craig Andera <[EMAIL PROTECTED]> wrote: > > > > > &g

Re: [Flexwiki-users] www.flexwiki.com cutover Thursday

, that would be great. Nearly shipping now! From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Craig Andera Sent: Thursday, November 08, 2007 4:02 PM To: 'FlexWiki Users Mailing List' Subject: Re: [Flexwiki-users] www.flexwiki.com cutover Thursday Well, I didn

Re: [Flexwiki-users] www.flexwiki.com cutover Thursday

om: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Craig Andera Sent: Tuesday, November 06, 2007 1:59 PM To: 'FlexWiki Users Mailing List' Subject: [Flexwiki-users] www.flexwiki.com cutover Thursday As a heads-up, I am planning to cut www.flexwiki.com over to FlexWiki 2.0.0.16

[Flexwiki-users] www.flexwiki.com cutover Thursday

As a heads-up, I am planning to cut www.flexwiki.com over to FlexWiki 2.0.0.168 (the potential RC1 build) on Thursday, November 8th, at around 3PM EST (which is 20:00 GMT). There will probably be an outage while I do so. Hopefully the cutover will take less than an hour. -

Re: [Flexwiki-users] Topic Attachments progress report

> I mean I did not implement the attachments methods for the SqlStore. > So > currently it will only work for FileSystemStore and if someone tries it > with > SqlStore it will just get to the end of the chain and throw as the next > provider will be null. > > Just to make sure this is clear. It mu

Re: [Flexwiki-users] /admin changes

> Thanks for sorting this out Craig. With one thing and another, I never > got the time to look at it before you did :o( Don't sweat it - everyone here understands being busy. > I'm looking forward to seeing FlexWiki 2.0 on flexwiki.com :o) Yeah, here's hoping that we don't find any showstoppe

Re: [Flexwiki-users] Topic Attachments progress report

I have a few comments. Inline. > This is currently working only for the FileSystem content provider. So, this statement concerns me a bit. Perhaps we've been over this before, but I'm sort of wondering what this means. What did you have to do to get this to work that means it doesn't work for Sq

[Flexwiki-users] RequestContext requirement

This morning in the shower [1], I thought of a much better way to handle the RequestContext stuff that means it will *not* be required on every request. That means we can get rid of those superfluous OperationInExistingContext methods I made John add. J Anyway, just a heads-up. I'll rip all th

[Flexwiki-users] /admin changes

OK, I just got done checking in some changes to the /admin pages. The big thing I added was a page where you can edit the flexwiki.config file. That should pretty well end the need to have FTP or file access to the app: just unzip and you can do everything else via the web app. (Well, everything ex

Re: [Flexwiki-users] Changes

Looks good to me. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Davidson Sent: Saturday, November 03, 2007 10:00 PM To: FlexWiki Users Mailing List Subject: Re: [Flexwiki-users] Changes The code I needed to change was in EditServiceImplementation. Following your recom

Re: [Flexwiki-users] Changes

ntive in it and grabbed a context, which is of course not allowed now. Will have to do a minor rewrite to pass a TopicInfo into the plugin rather than determine the relevant TopicInfo in code. Not a problem, but an example of Murphy at Work John Davidson On 10/29/07, Craig Andera <[E

Re: [Flexwiki-users] Changes

Yes, well, it's essentially a rewrite of what you did. J Not that it was pointless - the new stuff covers everything in the content pipeline, not just WikiTalk. Even "static" pages should benefit, but of course in theory the real win is WikiTalk'd pages, since those are the ones that can be re

[Flexwiki-users] Changes

I just checked in a pretty big change. Big in the sense of lots of files affected. Moderate in terms of the impact. What I've added is another content pipeline provider called DependencyRecorder. This is a provider that sits at the very front of the chain and essentially records every request

Re: [Flexwiki-users] TableOfContents Implementation

Very cool, and it's super easy to use. I like it. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of John Davidson Sent: Friday, October 26, 2007 9:43 AM To: FlexWiki Users Mailing List Subject: [Flexwiki-users] TableOfContents Implementation The automatic generation of a Table

Re: [Flexwiki-users] File Locking Implementation

> > I think I understand(?) it, but you should validate the test > > TopicIsReadOnly in TopicCacheProviderTests after checkin. That code > is > > probably more complex than the actual cache implementation. > > OK, I'll have a look at it. Took a quick look. Looks good.

Re: [Flexwiki-users] File Locking Implementation

> I think I understand(?) it, but you should validate the test > TopicIsReadOnly in TopicCacheProviderTests after checkin. That code is > probably more complex than the actual cache implementation. OK, I'll have a look at it.

Re: [Flexwiki-users] File Locking Implementation

> Also, I have made progress on creating Unit Tests as promised with a > number for NamespaceManager and FileSystemStore. I was less than > successful when I tried to add some to the TopicCacheProvider. The > existing tests there are not easy to follow and replicate. Could you > provide some hints.

Re: [Flexwiki-users] File Locking Implementation

Well, I wrote all that code (factoring out the built-in topics into its own provider was a huge improvement on the old way of doing it, with special cases everywhere), so you can blame me if it's weird or busted. :) So this is sort of a tough problem. BuiltinTopicProvider doesn't really have anywh

Re: [Flexwiki-users] File Locking Implementation

> 3) What about a "Lock Topic"/"Unlock Topic" button right there in the > right border if the user has the proper rights. Is that easy to do? It > seems it would be nice to bubble that functionality up rather than > forcing the user to go into the lock management page and hunt down the > topic. >

Re: [Flexwiki-users] I think we should ship RC0

> The > public expects V2.0 of any product to have some significant > functionality and, sorry, but security updating just doesn't sell. I agree - security is something that most won't care about. But we've got lots of other stuff in there as well, such as the features you and John have mentioned:

[Flexwiki-users] I think we should ship RC0

It's been a bit quiet here lately. I've been on travel, but am back and am working on FlexWiki again. So here's what I'm thinking: we never did reach a conclusion about performance, other than to say that it's good overall, but that there definitely exist cases where it's enough worse than 1.8 soas

Re: [Flexwiki-users] Topic names

> > to me (at the moment) for TopicName being responsible for deciding > what's a > > valid name and what isn't and then have each store responsible for > actually > > encoding/decoding the name in the appropriate store. Not sure how > well this > > At the end of the day, I think this is how it mu

Re: [Flexwiki-users] url mapping

I'm not sure exactly where the code is, but I do know we're not rewriting [1]. Instead, I believe that we're using Request.Path, which is the bit after the default.aspx. Hopefully that helps. [1] We should be. The design of the URLs in FlexWiki are horribly broken. But I was part of the design de

Re: [Flexwiki-users] FlexWiki as a Threaded Message Board

Wow, that might actually work. :) I'm very impressed. Of course, it's also depressing. I work for three years and add *one* fairly minor feature, and you guys add cool stuff twice a month. :) > -Original Message- > From: [EMAIL PROTECTED] [mailto:flexwiki- > [EMAIL PROTECTED] On Behalf

Re: [Flexwiki-users] Admin Page Feature Request

If you want to default to a) read-only to authenticated users and b) every topic writable by Administrators, then if you put in [1] and [2], you should be good to go. Without [2], there's no statement about anyone but Administrators, and in the absence of any statement, permission is denied. Which

Re: [Flexwiki-users] Building on x64

I don't really remember what we use that stuff for, but I commented it out and ran "build clean dist" and it ran to completion. Looking a bit, I think we were using it for the now-defunct integration testing. It looks like I was using it to get the name of the machine. Nant now supports enviro

Re: [Flexwiki-users] ASP.NET Exception: Exception processing topic change 2007 ... System.ArgumentOutOfRangeException: Valid values are between 0 and 999, inclusive.

> Hm, It looks like your username might be causing some problems. I'll > try to look into this today. Looks more to me like a case of an illegal filename somehow getting generated: 3389 is indeed an illegal number of milliseconds, not being less than 999. :) --

Re: [Flexwiki-users] Performance analysis of 25000 pages

> A few more things (I decided to investigate a bit more tonight)... > > I am now much more concerned about the underlying data. I'm not surprised. I went through the same thing when I was analyzing the flexwiki.com data. > (1) One example that I just look at is a page we have that uses > WikiT

Re: [Flexwiki-users] Performance analysis of 25000 pages

> The one thing that concerns me about the underlying data is that the > iterations run through all 25000 pages and then come back and run > again. After thinking about it last night, I think this might be a > very bad analog for the real world. Specifically, this means that if I > hit page1 and

Re: [Flexwiki-users] Admin Page Feature Request

Helen - did our latest answers get you going? From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Helen Ersando Sent: Sunday, September 23, 2007 11:12 PM To: FlexWiki Users Mailing List Subject: Re: [Flexwiki-users] Admin Page Feature Request hi, how would i be able to include

Re: [Flexwiki-users] Performance analysis of 25000 pages

> OK.  I finally got the spreadsheet working and have results.  Below is > the data based on a run from the build before the most recent.  I’ll > have to go get the latest build this week and rerun overnight to > generate data but the analysis will be very very fast since I can now > just dump log

Re: [Flexwiki-users] DenyRead and WikiTalk

> I'm not sure what the 1000x exception rule of thumb is An exception is roughly 1000x as slow as "normal" flow control statements. So the general rule of thumb is that if the exception is likely to occur more than one in a thousand times you perform an operation, you might want to consider a norm

Re: [Flexwiki-users] DenyRead and WikiTalk

> Adding HasPermission check to avoid this issue would mean changing the > way the AuthorizationProvider::TextReaderForTopic behaves. Instead of > using the AssertTopicPermission, which creates the > FlexWikiAuthorizationException if the call to HasPermission fails, > there would just be a call to

Re: [Flexwiki-users] DenyRead and WikiTalk

> You're right about catch being expensive. It appears to use an > additional 40 - 60 ms. the good news is that it is not a percentage so > the added time on long running pages is sometimes on the lower end. > > If there is any other way I would use it, but the code that throws the > FlexWikiAutho

Re: [Flexwiki-users] DenyRead and WikiTalk

> I think the correct behavior should be that when the WikiTalk finds it > is not able to read a Topic it should ignore that particular Topic, > rather than return an error that stops the process. So, thinking about it a little more, I'm not sure whether this will work or not. Hopefully so, but le

Re: [Flexwiki-users] DenyRead and WikiTalk

> I think the correct behavior should be that when the WikiTalk finds it > is not able to read a Topic it should ignore that particular Topic, > rather than return an error that stops the process. Yeah, I had to make pretty much exactly this change several other places in the web app. In the absen

[Flexwiki-users] BUG 1797801

I just checked in a fix for bug 1797801 Arbitrary namespace parameters cause error. This will allow people to add arbitrary properties to namespace providers, which is useful for doing things like turni

Re: [Flexwiki-users] ASP error: Parser Error Message: Unrecognized configuration section 'mailSettings'

One more thing. If you obtained your copy of FlexWiki from the SourceForge site, then I’d recommend upgrading to the latest version available from http://builds.flexwiki.com instead. Much faster, more stable, has fewer bugs, and looks prettier. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]

Re: [Flexwiki-users] ASP error: Parser Error Message: Unrecognized configuration section 'mailSettings'

So, the wiki page largely describes how to set up FlexWiki 1.8. You’re setting up FlexWiki 2.0, and things have changed slightly. Here’s what you need to do: 1) It’s the Namespaces folder, not the WikiBases folder under 2.0. 2) You need to set the ASP.NET version to 2.0. Obviously,

Re: [Flexwiki-users] Performance Test Results

> One thing that should happen with declaring a RC is that flexwiki.com > should be upgraded to run the 2.0 RC distribution. The the log4net > logs need to be monitored for a while to determine if there are any > major errors not discovered through testing. +1. > I am not sure how we do the mon

[Flexwiki-users] Performance Test Results

OK, I ran the full flexwiki.com corpus tests against the latest build last night. Here are the results: . As I've said before, it's pretty hard to give a single number to the performance, since some pages are faster and some are slower. . Average page execution time in FlexWi

[Flexwiki-users] FlexWiki 2.0 Performance

I just checked in some more changes. And I think this is the last of the easy hits I can do. What I've done is add a per-request cache. You use it like this [1], although I've already added it in the one place where it makes the most sense (default.aspx/DoPage). I added the code so that the authori

Re: [Flexwiki-users] Admin Page Feature Request

Yeah, I think your first step needs to be to add this line [1]. Without digging into it further (sorry - been meaning to do this, but haven't had time for anything FlexWiki in the last week or so), I'm guessing what's happening is once you put in the DenyEdit for authenticated users, the call to ad

Re: [Flexwiki-users] XslTransform in ClassicBehavior (used for external RSS)

> Another alternative I was thinking about, was to move the settings > into their own dll. That would give a higher degree of separation from > the web app add maybe get us towards where Craig wants to go by having > the settings editable within the wiki while at the same time meeting > David's req

Re: [Flexwiki-users] Holding Your Breath

Well, we've heard a bit from him, but the numbers are all preliminary. I can tell you from experience it takes quite a while to run a full test, and I only checked in the latest optimizations a couple days ago. Quite honestly, because of the optimizations the previous tests aren't very interesting

Re: [Flexwiki-users] Very early performance info for //wiki

> > * Based on these statistics, would you or would you not upgrade the > > wiki to > > 2.0? Or is it too early to tell? > > I wouldn't do it yet. Having pages that are ten times slower is just > beyond reasonable. While it's a small percentage of the corpus, for > the people that use those page

Re: [Flexwiki-users] Very early performance info for //wiki

Very interesting data indeed! I'm not at all surprised to see that response times are slower on the first hit - there's a fair amount of I/O while the cache is being populated, and 2.0 does more I/O in general than 1.8 due to the rearchitecture. A couple of things: * Based on these statistics,

Re: [Flexwiki-users] CSS Feature Request

ow errors (or are at least ignored). Then if we added other output forms it would be possible to have them declare they couldn't handle such "output-format-specific" namespaces. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Craig Andera Sent: Monday, Septembe

Re: [Flexwiki-users] Admin Page Feature Request

> is there a way that we can set who can just "edit" the > _ContentBaseDefinition topic without affecting the other topics under a > particular namespace? AllowManageNamespace and DenyManageNamespace define who can edit _ContentBaseDefinition (as well as who can lock and unlock topics whenever we

[Flexwiki-users] FlexWiki 2.0 Performance

OK, I just checked in my changes. These include a few things: . The major performance enhancement to BELArray.SortBy. This should make DarrenSQLIS and a few other problematic topics *much* *much* faster. . Caching for a namespace Exists call. This turns out to be fairly impor

[Flexwiki-users] CSS Feature Request

I have a feature request. I'd implement this myself, but I'm really trying to resist the temptation to hare off and add features when I ought to be spending time working on performance. I think the recent comment that CSS control could be better is correct. The work that Derek has done recentl

Re: [Flexwiki-users] Admin Page Feature Request

> so leave that file and have > [2] in the EditProvider.aspx.cs... and this solves my problem... i can > now get the loaded connection string (from flexwiki.config file)... > then hid the field for the connection string and have it set to the > DefaultedConnectionString value :) OK, glad you figur

[Flexwiki-users] Performance

I rewrote BELArray.SortBy. That problematic topic DarrenSQLIS went from a typical cached render time of about 35 seconds to a typical cached render time of about 3 seconds. :) I'm over my allotted FlexWiki time for today, so I'll get this checked in tomorrow. I'll have to rerun all the problema

Re: [Flexwiki-users] Admin Page Feature Request

OK, finally getting back to this. Sorry for the delay. I can definitely see the problem with this code fragment [4] - it's that you're creating a new, empty FederationConfiguration and then trying to read parameters from it. You want to get the one that FlexWiki has already loaded. But if all y

Re: [Flexwiki-users] Documentation idea

> The problem here as David points out, is that of allowing new input and > how to incorporate that into the collected 'truth'. As a suggestion, it would not be difficult to diff what is in the distribution and what is on flexwiki.com. Assuming we release the latest build on flexwiki.com a more of

Re: [Flexwiki-users] Admin Page Feature Request

Sorry it has taken so long - I will look at this today. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Helen Ersando Sent: Tuesday, September 11, 2007 9:47 PM To: FlexWiki Users Mailing List Subject: Re: [Flexwiki-users] Admin Page Feature Request this is the fragment:

Re: [Flexwiki-users] Access to Rename Functionality

> In this discussion, I think there are two capabilities that are not > being clearly distinguished. > > First, there's the ability to rename a single page. Second, there's > the ability when you rename a single page to have the system go find > all the references to that page and change them to

Re: [Flexwiki-users] Documentation idea

> I don't believe marking the documentation with properties such as > these will cause any issue with operating as you suggest. This would > allow us to have one body of documentation in SVN and make it clear if > the documentation applies. > > Additionally if a new feature is added then after rel

  1   2   3   4   5   >