You can download PrestaShop password resetter here. Download archive, extract it and upload to your shop’s root directory and access it with your browser.

Here are some screenshots:

Select emails for which you want to backup passwords and click “Download old passwords”:

Backup old PrestaShop password(s)

Now you can reset password(s). Select email(s) ( sorry I forgot to select email in next screenshot ) and click “Reset”:

Reset PrestaShop password

Now after you finished your job you can restore old passwords. Now you do not need to select any emails – just click Browse, choose the file you downloaded before and click “Upload File”:

Restore PrestaShop Password

This script is tested with PrestaShop 1.3 and 1.4 versions. The source code is well documented so you can check it your self and change it to your needs.

Well that’s it. If you have some questions just write a comment or an email to: donatas@invertus.lt

Cheers!

v1.7 2011/07/14 :
-  Added option to subscribe auctions – customers can subscribe to auction and get information about new bids.
-  Added ability to ban users from auctions – if you have some problems with malicious bidders you can ban some IP addresses or range of IP addresses.

Check our demo:

PrestaShop v1.3:

Demo address: http://www.invertus.lt/demo/ps13/
Demo admin address: http://www.invertus.lt/demo/ps13/admin1/
Module can be found in Modules tab -> under “Invertus” section.

PrestaShop v1.4:

Demo address: http://www.invertus.lt/demo/ps14/
Demo admin address: http://www.invertus.lt/demo/ps14/admin1/
Module can be found in Modules tab -> under “Other Modules” section.

Demo user login:
username: demo@invertus.lt
password: demologin

You can buy our module here: addons.prestashop.com.

That’s was PrestaShop newsletter says:

“- New image system so you can have a product catalogue with a million images!

« The sky’s the limit for your shop with the v.1.4.3 high-performance image system! PrestaShop is ideal for any shopkeeper no matter the size of the shop. »”

This new feature is not turned on by default in PrestaShop 1.4.3.0 – you have to enable it manually. Go to Preferences->Products and select Activate legacy images compatibility: to no:

Activate legacy images compatibility

If you have upgraded your PrestaShop system then you’ll have to move your images to the new images storage system. Go to Preferences->Image and go to the bottom of the page:

Move images to new storage system

Well done PrestaShop! We will definitely try this new version ASAP!

PrestaShop changed Cart’s class method from:

public function OrderExists()
{       
 $result = Db::getInstance()->ExecuteS('SELECT `id_cart` FROM `'
._DB_PREFIX_.'orders` WHERE `id_cart` = '.(int)($this->id));
 return Db::getInstance()->NumRows();
}

To:

public function OrderExists()
{
 return (bool)Db::getInstance()->getValue('SELECT `id_cart` FROM `'
._DB_PREFIX_.'orders` WHERE `id_cart` = '.(int)$this->id);

}

As you can see now it returns Boolean value not Integer.

Klarna payment module checks if the order exists with current cart with this line:

$cart->OrderExists() === 0

So now this statement returns false instead of true because variable type is not integer. It returned number of rows in earlier versions  – so 0 means that there was no any order with the current cart and the statement was correct.

You can find this line in file: modules/kreditor/kreditor.php and in modules/cashondeliverywithfee/cashondeliverywithfee.php.

Check these files and change statement from:

$cart->OrderExists() === 0

to:

!$cart->OrderExists()

It will solve the problem.

It’s early morning now and I hope I described this problem clearly. Well I need more coffee. Hope this post saves somebodies time.

1. Check if you are changing your password in correct server and correct database

Many times people just mix databases or servers. If you are sure then check this post maybe it will help you. If this method didn’t solved your problem go to step 2.

2. Check your __PS_BASE_URI__ parameter in settings.inc.php file

Your PrestaShop is  installed in web server root directory or sub directory. If you moved your shop to other directory then __PS_BASE_URI__ is incorrect and you will not be able to log in to your back office anymore. Or you could change this parameter accidentally.

Find file /config/settings.inc.php. Open it with text editor and check __PS_BASE_URI__ parameter. If your PrestaShop is located in a sub directory then it should look like this:

