@jodean, have you updated the site's root .htaccess to include the rewrite rules provided in the .htaccess file provided in the root directory of the plugin's distribution?

Yes, the .htaccess in the download has been included in the sites public_html root directory.

RewriteEngine on
RewriteBase /shop/
RewriteRule ^index.php$ - [L]

###############################################################################

Start Ultimate (SEO) URLs

###############################################################################

Notes:

You should not make any changes in this section unless you really understand

how it will impact your web site. Mistakes can break things.

###############################################################################

Handles the new URL formats

RewriteRule ^(.)-c-([0-9_]+)/(.)-p-([0-9]+)(.)$ index.php?main_page=product_info&products_id=$4&cPath=$2&%{QUERY_STRING} [L]
RewriteRule ^(.)-c-([0-9_]+)/(.)-pi-([0-9]+)(.)$ index.php?main_page=popup_image&pID=$4&cPath=$2&%{QUERY_STRING} [L]
RewriteRule ^(.)-c-([0-9_]+)/(.)-pr-([0-9]+)(.)$ index.php?main_page=product_reviews&products_id=$4&cPath=$2&%{QUERY_STRING} [L]
RewriteRule ^(.)-c-([0-9_]+)/(.)-pri-([0-9]+)(.)$ index.php?main_page=product_reviews_info&products_id=$4&cPath=$2&%{QUERY_STRING} [L]

Original (unchanged) URL formats

RewriteRule ^(.)-p-([0-9]+)(.)$ index.php?main_page=product_info&products_id=$2&%{QUERY_STRING} [L]
RewriteRule ^(.)-m-([0-9]+)(.)$ index.php?main_page=index&manufacturers_id=$2&%{QUERY_STRING} [L]
RewriteRule ^(.)-pi-([0-9]+)(.)$ index.php?main_page=popup_image&pID=$2&%{QUERY_STRING} [L]
RewriteRule ^(.)-pr-([0-9]+)(.)$ index.php?main_page=product_reviews&products_id=$2&%{QUERY_STRING} [L]
RewriteRule ^(.)-pri-([0-9]+)(.)$ index.php?main_page=product_reviews_info&products_id=$2&%{QUERY_STRING} [L]
RewriteRule ^(.)-ezp-([0-9]+)(.)$ index.php?main_page=page&id=$2&%{QUERY_STRING} [L]
RewriteRule ^(.)-c-([0-9_]+)(.)$ index.php?main_page=index&cPath=$2&%{QUERY_STRING} [L]

Rewrite all other requests (if the file / directory does not exist)

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php?main_page=$1&%{QUERY_STRING} [L]

The .htaccess code needed to be at the website level not the public_html level.

is there any way to exclude the code -c-13_49_55 from the generated url?

https://tennesseetraditionalflies.com/shop/mayflies-c-13_49_55/

jodean:

is there any way to exclude the code -c-13_49_55 from the generated url?

https://tennesseetraditionalflies.com/shop/mayflies-c-13_49_55/
Nope, that's how USU 'knows' which category (the -c) to point the 'base' Zen Cart code to.

I have just installed this on my site, Zen Cart 1.5.5f, copied the files over and merged the htaccess to the below. It shows up in the admin as installed, and I am able to set rewrite the urls to true, but nothing changes on the site, the urls are all still the same as before.

My site is https://television.show any help appreciated.

Here is my htaccess, in the root folder, where the site is:

###############################################################################

Add custom headers and options

###############################################################################

Notes:

Examples: Adding IE compatibility / edge flags, language and encoding flags,

php or suphp directives, configure other Apache modules such as page_speed,

and enable or disable Apache httpd options.

Do NOT configure anything directly relating to physical or virtual resources

in this section. These should be addressed later on in this file.

###############################################################################
#Options -Indexes

###############################################################################

Enable mod_rewrite processing using the rules in this .htaccess file

###############################################################################

Notes:

<IfModule> should be avoided at all costs. If mod_rewrite is not available

it is almost always better to return HTTP 500 status. This way we see there

is an issue as soon as the .htaccess file is uploaded.

For mod_rewrite to work, the Apache server option to allow symbolic links to

be followed must be enabled. Most providers supporting mod_rewrite will

already have it enabled for you, but if your rewrite rules are not working

you can un-comment the first directive below to manually enable the option.

