| Author | Messages | |
Terp
Posts:80
| | 09/22/2007 5:35 PM |
| John, I never played with the DNN site map, as I've been using a site to index my site and create an XML site map that I upload to Google via the Webmaster Tool interface. However, after noticing the sitemap.aspx file in the root of my install, I decided to check it out...and my site map is blank?!? I went to http://www.snapsis.com/sitemap.aspx and yours displays properly, of course. :) Is there a setting I have to toggle to get this joker to work? Given the way in which I have been updating my sitemap and further giving that I am still adding pages/content and moving everything along, I was thinking that pointing Google to this file would be most efficient for now. | | | |
| |
| John Mitchell
Posts:3085
| | 09/22/2007 6:10 PM |
| If you are using PageBlaster then you need to exclude the SiteMap since it is an XML output. I have a pattern that looks like this path pattern="\.axd|\.asxh|rss|fck|LinkClick|Cart|Install|thumb|sitemap" excludeFrom="All" | | | |
| Terp
Posts:80
| | 09/22/2007 6:30 PM |
| Sadly, I haven't had a chance to play with PB yet, but I assume that would go in the snapsis.pageblaster.config file somewhere and would be automatically inserted wherever it goes if I enter the parameters into the module? :) Here's what I did: 
Does that look right? ...need to learn the syntax, I guess. I didn't use the quotes, but figured they are added once written to wherever it goes. :) | | | |
| Terp
Posts:80
| | 09/22/2007 6:34 PM |
| Okay, I read the "...set THIS page to be excluded..." and think I have to enter this manually. I'll look to see where the rule I created was written and go from there.... {edit} Appears to have been written to the config generically and not page specific, so although it says "this page," the rule applies to all pages? Looks like it went it okay, except it put the pattern in as a parenthetical..not sure if this matters, but I removed them to mimic what you entered above...still no dice and my host settings won't display, so perhaps I have something wrong here. path pattern="(\.asmx|\.axd|\.asxh|rss|fck|admin|install|thumb|wizard|cart"excludeFrom="All" | | | |
| John Mitchell
Posts:3085
| | 09/22/2007 8:01 PM |
| Sorry, I should have been more clear. The SiteMap.aspx page is seperate from the "normal" DotNetNuke content pages, and doesn't allow you to add a modules, so you have to exclude it in the main Snapsis.PageBlaster.Config file (the one in the root of your website).
The module configuration you show above is for sepecific virtual pages (tabid=nn) and those excludes only work on the specific page you add it to.
The exclude pattern I posted above is from the main Snapsis.PageBlaster.config which allows you to add exclude rules that will affect every page in your website. | | | |
| Terp
Posts:80
| | 09/22/2007 8:14 PM |
| Posted By John Mitchell on 09/22/2007 8:01 PM
Sorry, I should have been more clear. The SiteMap.aspx page is seperate from the "normal" DotNetNuke content pages, and doesn't allow you to add a modules, so you have to exclude it in the main Snapsis.PageBlaster.Config file (the one in the root of your website).
The module configuration you show above is for sepecific virtual pages (tabid=nn) and those excludes only work on the specific page you add it to.
The exclude pattern I posted above is from the main Snapsis.PageBlaster.config which allows you to add exclude rules that will affect every page in your website.
No, no, no, you were clear, John. Thanks; I am the one who is confused. :)
While I did add the pattern in the module on a specific page and it states that it is for a specific page, when I looked in the snapsis.pageblaster.config, it went in under the ExcludePaths section and inserted the path pattern as posted above. I do not see anything that would suggest it is page-specific. That's why I am confused. :) | | | |
| John Mitchell
Posts:3085
| | 09/22/2007 8:24 PM |
| The excldePath in the main config works by comparing the Url to the pattern. So any Url with "sitemap" in it will be excluded, and the will keep PageBlaster from interferring with the output of http://www.yoursite.com/SiteMap.aspx
That same pattern also exclides all urls that have .axd, .asxh, rss, fck, admin, etc. | | | |
| Terp
Posts:80
| | 09/22/2007 8:48 PM |
| Posted By John Mitchell on 09/22/2007 8:24 PM
The excldePath in the main config works by comparing the Url to the pattern. So any Url with "sitemap" in it will be excluded, and the will keep PageBlaster from interferring with the output of http://www.yoursite.com/SiteMap.aspx
That same pattern also exclides all urls that have .axd, .asxh, rss, fck, admin, etc.
Right, I am totally following you on this and understand exactly what you are saying. What's confusing me is that you mentioned:
"The module configuration you show above is for sepecific virtual pages (tabid=nn) and those excludes only work on the specific page you add it to." Yet when I did it using the module, it went into the snapsis.pageblaster.config file generically under the excludepath section, right where I would have added it if I did it manually as you suggested. Given that I used the module to insert it on a particular page, I thought it would show an entry in the PB config with a path or something more page specific. Does that make sense? I used the module and no tabid or anything was attached to the path pattern...came out just as you typed it in the firt post. :) I swear I am not as dumb as I must sound, John. :) | | | |
| John Mitchell
Posts:3085
| | 09/22/2007 10:06 PM |
| Ok, the reason I wasn't following you is because that should not have happened. If you use a module on a page then it updates its own config file in DesktopModules/Snapsis/PageBlaster/Config/PageRules.
Maybe you thought it had updated the main config file in the root because that exclude pattern was already in there. | | | |
| Terp
Posts:80
| | 09/22/2007 10:24 PM |
| Posted By John Mitchell on 09/22/2007 10:06 PM
... because that exclude pattern was already in there.
lol
| | | |
| Terp
Posts:80
| | 09/29/2007 5:27 PM |
| Posted By John Mitchell on 09/22/2007 6:10 PM If you are using PageBlaster then you need to exclude the SiteMap since it is an XML output. I have a pattern that looks like this path pattern="\.axd|\.asxh|rss|fck|LinkClick|Cart|Install|thumb|sitemap" excludeFrom="All"
John, I took a week off to ensure that it wasn't the sleep deprivation that caused me to space on this one, but I am still confused. 
I thought you suggested that I would need to add the aforementioned path pattern to the snapsis config, though in a subsequent post you mentioned that it is already in there. It is, in fact, already in there as posted above, so I was confused when you said I need to put it in there, given that it ships in there as posted above. ;) I was just going to leave it, as I have been using an XML sitemap generator, but I also notice that my host --> host settings page is blank, too, so I am assuming it is a related issue and needs to somehow be added to the pattern (that's already in there). :) | | | |
| John Mitchell
Posts:3085
| | 09/29/2007 6:54 PM |
| When we first started this thread I didn't know if you had that entry in your config file. It's not something that I put in as default until the most recent version, and you may have taken it out.
I don't know what may be the problem with the Host Settings page, but I don't think it is related. | | | |
| Terp
Posts:80
| | 09/29/2007 7:29 PM |
| Gotcha! :) You can imagine the look on my face when I tried to work through the logic...you need to put the path pattern in...then you told me it was already in there...so I've been scratching my head trying to figure this out. ;) I just got PB a couple weeks ago, so now it all makes sense. Even with it in there, however, the sitemap doesn't work still, but not a show-stopper, as I don't really use it, though was considering it. I thought perhaps I needed to add the host settings in the pattern, too, given that it, too, displays a blank page. I'll post over in the other forums asking about the host settings issues...all pages in the host menu work EXCEPT the settings, so it makes sense that this is not PB related. | | | |
| John Mitchell
Posts:3085
| | 09/29/2007 9:26 PM |
| It sounds like you may have the core compression module still in use, but I would think that you would have more problems if that were the case.
Make sure the core compression is not in the web.config httpmodules list.
You can also try disabling PageBlaster and see if things work normally. That will help to narrow down where the problem is. | | | |
| Terp
Posts:80
| | 09/29/2007 9:41 PM |
| Good call, John. I can just pull out the pageblaser config file without breaking anything? I'll give that a shot. :) I believe I removed all the core compression junk, to include the .dll files... <addname="PageBlaster"type="Snapsis.HttpModules.PageBlaster.PageBlasterModule, Snapsis.HttpModules.PageBlaster"/><addname="UrlRewrite"type="DotNetNuke.HttpModules.UrlRewriteModule, DotNetNuke.HttpModules.UrlRewrite"/><addname="Exception"type="DotNetNuke.HttpModules.ExceptionModule, DotNetNuke.HttpModules.Exception"/><addname="UsersOnline"type="DotNetNuke.HttpModules.UsersOnlineModule, DotNetNuke.HttpModules.UsersOnline"/><addname="DNNMembership"type="DotNetNuke.HttpModules.DNNMembershipModule, DotNetNuke.HttpModules.DNNMembership"/><addname="Personalization"type="DotNetNuke.HttpModules.PersonalizationModule, DotNetNuke.HttpModules.Personalization"/><addname="ScriptModule"type="System.Web.Handlers.ScriptModule, System.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=xxxxxxxxx"/>
Off-topic, but I don't remember that script module and the publictoken in there before. Any ideas what that joker does? :) | | | |
| John Mitchell
Posts:3085
| | 09/29/2007 10:30 PM |
| Oh, the script module is new. It needs to be moved up to the top of the list, and PageBlaster should be after it. That may be the whole problem.
To disable PageBlaster you need to remove it from the Web.config. If you only remove the Snapsis.PageBlaster.Config file you'll get an error. | | | |
| Terp
Posts:80
| | 09/30/2007 12:02 AM |
| Okay, I can rule out PB...removed the line from the web.config and still no sitemap or more importantly no host settings. I moved the other line up above the PB line, too, but no dice. I posted in the DNN forums, so I'll see if someone else has had similar issues... | | | |
| Terp
Posts:80
| | 09/30/2007 12:10 AM |
| They nailed this error message: "Error: Host Settings is currently unavailable." :) If I had to guess, i would say that when I removed the filter line in the same http section (I was going to use PB filter instead), it somehow impacts the host settings, as I had some IPs in there under a rule yet no filter line in the web.config? Am I getting warmer? :) AssemblyVersion: 04.05.05
PortalID: 0
UserID: 1
UserName: host
ActiveTabID: 16
ActiveTabName: Host Settings
RawURL: /Host/Host Settings/tabid/16/portalid/0/Default.aspx
AbsoluteURL: /Default.aspx
UserAgent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; SU 3.005; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
InnerException: Error: Host Settings is currently unavailable.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: System.Web.Compilation.BuildManager.PostProcessFoundBuildResult
StackTrace:
Message: DotNetNuke.Services.Exceptions.ModuleLoadException: Error: Host Settings is currently unavailable. ---> System.Exception: E:\xxx\httpdocs\admin\Host\RequestFilters.ascx.vb(45): error BC30002: Type 'RequestFilterRule' is not defined. ---> System.Web.HttpCompileException: E:\xxx\httpdocs\admin\Host\RequestFilters.ascx.vb(45): error BC30002: Type 'RequestFilterRule' is not defined. at System.Web.Compilation.BuildManager.PostProcessFoundBuildResult(BuildResult result, Boolean keyFromVPP, VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetBuildResultFromCacheInternal(String cacheKey, Boolean keyFromVPP, VirtualPath virtualPath, Int64 hashCode) at System.Web.Compilation.BuildManager.GetVPathBuildResultFromCacheInternal(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.BaseTemplateParser.GetReferencedType(VirtualPath virtualPath, Boolean allowNoCompile) at System.Web.UI.BaseTemplateParser.GetUserControlType(VirtualPath virtualPath) at System.Web.UI.MainTagNameToTypeMapper.ProcessUserControlRegistration(UserControlRegisterEntry ucRegisterEntry) at System.Web.UI.BaseTemplateParser.ProcessDirective(String directiveName, IDictionary directive) at System.Web.UI.TemplateControlParser.ProcessDirective(String directiveName, IDictionary directive) at System.Web.UI.TemplateParser.ParseStringInternal(String text, Encoding fileEncoding) --- End of inner exception stack trace --- at System.Web.UI.TemplateParser.ProcessException(Exception ex) at System.Web.UI.TemplateParser.ParseStringInternal(String text, Encoding fileEncoding) at System.Web.UI.TemplateParser.ParseString(String text, VirtualPath virtualPath, Encoding fileEncoding) at System.Web.UI.TemplateParser.ParseFile(String physicalPath, VirtualPath virtualPath) at System.Web.UI.TemplateParser.ParseInternal() at System.Web.UI.TemplateParser.Parse() at System.Web.Compilation.BaseTemplateBuildProvider.get_CodeCompilerType() at System.Web.Compilation.BuildProvider.GetCompilerTypeFromBuildProvider(BuildProvider buildProvider) at System.Web.Compilation.BuildProvidersCompiler.ProcessBuildProviders() at System.Web.Compilation.BuildProvidersCompiler.PerformBuild() at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at DotNetNuke.UI.Skins.Skin.InjectModule(Control objPane, ModuleInfo objModule, PortalSettings PortalSettings) --- End of inner exception stack trace --- at DotNetNuke.Services.Exceptions.Exceptions.ProcessModuleLoadException(String FriendlyMessage, PortalModuleBase ctrlModule, Exception exc, Boolean DisplayErrorMessage) at DotNetNuke.Services.Exceptions.Exceptions.ProcessModuleLoadException(PortalModuleBase ctrlModule, Exception exc) at DotNetNuke.UI.Skins.Skin.InjectModule(Control objPane, ModuleInfo objModule, PortalSettings PortalSettings)
Source:
| | | |
| Terp
Posts:80
| | 09/30/2007 12:29 AM |
| I'm thinking I need to drop the http compression back in, add the request filter line to the web.config, hopefully gain access to the host settings, then remove the request filter rules, then remove the line in the web.config and the compression file from the /bin folder. Sound like a plan? I tried just adding the line to the web.config, but after the site returned application errors, I figured out I removed the compression file. ;) I would try it without asking, but given the conflict with PB, I am not sure if I will screw something up, so want to check before I run loose in the bin folder. :) | | | |
| John Mitchell
Posts:3085
| | 09/30/2007 8:51 AM |
| Yes, if you have configured the request filter then you will need to put the dll back and add it back in the web.config.
You'll just need to make sure the compression is disabled. | | | |
|
|