htaccess files should not be used for security restrictions

Share
Posted on November 21st, 2012 | Posted by admin

According to Apache documentation:

.htaccess files (or “distributed configuration files”) provide a way to make configuration changes on a per-directory basis. A file, containing one or more configuration directives, is placed in a particular document directory, and the directives apply to that directory, and all subdirectories thereof.

Many PHP web applications use .htaccess files to restrict access to specific files or directories that may contain sensitive information. For example, in order to restrict access to all files in a specific directory you can create a .htaccess file in that directory containing the string “deny from all”. In many cases it is wrong to impose security restrictions  using .htaccess files.  The reasons are:

Found solution for Magento – “SQLSTATE[HY000]: General error” on installation

Share
Posted on November 20th, 2012 | Posted by admin

I wrote already in the past about eCommerce System. I play with Magento till now from time to time. Unfortunately I had some problems with the installation and I could not find  help in the web. Therefore maybe this post  can be useful for some of you how is dealing whis Magento too.

The Problem

Every time on  the installation of Magento i saw following  exception.

Error in file: ".... app/code/core/Mage/Core/sql/core_setup/mysql4-install-0.8.0.php" - SQLSTATE[HY000]: General error: 1005 Can't create table './db203484_1/#sql-1dd4_17baf.frm' (errno: 121)
Trace:
#0 .../app/code/core/Mage/Core/Model/Resource/Setup.php(286): Mage::exception('Mage_Core', 'Error in file: ...')
#1 ...app/code/core/Mage/Core/Model/Resource/Setup.php(166): Mage_Core_Model_Resource_Setup->_modifyResourceDb('install', '', '0.8.11')
#2 .../app/code/core/Mage/Core/Model/Resource/Setup.php(154): Mage_Core_Model_Resource_Setup->_installResourceDb('0.8.11')
#3 .../app/code/core/Mage/Core/Model/Resource/Setup.php(120): Mage_Core_Model_Resource_Setup->applyUpdates()
#4 .../app/code/core/Mage/Core/Model/Config.php(215): Mage_Core_Model_Resource_Setup::applyAllUpdates()
#5 .../app/code/core/Mage/Core/Model/App.php(236): Mage_Core_Model_Config->init(Array)
#6 .../app/Mage.php(424): Mage_Core_Model_App->init('', 'store', Array)
#7 .../app/Mage.php(443): Mage::app('', 'store', Array)
#8 .../index.php(52): Mage::run()
#9 {main}

client denied by server configuration: app/etc/local.xml

Share
Posted on November 19th, 2012 | Posted by admin

You might have seen it in your Apache logs, but with Magento sites, your webserver might show messages that access to the file app/etc/local.xml. This is good, but web-access to the Magento local.xml file could indicate serious security problems. But what is causing this behaviour, and how to stop this from happening.

Magento checks for security

The message looks something like the following:

client denied by server configuration: MAGENTO_DIR/app/etc/local.xml

If you would check a bit further, you might notice that this message occurs when you try to visit the fileapp/etc/local.xml from within your browser: This is very good, because htaccess-rules should exist to block access to this XML-configuration file containing sensitive information about your database amongst others.

Winkelaanzicht specifieke informatie invoeren in Magento zonder extra winkelaanzicht (store view)

Share
Posted on November 18th, 2012 | Posted by admin

Regelmatig bouwen wij Magento import-scripts die databestanden uitlezen en automatisch nieuwe producten aanmaken, reeds bestaande producten updaten of producten uit een webshop verwijderen. Meestal is het wenselijk dat deze productinformatie met eigen informatie kan worden overschreven, dus dat de eigenaar van een webshop zelf bijvoorbeeld beschrijvingen, titels , productafbeeldingen of voorraadinformatie kan instellen. Deze imports draaien echter periodiek – zodat de productinformatie altijd up-to-date is – en het is niet de bedoeling dat de zelf ingevoerde informatie bij de eerst volgende keer dat de import draait verloren gaat.

Magento heeft voor deze situatie van huis uit eigenlijk een hele mooie oplossing. Wanneer er namelijk twee of meer winkelaanzichten (store view) worden aangemaakt – in de meeste gevallen zal een winkelaanzicht een taal representeren, de hiërarchie is; webshop > winkel > winkelaanzicht (taal) – dan is de informatie die ingevoerd ‘in’ een winkelaanzicht dominant over de informatie die geïmporteerd wordt. Deze winkelaanzichten liggen dus als het ware als extra laag over de geïmporteerde data heen. Productinformatie invoeren per winkelaanzicht kun je doen door op de producten beheer pagina bijvoorbeeld linksboven in het adminpanel de hiervoor bestemde option select te gebruiken:

Magento Facebook Connect and Publish

Share
Posted on November 17th, 2012 | Posted by admin

Sorting and describing brand names in your Magento store is not a challenge anymore. Whenever you put a new brand in the store or help your customers to find the required one, Magento shop by brand extension assists you in that. From now on your clients will be able to sort the products according to their brand names and make their search more convenient.