define('__PS_BASE_URI__', '/your_sub_directory_name/');

If it is in web server root directory then it should look like this:

define('__PS_BASE_URI__', '/');

It helped to me but if you still cannot access your admin admin then go to next stepl

3. Hack your PrestaShop (you’ll need FTP access)

It’s not actually a hacking because you’ll need access to your PrestaShop php files but it will allow you to access PreStashop back office with correct email and any at least 5 symbols random password – PrestaShop checks password length before authentication.

This method is unsecure because anybody will be able to login with correct email and any long enough password. 

OK find the file: your_admin_folder/login.php.

Find line:

$employee = $employee->getByemail($email, $passwd);

Change it to:

$employee = $employee->getByemail($email, null);

Now try to login  with correct email and at least 5 symbols random password. It worked for me – tested with PrestaShop 1.4.2.5 and 1.4.3.0

As I mentioned before this method is not actually hacking but it may be used for malicious purposes also

Updated 2011.07.02:

Well there is one more reason that can cause this problem – PHP bug: https://bugs.php.net/bug.php?id=42523

This problem was also reported to PrestaShop: http://forge.prestashop.com/browse/PSCFI-1110

If your PHP installation has this bug then $_SERVER['PHP_SELF'] variable will return the wrong value which is used in cookie path calculation.You can find this line in your admin folder/login.php file (54 line i PrestaShop 1.4.3.0):

$cookie = new Cookie('psAdmin', substr($_SERVER['PHP_SELF'],
strlen(__PS_BASE_URI__), -10));

Change this line to:

$cookie = new Cookie('psAdmin', substr($_SERVER['SCRIPT_NAME'],
strlen(__PS_BASE_URI__), -10));

It resolved the problem for me.

Hope you liked this post. Feel free to comment or suggest ideas for new articles 

We got this error:

No paytype(s)! Missing test parameter?

This is how I fixed it:

Open file modules/dibs/dibs.php.

Find line:

$dibsParams['test'] = (self::$TESTING === 1) ? 'yes' : 'no';

Replace it with this line:

if(self::$TESTING === 1)
{
    $dibsParams['test'] = 1;
}

It fixed the problem. Actually it is documented in DIBS documentation:

1. DIBS test parameter documentation

DIBS declared in their documentation that if you use standard payment window you should include test parameter in your form only if you are testing your system and the value should be only 1 – integer value. Read more here http://tech.dibs.dk/parameters/

If you use DIBS API the test parameter values should be yes or no. Read more here http://tech.dibs.dk/dibs_api/payment_functions/authcgi/

I tried to assign value 0 and it worked – strange. I think DIBS accepts 0 also but it does not accept 1 if your testing is not enabled by DIBS – read on.

2. DIBS testing

As I mentioned I tried to assign parameter test with value 1 but got the same problem. I could not make any tests. When it is assigned with value 0 – it worked. And this is why:

DIBS declared how testing should be performed. You should contact DIBS and ask them to enable testing environment. This is what DIBS documentation states:

“Your shop should have activated the test mode with DIBS. New shops always start with the test mode activated, but the test mode is deactivated as soon as the shop goes “live””

Read more here: http://tech.dibs.dk/10_step_guide/your_own_test/

3. Other noticed problems with DIBS

I also googled some incompatibilities with DIBS and other PreStashop modules. It seems that one page checkout and Mail alert module can also cause some problems. So teast DIBS before you go no production with this module. Read more about incompatibilities in this PrestaShop forum post.

4. Questions and Answers from DIBS support

1. If we want to integrate DIBS module in our webpage we should use this documentation page:  http://tech.dibs.dk/standard_payment_window_introduction/ – yes? If we use this method then test parameter can have only one value 1 (integer)?

Answer: yes.

2. If we use DIBS API then we should follow this documentation: http://tech.dibs.dk/dibs_api/payment_functions/authcgi/ – yes? And test parameter can have values “yes” or “no”?

Answer: yes.

3. If we want to test DIBS module we should ask DIBS to enable test environment like it is documented here: http://tech.dibs.dk/10_step_guide/your_own_test/ – yes?

