euroblaze | OXID e-Commerce User Blog

If you are using the OXID CE B2B Pro Shop, or for that any other standard OXID installation with the FCKEditor, and wish to insert images into your OXID:

• Product Descriptions
• Category Long Texts
• CMS Pages

or any other place the FCKEditor is used to edit content, one config file in the FCKEditor Module for OXID has to be set to define the file-storage location on the server, as well as the relative path to which URLs on web-page refer to.  Following are the adjustments to be made in the config.php file found at:

oxidshop@server:~/www/admin/fck/editor/filemanager/connectors/php/config.php

// Path to user files relative to the document root.
$Config['UserFilesPath'] = '/shopdir/out/' ;

// Fill the following value it you prefer to specify the absolute path for the
// user files directory. Useful if you are using a virtual directory, symbolic
// link or alias. Examples: 'C:\\MySite\\userfiles\\' or '/root/mysite/userfiles/'.
// Attention: The above 'UserFilesPath' must point to the same directory.
// $Config['UserFilesAbsolutePath'] = $_SERVER['DOCUMENT_ROOT'] . '/out/' ;
$Config['UserFilesAbsolutePath'] = '/home/shopdir/www/out/' ;

Drawback

The main drawbacks of this way of setting the FCKEditor image path are:

1. Cumbersome to dig into the FCKEditor installation and change code-files
2. When moving files from development, to staging, to production servers, this path has to be adjusted each time.  In addition, if you are using SVN for development purposes, the path has to be readjusted on each svn up, or figure out a way to eliminate it from the SVN paths.

Notes

Ideal would be for the FCKEditor Module for OXID to extract this path from OXID’s config.inc.php file, which would also offer the advantage of a single-point-of-maintenence.

See also

Images in OXID Article-Descriptions and CMS-Content

The default OXID eSales software comes without a WYSIWYG Editor.  euroblaze uses the FCKEditor to facilitate this to shop-owners who don’t want to deal with writing HTML code.

Inserting Images into FCKEditor

To upload pictures into your content edited by the editor, follow the markings on the screens below:

Related Articles

• Add Images into OXID Shop Using FCKEditor
• Images in Article-Descriptions and CMS-Content

This article is a continuation of Improving Performance of OXID Shops – Part 01

A configuration variable can be introduced into config.inc.php for specifying a URL for specifying an alternative location for images and other static media files like site-videos, flash-content or downloadable PDF etc.

$this->sAltImageDir = 'http://www.myshop.de:801/';

In our example, this particular location, is where our /out/pictures/ folder is mapped to. An NGINX server listens on port 801.

In this example we used the same server for hosting the Apache application-server (AAS) as well as the NGINX content-server (NCS) on the same server-instance.

The following sections contain a detailed account of how NGINX can be configured on a Debian Lenny/5.0 server.

NGINX on Debain 5.0/Lenny for OXID eShops

Debian/5.0 ships with Version 0.6.x of NGINX (latest from nginx.org is version 0.8.x), which works just well for our purpose.

NGINX configuration files and organization in the /etc/ folder is similar to that of Apache2.  Individual sites and Virtualhost(s) (or simply called server(s) in NGINX jargon) can be configured in /etc/nginx/sites-enabled/default.   The configuration block for our tests simply looks like:

server {
     listen   801;
     server_name  www.myshop.de;
     access_log  /var/log/nginx/localhost.access.log;

  location / {
     root   /home/myshop/www/out/pictures/;
     index  index.html index.htm;
}

Obviously, here www.myshop.de is the URL of your shop, files for which load from/home/myshop/www/ ($SHOP) and the pictures load from $SHOP/out/pictures.

Processes

The process list on the web-server instance looks as follows:

vm0:~# ps ax | grep -E "apache|nginx"
 1889 ?        Ss     0:00 /usr/sbin/apache2 -k start
 1905 ?        S      0:00 /usr/sbin/apache2 -k start
 1906 ?        S      0:00 /usr/sbin/apache2 -k start
 1907 ?        S      0:00 /usr/sbin/apache2 -k start
 1908 ?        S      0:00 /usr/sbin/apache2 -k start
 1909 ?        S      0:00 /usr/sbin/apache2 -k start
 2058 pts/0    S+     0:00 grep apache
 1756 ?        Ss     0:00 nginx: master process /usr/sbin/nginx
 1757 ?        S      0:00 nginx: worker process
 2060 pts/0    S+     0:00 grep nginx

For optimizing performance your OXID eShop or getting a new one developed, please contact euroblaze at +49-711-7947-2394 or oxid@euroblaze.de.

When creating B2C e-Commerce Shops, it is important to provide a high performance of online-shops.  For one thing it is important to keep an online-shop fast so that they are able to “quickly take care of business” and hence better the conversion rate.  For the other it is important to plan sufficient capacity so the the number of users/buyers can scale, even so in high-peak seasons.

The classical LAMP installation, though powerful in it’s server-side processing capabilities and features, is usually not the fastest server solution for certain types of data such as static media content such as images and videos.  Due to this OXID shops hosted on LAMP, while relying on Apache2/PHP5 and MySQL’s robust features, can benefit significantly in speed by relying on a high-performance static-content servers, such as NGINX.

There are several server configurations possible:

1. Apache and NGINX running on the same machine, the former hosting the OXID eSales application and the latter hosting only the related static content.
2. Apache running on an application server (AS) machine and NGINX serving static content (CS, Content-Server) from a separate machine.
3. Apache running on an application server, and NGINX service content from a network of content servers – a classical Content Delivery Network (CDN)

This series of articles explains how to setup OXID eSales shops in the 3 above configurations.

• NGINX for OXID eShop Images and Media Files – Part 02

Inspiration & Resources

Inspiration for this solution was taken from the following resources:

• Best Practices for Speeding Up Your Web Site – Yahoo Developer Network
• High Performance Web Sites: Rule 2 – Use a Content Delivery Network – Yahoo Developer Network
• OXID mit Vollgas – Henrik Steffen, Top Concepts GmbH (in German)

If you are using special zoom-tools like Magic Zoom, you may have to make modifications to the integration module with OXID, so that the tool uses appropriate high-performance URL for loading media-content.