Ceon URI Mapping v4.x

[dp-web]

Verify your installation of both products, as we are using the same and have no issues... XML files reflect the rewritten URLs. Also, helps to identify the version(s) of the software, but this may be something to address in the Google Sitemap XML thread as it seems that it is what is not working correctly, or on a separate thread as these two products work together when the applicable files are properly merged/installed. (Successfully working on ZC 1.5.1 and expect no different on ZC 1.5.3)

Hi, we're running on Zen Cart v1.5.1. Our Ceon version is v4.4.1. Our Sitemap is called Sitemap XML and is v3.2.12 19.09.2013.

Your confirmation that both of these modules work together and output as needed is good, and it really is an installation issue somewhere along the line.

Cheers,
dp

[DivaVocals]

Our output file is only giving us the old, standard Zen Cart product ID URL - which Google really doesn't like inside XML sitemaps as it requires a 200 response header rather than a 301.

Not a true statement.. Google doesn't CARE as long as the URL is VALID.. but that is ANOTHER topic..

The documentation states that the module deals with this and how to set it up, but the output is only ever the same, with the original URL.

Is there anyway to pull the new URL out (generated by CEON module) and input it into the Sitemap XML file? The info should be inside the database somewhere...

The issue is the Google Sitemap XML module.. Search this thread or the Google Sitemap XML support thread.. there is a posted fix which has sounds like NEVER made it's way into the Google Sitemap XML module..

[dp-web]

Not a true statement.. Google doesn't CARE as long as the URL is VALID.. but that is ANOTHER topic..

The issue is the Google XML module.. Search this thread or the Google XML support thread.. there is a posted fix which has sounds like NEVER made it's way into the Google XML module..

Hi Diva,

Thanks for your response. On my reading travels I've come across a lot of sites saying 301's are not good. But, I've just finished a Google Hangout with John Mueller Google WMT engineer) today and he did confirm that yes, Google DON'T care about the 301's redirects in the sitemap, in fact he said up to 5 is okay (ideally non but it's not always possible). So, with your confirmation as well, I can cross this off my list as possible causes for a dip in traffic.

I'll dig through the XML Sitemap thread to find the fix you mentioned. The module doesn't appear to have been updated in a while so might not have been added.

Thanks again.
dp

[DivaVocals]

Hi Diva,

Thanks for your response. On my reading travels I've come across a lot of sites saying 301's are not good. But, I've just finished a Google Hangout with John Mueller Google WMT engineer) today and he did confirm that yes, Google DON'T care about the 301's redirects in the sitemap, in fact he said up to 5 is okay (ideally non but it's not always possible). So, with your confirmation as well, I can cross this off my list as possible causes for a dip in traffic.

I'll dig through the XML Sitemap thread to find the fix you mentioned. The module doesn't appear to have been updated in a while so might not have been added.

Thanks again.
dp

The fix I speak of is in the Google XML support thread.. It was posted some time back so be prepared to dig a little.. try searching the thread specifically for "Ceon"

[dp-web]

The fix I speak of is in the Google XML support thread.. It was posted some time back so be prepared to dig a little.. try searching the thread specifically for "Ceon"

Thanks again. I've found the fix, and yes it was out of date, but I've corrected the code but the module still only outputs the URL's in the original zen format.

The CEON module works as it should (and there are only a few options anyway) so I know its doing what its supposed to in terms of URL rewriting.

I un-installed the Sitemap XML module, cleared out the files, re-installed and set it back up, but its still not working. Not sure where else to go now with it.

dp

[DivaVocals]

Thanks again. I've found the fix, and yes it was out of date, but I've corrected the code but the module still only outputs the URL's in the original zen format.

The CEON module works as it should (and there are only a few options anyway) so I know its doing what its supposed to in terms of URL rewriting.

I un-installed the Sitemap XML module, cleared out the files, re-installed and set it back up, but its still not working. Not sure where else to go now with it.

dp

All I can do is suggest you check your install of BOTH modules again..

Honestly if it's the Sitemap that's not generating the correct URI's the issue really is with the sitemap module (see post from the original Ceon author below).. Unfortunately the author of the Sitemap module isn't interested in figuring out the fix.. But the most likely REASON why is clearly stated below..

Hi,



