Just thought I'd check. I'm seeing lots of these errors in the trace log when running from VS2013:
SEOChecker: Error in HttpModule for url rewriting System.UriFormatException: Invalid URI: The hostname could not be parsed. at System.Uri.CreateThis(String uri, Boolean dontEscape, UriKind uriKind) at System.Uri..ctor(String uriString) at System.UriBuilder.get_Uri() at SEOChecker.Core.Extensions.UrlBuilderExtensions.ToUri(UrlBuilder builder) at SEOChecker.Core.Extensions.HttpContextExtensions.RawUri(HttpContext context) at SEOChecker.Core.Extensions.HttpContextExtensions.RawUrl(HttpContext context) at SEOChecker.HttpModules.UrlModule.(Object , EventArgs )
A kind of multi-disciplinary approach, including a package update ;)
Also the usual lack of clear documentation with real-world examples to guide you through perfect storm of dynamic vs. strongly typed vs. vanilla vs. property convertor syntax. It's my personal dev nightmare to be honest.
Yes indeed sometimes the dynamic vs. strongly typed stuff can be a big source of confusion. I feel the same way and I think that it's something HQ are trying to improve in the future.
Lots of trace log errors on localhost
Just thought I'd check. I'm seeing lots of these errors in the trace log when running from VS2013:
I don't get them on the live server.
As I'm developing I'm also getting issues reading an Archetype that purports to be having problems with SEOChecker. Details in this issue: https://our.umbraco.org/projects/backoffice-extensions/archetype/sound-off!/62014-Accessing-Archetype-from-own-class (5th post refers).
Are these two issues connected?
Thanks,
Craig
Hi Craig
Just wondering if you have setup a local hostname on the rootnode in Umbraco when developing locally?
/Jan
Hi Jan,
it was finally resolved in this thread: https://our.umbraco.org/projects/backoffice-extensions/archetype/sound-off!/62014-Accessing-Archetype-from-own-class
A kind of multi-disciplinary approach, including a package update ;)
Also the usual lack of clear documentation with real-world examples to guide you through perfect storm of dynamic vs. strongly typed vs. vanilla vs. property convertor syntax. It's my personal dev nightmare to be honest.
Cheers,
Craig
Hi Craig
Aaah, ok - Good you figured it out :)
Yes indeed sometimes the dynamic vs. strongly typed stuff can be a big source of confusion. I feel the same way and I think that it's something HQ are trying to improve in the future.
Happy sunday mate!
/Jan
is working on a reply...