Zen Cart Logo
Forums / All Other Contributions/Addons / Ultimate SEO v3 (and v2.200) [Support Thread]

Ultimate SEO v3 (and v2.200) [Support Thread]

Views: 427,490

Results 941 to 960 of 1,706
17 Sep 2015, 6:07 PM
#941
lat9 avatar

lat9

Administrator

Join Date:
Sep 2009
Location:
Stuart, FL
Posts:
14,066
Plugin Contributions:
56

Ultimate SEO v3 (and v2.200) [Support Thread]

@Siem, I've modeled your settings in a local test site, setting*** Alternate URLs end with*** to blank like you have. With that setting, the default .htaccess file and enabling the language sidebox, I get a link that looks like http://localhost/testsite/index?language=en which properly displays, when clicked, the main page.

Perhaps there's a setting in your .htaccess that's a bit off; if you'd post its contents wrapped by the CODE tags (the big # above the post-writing textbox), perhaps that would provide a clue.

18 Sep 2015, 6:57 PM
#942
siem avatar

siem

New Zenner

Join Date:
Mar 2015
Posts:
28
Plugin Contributions:
0

Re: Ultimate SEO v3 (and v2.200) [Support Thread]

The contents of the .htaccess:

###############################################################################
# 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.
###############################################################################

I believe it is identical to the .htaccess file included in the plugin? Maybe I didn't understand everything in it and there is something here which I should change to match some other setting?

Thanks for trying to help.

18 Sep 2015, 7:01 PM
#943
lat9 avatar

lat9

Administrator

Join Date:
Sep 2009
Location:
Stuart, FL
Posts:
14,066
Plugin Contributions:
56

Re: Ultimate SEO v3 (and v2.200) [Support Thread]

Is your Zen Cart installed in the root directory of your hosted file-system? I'm just punting here, it's lhungil that knows this stuff left, right and upside down!

21 Sep 2015, 2:15 PM
#944
siem avatar

siem

New Zenner

Join Date:
Mar 2015
Posts:
28
Plugin Contributions:
0

Re: Ultimate SEO v3 (and v2.200) [Support Thread]

lat9:

Is your Zen Cart installed in the root directory of your hosted file-system? I'm just punting here, it's lhungil that knows this stuff left, right and upside down!

It's installed in the documentroot? The config in ......../apache2/sites-enabled/ has the directory the store is in as the root directory. I think that's what you meant?

21 Sep 2015, 4:29 PM
#945
lat9 avatar

lat9

Administrator

Join Date:
Sep 2009
Location:
Stuart, FL
Posts:
14,066
Plugin Contributions:
56

Re: Ultimate SEO v3 (and v2.200) [Support Thread]

Yes, that's what I meant. I'm all out of questions and suggestions; let's wait for lhungil to get back as I'm sure that he'll know straight-away what's up.

22 Sep 2015, 8:20 PM
#946
lhungil avatar

lhungil

Totally Zenned

Join Date:
Feb 2012
Location:
mostly harmless
Posts:
1,818
Plugin Contributions:
4

Re: Ultimate SEO v3 (and v2.200) [Support Thread]

Siem:

... No info in the debug logs, the ones in /logs/ the ones in /logs/ultimate_urls/ after saying in the admin interface I want the ultimate urls debug logs turned on, and also nothing in the regular error logs elsewhere on the server.
This is very disconcerting. Can you verify the user your web server runs as has access to write to "/logs/" (usually www-data on Debian)? Can you verify the user you are using to access the web server's filesystem has read access to "/logs/" (and sub-directories and files)?

What version of PHP is in use on the web server (Zen Cart Admin -> Version)? What bridge is being used to communicate between Apache2 <==> PHP (libapache2-mod-php5, libapache2-mod-php5filter, libapache2-mod-suphp, libapache2-mod-fcgid, libapache2-mod-scgi, etc)? Is the filesystem local or accessed over a network (NFS, SMB, etc)?

lat9:

@Siem, I've modeled your settings in a local test site, setting*** Alternate URLs end with*** to blank like you have. With that setting, the default .htaccess file and enabling the language sidebox, I get a link that looks like http://localhost/testsite/index?language=en which properly displays, when clicked, the main page. ...
Same in all of my test environments. The following snippet found at the end of the ".htaccess" file you supplied tells mod_rewrite (Apache2) to send a request for "/index?language=en" internally to "/index.php?main_page=index&language=en".

