Jump to content
Chemo

[Contribution] Ultimate SEO URLs - by Chemo

Recommended Posts

found the problem with the buynow stuff. i had been searching the posts and had tried various things people had recommended before posting and one of them was to change application_top.php in the case for buy_now from GET to POST or vice versa - don't recall. Anyway, changed it back and all is well. sorry for the trouble. thanks for the quick assistance on this too.

 

Unfortunately, through further testing, it occurs before logging in.  I can click the buynow button and when it gets to the cart, the cart is empty.  I haven't even logged in at that point.  Any idea what is causing this?  Thanks so much!

Share this post


Link to post
Share on other sites
Further I have added some own fields to the DB. They expand my products description ... e.g. my products_name is 'Chrysler' - and one of my new fields contains the color. How can I add this to the URL? E.g. I want to have

 

http://www.domain.de/catalog/chrysler-red-p-1.html

 

Well - until now I tried to include it like the product_name ... but this didn't work - like I expected ... :lol:

 

My code should look like the following I guess:

 

if ( defined('PRODUCT_NAME_'.$p2[1]) ){
    	 $rewrite_page_product = short_name(constant('PRODUCT_NAME_'.$p2[1])) . '-' . PRODUCT_MYFIELD . '-p-' . $p2[1] . '.html';
     } else { $seo = false; }
     break;

 

But where do I get that what I called PRODUCT_MYFIELD from? I thought the html_output.php is included in the application_top.php ... and this is required for the index.php!? But in this there I whether could find PRODUCT_NAME (only PRODUCT_LIST_NAME) nor anything looking like PRODUCT_MYFIELD :(

So ... where might my field already be queried out of the DB? And how is it called then? :'(

Share this post


Link to post
Share on other sites

The values are not pulled from the DB but rather is cached and evaluated. This is much faster than querying for them individually but has drawbacks for stores that have more than 5,000 products or categories (*maybe*).

 

To use your code you can either query for your field on each call to tep_href_link() if needed OR you can cache them along the same lines. However, keep in mind that those magical defines are not infinite in use...there is an upper limit to memory :)

 

Bobby

Share this post


Link to post
Share on other sites

Hi Bobby,

 

Yes, I guess I didn't understand how it is working before. But now I do ... :)

 

But this doesn't mean that I now don't have still any problems ;) Could you please take a look to this thread here:

 

http://forums.oscommerce.com/index.php?sho...ic=133977&st=60

 

There I wrote what I want to do ... and what I did already ... perhaps can you explain some more details - I'm still learning ... B)

Share this post


Link to post
Share on other sites

the seo mod is great but now since I turned off sef in oscommerce all my other URL's are NOT search engine friendly. I have the articles manager mod installed and those are the URL's I am talking about. Can we make this mod work so that my articles are all search engine friendly. It would be awesome if the mod would work like it does with the products by putting the title of the article in the URL.

 

Comments please

Share this post


Link to post
Share on other sites

A release has been made that adds SEO URLs to articles...it wasn't coded by me but it works on several stores that I'm aware of. However, I can't support it as it's not part of the release.

 

Bobby

Share this post


Link to post
Share on other sites

Hey Bobby,

 

:D

This reminded me of a question I had.

 

What needs to be done to add this to the admin so that any product urls that are created there can be converted to seo urls. I am specifically interested in the contribution Feed base class + Froogle.

 

THanks,

Paul

Share this post


Link to post
Share on other sites

Paul,

 

The next step in development is to abstact the code so it is reuseable on the admin side. Basically, turn it into a class so one could include it on the admin side scripts and use the same code to construct the URLs.

 

That is still some time in the future as I've begun a HUGE project. I can't say too much about it on this forum out of fear they would delete this entire thread (yes, some moderators hate me that much) but I'm sure if you started checking profiles you would find a good link so you can read about the new project :)

 

Once I have the new project coded and running I'll get back to the osC contributions. To be honest, due to recent events with the moderator team my motivation to develop and/or release contributions is greatly diminished.

 

Bobby

Share this post


Link to post
Share on other sites
A release has been made that adds SEO URLs to articles...it wasn't coded by me but it works on several stores that I'm aware of.  However, I can't support it as it's not part of the release.

 

Bobby

 

Can you point me in the right direction on which mod changes the URL to seo in articles?

 

Thanks Chemo!

Share this post


Link to post
Share on other sites

Hi

 

I asked this on anothe rpost but was redirected here. I went to instal the latest version which is easy enough to do but I got the the mod. for applicationtop and I don't have the code it says to look for.

 

So what I want to know is, do you have to instal another contribution before this one (the pname/cname thing) before you instal this one?


Kym

Projects Director @ ozEworks.com

Share this post


Link to post
Share on other sites
...

So what I want to know is, do you have to instal another contribution before this one (the pname/cname thing) before you instal this one?

If you are installing this for the first time just follow the directions...what else can I say?

 

The part that you are referring to is directions for upgrading...not installing for the first time.

 

Bobby

Share this post


Link to post
Share on other sites
Hi Chemo

 

I have two sites (both online), the ultimate seo contribution works perfectly on one site but not on the other. The rewrite option fails with a 404 page not found - the pages' names are rewritten correctly but seems like they are not being redirected correctly to pages that exist. Not sure if it is something on the server side (I am not hosting personally but the hosting compnay is reasonably helpful).

 

I also would be interested in the other little seo Gems that you said you had for paying cutomers..

 

Your contribution is excellent and I would love to just solve the 404 page not found error and get it working. The .htaccess file has been checked again and again (it is the same as the stock file - catalog in root)

 

I am up for paying for support here as the time factor is crucial.

 

Cheers

 

Asif

 

Hi Chemo,

 