Answer: yes.

5. Conclusion

OK I think the problem is solved. Assumptions were correct.  I have reported this problem to PrestaShop: http://forge.prestashop.com/browse/PSCFI-2191

If you have some questions I will reply them ASAP. Write me an email donatas@invertus.lt or just leave a comment on our blog!

Thank you!

Usually it’s better to wait for a couple of weeks after a new release. Many bugs will be noticed by others and soon they will be fixed. But do not wait to long. This is why:

1. Difficult and expensive to update very old versions

The more differences between installed version and the new version you are going to update, the more difficulties and incompatibilities you will encounter. PrestaShop is changing rapidly so  better upgrade your shop periodically.

2. More free stuff

Almost every new release has some new free useful stuff and functionality. You can be superior merchant for free. Your competitors are not sleeping also.

3. Developers usually write new modules only for the newest versions

Sooner or later you’ll need some new feature. If you are up to date there are many chances you’ll find required module in addons.prestashop.com (just buy and install – quick and cheap method).  It’s not profitable for developers to write addons (modules) for an outdated PrestaShop version – unique solutions cost more and takes more time.

4. Developers usually update their  modules  for a new version ASAP

You may request an update for your modules from developers. I think the little updates will not cost you much or even they may be done for free. Do not wait too long.

5. Old versions may contain vulnerabilities and your shop may get hacked.

Usually very old versions sooner or later are not maintained. PrestaShop is changing too fast to be able to maintain all old versions. I have no doubts they are concentrating on not so old and current releases. Better take care of your shop’s security.

Be an up to date merchant. Plan periodical updates, document them and they will be smooth. Updates definitely will give you advantages.

1. You should backup your web store data because:

• Systems are not perfect and sometimes they get hacked. Your hosting provider or PrestaShop it self may have vulnerabilities.  You may not notice the problem for a long period of time.
• Your passwords may get stolen – keep them safe and change periodically.
• Somebody can delete something accidentally e.g. not experienced developer.
• Hardware failures may lead to data loss
• …

2. Choose right hosting provider to minimize the risk

Almost every hosting provider backups server data periodically. Make sure they make backups.  The more often they do it the better. Some of them charge you if you want to recover your data – find out how much it would cost for you (it may be expensive). Find out how often your FTP, MySQL, e-mails data is backed up.

Do not forget that it takes time for hosting provider to recover your data and it’s not always possible to recover the latest version of your shop.

3. You should backup your data yourself if:

• you are upgrading PrestaShop system
• you are taking some risky actions that may lead to data loss
• you noticed that your shop is hacked and hosting provider can not give you an assistance. Change all passwords and do the backup ASAP!
• …

4. How to backup your PrestaShop

PrestaShop Wiki has an excellent article about how to backup your database (read it here) but it lacks information about FTP files and phpMyAdmin installation. More info how to install phpMyAdmin can be found here.

OK let’s backup your PrestaShop Files now.

For this you’ll need FTP username, password and FTP client.

Fillezilla FTP client is an excellent choice. Download it from here.

Download all FTP files from your server to a secure location. Do not forget to download .htaccess file if your website uses it. This file is not shown bay default in Filezilla client.  Click Server->Force showing hidden files in Filezilla top menu – now you’ll be able to see .htaccess file if it was created.

That’s it! Do not loose your data

1. Remove “Powered by PrestaShop™” from the footer

By default your footer looks like this:

Default Prestashop footer

First we will remove “Powered by PrestaShop™” in the footer of your website.

First of all you have to find blockcms.tpl file. If your website is located in a remote server you’ll have to connect to if with FTP client like Filezilla. Then go to Prestashop root directory (directory or subdirectory where your Prestashop system is installed). Then go to modules/blockcms/

blockcms directory

Download file blockcms.tpl and open it in text editor like notepad:

edit blockcms.tpl

Near the bottom of the file you’ll find this line:

<li>{l s='Powered by' mod='blockcms'}
<a href="http://www.prestashop.com">PrestaShop</a>&trade;</li>

Delete this line or just comment it like this:

