Jump to content
Pete

Module: XML Sitemap

Recommended Posts

I'm using the Markup Sitemap XML module to automatically generate a sitemap.xml file, and a custom template to add markup for images and exclude specific page templates.

I discovered that when I view the sitemap.xml in Chrome, it looks as how it was intended based on my custom template. But in Safari, the custom template is ignored and the sitemap.xml file that is generated is the equivalent of not using the custom template at all. In fact, when I delete the custom template from the server, both Safari and Chrome display the same sitemap.xml content.

My sitemap.xml file validates, so I'm confident that there isn't anything in my code that is causing the issue. Unfortunately, my submitted sitemap through Google Search Console is picking up the incorrect Safari version and generating errors for pages that aren't publicly viewable on the site.

Here is the url to the sitemap file:
https://processinteractive.com/sitemap.xml

Has anyone else experienced this issue? I'm not sure if there is a fix unless it is in the module itself.

 

Share this post


Link to post
Share on other sites

What do you mean with "custom template to add markup for images..."? The output is just XML. Why would one browser display another XML? That makes no sense.

Do you mean "if logged in as superuser I see another XML as when not logged in"?

Also, maybe you should have posted in the module support threads instead:

https://processwire.com/talk/topic/799-module-xml-sitemap/

https://processwire.com/talk/topic/3846-how-do-i-create-a-sitemapxml/

 

Share this post


Link to post
Share on other sites

@Lance O., are you using Markup Sitemap XML, which is the earlier module from Pete, or Markup Sitemap, which is a newer one developed by Mike Rockett?

As Dragan said above, you should always post module-specific questions to the existing support thread for that module. Let us know which module you're talking about, and I can merge this thread to the correct module-specific support thread.

Thanks!

Share this post


Link to post
Share on other sites

@gragan Ah, you are correct, the custom template for the sitemap.xml file is only displayed when I'm logged into PW. Good catch!

Sitemaps can support images to help them appear in Google Image search results:
https://support.google.com/webmasters/answer/178636?hl=en
https://www.xml-sitemaps.com/images-sitemap.html

Yes, maybe I should have searched for the module support thread instead of clicking on the broken link directly from the module itself:
http://processwire.com/talk/index.php/topic,867.0.html

Share this post


Link to post
Share on other sites

@teppo I was using Pete's Markup Sitemap XML, but apparently it has some bugs. I've installed Mike's Markup Sitemap module and it seems to have resolved the issues I was experiencing. I wish it had support for the image license, but otherwise feels like a nice update.

Edit: Looks like it does support image license.

Edit 2: But unfortunately it doesn't look like the image license is working correctly. I've reported the issue in that module's support thread:

 

  • Like 1

Share this post


Link to post
Share on other sites