I installed your wonderful Ultimate SEO URLs today. Thanks for providing such a wonderful contribution. I have experieced a similar situation to that of Asif. In my situation, the SEO runs perfectly on my hosting machine (Lunarpages). However, I got a "Not Found" on my local machine :( The script and database are the same. This leaves us the only difference is my settings for Apache and PHP. I am not sure what I should look for at this moment. Any help is greatly appreciated.

 

Thanks,

Stephen

Share this post


Link to post
Share on other sites
Hi Chemo,

 

I installed your wonderful Ultimate SEO URLs today. Thanks for providing such a wonderful contribution. I have experieced a similar situation to that of Asif. In my situation, the SEO runs perfectly on my hosting machine (Lunarpages). However, I got a "Not Found" on my local machine :( The script and database are the same. This leaves us the only difference is my settings for Apache and PHP. I am not sure what I should look for at this moment. Any help is greatly appreciated.

 

Thanks,

Stephen

 

Stephen,

 

Is your local machine windows? do you have mod rewrite enabled?


osC Contributions I have published.

 

Note: Some I only provided minor changes, updates or additions!

Share this post


Link to post
Share on other sites

Thanks. You really give great support to this contribution. I was probably too tired when I went to do it to realise that. :)


Kym

Projects Director @ ozEworks.com

Share this post


Link to post
Share on other sites

Must still be tired :( Loading one file cannot get it to be recognised by the osCOmmerce - there has to be more to it so bear with me a moment.

 

I loaded the seo_redirect file. I also opened it and read the comments. In the comments is says to insert the following line in application_top.php.

 

include('includes/seo_redirect.php');

 

which makes sense as now the seo-redirect program will get called.

 

The comments say "Find the SEO URLs code in application_top. Here is a small snippet:"

 

I don't have that snippet. I figure it is from another contribution probably the cName/pName thing. You are telling me I don't need to have installed that one for this one to work. So I look for somewhere to add that line and I see the Search Engine Friendly URLS code

 

"if (SEARCH_ENGINE_FRIENDLY_URLS == 'true') { ..."

 

I guess I put the include here. But do I put the include before or after? Does it matter?

 

How does it work with this feature which is part of standard osCommerce? Are they compatible or do you have to make sure no-one sets that flag to true?

 

Thanks for your time

Edited by FlyingKites

Kym

Projects Director @ ozEworks.com

Share this post


Link to post
Share on other sites
Stephen,

 

Is your local machine windows? do you have mod rewrite enabled?

 

Thanks Chris! My machine is a linux box (red hat 9.x). The apache/PHP are: Apache/1.3.33 (Unix) PHP/4.3.10. The apache loaded modules are: mod_php4, mod_setenvif, mod_so, mod_auth, mod_access, mod_rewrite, mod_alias, mod_userdir, mod_actions, mod_imap, mod_asis, mod_cgi, mod_dir, mod_autoindex, mod_include, mod_status, mod_negotiation, mod_mime, mod_log_config, mod_env, http_core.

 

I use the .htaccess at the root level at /usr/local/apache/htdocs. The osC index.php is at /usr/local/apache/htdocs. The .htaccess is:

 

Options +FollowSymLinks

RewriteEngine On

RewriteBase /

RewriteRule ^(.*)-p-(.*).html$ product_info.php?products_id=$2&%{QUERY_STRING}

RewriteRule ^(.*)-c-(.*).html$ index.php?cPath=$2&%{QUERY_STRING}

RewriteRule ^(.*)-m-(.*).html$ index.php?manufacturers_id=$2&%{QUERY_STRING}

 

Thanks again.

Stephen

Share this post


Link to post
Share on other sites

Make sure in your Apache configuration file you have the AllowOverride setting to "All" or "Options".

 

Bobby

Share this post


Link to post
Share on other sites
Make sure in your Apache configuration file you have the AllowOverride setting to "All" or "Options".

 

Bobby

 

Hi Bobby,

 

I am posting the entire httpd.conf of my linux box here. Hopefully you can quickly spot the problem. BTW, when I ./configure the apache, I only did --enable-module=rewrite. I didn't do --enable-shared=rewrite. I am no expert in this. Do I need to do both?

 

 

##

## httpd.conf -- Apache HTTP server configuration file

##

 

#

# Based upon the NCSA server configuration files originally by Rob McCool.

#

# This is the main Apache server configuration file. It contains the

# configuration directives that give the server its instructions.

# See <URL:http://httpd.apache.org/docs/> for detailed information about

# the directives.

#

# Do NOT simply read the instructions in here without understanding

# what they do. They're here only as hints or reminders. If you are unsure

# consult the online docs. You have been warned.

#

# After this file is processed, the server will look for and process

# /usr/local/apache/conf/srm.conf and then /usr/local/apache/conf/access.conf

# unless you have overridden these with ResourceConfig and/or

# AccessConfig directives here.

#

# The configuration directives are grouped into three basic sections:

# 1. Directives that control the operation of the Apache server process as a

# whole (the 'global environment').

# 2. Directives that define the parameters of the 'main' or 'default' server,

# which responds to requests that aren't handled by a virtual host.

# These directives also provide default values for the settings

# of all virtual hosts.

# 3. Settings for virtual hosts, which allow Web requests to be sent to

# different IP addresses or hostnames and have them handled by the

# same Apache server process.

#

# Configuration and logfile names: If the filenames you specify for many

# of the server's control files begin with "/" (or "drive:/" for Win32), the

# server will use that explicit path. If the filenames do *not* begin

# with "/", the value of ServerRoot is prepended -- so "logs/foo.log"

# with ServerRoot set to "/usr/local/apache" will be interpreted by the

# server as "/usr/local/apache/logs/foo.log".

#

 

### Section 1: Global Environment

#

# The directives in this section affect the overall operation of Apache,

# such as the number of concurrent requests it can handle or where it

# can find its configuration files.

#

 

#

# ServerType is either inetd, or standalone. Inetd mode is only supported on

# Unix platforms.

#

ServerType standalone

 

#

# ServerRoot: The top of the directory tree under which the server's

# configuration, error, and log files are kept.

#

# NOTE! If you intend to place this on an NFS (or otherwise network)

# mounted filesystem then please read the LockFile documentation

# (available at <URL:http://www.apache.org/docs/mod/core.html#lockfile>);

# you will save yourself a lot of trouble.

#

ServerRoot "/usr/local/apache"

 

#

# The LockFile directive sets the path to the lockfile used when Apache

# is compiled with either USE_FCNTL_SERIALIZED_ACCEPT or

# USE_FLOCK_SERIALIZED_ACCEPT. This directive should normally be left at

# its default value. The main reason for changing it is if the logs

# directory is NFS mounted, since the lockfile MUST BE STORED ON A LOCAL

# DISK. The PID of the main server process is automatically appended to

# the filename.

#

#LockFile /usr/local/apache/logs/httpd.lock

 

#

# PidFile: The file in which the server should record its process

# identification number when it starts.

#

PidFile /usr/local/apache/logs/httpd.pid

 

#

# ScoreBoardFile: File used to store internal server process information.

# Not all architectures require this. But if yours does (you'll know because

# this file will be created when you run Apache) then you *must* ensure that

# no two invocations of Apache share the same scoreboard file.

#

ScoreBoardFile /usr/local/apache/logs/httpd.scoreboard

 

#

# In the standard configuration, the server will process httpd.conf (this

# file, specified by the -f command line option), srm.conf, and access.conf

# in that order. The latter two files are now distributed empty, as it is

# recommended that all directives be kept in a single file for simplicity.

# The commented-out values below are the built-in defaults. You can have the

# server ignore these files altogether by using "/dev/null" (for Unix) or

# "nul" (for Win32) for the arguments to the directives.

#

#ResourceConfig /usr/local/apache/conf/srm.conf

#AccessConfig /usr/local/apache/conf/access.conf

 

#

# Timeout: The number of seconds before receives and sends time out.

#

Timeout 300

 

#

# KeepAlive: Whether or not to allow persistent connections (more than

# one request per connection). Set to "Off" to deactivate.

#

KeepAlive On

 

#

# MaxKeepAliveRequests: The maximum number of requests to allow

# during a persistent connection. Set to 0 to allow an unlimited amount.

# We recommend you leave this number high, for maximum performance.

#

MaxKeepAliveRequests 100

 

#

# KeepAliveTimeout: Number of seconds to wait for the next request from the

# same client on the same connection.

#

KeepAliveTimeout 15

 

#

# Server-pool size regulation. Rather than making you guess how many

# server processes you need, Apache dynamically adapts to the load it

# sees --- that is, it tries to maintain enough server processes to

# handle the current load, plus a few spare servers to handle transient

# load spikes (e.g., multiple simultaneous requests from a single

# Netscape browser).

#

# It does this by periodically checking how many servers are waiting

# for a request. If there are fewer than MinSpareServers, it creates

# a new spare. If there are more than MaxSpareServers, some of the

# spares die off. The default values are probably OK for most sites.

#

MinSpareServers 5

MaxSpareServers 10

 

#

# Number of servers to start initially --- should be a reasonable ballpark

# figure.

#

StartServers 5

 

#

# Limit on total number of servers running, i.e., limit on the number

# of clients who can simultaneously connect --- if this limit is ever

# reached, clients will be LOCKED OUT, so it should NOT BE SET TOO LOW.

# It is intended mainly as a brake to keep a runaway server from taking

# the system with it as it spirals down...

#

MaxClients 150

 

#

# MaxRequestsPerChild: the number of requests each child process is

# allowed to process before the child dies. The child will exit so

# as to avoid problems after prolonged use when Apache (and maybe the

# libraries it uses) leak memory or other resources. On most systems, this

# isn't really needed, but a few (such as Solaris) do have notable leaks

# in the libraries. For these platforms, set to something like 10000

# or so; a setting of 0 means unlimited.

#

# NOTE: This value does not include keepalive requests after the initial

# request per connection. For example, if a child process handles

# an initial request and 10 subsequent "keptalive" requests, it

# would only count as 1 request towards this limit.

#

MaxRequestsPerChild 0

 

#

# Listen: Allows you to bind Apache to specific IP addresses and/or

# ports, instead of the default. See also the <VirtualHost>

# directive.

#

#Listen 3000

#Listen 12.34.56.78:80

 

#

# BindAddress: You can support virtual hosts with this option. This directive

# is used to tell the server which IP address to listen to. It can either

# contain "*", an IP address, or a fully qualified Internet domain name.

# See also the <VirtualHost> and Listen directives.

#

#BindAddress *

 

#

# Dynamic Shared Object (DSO) Support

#

# To be able to use the functionality of a module which was built as a DSO you

# have to place corresponding `LoadModule' lines at this location so the

# directives contained in it are actually available _before_ they are used.

# Please read the file http://httpd.apache.org/docs/dso.html for more

# details about the DSO mechanism and run `httpd -l' for the list of already

# built-in (statically linked and thus always available) modules in your httpd

# binary.

#

# Note: The order in which modules are loaded is important. Don't change

# the order below without expert advice.

#

# Example:

# LoadModule foo_module libexec/mod_foo.so

LoadModule php4_module libexec/libphp4.so

 

#

# ExtendedStatus controls whether Apache will generate "full" status

# information (ExtendedStatus On) or just basic information (ExtendedStatus

# Off) when the "server-status" handler is called. The default is Off.

#

#ExtendedStatus On

 

### Section 2: 'Main' server configuration

#

# The directives in this section set up the values used by the 'main'

# server, which responds to any requests that aren't handled by a

# <VirtualHost> definition. These values also provide defaults for

# any <VirtualHost> containers you may define later in the file.

#

# All of these directives may appear inside <VirtualHost> containers,

# in which case these default settings will be overridden for the

# virtual host being defined.

#

 

#

# If your ServerType directive (set earlier in the 'Global Environment'

# section) is set to "inetd", the next few directives don't have any

# effect since their settings are defined by the inetd configuration.

# Skip ahead to the ServerAdmin directive.

#

 

#

# Port: The port to which the standalone server listens. For

# ports < 1023, you will need httpd to be run as root initially.

#

Port 80

 

#

# If you wish httpd to run as a different user or group, you must run

# httpd as root initially and it will switch.

#

# User/Group: The name (or #number) of the user/group to run httpd as.

# . On SCO (ODT 3) use "User nouser" and "Group nogroup".

# . On HPUX you may not be able to use shared memory as nobody, and the

# suggested workaround is to create a user www and use that user.

# NOTE that some kernels refuse to setgid(Group) or semctl(IPC_SET)

# when the value of (unsigned)Group is above 60000;

# don't use Group "#-1" on these systems!

#

User nobody

Group nobody

 

#

# ServerAdmin: Your address, where problems with the server should be

# e-mailed. This address appears on some server-generated pages, such

# as error documents.

#

ServerAdmin stephen@localhost.localdomain

 

#

# ServerName allows you to set a host name which is sent back to clients for

# your server if it's different than the one the program would get (i.e., use

# "www" instead of the host's real name).

#

# Note: You cannot just invent host names and hope they work. The name you

# define here must be a valid DNS name for your host. If you don't understand

# this, ask your network administrator.

# If your host doesn't have a registered DNS name, enter its IP address here.

# You will have to access it by its address (e.g., http://123.45.67.89/)

# anyway, and this will make redirections work in a sensible way.

#

# 127.0.0.1 is the TCP/IP local loop-back address, often named localhost. Your

# machine always knows itself by this address. If you use Apache strictly for

# local testing and development, you may use 127.0.0.1 as the server name.

#

#ServerName www.example.com

 

#

# DocumentRoot: The directory out of which you will serve your

# documents. By default, all requests are taken from this directory, but

# symbolic links and aliases may be used to point to other locations.

#

DocumentRoot "/usr/local/apache/htdocs"

 

#

# Each directory to which Apache has access, can be configured with respect

# to which services and features are allowed and/or disabled in that

# directory (and its subdirectories).

#

# First, we configure the "default" to be a very restrictive set of

# permissions.

#

<Directory />

Options FollowSymLinks

AllowOverride All

</Directory>

 

#

# Note that from this point forward you must specifically allow

# particular features to be enabled - so if something's not working as

# you might expect, make sure that you have specifically enabled it

# below.

#

 

#

# This should be changed to whatever you set DocumentRoot to.

#

<Directory "/usr/local/apache/htdocs">

 

#

# This may also be "None", "All", or any combination of "Indexes",

# "Includes", "FollowSymLinks", "ExecCGI", or "MultiViews".

#

# Note that "MultiViews" must be named *explicitly* --- "Options All"

# doesn't give it to you.

#

Options Indexes FollowSymLinks MultiViews

 

#

# This controls which options the .htaccess files in directories can

# override. Can also be "All", or any combination of "Options", "FileInfo",

# "AuthConfig", and "Limit"

#

AllowOverride All

 

#

# Controls who can get stuff from this server.

#

Order allow,deny

Allow from all

</Directory>

 

#

# UserDir: The name of the directory which is appended onto a user's home

# directory if a ~user request is received.

#

<IfModule mod_userdir.c>

UserDir public_html

</IfModule>

 

#

# Control access to UserDir directories. The following is an example

# for a site where these directories are restricted to read-only.

#

#<Directory /home/*/public_html>

# AllowOverride FileInfo AuthConfig Limit

# Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec

# <Limit GET POST OPTIONS PROPFIND>

# Order allow,deny

# Allow from all

# </Limit>

# <LimitExcept GET POST OPTIONS PROPFIND>

# Order deny,allow

# Deny from all

# </LimitExcept>

#</Directory>

 

#

# DirectoryIndex: Name of the file or files to use as a pre-written HTML

# directory index. Separate multiple entries with spaces.

#

<IfModule mod_dir.c>

DirectoryIndex index.html index.htm index.php

</IfModule>

 

#

# AccessFileName: The name of the file to look for in each directory

# for access control information.

#

AccessFileName .htaccess

 

#

# The following lines prevent .htaccess files from being viewed by

# Web clients. Since .htaccess files often contain authorization

# information, access is disallowed for security reasons. Comment

# these lines out if you want Web visitors to see the contents of

# .htaccess files. If you change the AccessFileName directive above,

# be sure to make the corresponding changes here.

#

# Also, folks tend to use names such as .htpasswd for password

# files, so this will protect those as well.

#

<Files ~ "^\.ht">

Order allow,deny

Deny from all

Satisfy All

</Files>

 

#

# CacheNegotiatedDocs: By default, Apache sends "Pragma: no-cache" with each

# document that was negotiated on the basis of content. This asks proxy

# servers not to cache the document. Uncommenting the following line disables

# this behavior, and proxies will be allowed to cache the documents.

#

#CacheNegotiatedDocs

 

#

# UseCanonicalName: (new for 1.3) With this setting turned on, whenever

# Apache needs to construct a self-referencing URL (a URL that refers back

# to the server the response is coming from) it will use ServerName and

# Port to form a "canonical" name. With this setting off, Apache will

# use the hostname:port that the client supplied, when possible. This

# also affects SERVER_NAME and SERVER_PORT in CGI scripts.

#

UseCanonicalName On

 

#

# TypesConfig describes where the mime.types file (or equivalent) is

# to be found.

#

<IfModule mod_mime.c>

TypesConfig /usr/local/apache/conf/mime.types

</IfModule>

 

#

# DefaultType is the default MIME type the server will use for a document

# if it cannot otherwise determine one, such as from filename extensions.

# If your server contains mostly text or HTML documents, "text/plain" is

# a good value. If most of your content is binary, such as applications

# or images, you may want to use "application/octet-stream" instead to

# keep browsers from trying to display binary files as though they are

# text.

#

DefaultType text/plain

 

#

# The mod_mime_magic module allows the server to use various hints from the

# contents of the file itself to determine its type. The MIMEMagicFile

# directive tells the module where the hint definitions are located.

# mod_mime_magic is not part of the default server (you have to add

# it yourself with a LoadModule [see the DSO paragraph in the 'Global

# Environment' section], or recompile the server and include mod_mime_magic

# as part of the configuration), so it's enclosed in an <IfModule> container.

# This means that the MIMEMagicFile directive will only be processed if the

# module is part of the server.

#

<IfModule mod_mime_magic.c>

MIMEMagicFile /usr/local/apache/conf/magic

</IfModule>

 

#

# HostnameLookups: Log the names of clients or just their IP addresses

# e.g., www.apache.org (on) or 204.62.129.132 (off).

# The default is off because it'd be overall better for the net if people

# had to knowingly turn this feature on, since enabling it means that

# each client request will result in AT LEAST one lookup request to the

# nameserver.

#

HostnameLookups Off

 

#

# ErrorLog: The location of the error log file.

# If you do not specify an ErrorLog directive within a <VirtualHost>

# container, error messages relating to that virtual host will be

# logged here. If you *do* define an error logfile for a <VirtualHost>

# container, that host's errors will be logged there and not here.

#

ErrorLog /usr/local/apache/logs/error_log

 

#

# LogLevel: Control the number of messages logged to the error_log.

# Possible values include: debug, info, notice, warn, error, crit,

# alert, emerg.

#

LogLevel warn

 

#

# The following directives define some format nicknames for use with

# a CustomLog directive (see below).

#

LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined

LogFormat "%h %l %u %t \"%r\" %>s %b" common

LogFormat "%{Referer}i -> %U" referer

LogFormat "%{User-agent}i" agent

 

#

# The location and format of the access logfile (Common Logfile Format).

# If you do not define any access logfiles within a <VirtualHost>

# container, they will be logged here. Contrariwise, if you *do*

# define per-<VirtualHost> access logfiles, transactions will be

# logged therein and *not* in this file.

#

CustomLog /usr/local/apache/logs/access_log common

 

#

# If you would like to have agent and referer logfiles, uncomment the

# following directives.

#

#CustomLog /usr/local/apache/logs/referer_log referer

#CustomLog /usr/local/apache/logs/agent_log agent

 

#

# If you prefer a single logfile with access, agent, and referer information

# (Combined Logfile Format) you can use the following directive.

#

#CustomLog /usr/local/apache/logs/access_log combined

 

#

# Optionally add a line containing the server version and virtual host

# name to server-generated pages (error documents, FTP directory listings,

# mod_status and mod_info output etc., but not CGI generated documents).

# Set to "EMail" to also include a mailto: link to the ServerAdmin.

# Set to one of: On | Off | EMail

#

ServerSignature On

 

# EBCDIC configuration:

# (only for mainframes using the EBCDIC codeset, currently one of:

# Fujitsu-Siemens' BS2000/OSD, IBM's OS/390 and IBM's TPF)!!

# The following default configuration assumes that "text files"

# are stored in EBCDIC (so that you can operate on them using the

# normal POSIX tools like grep and sort) while "binary files" are

# stored with identical octets as on an ASCII machine.

#

# The directives are evaluated in configuration file order, with

# the EBCDICConvert directives applied before EBCDICConvertByType.

#

# If you want to have ASCII HTML documents and EBCDIC HTML documents

# at the same time, you can use the file extension to force

# conversion off for the ASCII documents:

# > AddType text/html .ahtml

# > EBCDICConvert Off=InOut .ahtml

#

# EBCDICConvertByType On=InOut text/* message/* multipart/*

# EBCDICConvertByType On=In application/x-www-form-urlencoded

# EBCDICConvertByType On=InOut application/postscript model/vrml

# EBCDICConvertByType Off=InOut */*

 

 

#

# Aliases: Add here as many aliases as you need (with no limit). The format is

# Alias fakename realname

#

<IfModule mod_alias.c>

 

#

# Note that if you include a trailing / on fakename then the server will

# require it to be present in the URL. So "/icons" isn't aliased in this

# example, only "/icons/". If the fakename is slash-terminated, then the

# realname must also be slash terminated, and if the fakename omits the

# trailing slash, the realname must also omit it.

#

Alias /icons/ "/usr/local/apache/icons/"

 

<Directory "/usr/local/apache/icons">

Options Indexes MultiViews

AllowOverride None

Order allow,deny

Allow from all

</Directory>

 

# This Alias will project the on-line documentation tree under /manual/

# even if you change the DocumentRoot. Comment it if you don't want to

# provide access to the on-line documentation.

#

Alias /manual/ "/usr/local/apache/htdocs/manual/"

 

<Directory "/usr/local/apache/htdocs/manual">

Options Indexes FollowSymlinks MultiViews

AllowOverride None

Order allow,deny

Allow from all

</Directory>

 

#

# ScriptAlias: This controls which directories contain server scripts.

# ScriptAliases are essentially the same as Aliases, except that

# documents in the realname directory are treated as applications and

# run by the server when requested rather than as documents sent to the client.

# The same rules about trailing "/" apply to ScriptAlias directives as to

# Alias.

#

ScriptAlias /cgi-bin/ "/usr/local/apache/cgi-bin/"

 

#

# "/usr/local/apache/cgi-bin" should be changed to whatever your ScriptAliased

# CGI directory exists, if you have that configured.

#

<Directory "/usr/local/apache/cgi-bin">

AllowOverride None

Options None

Order allow,deny

Allow from all

</Directory>

 

</IfModule>

# End of aliases.

 

#

# Redirect allows you to tell clients about documents which used to exist in

# your server's namespace, but do not anymore. This allows you to tell the

# clients where to look for the relocated document.

# Format: Redirect old-URI new-URL

#

 

#

# Directives controlling the display of server-generated directory listings.

#

<IfModule mod_autoindex.c>

 

#

# FancyIndexing is whether you want fancy directory indexing or standard

#

IndexOptions FancyIndexing

 

#

# AddIcon* directives tell the server which icon to show for different

# files or filename extensions. These are only displayed for

# FancyIndexed directories.

#

AddIconByEncoding (CMP,/icons/compressed.gif) x-compress x-gzip

 

AddIconByType (TXT,/icons/text.gif) text/*

AddIconByType (IMG,/icons/image2.gif) image/*

AddIconByType (SND,/icons/sound2.gif) audio/*

AddIconByType (VID,/icons/movie.gif) video/*

 

AddIcon /icons/binary.gif .bin .exe

AddIcon /icons/binhex.gif .hqx

AddIcon /icons/tar.gif .tar

AddIcon /icons/world2.gif .wrl .wrl.gz .vrml .vrm .iv

AddIcon /icons/compressed.gif .Z .z .tgz .gz .zip

AddIcon /icons/a.gif .ps .ai .eps

AddIcon /icons/layout.gif .html .shtml .htm .pdf

AddIcon /icons/text.gif .txt

AddIcon /icons/c.gif .c

AddIcon /icons/p.gif .pl .py

AddIcon /icons/f.gif .for

AddIcon /icons/dvi.gif .dvi

AddIcon /icons/uuencoded.gif .uu

AddIcon /icons/script.gif .conf .sh .shar .csh .ksh .tcl

AddIcon /icons/tex.gif .tex

AddIcon /icons/bomb.gif core

 

AddIcon /icons/back.gif ..

AddIcon /icons/hand.right.gif README

AddIcon /icons/folder.gif ^^DIRECTORY^^

AddIcon /icons/blank.gif ^^BLANKICON^^

 

#

# DefaultIcon is which icon to show for files which do not have an icon

# explicitly set.

#

DefaultIcon /icons/unknown.gif

 

#

# AddDescription allows you to place a short description after a file in

# server-generated indexes. These are only displayed for FancyIndexed

# directories.

# Format: AddDescription "description" filename

#

#AddDescription "GZIP compressed document" .gz

#AddDescription "tar archive" .tar

#AddDescription "GZIP compressed tar archive" .tgz

 

#

# ReadmeName is the name of the README file the server will look for by

# default, and append to directory listings.

#

# HeaderName is the name of a file which should be prepended to

# directory indexes.

#

ReadmeName README.html

HeaderName HEADER.html

 

#

# IndexIgnore is a set of filenames which directory indexing should ignore

# and not include in the listing. Shell-style wildcarding is permitted.

#

IndexIgnore .??* *~ *# HEADER* README* RCS CVS *,v *,t

 

</IfModule>

# End of indexing directives.

 

#

# Document types.

#

<IfModule mod_mime.c>

 

#

# AddLanguage allows you to specify the language of a document. You can

# then use content negotiation to give a browser a file in a language

# it can understand.

#

# Note 1: The suffix does not have to be the same as the language

# keyword --- those with documents in Polish (whose net-standard

# language code is pl) may wish to use "AddLanguage pl .po" to

# avoid the ambiguity with the common suffix for perl scripts.

#

# Note 2: The example entries below illustrate that in quite

# some cases the two character 'Language' abbreviation is not

# identical to the two character 'Country' code for its country,

# E.g. 'Danmark/dk' versus 'Danish/da'.

#

# Note 3: In the case of 'ltz' we violate the RFC by using a three char

# specifier. But there is 'work in progress' to fix this and get

# the reference data for rfc1766 cleaned up.

#

# Danish (da) - Dutch (nl) - English (en) - Estonian (ee)

# French (fr) - German (de) - Greek-Modern (el)

# Italian (it) - Korean (kr) - Norwegian (no) - Norwegian Nynorsk (nn)

# Portugese (pt) - Luxembourgeois* (ltz)

# Spanish (es) - Swedish (sv) - Catalan (ca) - Czech(cs)

# Polish (pl) - Brazilian Portuguese (pt-br) - Japanese (ja)

# Russian (ru)

#

AddLanguage da .dk

AddLanguage nl .nl

AddLanguage en .en

AddLanguage et .ee

AddLanguage fr .fr

AddLanguage de .de

AddLanguage el .el

AddLanguage he .he

AddCharset ISO-8859-8 .iso8859-8

AddLanguage it .it

AddLanguage ja .ja

AddCharset ISO-2022-JP .jis

AddLanguage kr .kr

AddCharset ISO-2022-KR .iso-kr

AddLanguage nn .nn

AddLanguage no .no

AddLanguage pl .po

AddCharset ISO-8859-2 .iso-pl

AddLanguage pt .pt

AddLanguage pt-br .pt-br

AddLanguage ltz .lu

AddLanguage ca .ca

AddLanguage es .es

AddLanguage sv .sv

AddLanguage cs .cz .cs

AddLanguage ru .ru

AddLanguage zh-TW .zh-tw

AddCharset Big5 .Big5 .big5

AddCharset WINDOWS-1251 .cp-1251

AddCharset CP866 .cp866

AddCharset ISO-8859-5 .iso-ru

AddCharset KOI8-R .koi8-r

AddCharset UCS-2 .ucs2

AddCharset UCS-4 .ucs4

AddCharset UTF-8 .utf8

 

# LanguagePriority allows you to give precedence to some languages

# in case of a tie during content negotiation.

#

# Just list the languages in decreasing order of preference. We have

# more or less alphabetized them here. You probably want to change this.

#

<IfModule mod_negotiation.c>

LanguagePriority en da nl et fr de el it ja kr no pl pt pt-br ru ltz ca es sv tw

</IfModule>

 

#

# AddType allows you to tweak mime.types without actually editing it, or to

# make certain files to be certain types.

#

AddType application/x-tar .tgz

AddType application/x-httpd-php .php .phtml

AddType application/x-httpd-php-source .phps

 

#

# AddEncoding allows you to have certain browsers uncompress

# information on the fly. Note: Not all browsers support this.

# Despite the name similarity, the following Add* directives have nothing

# to do with the FancyIndexing customization directives above.

#

AddEncoding x-compress .Z

AddEncoding x-gzip .gz .tgz

#

# If the AddEncoding directives above are commented-out, then you

# probably should define those extensions to indicate media types:

#

#AddType application/x-compress .Z

#AddType application/x-gzip .gz .tgz

 

#

# AddHandler allows you to map certain file extensions to "handlers",

# actions unrelated to filetype. These can be either built into the server

# or added with the Action command (see below)

#

# If you want to use server side includes, or CGI outside

# ScriptAliased directories, uncomment the following lines.

#

# To use CGI scripts:

#

#AddHandler cgi-script .cgi

 

#

# To use server-parsed HTML files

#

#AddType text/html .shtml

#AddHandler server-parsed .shtml

 

#

# Uncomment the following line to enable Apache's send-asis HTTP file

# feature

#

#AddHandler send-as-is asis

 

#

# If you wish to use server-parsed imagemap files, use

#

#AddHandler imap-file map

 

#

# To enable type maps, you might want to use

#

#AddHandler type-map var

 

</IfModule>

# End of document types.

 

#

# Action lets you define media types that will execute a script whenever

# a matching file is called. This eliminates the need for repeated URL

# pathnames for oft-used CGI file processors.

# Format: Action media/type /cgi-script/location

# Format: Action handler-name /cgi-script/location

#

 

#

# MetaDir: specifies the name of the directory in which Apache can find

# meta information files. These files contain additional HTTP headers

# to include when sending the document

#

#MetaDir .web

 

#

# MetaSuffix: specifies the file name suffix for the file containing the

# meta information.

#

#MetaSuffix .meta

 

#

# Customizable error response (Apache style)

# these come in three flavors

#

# 1) plain text

#ErrorDocument 500 "The server made a boo boo.

# n.b. the single leading (") marks it as text, it does not get output

#

# 2) local redirects

#ErrorDocument 404 /missing.html

# to redirect to local URL /missing.html

#ErrorDocument 404 /cgi-bin/missing_handler.pl

# N.B.: You can redirect to a script or a document using server-side-includes.

#

# 3) external redirects

#ErrorDocument 402 http://www.example.com/subscription_info.html

# N.B.: Many of the environment variables associated with the original

# request will *not* be available to such a script.

 

#

# Customize behaviour based on the browser

#

<IfModule mod_setenvif.c>

 

#

# The following directives modify normal HTTP response behavior.

# The first directive disables keepalive for Netscape 2.x and browsers that

# spoof it. There are known problems with these browser implementations.

# The second directive is for Microsoft Internet Explorer 4.0b2

# which has a broken HTTP/1.1 implementation and does not properly

# support keepalive when it is used on 301 or 302 (redirect) responses.

#

BrowserMatch "Mozilla/2" nokeepalive

BrowserMatch "MSIE 4\.0b2;" nokeepalive downgrade-1.0 force-response-1.0

 

#

# The following directive disables HTTP/1.1 responses to browsers which

# are in violation of the HTTP/1.0 spec by not being able to grok a

# basic 1.1 response.

#

BrowserMatch "RealPlayer 4\.0" force-response-1.0

BrowserMatch "Java/1\.0" force-response-1.0

BrowserMatch "JDK/1\.0" force-response-1.0

 

</IfModule>

# End of browser customization directives

 

#

# Allow server status reports, with the URL of http://servername/server-status

# Change the ".example.com" to match your domain to enable.

#

#<Location /server-status>

# SetHandler server-status

# Order deny,allow

# Deny from all

# Allow from .example.com

#</Location>

 

#

# Allow remote server configuration reports, with the URL of

# http://servername/server-info (requires that mod_info.c be loaded).

# Change the ".example.com" to match your domain to enable.

#

#<Location /server-info>

# SetHandler server-info

# Order deny,allow

# Deny from all

# Allow from .example.com

#</Location>

 

#

# There have been reports of people trying to abuse an old bug from pre-1.1

# days. This bug involved a CGI script distributed as a part of Apache.

# By uncommenting these lines you can redirect these attacks to a logging

# script on phf.apache.org. Or, you can record them yourself, using the script

# support/phf_abuse_log.cgi.

#

#<Location /cgi-bin/phf*>

# Deny from all

# ErrorDocument 403 http://phf.apache.org/phf_abuse_log.cgi

#</Location>

 

### Section 3: Virtual Hosts

#

# VirtualHost: If you want to maintain multiple domains/hostnames on your

# machine you can setup VirtualHost containers for them. Most configurations

# use only name-based virtual hosts so the server doesn't need to worry about

# IP addresses. This is indicated by the asterisks in the directives below.

#

# Please see the documentation at <URL:http://www.apache.org/docs/vhosts/>

# for further details before you try to setup virtual hosts.

#

# You may use the command line option '-S' to verify your virtual host

# configuration.

 

#

# Use name-based virtual hosting.

#

#NameVirtualHost *:80

 

#

# VirtualHost example:

# Almost any Apache directive may go into a VirtualHost container.

# The first VirtualHost section is used for requests without a known

# server name.

#

#<VirtualHost *:80>

# ServerAdmin webmaster@dummy-host.example.com

# DocumentRoot /www/docs/dummy-host.example.com

# ServerName dummy-host.example.com

# ErrorLog logs/dummy-host.example.com-error_log

# CustomLog logs/dummy-host.example.com-access_log common

#</VirtualHost>

Share this post


Link to post
Share on other sites

In the future please do not post the enture contents of a file...especially one that is as lenghty as above.

 

Your settings are correct...I am at a loss since I'm not sitting in front of your terminal. Sorry I couldn't be of more help.

 

Bobby

Share this post


Link to post
Share on other sites

Great contribution Chemo! :)

 

Now... what would I have to change to make it do its thing to popup_image.php? (I don't use product_info at all; popup_image makes more sense for my products.)

 

Thanks!

Share this post


Link to post
Share on other sites

Help needed :'(

 

I spent few hours to try why when i active the SEO 's Rewrite i have some problems within my cart if some items have been selected with some options (attributes).

 

everything works weel if i use the cName's method, but i much really appreciate the rewriting method.

 

But here is my problem.

 

Imagine i have 2 products in my shoppiung cart. the first one have no attributes selected.

 

link is for exemple :

 

http://localhost/***/catalog/micro-uxs57e-p-122.html?osCsid=b3d3bb9a8a24fe08511d702e135d551f

 

the second products, have a attribute which has been selected... link for this product in the shopping cart become

 

http://localhost/***/catalog/product_info.php?products_id=122{1}1?osCsid=b3d3bb9a8a24fe08511d702e135d551f

 

note than we have the exact same OscId , and that's normal with SEO than "122{1}1" is not known in the cache, so it's normal than the html_output give us a "normal" product_info.php link instead of the one with the rewrite method.

 

BUT, when i click on the second link, i'm really surprised cause althought my navigator display osCsid=b3d3bb9a8a24fe08511d702e135d551f in the navbar, i losted my session ! All my link have now a new OscId infact something else than b3d3bb9a8a24fe08511d702e135d551f !!

 

I'm nearly sure i'm not the first person who have this problem, but any solution would really be appreciated.

 

Thanks by advance

 

C?dric

Edited by Percu.org

Share this post


Link to post
Share on other sites
Great contribution Chemo! :)

 

Now... what would I have to change to make it do its thing to popup_image.php?  (I don't use product_info at all; popup_image makes more sense for my products.)

 

Thanks!

Interesting...it shouldn't be that hard to do since most of the code is already there.

 

Before we try something harder let's do the simple thing. In includes/functions/html_output.php find this code which is located in the tep_href_link() function:

$seo_pages = array('index.php', 'product_info.php');

and change it to this (basically adding the popup_image.php file):

$seo_pages = array('index.php', 'product_info.php', 'popup_image.php');

Next, find this code just a little farther down:

   	 case 'products_id':
     $rewrite_product = true;      
     if ( defined('PRODUCT_NAME_'.$p2[1]) ){
    	 $rewrite_page_product = short_name(constant('PRODUCT_NAME_'.$p2[1])) . '-p-' . $p2[1] . '.html';
     } else { $seo = false; }
     break;  

Just after that paste this code which adds an SEO form to the popup_image file:

   	 case 'pID':
     $rewrite_product = true;      
     if ( defined('PRODUCT_NAME_'.$p2[1]) ){
    	 $rewrite_page_product = short_name(constant('PRODUCT_NAME_'.$p2[1])) . '-image-' . $p2[1] . '.html';
     } else { $seo = false; }
     break;  

Now the URL's for the popup_image should be SEO'd. The next step is to add the entry to the htaccess file so the server will know how to handle it. Find this code in the htaccess file located in your catalog directory:

RewriteRule ^(.*)-p-(.*).html$ product_info.php?products_id=$2&%{QUERY_STRING}

and just after paste this:

RewriteRule ^(.*)-image-(.*).html$ popup_image.php?pID=$2&%{QUERY_STRING}

Save both files and the popup_images should be SEO'd :) I've tested this on my dev server and it works nicely. It should be noted that it'll work for the rewrite method and different code is needed for the cName version.

 

Help needed  :'(

 

I spent few hours to try why when i active the SEO 's Rewrite i have some problems within my cart if some items have been selected with some options (attributes).

 

everything works weel if i use the cName's method, but i much really appreciate the rewriting method.

 

But here is my problem.

 

Imagine i have 2 products in my shoppiung cart. the first one have no attributes selected.

 

link is for exemple :

 

http://localhost/***/catalog/micro-uxs57e-p-122.html?osCsid=b3d3bb9a8a24fe08511d702e135d551f

 

the second products, have a attribute which has been selected... link for this product in the shopping cart become

 

http://localhost/***/catalog/product_info.php?products_id=122{1}1?osCsid=b3d3bb9a8a24fe08511d702e135d551f

 

note than we have the exact same OscId , and that's normal with SEO than "122{1}1" is not known in the cache, so it's normal than the html_output give us a "normal" product_info.php link instead of the one with the rewrite method.

 

BUT, when i click on the second link, i'm really surprised cause althought my navigator display osCsid=b3d3bb9a8a24fe08511d702e135d551f in the navbar, i losted my session ! All my link have now a new OscId infact something else than b3d3bb9a8a24fe08511d702e135d551f !!

 

I'm nearly sure i'm not the first person who have this problem, but any solution would really be appreciated.

 

Thanks by advance

 

C?dric

I have looked over the code at least 5 times now and the ONLY way I can see where that situation would present is if you have the stock osC option of SEF URLs enabled. If this is the case please disable the option and the return URL for the product on the shopping cart page will function correctly.

 

The problem is in the code where if the SEF is enabled it strips everything and replaces them with forward slashes. For example, products_info/products_id/XX. Directly after transforming it the proper separator to use is the "?" character. Notice that the faulty URL you provided has 2 "?" marks (the second should be an "&" symbol). The "?" character tells the server that everything following are parameters and not part of the file name. The "&" character tells the server where one ends and another parameter begins.

 

Turn off the option and report back as to whether that handled the issue.

 

Admin Control Panel -> Configuration -> My Store -> Use Search-Engine Safe URLs (still in development) -> FALSE

 

Bobby

Edited by Chemo

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×