{* <li>{l s='Powered by' mod='blockcms'}
<a href="http://www.prestashop.com">PrestaShop</a>&trade;</li> *}

Now clear Prestashop cache. If yo do not know how read this post.

Now your footer should look like this:

Footer without "Powered by PrestaShop"

That’s it!

2. Remove “powered with PrestaShop™” from emails

Well this is not so easy to accomplish but I will tell you the easy way. All emails are saved in mails directory. It is located in Prestashop root directory:

mails directory

You should see separate directory for every language in mails direcotry. We have 5 languages in this example:

Emals directories for each language

If you go to some language directory you’ll see many files. Something like that:

Language directory content

Almost every file contains one of these lines (look near bottom of the file):

In html files:

<a href="{shop_url}" style="color:#DB3484; font-weight:bold;
 text-decoration:none;">{shop_name}</a>
powered with <a href="http://www.prestashop.com/"
style="text-decoration:none; color:#374953;">PrestaShop™</a>

or in txt files:

{shop_url} powered by PrestaShop™

OK first of all download whole mails directory to your computer. Now it is possible to check every file and change lines.

In html files we need to delete or change this part:

powered with <a href="http://www.prestashop.com/"
style="text-decoration:none; color:#374953;">PrestaShop™</a>

In txt files we need to delete or change this part:

powered by PrestaShop™

Task easy but we have huge amount of files – it will be long and tedious task to change one file after another. There is a better solution.

OK let’s say we downloaded mails directory to our C:\ disk. Now you have to download Notepad ++ and install it in your computer. Download it from here.

Install Notepad ++ and start this program. Go to Search->Find In Files:

Search -> find in files

Now fill this form:

Find and replace

• Find what – copy and place the part of the string you need to replace
• Replace with – you can enter here the new text o just white space
• Directory – choose your mails directory

Now click Replace in Files

You should see the number of ocurences which where replaced. So you have use those two lines to replace not desired text  in html and  txt files.

OK this task is finished. Hope you enjoyed reading this post.

powered with <a href="http://www.prestashop.com/" style="text-decoration:none; color:#374953;">PrestaShop™</a>

E-commerce developers or IT companies usually use tools they know best and of course they suggest to use them for their customers. This usually happens with little companies or freelance developers who specializes to work with one or few tools. We can not blame them because they are doing the right thing – it’s better to be the best in on area then to be good in many areas. Every starter merchant should consider this and decide if the suggested tools are appropriate.

OK and now the main 10 reasons why you should choose Prestashop:

1. It’s free and open source.

If your budget is tight it will save your money which can be used for advertizing (Google AdWords, banners…)

2. It’s SEO friendly

This is the first thing you should check. It is critical for your web store to be SEO friendly. It is easy to change URLs, TITLE tags… in Prestashop so your SEO experts will be happy with this platform.

3. It’s multilingual

In most cases you’ll need to translate your web store in one or few languages. It’s easy with Prestashop.

4. Prestashop is easy to develop

It’s important to know that there will be developers who can help you for a reasonable price and within reasonable period of time. For e.g. “Magento” developers are quite expensive because“Magento” is not easy to maintain (develop) – it’s quite complicated system.

5. It’s fast and it does not require expensive servers to run

We tried “Magento” but it required too much server resources so we went back to Prestashop.

6. It has many free modules

You can start your shop in minutes if you are in a rush and of course you save money.

7. It has modules and themes shop

You can buy required module or theme and improve your shop in minutes. Take a look here. Prestashop validates those modules and ensures quality – so you are not taking any risks. Besides unique solutions costs much more. Developers can sell modules multiple times so they charge less and they are wiling to fix their bugs because they get money for their products.

8. It’s easy to learn

You do not have to be an e-commerce expert to master Prestashop.

9. It has big community

Check Prestashop forum. You’ll find answers to most of your questions.

10. It is rapidly improving

Sometimes it’s annoying because you have to update your Prestashop constantly. But every new release gets better and better. E-commerce is changing rapidly so does and Prestashop

I hope this list will help you to decide if Prestashop is suitable for your needs