RewriteRule ^(.*)$ index\.php?main_page=$1&%{QUERY_STRING}

It appears your server is not processing this mod_rewrite directive for some reason when the URI "/index" is requested...

Can you check your server configuration (and VirtualHost configurations) to ensure no other directives are interfering? Do you have mod_security or mod_pagespeed installed / enabled? Can you verify there are no .htaccess files in parent directories (for example if the root is set to "/var/www/www4/", check "/var/www/.htaccess"). It is not uncommon for the "default" site to cause some issues if left enabled when serving multiple name based virtual hosts from on the same server (and nesting roots).

If your server has "mod_negotiation" enabled (usually the default on Debian) and you have a directory or file starting with "index" in the root folder (other than "index.php" - rare as none are included with a stock install of Zen Cart), this can also cause issues (delete the file / folder or disable "mod_negotiation" in the first section of the .htaccess file using "Options -MultiViews").

23 Sep 2015, 11:05 AM
#947
lat9 avatar

lat9

Administrator

Join Date:
Sep 2009
Location:
Stuart, FL
Posts:
14,066
Plugin Contributions:
56

Re: Ultimate SEO v3 (and v2.200) [Support Thread]

@lhungil: Welcome back!

24 Sep 2015, 11:47 AM
#948
siem avatar

siem

New Zenner

Join Date:
Mar 2015
Posts:
28
Plugin Contributions:
0

Re: Ultimate SEO v3 (and v2.200) [Support Thread]

Hi lhungil,

It's only when I try to select another language on the homepage that there are no logs even with log enabled. For all the other pages the standard? logs are created in /logs/ultimate_urls/

Permission for /logs/ is root, permission for /logs/ultimate_urls/ is www-data. This one does have access, hence the files which are created in all other cases.
The PHP version is: 5.4.36-0+deb7u3 (Zend: 2.4.0)
The bridge between PHP and Apache2 is libapache2-mod-php5 I think? By the loaded modules is a mod_php5 which is one of the ones you mentioned?
The filesystem is local.
mod_security and mod_pagespeed are not loaded.
There are no .htaccess files in the parent directories.
mod_negotiation is enabled, but there is no other file or directory in the root directory which starts with index (other than index.php which is supposed to be there).

Changing Alternate URLS end with from nothing to .php does work. So for now I just let it stay that way.

Hope the answers make any sense to you, and thanks everyone for trying to help.

24 Sep 2015, 4:50 PM
#949
lhungil avatar

lhungil

Totally Zenned

Join Date:
Feb 2012
Location:
mostly harmless
Posts:
1,818
Plugin Contributions:
4

Re: Ultimate SEO v3 (and v2.200) [Support Thread]

Thank you for clarifying. Previously you said no logs at all (which would be very disconcerting). However no logs only when "/index" is requested (plus seeing an Apache default 404 page) indicates the request never reached Zen Cart (or Ultimate URLs).

The issue is not with Ultimate URLs. Something in your server setup is intercepting requests for "/index" BEFORE the RewriteRule in the .htaccess is triggered (or is overriding the rules AFTER). This will most likely be an issue caused by something in your web server's Apache configuration (or some sort of "security" or "proxying" configuration).

The csuse could be an Apache server-wide or virtualhost directive (some occur AFTER rules in .htaccess files), issues caused by nested virtual host roots, something like mod_negotiation which triggers BEFORE .htaccess rules in a .htaccess file (try disabling MultiViews as suggested), an errant DirectoryIndex configuration, some sort of proxy / security software (and configuration), and the list goes on...

As long as you are okay with it, telling Ultimate URLs to add a suffix avoids the server configuration issue (something intercepting calls to "/index" and returning a 404) should work. If you are not okay with it and need further hekp, you may want to contact the hosting provider to troubleshoot and correct the underlying cause.

**NOTE 1:**It appears the server is running Debian. I've been unable to duplicate the issue with a stock VM running Debian 7 or Debian 8 (Apache2 default site disabled, multiple NameVirtualHosts with unnested document roots enabled, mod_php5 or mod_fcgi).