Don't forget, mod_rewrite directives are processed in order until a matching

RewriteRule with the [L] flag is encountered. So the more specific a rule is

the closer it should appear to the top of this file.

###############################################################################
#Options +FollowSymLinks
RewriteEngine on

###############################################################################

Tell mod_rewrite where this file is relative to the server document_root

###############################################################################

Notes:

This directive should only be enabled if this .htaccess file is not placed

in the document_root (usually public_html, www, or web) of the (sub)domain.

An easy way to determine the location relative to the server document_root is

to look at the URL used to access a file in this folder. For example if you

access a "page" in the same folder as this file by typing in the URL

"www.mydomain.com/myfolder/index.html" then "myfolder" will be the location

of this file relative to the server document_root.

Another quick and easy way to determine the correct setting for this is to

look at the defined value for DIR_WS_CATALOG and DIR_WS_HTTPS_CATALOG in

Zen Cart's configure.php files. All three values should match.

Don't forget the leading and trailing /. This directive requires both!

###############################################################################
#RewriteBase /shop/

###############################################################################

Redirect if request was for index.php (no query)

###############################################################################

Notes:

This is only required if the site generates references to index.php with no

parameters. This rule will force a 301 redirect to the site root when a

request is made for "/index.php" with no query terms (?key=value).

###############################################################################
#RewriteCond %{QUERY_STRING} ^$
#RewriteRule ^index.php$ / [R=301,L]

###############################################################################

Add any custom 301 redirects

###############################################################################

Notes:

In general these should be few and far between. If you use a RewriteRule

be sure to add the L flag to let Apache mod_rewrite know to stop processing

and skip any RewriteRules defined later in the .htaccess file.

###############################################################################

###############################################################################

Redirect if request was for index.php (with or without query)

###############################################################################

Notes:

This is a performance optimization. If the request is for index.php simply

pass the request on and do not process any other mod_rewrite directives in

this file.

Basically this avoids the overhead of checking if index.php is a real file

or directory (used in subsequent mod_rewrite rules) before sending the

request to index.php.

###############################################################################
RewriteRule ^index.php$ - [L]

###############################################################################

Start Ultimate (SEO) URLs

###############################################################################

Notes:

You should not make any changes in this section unless you really understand

how it will impact your web site. Mistakes can break things.

###############################################################################

Handles the new URL formats

RewriteRule ^(.)-c-([0-9_]+)/(.)-p-([0-9]+)(.)$ index.php?main_page=product_info&products_id=$4&cPath=$2&%{QUERY_STRING} [L]
RewriteRule ^(.)-c-([0-9_]+)/(.)-pi-([0-9]+)(.)$ index.php?main_page=popup_image&pID=$4&cPath=$2&%{QUERY_STRING} [L]
RewriteRule ^(.)-c-([0-9_]+)/(.)-pr-([0-9]+)(.)$ index.php?main_page=product_reviews&products_id=$4&cPath=$2&%{QUERY_STRING} [L]
RewriteRule ^(.)-c-([0-9_]+)/(.)-pri-([0-9]+)(.)$ index.php?main_page=product_reviews_info&products_id=$4&cPath=$2&%{QUERY_STRING} [L]

Original (unchanged) URL formats

RewriteRule ^(.)-p-([0-9]+)(.)$ index.php?main_page=product_info&products_id=$2&%{QUERY_STRING} [L]
RewriteRule ^(.)-m-([0-9]+)(.)$ index.php?main_page=index&manufacturers_id=$2&%{QUERY_STRING} [L]
RewriteRule ^(.)-pi-([0-9]+)(.)$ index.php?main_page=popup_image&pID=$2&%{QUERY_STRING} [L]
RewriteRule ^(.)-pr-([0-9]+)(.)$ index.php?main_page=product_reviews&products_id=$2&%{QUERY_STRING} [L]
RewriteRule ^(.)-pri-([0-9]+)(.)$ index.php?main_page=product_reviews_info&products_id=$2&%{QUERY_STRING} [L]
RewriteRule ^(.)-ezp-([0-9]+)(.)$ index.php?main_page=page&id=$2&%{QUERY_STRING} [L]
RewriteRule ^(.)-c-([0-9_]+)(.)$ index.php?main_page=index&cPath=$2&%{QUERY_STRING} [L]

