Archive for the Shopbetreiber Tipps Category

Date Criteria for Product Listing

OXID allows for 2 criteria for date-calculations upon which product sorting and filtering is based. This is governed by the configuration variable “Calculate newest Products by Date of Creation”, reachable under:

Master > Core-Settings > Settings > Products > “Calculate newest Products by Date of Creation (otherwise by Date of last Change)”.

Changing Shop Administration/Owner's Email Address

In order to set or reset the email address, to which all shop-generated emails are sent, use Master Settings > Core Settings as seen in below screenshot.

OXID Shop Owner Email-Address Settings

OXID Shop Owner Email-Address Settings

Schützen Sie den OXID Admin-Bereich mit .htaccess

Auch wenn OXID standardmäßig einen Authentifizierungsmechanismus für den Admin-Bereich verwendet, ist es ratsam zusätzlich .htaccess einzusetzen. Damit werden Hacker (und skrupellose Konkurrenten) von Ihrem OXID Admin-Bereich fern gehalten.

Im Folgenden eine kleine Anleitung zum Einrichten der .htaccess Authentifizierung unter Linux

Es werden 2 Dateien benötigt, um .htaccess in Ihrem Shop zu installieren:

  • Die .htaccess Datei selbst
  • Eine Passwort Text-Datei, die den verschlüsselten Benutzernamen inkl. Passwort enthält

OXID Owner Admin .htpasswd, .htaccess File

OXID Owner Admin .htpasswd, .htaccess File

Schritt 1

Erstellen Sie eine .htaccess Datei mittels touch oder vi und fügen Sie sie in Ihren OXID Admin-Bereich ein. Die Datei sollte die folgende Zeilen enthalten:

AuthName "OXID Admin"
AuthType Basic
AuthUserFile /full/nonweb/directory/.htpasswd
Require valid-user

Schritt 2

Erstellen Sie mit Hilfe des folgenden Befehls an einem beliebigen (nicht auf dem Web-Server befindlichen) Ort die .htpasswd Datei:

myshell: htpasswd /full/nonweb/directory/.htpasswd admin_username

Nach Eingabe werden Sie dazu aufgefordert, ein Passwort einzugeben und anschließend zu verifizieren.

Fertig! Sie Können die Funktion unter nun ausprobieren.

Protecting OXID Admin Area with .htaccess Password

Although OXID uses a standard authentication mechanism for protecting the /admin area, it is advisable to additionally apply .htaccess protection.  This will keep hackers (and maybe unscruplous competitors) out of your OXID-Admin area.

This quick howto helps you setup .htaccess authentication on Linux environments

2 files are needed for applying .htaccess protection to your shop:

  • The .htaccess file itself
  • A password text file in which the username and encrypted password are stored

OXID Owner Admin .htpasswd, .htaccess File

OXID Owner Admin .htpasswd, .htaccess File

Step 1

Create a .htaccess file in the /admin folder using touch or vi and place it in your OXID-Admin area.  This file should contain following contents.

AuthName "OXID Admin"
AuthType Basic
AuthUserFile /full/nonweb/directory/.htpasswd
Require valid-user

Step 2

At any location which is not exposed on the web-server, create a file called the location /full/nonweb/directory/ create the .htpasswd file, using the command-line htpasswd tool.  The exact command is:

myshell: htpasswd /full/nonweb/directory/.htpasswd admin_username

admin_username can usually be left as admin.

You will be prompted after the above shell command to provide a password, and then verify it.

That’s it!  You may now try this out at

Changing OXID Admin Password

To change the Admin-Password of OXID, please select any user, ensure that the user’s Access-Level is set to Admin and then scroll down to the user-editting form to input a new password.

Changing OXID Admin-Password

Changing OXID Admin Password

Please note that more than one administrator account may exist in OXID.

Order Confirmation Emails

For customizing the text included in Order-Confirmation-Emails sent to end-users after a purchase, CMS Pages under the “Emails” folder can be used, as seen in below screenshot.

Images in Article-Descriptions and CMS-Content

Since OXID is a rapidly developing system, it is a good idea to think about optimizing your upgrade processes from both within minor-versions and major-versions.

In order to make image URLs within article-descriptions and CMS-content as portable as possible, use such notations as:

<img alt="" src="[{$oViewConf->getImageUrl()}]my_picture.jpg" />

for inserting pictures in your WYSIWYIG-Editor.  This will ensure that the dynamic system-generated path to pictures is applied for display in shop front-end.

Limit Number of Customers who also bought this Product

On product-detail pages, it is possible for the shop admin to show which other products , other customers of a particular product also purchased.  The number of such “suggestions” could be very large, especially if there are a group of top-selling products in the shop.

You can limit the number of such suggested production on a product-detail page under Master Settings > Core Settings > Settings > Products, as seen below:

Standard OXID-Seiten für Web-Design Unternehmen

Wenn Sie als Web-Design Unternehmen Vorlagen von Seiten erstellen (im Bitmap/Photoshop/GIMP oder Vector/Illustrator/Inkscape Format), können Sie sich an den folgenden 6 Beispielen orientieren.

Diese 6 Seiten können anschließend von OXID e-Commerce Unternehmen (wie etwa euroblaze) verwendet werden, um funktionsfähige Templates zu erstellen.

Sie können auch alle 6 Screenshots im ZIP-Format herunterladen.