26 Sep 2015, 1:20 PM
#950
siem avatar

siem

New Zenner

Join Date:
Mar 2015
Posts:
28
Plugin Contributions:
0

Re: Ultimate SEO v3 (and v2.200) [Support Thread]

Thank you for helping and the clear questions. That helped a lot for me.

The server we use does indeed run Debian.

I think we'll just stick to using a suffix to make everything work. Maybe some other time when I actually have time to spare I'll try to look further into what may cause our problem, what setting elsewhere on the server is stopping Ultimate URLs to work. If I do find what caused it I will tell so here, maybe that would someday help someone else.

Thank you.

26 Sep 2015, 8:00 PM
#951
lhungil avatar

lhungil

Totally Zenned

Join Date:
Feb 2012
Location:
mostly harmless
Posts:
1,818
Plugin Contributions:
4

Re: Ultimate SEO v3 (and v2.200) [Support Thread]

Siem:

... I think we'll just stick to using a suffix to make everything work. Maybe some other time when I actually have time to spare I'll try to look further into what may cause our problem. ... If I do find what caused it I will tell so here, maybe that would someday help someone else. ...
Sounds like a plan, would be interested if you do at some point determine exactly what is causing the conflict.

28 Oct 2015, 4:31 AM
#952
divavocals avatar

divavocals

Totally Zenned

Join Date:
Jan 2007
Location:
Los Angeles, California, United States
Posts:
10,011
Plugin Contributions:
3

Re: Ultimate SEO v3 (and v2.200) [Support Thread]

Just wanted to confirm that I CAN upgrade from this version without having to uninstall..

28 Oct 2015, 5:09 AM
#953
lhungil avatar

lhungil

Totally Zenned

Join Date:
Feb 2012
Location:
mostly harmless
Posts:
1,818
Plugin Contributions:
4

Re: Ultimate SEO v3 (and v2.200) [Support Thread]

If you are upgrading from Zen Cart <1.5.0 as well (without a clean Zen Cart file set), I would recommend uninstalling first (and checking the DB). If already on Zen Cart >= 1.5.0 and all files from previous versions have been removed, should be able to upgrade w/o uninstalling first.

Would recommend taking a screenshot of the configuration before starting wither way. Some settings may need to be hand adjusted after the upgrade - for example converting any "character conversions" into "PCRE filters".

28 Oct 2015, 6:20 PM
#954
divavocals avatar

divavocals

Totally Zenned

Join Date:
Jan 2007
Location:
Los Angeles, California, United States
Posts:
10,011
Plugin Contributions:
3

Re: Ultimate SEO v3 (and v2.200) [Support Thread]

lhungil:

If you are upgrading from Zen Cart <1.5.0 as well (without a clean Zen Cart file set), I would recommend uninstalling first (and checking the DB). If already on Zen Cart >= 1.5.0 and all files from previous versions have been removed, should be able to upgrade w/o uninstalling first.

Would recommend taking a screenshot of the configuration before starting wither way. Some settings may need to be hand adjusted after the upgrade - for example converting any "character conversions" into "PCRE filters".
Got it!!

9 Nov 2015, 8:36 AM
#955
salvo72 avatar

salvo72

New Zenner

Join Date:
Feb 2013
Posts:
45
Plugin Contributions:
0

Re: Ultimate SEO v3 (and v2.200) [Support Thread]

I want to submit my problem
using the plugin I have split-url as an example:

/interni-c-83/complementi-darredo-c-83_97/porta-biancheria-c-83_97_180/
/interni-c-83/complementi-darredo-c-83_97/porta-biancheria-c-83_97_180/?pg=store

/idee-regalo-c-86/
/idee-regalo-c-86/?pg=store

....

how can I fix !! ?
thanks

9 Nov 2015, 8:52 AM
#956
lhungil avatar

lhungil

Totally Zenned

Join Date:
Feb 2012
Location:
mostly harmless
Posts:
1,818
Plugin Contributions:
4

Re: Ultimate SEO v3 (and v2.200) [Support Thread]

What modification have you installed to add the "pg=store"? It is not part of a stock Zen Cart installation. What BUSINESS result is achieved by adding "pg=store" to the query string?