I tried to install the module on my localhost and it worked great! Then I transferred the website to my real domain, but the links in the sitemap still direct to my localhost. can someone please help me. 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By eelkenet
      Hi! I've created a small Inputfield module called InputfieldFloatRange which allows you to use an HTML5 <input type="range" ../> slider as an InputField. I needed something like this for a project where the client needs to be able to tweak this value more based on 'a feeling' than just entering a boring old number. Maybe more people can use this so I'm hereby releasing it into the wild. 
      EDIT: You can now install it directly from the Modules directory: http://modules.processwire.com/modules/inputfield-float-range/
       
      What is it?
      The missing range slider Inputfield for Processwire. 
      What does it do?
      This module extends InputfieldFloat and allows you to use HTML5 range sliders for number fields in your templates.
      It includes a visible and editable value field, to override/tweak the value if required.  
      Features
      Min/max values Precision (number of decimals) Optional step value (Read more) Optional manual override of the selected value (will still adhere to the rules above) Configurable rounding of manually entered values (floor, round, ceil, disable) Usage
      Clone / zip repo Install FieldtypeFloatRange, this automatically installs the Inputfield Create new field of type `Float (range)` or convert an existing `Float`, `Integer` or `Text` field. To render the field's value simply echo `$page->field` Demo
      A field with Min=0, Max=1, Step=0.2, Precision=2

      Field with settings Min=0, Max=200, Step=0.25, Precision=2

       
      Todo
      Make the display-field's size configurable (will use the Input Size field setting)  Hopefully become redundant  
      Changelog
      005 (current version)
      - Fix bug where the Inputfield would not work properly within repeaters / repeater matrices
      004
      - Make rounding of manually entered values configurable (floor, round, ceil or disable)
      - Fix small JS bug when the value-display field was not displayed
      - Update README
      003
      - Code cleanup, add some ModuleInfo data & LICENSE
      - Submit to PW Modules directory (http://modules.processwire.com/modules/inputfield-float-range/)
      002
      - Fix issue where setting the step value to an empty value created problem with validation
      - Make the display-field optional
      001
      - Initial release
       
      Thanks!
       
       
    • By Gadgetto
      Status update links (inside this thread) for SnipWire development will be always posted here:
      2019-10-18
      2019-08-08
      2019-06-15
      2019-06-02
      2019-05-25
      If you are interested, you can test the current state of development:
      https://github.com/gadgetto/SnipWire
      Please note that the software is not yet intended for use in a production system (alpha version).
      If you like, you can also submit feature requests and suggestions for improvement. I also accept pull requests.
      ---- INITIAL POST FROM 2019-05-25 ----
      I wanted to let you know that I am currently working on a new ProcessWire module that fully integrates the Snipcart Shopping Cart System into ProcessWire. (this is a customer project, so I had to postpone the development of my other module GroupMailer).
      The new module SnipWire offers full integration of the Snipcart Shopping Cart System into ProcessWire.
      Here are some highlights:
      simple setup with (optional) pre-installed templates, product fields, sample products (quasi a complete shop system to get started immediately) store dashboard with all data from the snipcart system (no change to the snipcart dashboard itself required) Integrated REST API for controlling and querying snipcart data webhooks to trigger events from Snipcart (new order, new customer, etc.) multi currency support self-defined/configurable tax rates etc. Development is already well advanced and I plan to release the module in the next 2-3 months.
      I'm not sure yet if this will be a "Pro" module or if it will be made available for free.
      I would be grateful for suggestions and hints!
      (please have a look at the screenshots to get an idea what I'm talking about)
       




    • By Robin S
      Another little admin helper module...
      Template Field Widths
      Adds a "Field widths" field to Edit Template that allows you to quickly set the widths of inputfields in the template.

      Why?
      When setting up a new template or trying out different field layouts I find it a bit slow and tedious to have to open each field individually in a modal just to set the width. This module speeds up the process.
      Installation
      Install the Template Field Widths module.
      Config options
      You can set the default presentation of the "Field widths" field to collapsed or open. Field widths entered into the Template Field Widths inputfield are only applied if the Edit Template form is submitted with the Template Field Widths inputfield in an opened state. "Collapsed" is the recommended setting if you think you might also use core inputs for setting field widths in a template context. You can choose Name or Label as the primary identifier shown for the field. The unchosen alternative will become the title attribute shown on hover. You can choose to show the original field width next to the template context field width.  
      https://github.com/Toutouwai/TemplateFieldWidths
      https://modules.processwire.com/modules/template-field-widths/
    • By adrian
      Tracy Debugger for ProcessWire
      The ultimate “swiss army knife” debugging and development tool for the ProcessWire CMF/CMS

       
      Integrates and extends Nette's Tracy debugging tool and adds 35+ custom tools designed for effective ProcessWire debugging and lightning fast development
      The most comprehensive set of instructions and examples is available at: https://adrianbj.github.io/TracyDebugger
      Modules Directory: http://modules.processwire.com/modules/tracy-debugger/
      Github: https://github.com/adrianbj/TracyDebugger
      A big thanks to @tpr for introducing me to Tracy and for the idea for this module and for significant feedback, testing, and feature suggestions.
×
×
  • Create New...