Nov 21, 2008, 08:26 AM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
Search via SMF or Google: modx forums all of modxcms.com web
  MODxCMS.com   Forums   Help Login Register  
Pages: 1 ... 10 11 [12]   Go Down
  Print  
Author Topic: Support/Comments for sitemap  (Read 36819 times)
0 Members and 1 Guest are viewing this topic.
markg
Full Member
***
Posts: 238


« Reply #165 on: Oct 01, 2008, 10:51 PM »

OK,

will answer my own question here.

Despite turning off TinyMCE for this document it kept putting in <p> tags everytime I saved it. (Those of you used to Tiny MCE will well know the problems it causes.)

Anyway, what I did as a work around was create a new template (called empty) and placed the call in there.

Then, in the document I just left it completely blank. Voila, I now have an unstyled xml file.

Logged
bmilton
Jr. Member
*
Posts: 20



WWW
« Reply #166 on: Oct 02, 2008, 05:11 PM »

Hi,

I think that this Sitemap tool is really useful, but I've discovered a problem.  It does not co-exist well with a site that is using the SEO Strict URL plug-in.  Since both tools are tailored towards SEO enthusiasts, I think it is likely that someone will try to use both on their site.

Here's the deal...The SEO Strict URL plugin is re-writing all of the URLs.  So for example on my site I like the look of base name only with no extension.

I prefer: http://seoconductor.com/about
and not: http://seoconductor.com/about.html

So, in my sitemap I want all of my important pages to be listed just as I am presenting them to the public (without the extension). 

The problem is that while I am presenting them without extension to the public, the Sitemap plug-in is unaware of the rewrite that is being done by the Strict URL plug-in.  The result is that it lists all of the documents in the sitemap with .html extension.  Then when googlebot looks at the sitemap it will find that every single URL in the sitemap is being is being 301 redirected and complain.

I found a temp workaround for this if you want to use Base Name and the Sitemap Snippet:
1.  Turn off the "Suffix for URLs" setting in Modx Config.  I.E. clear the ".html" setting.
2.  Configure your docs to use "Base Name" via the Strict URL plug-in.

This isn't ideal though, because you won't be able to utilize the SEO Strict Override TV to "append extension" for select documents.  What happens is it will have nothing to append since it takes this extension from the MODX "Suffix For URL" setting that we already cleared.  In this case I found another workaround...for the specific doc that you need to have the extension just change the doc alias such that it has .html at the end.

What I'd love to see is a way to make these two plug-ins more aware of each other. Over time I tend to forget all these workarounds I put in place.

Is there any way to code the sitemap snippet to check for the SEO Strict configuration before appending a doc to the sitemap?

Thanks,
-Brian


Logged

Brian Milton
Owner/Campaign Manager

SEO conductor
- We offer comprehensive SEO campaign management.
By orchestrating all aspects of your website, we provide a coordinated and quality effort that ensures success.
tkfm
Committed to MODx
*****
Posts: 608


WWW
« Reply #167 on: Oct 02, 2008, 07:35 PM »

I think this happens when '(blank)' template is used for the sitemap document.

I made a new template which contains only [*content*] and attached seoOverride TV to that simple template.
If you set that template to your sitemap document, URL rewriting of SEO Strict plugin works.
Logged
bmilton
Jr. Member
*
Posts: 20



WWW
« Reply #168 on: Oct 02, 2008, 08:27 PM »

Hey tkfm,

I'm not sure I follow or maybe we are talking about different things.

I also have a template just for the Sitemap.xml doc called "Sitemap".  This template only contains the line [*content*] like you said.

Can you clarify what you mean when you say:
I made a new template which contains only [*content*] and attached seoOverride TV to that simple template.

When you say attached SeoOverride TV to that template do you mean as an "Assigned Template Variable" ?  I've also done that.

When you say that "rewriting of SEO strict plugin works" do you mean that you are able to examine the resulting sitemap.xml file that is generated for the site and each URL listed in the sitemap reflects the proper setting for the corresponding document's SeoOverride TV?  That doesn't happen for me.  Every single URL generated uses the Friendly URL config that would appear without SEO Strict being installed. In my case it means every URL has a .html extension regardless of the SeoOverride setting.

-Brian
Logged

Brian Milton
Owner/Campaign Manager

SEO conductor
- We offer comprehensive SEO campaign management.
By orchestrating all aspects of your website, we provide a coordinated and quality effort that ensures success.
tkfm
Committed to MODx
*****
Posts: 608


WWW
« Reply #169 on: Oct 02, 2008, 08:36 PM »

When you say attached SeoOverride TV to that template do you mean as an "Assigned Template Variable" ?  I've also done that.
Sorry for my bad English, I meant 'Assign seoOverride TV to that new template' as you already did.

Quote
When you say that "rewriting of SEO strict plugin works" do you mean that you are able to examine the resulting sitemap.xml file that is generated for the site and each URL listed in the sitemap reflects the proper setting for the corresponding document's SeoOverride TV?
Yes. I am not doing so complicated URL rewriting, but seoOverride TV's value seems to be effected in the output of sitemap snippet.
But as I wrote at the following thread, I slightly changed URL rewriting rule of SEO Strict URL plungin.
I think that it's the only difference between us...
http://modxcms.com/forums/index.php/topic,12452.msg178032.html#msg178032
Logged
Pages: 1 ... 10 11 [12]   Go Up
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP

Copyright © 2005-2008 MODxCMS, All rights reserved. Contact Us
Styles by ziworks.com

Powered by SMF 1.1.4 | SMF © 2005, Simple Machines LLC

Valid XHTML 1.0! Valid CSS!