|
Reply
SelArom,
7/15/2008 9:51:27 PM
I have a blogs pagegroup on my site like site.com/blog.aspx where blogs.aspx is a page group linking to site.com/blog/default.aspx. the problem is if I go to site.com/blog, it's redirecting instead to site.com/blog/default.aspx404;http://localhost/blog.
now I know that this was a bug reported before, but this seems like a different issue because although normally, even though it appends this incorrectly, the page still loads. however it looks like the controls on that page are being affected and throwing null reference errors...
I have these controls on the page: blogposts, categories (Blogs provider), calendar control, and blog archive controls. this is the error I get:
Object reference not set to an instance of an object. 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.NullReferenceException: Object reference not set to an instance of an object.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. |
Stack Trace:
[NullReferenceException: Object reference not set to an instance of an object.]
Telerik.Web.HttpUrlQuery.Contains(String Name) +26
Telerik.Web.HttpUrlQuery.Set(String Name, String NewValue, Boolean UrlEncode) +56
Telerik.Web.HttpUrlQuery..ctor(NameValueCollection QueryString, Boolean UrlEncode) +204
Telerik.Web.HttpUrlQuery.get_Current() +47
Telerik.Cms.Engine.WebControls.ContentArchive.CreateArchiveItemValue(Int32 year, Int32 month) +15
Telerik.Cms.Engine.WebControls.ContentArchive.BindArchive(ListControl list) +674
Telerik.Cms.Engine.WebControls.ContentArchive.CreateChildControls() +482
System.Web.UI.Control.EnsureChildControls() +87
System.Web.UI.Control.PreRenderRecursiveInternal() +50
System.Web.UI.Control.PreRenderRecursiveInternal() +170
System.Web.UI.Control.PreRenderRecursiveInternal() +170
System.Web.UI.Control.PreRenderRecursiveInternal() +170
System.Web.UI.Control.PreRenderRecursiveInternal() +170
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2041
|
|
|
Reply
,
7/18/2008 6:10:08 AM
Hello SelArom,
You are right that we had similar known issue which was returning the same exception, but we think that this time the case is a bit different. Can you please provide us with live link where we can observe this behavior and troubleshoot this further. Also, it would be really helpful if you can elaborate on the exact scenario, defined in the project's web.config for displaying a 404 error message.
Thank you for your time.
Regards,
Nikifor
the Telerik team
|
|
Reply
SelArom,
7/18/2008 8:55:57 AM
i don't have a link I can publish publicly, will attach info in a bug report in myclient.net, thanks!
|
|
Reply
,
7/21/2008 9:26:31 AM
Hello SelArom,
Thank you for the elaboration.
This problems is caused by a bug in the CMS and is related to adding
Extensionless URL in the project. We have already included this in the
list of bugs scheduled for fixing in the next release, so this issue
would be addressed as soon as possible.
Please accept our apologies for the caused inconvenience.
Sincerely yours,
Nikifor
the Telerik team
|
|
Reply
SelArom,
7/21/2008 9:28:49 AM
thank you for following up, is this going to be a full release (like 4.0 or even 3.3 or something) or a hotfix? or maybe just some kind of workaround? because this is going to cause problems on our live site and we may not be able to wait that long. we'll need some kind of solution to avoid showing our visitors these errors!
thanks
|
|
Reply
,
7/22/2008 10:27:33 AM
Hello SelArom,
We made further investigation of this issue, and when we examined the provided link with the HTTPWatch program we started suspecting a misconfiguration in the IIS for probable cause of this problem. This is why it would be really helpful if you can export the configuration of your Website and send it to us through the support thread. To export the file please do the following:
1. Right click on the Website and choose All Tasks;
2. Choose Save configuration to a file and place it in the appropriate destination.
Thank you for your assistance.
Sincerely yours,
Nikifor
the Telerik team
|
|
Reply
SelArom,
7/22/2008 10:31:54 AM
are there different instructions for iis 7? because I'm running vista on my development machine and i don't see that option "All Tasks".
I will do this for the production site, however, which is on iis 6 and attach it to the support ticket.
|
|
Reply
,
7/24/2008 8:03:57 AM
Hello SelArom,
It seems that the problem is more complicated than
we thought and we would not be able to provide a temporary workaround.
The discovered bug seems to be provoked by regression in the source code or something similar.
We suggest you try to using wildcard mapping instead of the Extensionless
URLs so that each request would be redirected through this mapping.
We apologize for any inconvenience caused.
Regards,
Nikifor
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
|
|
Reply
Zack,
7/28/2008 6:33:28 PM
Nikifor,
As a programmer I certainly appreciate the complexity of software development, however in this situation I think Telerik owes its customers a better response.
This bug is already causing us issues with our analytics and has the potential to do the same with our rankings in various search engines as well.
I understand the wildcard mapping may in fact solve this problem but it adds processing overhead to each request on our web servers, not to mention the configuration hassle.
I hope that Telerik will make this a priority issue and fix this bug ASAP.
Zack
|
|
Reply
,
7/30/2008 9:38:23 AM
Hello Zack,
Please, excuse us for the inconvenience caused.
We continued this thread on a private support ticket and did not update this thread. We apologize for that.
Just to clarify, the problem was sent to the development team for fixing.
We try to provide a solution in the coming release.
Greetings,
Nikifor
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
|
|
Reply
Zack,
11/6/2008 5:21:50 PM
Nikifor,
Has this issue been resolved in 3.5 or the subsequent service pack? I'm hoping that I don't have to wait until 4.0 for a resolution to this issue... ;-)
Thanks,
Zack
|
|
Reply
,
11/7/2008 2:22:18 AM
Hello Zack,
Yes, we confirm that this error is fixed in Sitefinity 3.5.
Best wishes,
Georgi
the Telerik team
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
|