SitemapXML v.2

[shags38]

Any thoughts been given to adding Image details to the XML Sitemaps?

See https://support.google.com/webmasters/answer/178636

Great question Lloyd !! - I asked a similar question maybe a couple of years back with no definitive response.

cheers,
Mike

[shags38]

v1.5.5f PHP 7.1

Images are not being submitted in the sitemap submissions, i.e. not showing as having been submitted in WMT. One remaining site I have that is still 1.5.1 the images are being submitted (sitemapxml v3.2.6).

So the question is has anything changed in sitemapxml version 3.2.9 that excludes images? or would PHP 7.1. have any effect? If not then where should I look to see why images are not being submitted? what file(s)? ... no myDEBUG error reports are generated.

thanks, Mike

[KGL Racing]

Hello,

i just installed the latest version of Sitemap XML, but when i go to tools/ Sitemap XML i only see an empty page with one button "upgrade SitemapXML SQL"
When i push this nothings happens and i don't get anything else.
Ant idea what to do to make this works?

[shags38]

Hello,

i just installed the latest version of Sitemap XML, but when i go to tools/ Sitemap XML i only see an empty page with one button "upgrade SitemapXML SQL"
When i push this nothings happens and i don't get anything else.
Ant idea what to do to make this works?

see the fix for this in comment #1800 (page 180) https://www.zen-cart.com/showthread....92#post1330192

cheers,
Mike

[KGL Racing]

see the fix for this in comment #1800 (page 180) https://www.zen-cart.com/showthread....92#post1330192

cheers,
Mike

Great mike, this works for me!

[shags38]

v1.5.5f PHP7.1 using plugin version 3.9.2

I am using Ultimate SEO URL's (USU) however sitemap(s) are being submitted as standard ZC urls (cPath?) - the issue is that sitemap submissions are NOT BEING INDEXED ... (5 sites)

I still have one site as v1.5.1 using a previous version of this plugin and the sitemaps are submitted using USU and submitted pages are being indexed.

Configuration settings for the old v1.5.1 and the newer 1.5.5f sites are the same in both admin/configuration/sitemapxml and /usu (I cannot see anything different) so I am stumped as to why the USU urls are not being submitted.

.... and yes I have seen a decline in SERP's rankings since the sites were upgraded to v1.5.5f with this sitemap problem. Yes Google is still finding pages and indexing them BUT not all of them and not as regularly as the CRON requests because the sitemap generated is using ZC standard urls - Google's response to all of the submitted url's is 'URL is not on Google - This page is not in the index, but not because of an error'. (see image)

IMAGES ARE NOT BEING INDEXED because the image submitted is for a product page that Google does not recognize!

I look forward to some assistance with this please. (it is more than likely I have done something wrong or not done something correctly).

many thanks,
Mike

Attachment 18134

[torvista]

I found that my long-installed sitemapxml admin page was showing correctly on my hosting but showing only the upgrade button on my local development site.

I find in:
YOUR_Admin\sitemapxml.php
line 255:

elseif (SITEMAPXML_VERSION_CURRENT != $current_version) { 

This is finding that $current_version is indeed not equal to SITEMAPXML_VERSION_CURRENT.
SITEMAPXML_VERSION_CURRENT is a created constant made up from
SITEMAPXML_VERSION which is in the database from the last installation, and
_CURRENT is appended to represent this current state/before any upgrade.

Now the variable $current_version is set in
YOUR_ADMIN/includes/init_includes/init_sitemapxml.php

where it parses the names of the installer files in
YOUR_ADMIN\includes\installers\sitemapxml
to end up with 3.9.5 for the latest version of the installer.

I find that on my hosting
$current_version = 3.9.5, so that works ok.

I find that on my dev server
$current_version = 2.1.3, so that does NOT work and prompts for the upgrade.

Why?...because zen colorbox is installed and in

YOUR ADMIN/includes/init_includes/init_zcb_config.php
it also sets a variable with the same name of $current_version, which is 2.1.3, and so this value gets used.

So why does this variable get used differently on my dev server (windows, php 7.1.23) to my hosting (linux, php 7.1.23)?
Files and database are identical.

Answers not on a postcard please!!

Note that the quick fix has already been posted here
https://www.zen-cart.com/showthread....92#post1330192
but the underlying problem needs to be resolved.

[mc12345678]

I found that my long-installed sitemapxml admin page was showing correctly on my hosting but showing only the upgrade button on my local development site.

I find in:
YOUR_Admin\sitemapxml.php
line 255:

elseif (SITEMAPXML_VERSION_CURRENT != $current_version) { 

This is finding that $current_version is indeed not equal to SITEMAPXML_VERSION_CURRENT.
SITEMAPXML_VERSION_CURRENT is a created constant made up from
SITEMAPXML_VERSION which is in the database from the last installation, and
_CURRENT is appended to represent this current state/before any upgrade.

Now the variable $current_version is set in
YOUR_ADMIN/includes/init_includes/init_sitemapxml.php

where it parses the names of the installer files in
YOUR_ADMIN\includes\installers\sitemapxml
to end up with 3.9.5 for the latest version of the installer.

I find that on my hosting
$current_version = 3.9.5, so that works ok.

I find that on my dev server
$current_version = 2.1.3, so that does NOT work and prompts for the upgrade.

Why?...because zen colorbox is installed and in

YOUR ADMIN/includes/init_includes/init_zcb_config.php
it also sets a variable with the same name of $current_version, which is 2.1.3, and so this value gets used.

So why does this variable get used differently on my dev server (windows, php 7.1.23) to my hosting (linux, php 7.1.23)?
Files and database are identical.

Answers not on a postcard please!!

Note that the quick fix has already been posted here
https://www.zen-cart.com/showthread....92#post1330192
but the underlying problem needs to be resolved.

Colorbox (and a few other plugins) uses an auto-installer plugin to locally define and use $current_version in the file it is defined. Can think of a few different ways to address this issue. All plugins that use that auto-installer could be modified to use an additional factor to provide a unique "current_version" variable for each plugin (increasing the number of variables defined in the system intended to be used only locally. A test and storage of an existing value of $current_version could be made coming into each of those to be restored at exit. This plugin could do something similar of uniquely defining the variable or obtaining it locally so that no other definition would interfere.

As to why things work one way on one system as compared to another, it has been posted elsewhere in the forum that the sequence of file loading can be alphabetic or reverse alphabetic if not mistaken. The alternate sequence may be something else, but basically on the live server the sequence of loading supports sustaining the value of $current_version as defined to support sitemapXML, but in the other it doesn't.

[torvista]

the sequence of file loading can be alphabetic or reverse alphabetic

Can you find that? I couldn't. I don't like not getting to the bottom of odd stuff like this.
It is not an isolated case, as seen by others reporting it previously, so warrants further investigation.

[mc12345678]

Can you find that? I couldn't. I don't like not getting to the bottom of odd stuff like this.
It is not an isolated case, as seen by others reporting it previously, so warrants further investigation.

While there may still be a forum post about it, I was able to recall that it is a topic of discussion (issue) in the github for ZC: https://github.com/zencart/zencart/issues/1228. As outlined there it appears that at least for one set of sampling the date/time of placement to the system has an effect. As outlined in the writeup, the associated system dictates the sequence when the "problem" function is used.