Rewrite all other requests (if the file / directory does not exist)

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)$ index.php?main_page=$1&%{QUERY_STRING} [L]

###############################################################################

Add any other directives relating to the handling of physical files

###############################################################################

Notes:

If processing makes it this far, the request was for a real file or folder.

Example: Adding further processing related to browser caching or security.

###############################################################################
#Force non-www:
RewriteEngine on
RewriteCond %{HTTP_HOST} ^www.television.show [NC]
RewriteRule ^(.*)$ http://television.show/$1 [L,R=301]

php -- BEGIN cPanel-generated handler, do not edit

Set the “ea-php56” package as the default “PHP” programming language.

If it helps I have the error log on and it gives this:

=====> URL Generation Log Started, for page: /my-admin/configuration.php?gID=55&cID=753.

Request sent to href_link('index', '', 'NONSSL', true, true, false, true)
Generated URL: http://television.show/

Request sent to href_link('index', '', 'NONSSL', true, true, false, true)
Generated URL: http://television.show/

To follow on with this, I have this morning spent a while triple checking that every file is in exactly the correct place, and I have tried various changes with the htaccess file, removing the old parts from my original file, and replacing them and nothing seems to make any difference, I never get any re-written URLS... the module said it was installed, and it is switched on in the admin.. the site was a new install and has had no previous versions installed... would appreciate any help.

As another update I get that same log in the error log everytime I log into the admin, or try to make any changes to the module.

phil99:

If it helps I have the error log on and it gives this:

=====> URL Generation Log Started, for page: /my-admin/configuration.php?gID=55&cID=753.

Request sent to href_link('index', '', 'NONSSL', true, true, false, true)
Generated URL: http://television.show/

Request sent to href_link('index', '', 'NONSSL', true, true, false, true)
Generated URL: http://television.show/
That's not an 'error' log, it's a log of USU's processing. Do you have any myDEBUG-adm*.log files (or myDEBUG-*.log) present in the site's /logs directory?

Thanks for your help and response...No there is not... however I switched on

Enable automatic redirects?
This will activate the automatic redirect code and send 301 headers for old to new URLs.

To true... the site already had products listed etc... so did I need to put that on? The links on the site still use the old URLS, but when clicked go to the new URLS....

phil99:

Thanks for your help and response...No there is not... however I switched on

Enable automatic redirects?
This will activate the automatic redirect code and send 301 headers for old to new URLs.

To true... the site already had products listed etc... so did I need to put that on? The links on the site still use the old URLS, but when clicked go to the new URLS....
Enabling automatic redirects will help with the site's SEO, given that the 'old' URLs might be bookmarked by customers and/or search engines.

You'll need to check your Template Monster template's tpl_modules_featured_products.php, tpl_modules_specials_default.php and whatever script is creating that Categories mega-menu as it appears that the associated code is not using the zen_href_link function to create those product/category links.

v1.5.5f php7.1

Hi Cindy,

I am trying to update from v2.215 to v3.0.6 without success. Following your installation instructions in the readme I deleted all files associated with the 2.215 version of the plugin and deleted all tables in configuration_group and configuration in the database (v2.215 doesn't have an uninstall.sql file and the uploading of the two files in the 'uninstall folder' didn't appear to work) - so I thought manually deleting the tables was the next best thing to do.

So deleting all files and the DB tables resulted in a blank white screen for both admin and store. Uploading installation files for 3.0.6 didn't retrieve admin (so couldn't complete installation) nor store - both remained blank. As the plugin doesn't overwrite any ZC core files I'm at a loss to know what went wrong?

I did this upgrade attempt on a live site - fortunately I had a full backup and am now back to where I was.

I am now going to make a copy of my site and attempt an upgrade on that site copy .... before i do, do you have any suggestions as to how I should go about it given that there is no uninstall.sql file for 2.215? ... is attempting an upgrade all the way to 3.0.6 'a bridge too far'?

Al I really need is for the canonical issue to work - that was fixed on v3.0.0 right? should I just try upgrading to 3.0.0?

cheers,
Mike

so with installation the .htaccess file will overwrite the existing file in the root right? - so domain redirections (non www to www to force https etc) (not usu) will be lost, right? so I assume immediately after upgrading that those redirects need to be pasted into the new .htaccess file?

