#183 FlexWiki.Web.LastModified.DoSearch() Exception Randomly

[Steve Novoselac]

On what seems like is random, the recent changes link
throws this error. Some time later, it seems to work
out of no where again.

FlexWiki.Web.LastModified.DoSearch()

[NullReferenceException: Object reference not set to an
instance of an object.]
FlexWiki.Web.LastModified.DoSearch() in
c:\Builds\ccnet\server\flexwikicore\build\FlexWiki.Web\LastModified.aspx.cs:103

_ASP.LastModified_aspx.__Render__control1(HtmlTextWriter
__output, Control parameterContainer) +105
System.Web.UI.Control.RenderChildren(HtmlTextWriter
writer) +27
System.Web.UI.Control.Render(HtmlTextWriter writer) +7
System.Web.UI.Control.RenderControl(HtmlTextWriter
writer) +243
System.Web.UI.Page.ProcessRequestMain() +1926

[Craig Andera]

Logged In: YES
user_id=879696

What version are you running?

[Steve Novoselac]

Logged In: YES
user_id=1427513

Version 1.8.0.1696

Also happened in a previous version we were running.

[Craig Andera]

Logged In: YES
user_id=879696

Ugh, I can see we've been horribly delinquent on responding
to this one.

Can you try the latest interim build, available at
http://builds.flexwiki.com/?

[Steve Novoselac]

Logged In: YES
user_id=1427513

any timeline on this? it pretty much makes the wiki unusable
without recent changes

[Craig Andera]

Logged In: YES
user_id=879696

Repeat: can you try the latest interim build, available at
http://builds.flexwiki.com?

[Steve Novoselac]

Logged In: YES
user_id=1427513

ok, updated to build 1730 - I will let you know if I see
the exception again.

[Craig Andera]

Logged In: YES
user_id=879696

Excellent, thanks. I'm changing the status of the bug to
pending. We'll reopen it if you still encounter the error.

[Steve Novoselac]

Logged In: YES
user_id=1427513

hmm, bad news: happened again

[NullReferenceException: Object reference not set to an
instance of an object.]
FlexWiki.Web.LastModified.DoSearch() in
c:\Builds\ccnet\server\flexwikicore-18\build\FlexWiki.Web\LastModified.aspx.cs:103
_ASP.LastModified_aspx.__Render__control1(HtmlTextWriter
__output, Control parameterContainer) +105
System.Web.UI.Control.RenderChildren(HtmlTextWriter
writer) +27
System.Web.UI.Control.Render(HtmlTextWriter writer) +7
System.Web.UI.Control.RenderControl(HtmlTextWriter
writer) +243
System.Web.UI.Page.ProcessRequestMain() +1926

[Craig Andera]

Logged In: YES
user_id=879696

Blah. This looks like a caching bug. I'm not sure I can fix
this - the caching code is pretty complex, and I'm working
heavily on replacing it.

What I can do easily is to make the error message more
friendly. Would that suffice? Basically, I'm asking what
your second choice after "Make the problem go away" is.

[Steve Novoselac]

Logged In: YES
user_id=1427513

well, if it is caching, can you just catch the exception and
put a button/link to clear the cache? I guess I dont know if
that will work since I went to the admin area and cleared it
and I still get the error, but if i do an iisreset it works
again - but you are right, looks like a caching issue.

[Craig Andera]

Logged In: YES
user_id=879696

If you've tried clearing the cache, then adding a button to
do it won't help at all. If it requires resetting IIS, the
obviously we don't really want to expose that functionality
through the user interface at all (security).

My inclination at this point is to table the bug. The code
is changing a lot in the 2.0 release, although I realize
that doesn't help you much right now. If you have a
suggestion for something easier than a true fix, I'd be
happy to consider incorporating it.

Sorry - I know this isn't a great answer.