9 Nov 2015, 9:33 AM
#957
salvo72 avatar

salvo72

New Zenner

Join Date:
Feb 2013
Posts:
45
Plugin Contributions:
0

Re: Ultimate SEO v3 (and v2.200) [Support Thread]

yes the string is at:

/httpdocs/includes/classes/categories_ul_generator.php a file integrated of ########## template source !!!

9 Nov 2015, 9:52 AM
#958
salvo72 avatar

salvo72

New Zenner

Join Date:
Feb 2013
Posts:
45
Plugin Contributions:
0

Re: Ultimate SEO v3 (and v2.200) [Support Thread]

and i have a problem similar an other website

i have duplicate of indexing page of google

the ulr rewrite:

http://ww.site.com/gancio-traino-nissan-2wd-5526026mamc-p-731.html

and this

<link rel="canonical" href="http://ww.site.com/index.php?main_page=product_info&products_id=731" />

in this mode i have a canonical error every page of website!!

very thanks for ypur support

9 Nov 2015, 5:18 PM
#959
lhungil avatar

lhungil

Totally Zenned

Join Date:
Feb 2012
Location:
mostly harmless
Posts:
1,818
Plugin Contributions:
4

Re: Ultimate SEO v3 (and v2.200) [Support Thread]

salvo72:

the string is at: /httpdocs/includes/classes/categories_ul_generator.php ...
Recommend removing this string from the 3rd party code if it serves no business purpose.

If it does serve a business purpose, you will need to tell Zen Cart to ignore the query string when generating the canonical link. This can be sone by adding "pg" to the list in "/includes/init_includes/overrides/init_canonical.php".

If the template / plugin author does not mention making this change (and does not include their own override file - to reference and merge during install), would recommend asking them politely to include the change in their documentation

salvo72:

... i have duplicate of indexing page of google ...
Double check the installation of Ultimate URLs and all files. Make sure the latest version is installed (and no files are left over from really old versions). Make sure the installed Zen Cart theme correctly utilizes without modification the variables added by "init_canonical.php".

For further support, please provide andwers to ALL of the questions in the forum "Posting Tips". Answers to these are essential to help us help you. The "Posting Tips" can be found by: Using a desktop or laptop to access the forums, clicking the reply button, and scrolling up (they appear above the textarea where you type).

11 Nov 2015, 1:22 PM
#960
lat9 avatar

lat9

Administrator

Join Date:
Sep 2009
Location:
Stuart, FL
Posts:
14,066
Plugin Contributions:
56

Re: Ultimate SEO v3 (and v2.200) [Support Thread]

I've got a client running USU 2.212 on Zen Cart v1.5.0. The site is fairly customized, notably using the Multi-Site Module running on a Windows Server and has been getting logs similar to the following:

[12-Oct-2015 14:09:29 America/New_York] PHP Fatal error:  Out of memory (allocated 13107200) (tried to allocate 25165824 bytes) in C:\Websites\test\includes\classes\seo.url.php(1196) : eval()'d code on line 10923
[12-Oct-2015 14:09:29 America/New_York] PHP Stack trace:
[12-Oct-2015 14:09:29 America/New_York] PHP   1. {main}() C:\Websites\test\index.php:0
[12-Oct-2015 14:09:29 America/New_York] PHP   2. require() C:\Websites\test\index.php:26
[12-Oct-2015 14:09:29 America/New_York] PHP   3. require() C:\Websites\test\includes\application_top.php:162
[12-Oct-2015 14:09:29 America/New_York] PHP   4. SEO_URL->__construct() C:\Websites\test\includes\autoload_func.php:82
[12-Oct-2015 14:09:29 America/New_York] PHP   5. SEO_URL->generate_products_cache() C:\Websites\test\includes\classes\seo.url.php:83
[12-Oct-2015 14:09:29 America/New_York] PHP   6. SEO_URL->get_cache() C:\Websites\test\includes\classes\seo.url.php:1025

The logs are usually accompanied by a server lock-up. The site's seo_cache table is 358.3 KiB in size.

Are there any configuration settings that I can look at/modify to possibly circumvent this out-of-memory condition?