Mike, the issues surrounding a USU upgrade from a version that old are normally making sure that (a) all the configuration-related bits are removed from the database and (b) that the core-file changes by those previous versions are also removed.

Make sure that that old version of USU doesn't provide files in the [/ADMIN]/includes/init_includes/overrides sub-directories. Use the Zen Cart "Developers' Tool Kit" to search for all occurrences of USU and SEO in all admin/storefront files.

For the changes to the .htaccess, I'd copy the block of rewrites from that provided by the USU distribution and paste that block into your current .htaccess (after any 'Deny' processing). That way, you keep all your non-www-to-www and force-https directives (as well as the Deny's) and just apply the update that's required for USU to do its thing.

Hey guys & gals,
I am currently on cart v1.5.4 and previous to that version I installed Ultimate Urls 2.15. I have several issues that I want to fix by doing an upgrade but have a few questions. Right now the admin page for 2.15 is not shown under configuration but I can access it by manually entering the id number in the configuration url (/configuration.php?gID=35) to get to it. With that said I also use the DPU 3.2.0 price updater plugin to calculate prices on the fly as my products have setup charges plus running charges and DPU displays 1 price on the product page. The problem is (and I didn't realize this until this week) is that while all of my .php product pages correctly display the price using the DPU price updater, the html version of the same pages does not display the price and the gif spins constantly as if it is working but the price never displays. Somehow I missed this error when I originally installed the 2.15 plugin and I wonder how many customers & orders I have lost because of them landing on the non functioning html pages.
My questions are:

1. Can the newest version DPU correctly display prices on the html versions?
2. Can the newest Ultimate Urls allow the DPU 3.2.0 I am currently using to display the prices correctly on the html version pages?
3. To upgrade the 2.15 to the current version is it just a matter of uninstalling all the old/original Ultimate Urls files installed (readme wasn't crystal clear to me) then proceed with the new version?
   Thanks,
   John

Noting, first, that the current version of USU (v3.0.6) supports Zen Cart versions 1.5.5 and later. There are 'significant' notifiers built into that and later versions of Zen Cart that enable the plugin to be drop-in.

Updating USU from one of its v2 flavors is messy, but documented here: https://github.com/lat9/usu/blob/master/pages/upgrade_from_v2.md. It's probably best, from a database-configuration standpoint, to run the v2 uninstall.sql and then re-install so that the database settings are proper. You'll also need to review the files 'delivered' by the version you're using (v2.215) so that you can remove its 'new' files and back out any core/template-file changes required by that older version.

Hi,
I have just downloaded the add-on and I’m very impressed at how easy it is to install and how well it works.

While testing the add-on I appear to have found a small issue on categories containing more than 10 products.

On a new Zencart install (1.5.7) I have installed this add-on and noticed the following:

The demo products pre-installed on the cart have a category (called Test Examples) with 16 products. With the standard settings this splits the products into two pages. These pages have the following URLs and canonical links:

Page 1 url in browser bar: example-website-com/test-examples-c-23/
Page 1 Canonical link: example-website-com/test-examples-c-23/

Page 2 url in browser bar: example-website-com/test-examples-c-23/?sort=20a&page=2
Page 2 Canonical link: example-website-com/test-examples-c-23/?page=2

When navigating from page 2 back to page 1 (using the [Prev] button) I have noticed that an alternative url is displayed (please see below).

Alternative Page 1 url in browser bar: example-website-com/test-examples-c-23/?sort=20a&page=1
Alternative Page 1 Canonical link: example-website-com/test-examples-c-23/?page=1

I would be very grateful if someone can look into the two issues:

1. The canonical link should be identical to the url in the browser bar (ideally the url would be rewritten to remove the sort=20a from the browser bar)
2. There should only be one canonical link for page 1 – the ‘alternative’ canonical link which has ?page=1 added on the end appears to be duplicate content.

Any help with these issues would be much appreciated.
Many thanks.
Richard

Richard, thanks for the report. I'll give it a look later today or in the morning.

lat9:

Richard, thanks for the report. I'll give it a look later today or in the morning.
Still no answer, but something's changed going from zc155f (where those additional parameters don't display in the canonical link) and zc157 (where they do).:huh:

I am confused. The download is for 3.0.6 but the support thread is for Ultimate SEO 2.200. Can anyone clear up the confusion?