Must be a problem with that module. Ceon URI Mapping will output the static URI for any code that uses zen_href_link(). It has no concept of what module is using it via that function.

Best ask your question on the thread for this other module.

Sorry I can't be more help than that but at least you know the issue isn't with Ceon URI Mapping.

All the best..

Conor
ceon

[whitsolltd]

Hello

I have installed this module on Zen Cart 1.5.3 and everything is showing as OK in the installation and configuration checker. I am however having an issue with the redirects, in that every custom url returns to the homepage. I have tried the fix of adding the / to the .htaccess rule

the site is a b a c a o r g a n i c . co.uk and you can see the behaviour by clicking 'mattresses' then 'pocket sprung'

Any suggestions on this much appreciated.

Many thanks

[mc12345678]

Hello

I have installed this module on Zen Cart 1.5.3 and everything is showing as OK in the installation and configuration checker. I am however having an issue with the redirects, in that every custom url returns to the homepage. I have tried the fix of adding the / to the .htaccess rule

the site is a b a c a o r g a n i c . co.uk and you can see the behaviour by clicking 'mattresses' then 'pocket sprung'

Any suggestions on this much appreciated.

Many thanks

Maybe something in the .htaccess file is fowling the CEON rewrite? Could you provide a copy of your .htaccess file, but be sure to obscure your admin directory as it is one of the rewritecond's included... Also, if there is anything else that is to remain obscured, at least identify that there is something there, but do not provide the details of what it was. Otherwise, perhaps the installation wasn't complete?

[whitsolltd]

Thanks for coming back so quickly. I have reinstalled a couple of times to no avail. Here is the .htaccess info.

## BEGIN CEON URI MAPPING REWRITE RULE
RewriteEngine On
Options +SymLinksIfOwnerMatch

# Don't rewrite any URIs ending with a file extension (ending with .[xxxxx])
RewriteCond %{REQUEST_URI} !\.[a-z]{2,5}$ [NC]
# Don't rewrite any URIs for some, popular specific file format extensions,
# which are not covered by main file extension condition above
RewriteCond %{REQUEST_URI} !\.(mp3|mp4|h264)$ [NC]
# Don't rewrite any URIs for some specific file format extensions,
# which are not covered by main file extension condition above
# Uncomment the following line to apply this condition! (Remove the # at the start of the next line)
#RewriteCond %{REQUEST_URI} !\.(3gp|3g2|h261|h263|mj2|mjp2|mp4v|mpg4|m1v|m2v|m4u|f4v|m4v|3dml)$ [NC]
# Don't rewrite admin directory
RewriteCond %{REQUEST_URI} !^/XXXXX [NC]
# Don't rewrite editors directory
RewriteCond %{REQUEST_URI} !^/editors/ [NC]
# Don't rewrite logs directory
RewriteCond %{REQUEST_URI} !^/logs/ [NC]
# Don't rewrite new directory
RewriteCond %{REQUEST_URI} !^/new/ [NC]
# Don't rewrite abaca directory
RewriteCond %{REQUEST_URI} !^/abaca/ [NC]
# Don't rewrite cgi-bin directory
RewriteCond %{REQUEST_URI} !^/cgi\-bin/ [NC]
# Don't rewrite blog directory
RewriteCond %{REQUEST_URI} !^/blog/ [NC]
# Don't rewrite tempEP directory
RewriteCond %{REQUEST_URI} !^/tempEP/ [NC]
# Don't rewrite magicscroll directory
RewriteCond %{REQUEST_URI} !^/magicscroll/ [NC]
# Handle all other URIs using Zen Cart (its index.php)
RewriteRule .* index.php [QSA,L]

## END CEON URI MAPPING REWRITE RULE

[mc12345678]

And that is the content of your entire .htaccess file? Nothing before, nothing after the CEON added code?

I have in the RewriteRule a slight difference to what you have. I have:

RewriteRule ^(.*)$ /index.php [QSA,L]

What I consider the significant difference being ^(.*)$ instead of .* alone.

Still, that is the entirety of your .htaccess file? I had gone through similar iterations on the site to obtain fully satisfactory results with the setup at the time. The differences may be inconsequential; however, I don't want to modify what isn't broke as there have been no issues with the rewrites after applying the above.