What are the wishes for Prestashop 1.7

[musicmaster]

Lesley Paone (DH42) started a discussion on his blog "Prestashop 1.7 looking past 1.6".

 

His wishes are:

• Features as modules
• Tighter module integration
• Better password security
• Images targeted to languages
• CSS editor and backoffice theme editor
• Header and footer editor
• Htaccess editor
• Backoffice access to error messages and debug profiling
• Better product configuration
• Better language support
• Blog integration
• Configurable 404 page
• Clean URLS
• Better favicon support
• Easier customizable checkout
• Full site HTTPS support
• Simple maintenance buttons

 

I would like to hear what suggestions others have. (mine will follow later - running late now).

 

 

[tuk66]

Much better overrides. It has to be something entirely else, because it is pain now.

[musicmaster]

My wishes concentrate on the core of the shopping software:

 

 - we lack options for product attributes. At the moment we have only the product-attribute combinations - that are very database heavy - and the customizations that are so inflexible that you can't even define a select box for them. Regularly we see on the forum some guy who has a product that can be customized with five or six variables and we have to tell him to find other software or buy a module as Prestashop won't work when you have a million combinations for one product. 

 

My proposal would be the use of "sub-products". These are normal products. They are linked to the main product through a similar comma-separated list as accessories. The big difference being that they would be shown on the same page as their "mother"-product. You would have one new product field "subpage-only" to indicate that they should not be listed as independent products. In the product-detail table you would have a new field "depends on" that links one subproduct to the main product. That way they will all appear on the same page and can be deleted at once. You could make subproducts a separate set of fields in the product page. That way the software would stay backwards compatible. Some complications to consider: should discounts work on the subproducts? Can they be deactivated or out of stock? 

 

 - a related problem are accessories. In many cases you don't want the customer to buy an accessory as a separate product. You want him to consider it as an option to the main product (for example: the towing hook as option at a car sale). That forces you to define it as yet another combination. But that is overkill as that accessory already has its own stock and image.

 

 - customers cannot check attributes on the category page. You are forced to direct them to the product page.

 

 - discounts are not flexible enough. 3 for 10 euro is not possible (it will be 9.99 or 10.02).

 

 - it should be possible to deactivate attribute combinations. Now you are forced to delete them when they are not on stock.

 

To solve these problems we need a major revision of the shopping cart software

 - add lightweight attributes that don't influence stock

 - expand the functionality of the "add to cart" button so that it can send more than several products to the cart at once.

 

Another wish is the possibility to have broken quantities. Some products are sold by weight or by length but Prestashop does not allow at the moment to have broken values. You can try to go around this by defining the price per gram or centimeter. But that often results in rounding problems because the values are too small.

 

Another problem is the checkout process. This has too little flexibility:

 - there is no way to define costs for certain payment methods

 - transporters who offer options to choose either a timeframe or a location to retrieve the package are not supported. There is a Kiala module that supports the latter, but it is quite a dirty hack - not a decent solution. Yet we can expect that the use of such options will increase over time.

 

As I see it these are problems in the core of Prestashop. Repairing them should have priority.

Edited September 4, 2016 by musicmaster (see edit history)

[Tony Webb]

My wish is a simple one;

That the shopping cart display something like (need delivery address) rather than FREE shipping as the default.

 

I've been working on this for 3 days and have still not been able to resolve this. Even the nimo video on this subject is out of date as it doesn't work. The 1st part editing the drop down cart doesn't work.

[johnwolf]

Following the dh42 blog and this thread discussion, I also find it interesting to suggest my wishes and expectations from PrestaShop 1.7.

My Points are given below'

• Newsletter Subscribers Management and Server Configuration
• Fast One Page Checkout
• Clean URLs
• HTTPs Support
• By Default Blog
• Excessive features should be removed
• Module Sections
• Tabs on Home and Product Pages
• Password Algorithm
• No URL Change for Language
• 404 Page Customization

More details

Edited June 10, 2015 by johnwolf (see edit history)

[henzan02]

1. Speed

2. Speed

3. Speed

[jetx]

Shipping is one of the biggest headaches in Prestashop. As there are no 3rd party modules which handle this properly (I have spent money on almost every one of them), it is essential that Prestashp address this urgently.

 

• the ability to import and export shipping methods and rates
• the ability to duplicate a carrier (automatically assigning a new id to the duplicate)
• the ability to add separate handling charges to each carrier
• shipping rates by weight, price and volumetric
• minimum package height, width, depth, weight for each carrier

[johnwolf]

Hopefully some of the issues will be addressed in PrestaShop 1.6.1.0 which is expected in July 2015. I think there is long time ahead for occurrence of PrestaShop 1.7. 

[thepan]

• Moving resource hungry features into modules is one of the most important in my opinion. Then adding a checkbox list of features to be installed to the Prestashop installer to give everyone the choice.

Clean URLs 

BLOG!!! 

[johnwolf]

"Then adding a checkbox list of features to be installed to the PrestaShop installer to give everyone the choice."

Just an awesome idea, PrestaShop should ask during installation that whether you want to do a custom installation or typical(default) installation. 

@thepan you have not mentioned here speed as some others users said here, do you satisfied with the current speed and loading time of PrestaShop?

[Rolige]

1. Speed

2. Speed

3. Speed

The new version of PrestaShop 1.6.1.0 will be up to 65% faster than 1.6.0.14, here the full article: http://build.prestashop.com/news/prestashop-1-6-1-0-performances/

Edited June 26, 2015 by COTOKO (see edit history)

[thepan]

@thepan you have not mentioned here speed as some others users said here, do you satisfied with the current speed and loading time of PrestaShop?

 

Speed is and alsways will be something to improve. But it seems like with 1.6.1 they really took the time and reworked many SQL queries. 

And also they just announced on build.prestashop.com that Prestashop will drop the support for PHP 5.2 and 5.3 with the next major release 1.7.

That alone gonna make a huge different for speed, if the codebase gets revised and transfered.

[thepan]

Just wanted to add something really important to the list:

 

• Feature Values should be set per combination  not per product

[El Patron]

A WYSIWYG editor compatible with helpers.  

[alihkhawaher]

I need a few things which will make presta shop much easier and less time consuming and i dont think they are hard to implement.

 

1. Full ability to edit orders information and update them.

2. When creating new products. I want an on the fly combination creation, category creation, company creation. I do not want to go to several steps to create a company or brand. The product import does it why not the form too. It takes huge amount of time to do these things

3. Full right to left support

4. Fater checkout process and less steps

5. Better search (multi language)

6. Choose address using google maps or just coordinations.

7. Better product import. I.e. imports products and combinations by duplicating the products ids and only changing attributes in the csv. So products and combinations can be imported in one step and in one csv file

8. Multi language products import

9. When we specify local file as the product image i.e. c:\some_folder\image.jpg. it should upload them automatically.

 

I could only think about these just now. I will add more if remmeber more of the difficulties i am facing with the software

[mustaheer]

Option for user to pick the delivery time and date.

[dambie]

Mass Product Quantity & Price Update !!!!

[ecointeg]

I would pinpoint the following:

1. Possibility to show only existing combinations on a product page. So that if a customer chooses the first attribute the second attribute only shows the range of possible variants that corresponds to the chosen first attribute. For instance, if you choose a color group for gel polish of a certain brand (say, pink) the second option is to choose among polishes that fall in this group and not among all possible colors for this product.

2. More flexibility at checkout and registration. Please, let a shop manager to decide on what to require. For instance, it would be great to have an ability to completely disable a billing address.

3. An option to set features for combinations.

4. An ability to use states as well as countries to manage shipping locations and costs.

5. A real guest checkout that would not create a new customer when an order is placed. And a possibility to make a guest checkout as simple as possible, disabling the unnecessary fields.

[kikis]

Simplier and easy Warehouses!!!

 

It is a nightmare the warehouse feature right now. 

As simple is to update products stock without advanced stock managment make it the same simple with warehouses.

 

For example in the admin panel when we edit a product at the tab Quantities if we have warehouses to show there and let as to write stock for each warehouse. 

 

Advanced stock managment is a nightmare....  I don't want to have supliers... I don't want to make my life difficult when I must change the stock of a product.

It is so easy if we don't have advanced stock managment feuture.

But without this we cannot have warehouses. 

 

Make it better please

[Rolige]

The menu still being responsive, here my demo store with PS v1.6.1.1

It's possible you has changed something in the CSS or some custom module is breaking the style.

[radus]

HHVM + HTTP2 compatibility => bigger speeed @ lower resources

[El Patron]

back office support of javascript bottom and CCC of .css files.

[mimpro]

I wish on the backoffice there is option not to use Ajax, since sometime ajax make more problems and it should be an option for users, when to use AJAX and when to deackitave it.

I wish there is a way to prestashop start to redesign the core for supporting marketplace features, instead of using modules that requires override, so maybe just make new section just for the marketplace functions, and we can develop more from there, since the object for marketplace sellers are created in core.

[discoversajib21]

• upgrade TinyMCE editor.
• upgrade override function.
• backend product page more faster to edit product

 

[FoodFromCyprus]

User friendly 'Addons' website with downloadable free and paid modules and themes including old versions.

[MacRoy]

Hi!

 

Integrating the login at the top right with one more choice for "consumers" and a login for "companies", thus two choices instead of just one choice as it is today.

 

For business as usual without VAT for consumers with VAT. This is a feature that I and many others would appreciate!

 

 

What do you think?

 

Regards

MacRoy

[zod]

Before some tools for web designers (like a CSS editor inside BO or other things i don't feel the need), i think Prestashop should improve some features it has in the core and is very important for vendors.

1. Management for the automatic emails. Communication is very important, and shops are different each others, there should be more control on emails sent. Now every email template is static, inside the "/mail" folder, and it has different code for each language, the content is mixed with the html code. I think this part should have a major enhancement: all emails should be managed in Back Office, with a list to add, edit and delete email templates (some email should be mandatory for functionality, some other could be custom, to use them in new "order status"). Then, vendors should have the ability to modify the content: it is very frequent they want change sentences, add notes and warnings, links, banner for holidays etc...

2. Management for the template of the invoices. I am not sure how to accomplish this easily, but vendors don't like the generated PDF, they often want some "manipulations".

3. Scheduled emails, and/or Newsletter. If we have number 1. here above, we could add some more features: "After 3 weeks i would send an email to ask if the buyer is happy with his product..." or "If someone has no orders after 3 weeks since registration, i would be notified or i would send him a special email..."
Also, we have the newsletter subscribers, so we could send offers and coupons, build emails adding products from the catalog, send emails to special groups, or who abandoned carts... etc... We could have a different configuration for this mailing list, to avoid problems with hosting limitations.

4. Edit Orders. Another very important thing in a shop management is to fix some problems when a customer calls. Actually there are few possibilities to edit the order someone made: we can add products, make discounts, add payment methods (as simple note for a payment received).
In my opinion there should be the ability to modify Carrier, and also the weight and shipping cost. Then the product's description and price could be modified, for some special agreement between vendor and customer (custom product maybe? Gadget added?). Then the order statuses got a great improvement in PS 1.6.1, we have buttons to send bankwire informations again, but what if i change from "Waiting for Bankwire" to "Waiting for PayPal"? There should be a button to ask people to pay with that, an email would be sent and a button should appear in their "order history" like "pay your order with PayPal". Finally, some order statuses, and payment methods could be messed up in the order, because of the mistakes, so there should be the ability to delete them.

5. Payment and Carriers. What i had to solve, more than once, was the ability to restrict some payment methods to some Carriers, or to some Zones. Now PS has restriction by Currencies, User Groups, or Nations. It's ok, but I could have for example a cash on delivery enabled only for a special Carrier, or Zone.

I know that some of these features are now possible with extra modules, but it could be nice to have them in the core.
 

Edited November 18, 2015 by zod (see edit history)

[criacaosites]

1. A class complete to create combinations and get combinations;

Integrate a way to show only available combinations;

Thing about optimization of load/performance backoffice and frontoffice (via parameter of gtmetrix);

Use SEO strategies onpage (theme and breadchump);

Create a dinamic change of status of payment;

Edited January 18, 2016 by criacaosites (see edit history)

[Sylvain CM]

Hi, this conversation looks like it will be better in the dedicated section, I'm moving it

[jafarek]

My wishes:
- Variants of the product without limits (sell contact lenses that have the several thousand combinations - sometimes even several million)
- Assignment of the product for shipment (sometimes I do not want to send the product which is produced only on request with COD)
- URL management - eg. Removing product codes

[PrestaShopDeveloper]

Loose coupling for the module hooks - That was my wish for PrestaShop 1.4, so I'm still deaming for the time when 1 module will be able to hook more than once to the same hook on different positions.

[alihkhawaher]

Better shipping options.

 

RIght now I cannot specify shipping rules + payments per postal codes/areas, Especially when creating carriers, We can only choose per region (i.e Middle East). Which is useless and too wide since I want to ship locally and each area have its on price. Even per country. Each country costs is different. But I cannot choose. I think this is a big issue in carriers facility in prestashop. I hope they re-write it. 

[frii]

better product id number arrangement (ability to re-sort products or new products fill the empty id from deleted products) because I have lot of new products and often delete products so the product id keeps increasing

[verano]

I wish one more menu like Product Features for standard equipment & features

http://pdf.directindustry.com/pdf/karcher/sth-556-w-snow-thrower/5768-430049.html  P.2 

Edited January 24, 2016 by elitosb (see edit history)

[Tyavuz2]

I would like having prestashop have multi vendor built-in

[ps3z]

Pricing system should be improved for Prestashop 1.7

 

When i do pricing to my products on Prestashop 1.6

 

Forexample:

 

Base price : 250usd

Final sale price 119,90usd - (we can set it by fixed price feature) but it just allowing with tax excluded. there should be tax included price too, so we dont need waste time to calculate it

 

also it doesnt leave base price as strikeout for show old price on frontend, that should be fixed too for create beautiful campaigns.  i solve that issues by custom pricing/reduction module,but prestashop needs that feature in default one

 

 

 

Regards

Ps3z

Edited January 26, 2016 by ps3z (see edit history)

[tdr170]

How about a PayPal USA module that actually works, right now I have to use the Euro version as orders are not passed from PayPal back to the shop.

Instead of being redirected to the Order confirmation page you get Order history and all items are still in the cart.

No order is recorded in the back office even though PayPal shows the order.

This has been the case for some time and I have tested on multipul versions.

This has been reported to the forge and still no fix.

I even posted a version of the Euro module I modified with the US PayPal logo for others here on the forum.

Please fix this or do not release 1.7, even better fix it for 1.6.

[iqit-commerce]

Before some tools for web designers (like a CSS editor inside BO or other things i don't feel the need), i think Prestashop should improve some features it has in the core and is very important for vendors.

 

1. Management for the automatic emails. Communication is very important, and shops are different each others, there should be more control on emails sent. Now every email template is static, inside the "/mail" folder, and it has different code for each language, the content is mixed with the html code. I think this part should have a major enhancement: all emails should be managed in Back Office, with a list to add, edit and delete email templates (some email should be mandatory for functionality, some other could be custom, to use them in new "order status"). Then, vendors should have the ability to modify the content: it is very frequent they want change sentences, add notes and warnings, links, banner for holidays etc...

 

2. Management for the template of the invoices. I am not sure how to accomplish this easily, but vendors don't like the generated PDF, they often want some "manipulations".

 

3. Scheduled emails, and/or Newsletter. If we have number 1. here above, we could add some more features: "After 3 weeks i would send an email to ask if the buyer is happy with his product..." or "If someone has no orders after 3 weeks since registration, i would be notified or i would send him a special email..."

Also, we have the newsletter subscribers, so we could send offers and coupons, build emails adding products from the catalog, send emails to special groups, or who abandoned carts... etc... We could have a different configuration for this mailing list, to avoid problems with hosting limitations.

 

4. Edit Orders. Another very important thing in a shop management is to fix some problems when a customer calls. Actually there are few possibilities to edit the order someone made: we can add products, make discounts, add payment methods (as simple note for a payment received).

In my opinion there should be the ability to modify Carrier, and also the weight and shipping cost. Then the product's description and price could be modified, for some special agreement between vendor and customer (custom product maybe? Gadget added?). Then the order statuses got a great improvement in PS 1.6.1, we have buttons to send bankwire informations again, but what if i change from "Waiting for Bankwire" to "Waiting for PayPal"? There should be a button to ask people to pay with that, an email would be sent and a button should appear in their "order history" like "pay your order with PayPal". Finally, some order statuses, and payment methods could be messed up in the order, because of the mistakes, so there should be the ability to delete them.

 

5. Payment and Carriers. What i had to solve, more than once, was the ability to restrict some payment methods to some Carriers, or to some Zones. Now PS has restriction by Currencies, User Groups, or Nations. It's ok, but I could have for example a cash on delivery enabled only for a special Carrier, or Zone.

 

I know that some of these features are now possible with extra modules, but it could be nice to have them in the core.

 

 

+1

[SWcoins.com]

 

Basic ability to edit products and categories in bulk

Ability to have empty categories auto disable

Ability to have out of stock products auto disable

[verano]

Available for order & Show price ->If I uncheck these boxes in Managing Products Add to cart button does not appear in Front office. It is good in its place appears a new button Send request for price

[Ahmed AlShami]

Wow, If all suggestions were done, Prestashop will eat the hell out of the market 

[criacaosites]

css sprite too

[El Patron]

copy joomla tinymce ...Having a much more flexible and configurable native tinymce would be dreamy.  What I am seeing being released by 3rd party developers is not at the end of the day going to further PS usage but a native solution would.  happy day, el

[Guest]

Wow, If all suggestions were done, Prestashop will eat the hell out of the market 

 

That is something to understand, instead of being AGAINST the community, please be WITH your community and improve the CORE code before filling new versions with useless fancy stuff again like rocket luncher or other stupid tools.

 

Best Regards for Prestashop.

[Mister Denial]

copy joomla tinymce ...Having a much more flexible and configurable native tinymce would be dreamy.  What I am seeing being released by 3rd party developers is not at the end of the day going to further PS usage but a native solution would.  happy day, el

 

True! Especially for those of us who use an integrated blog module, there are some convenient formatting options missing, like easy shortcuts to have text wrap around images (align left, right, etc). I know, it's possible to add this by hand by going into the code instead of WYSIWYG, but still, it would be easier not having to browse the code to get this done.

 

Otherwise, I agree with the last comments, if the team keeps solidifying the core code, and adding the suggestions made here, Prestashop is going to blow everything else out of the water. I switched to Prestashop shortly before 1.4 and have not regretted it.

[ddaniele]

Since you're asking:

 

1- Attributes:  There's something that needs to be done before Prestashop can be used in many more environments.  Currently the only viable option is a third party module which works well in instances where only a limited number of products have options.  In instances where almost every product contains a few options, it also becomes a time consuming, tedious task. This is one of the biggest downside to Prestashop and has been mentioned with regularity.

 

2- Easier/more customizable checkout process. (Also a crowd favorite)

 

3- Speed:  Very slow, even though I'm on a fast dedicated server.  The SQL needs to be optimized. (Another crowd favorite)

 

I've been using Prestashop since V1.3 and I've seen it grow to a much improved platform although I feel that certain design issues still persist such as the above.

 

 

 

 

 

[Mister Denial]

Since you're asking:

 

1- Attributes:  There's something that needs to be done before Prestashop can be used in many more environments.  Currently the only viable option is a third party module which works well in instances where only a limited number of products have options.  In instances where almost every product contains a few options, it also becomes a time consuming, tedious task. This is one of the biggest downside to Prestashop and has been mentioned with regularity.

 

2- Easier/more customizable checkout process. (Also a crowd favorite)

 

3- Speed:  Very slow, even though I'm on a fast dedicated server.  The SQL needs to be optimized. (Another crowd favorite)

 

I've been using Prestashop since V1.3 and I've seen it grow to a much improved platform although I feel that certain design issues still persist such as the above.

 

Agreed, with all of the above.

 

Regarding n°3, I have found that it is possible to get sub-4 seconds performance out of PS 1.6.x, but it requires removing the stats and several other options, plus using the Page Cahce module, which reduces the TTFB from 800-1200 ms to about 250ms. The thing is, I believe it is possible to get good speed out of Preastahop, even on a VPS like I am, but there is a lack of documentation on which configs work best on which type of server. By browsing the forums, you get lots of input, like using MariaDB, or going full Nginx/SPDY, etc etc, but there is no real benchmarking done by the PS team and a document where they say "here's 3 configs that work the best with PRestashop" that you coulg give to your hosting company and say "this is what I want", that's missing. There's no guideline, just guessing and experimenting until you get a config that works.

 

I am, for example, convinced I could get more bang out of the hardware I have, but I don't know how to tweak it right, and Myhosting has no Prestashop expert in their experts team.

 

Also, the image servers, I sometimes get the feeling nobody really knows how to make it work properly.

 

Or the Memcache and all those options, which one should we pick? What works best? There has to be some experience in the Prestashop team, and having a guide that outlines the ideal configuration or 2-3 variations thereof would be good.

[nedge2k]

I'd like to see improvements to attributes - especially being able to SET a price for an attribute rather than increase/decrease based on the main product price. I have some products that have a couple hundred attributes. Others that have multiple layers and their part numbers are based on the combination selected. I had to hack a lot of core code in Virtuemart to make life easier with attributes - it's a nightmare when upgrading.

 

Shipping by weight + packaging type would be good. I added this functionality to Virtuemart - I assume this is how amazon works. The basic idea is that instead of adding dimensions for each product, you have a selection of of packaging types (box1, box2, jiffy1, jiffy2, etc.) and you assign a product a packaging type and a weight. The packaging types have weight limits and price modifiers (some boxes cost more/less etc.), products have a qty limit for a given packaging type. if you exceed the weight/qty limit, you bump up to the next higher type. The shipping services are then limited by packaging type - some things too big/heavy for one service etc. This is a very simple system that works very well and cuts down on measuring products, calculating volumetric weights etc. etc. It's extremely handy for companies that manufacture and sell items that don't ship in conventional "retail packaging".

[Brazzan]

My suggestions mostly involve B2B-mode. So, here we go

 

Customer number

For some businesses the id_customer might work as a customer number. But for most, it won't. Most of us have a business system behind the scenes (SAP, Visma, Navision etc) where customer information is stores, amongst other things. Those customer numbers are the ones we tend to want to use.

When a new customer account is created via the shop, it's also created in the business system and the customer id is returned. This way there are no collitions, and every customer follows the same customer number standard. No matter if the customer is created by hand (email/phone orders) or automatically (via the shop).

 

We implemented a field for this on the customer card in Prestashop ourself. The integration part is up to everyone to figure out themselfs.

 

One account, multiple contacts

More often then not in a B2B-shop, there is a need for multiple "contacts" under one customer account, and where every contact has their own login credentials. In our case we have big businesses that have businesses in multiple geografical areas, but collectivly one customer number. Each area has their own "buyers" that decide what to buy and when. The customer as a whole has some discounts, so to create multiple (sometimes up to 50) separate accounts, and manage certain discounts for these, would be an administrative nightmare.

 

We solved this by having one customer account, and then develop a module that could handle multiple contacts, all with different logins. We managed to build this and keep all the login functionality as it is, with forgot password and everything. All these contacts order under the same customer number, with the same discount, and same company details. But we have multiple addresses for the contacts to choose from.

 

This would be a fairly easy thing to implement as a standard if B2B mode is activated I believe.

 

If B2B activated - classify addresses

When we solved the above point, we also implemented a classification of the addresses connected to the customer. Addresses are classified as invoice or

delivery. Most of our customers that have the need for multiple contacts also have the need for multiple delivery adresses, but only one invoice address.

 

SIRET - make it a general business identification number

Siret is the french version of a business identification number. This number has a validation function connected to it, which basically meens that most other

identification numbers won't be validated. We removed this validation and called it Organisation number instead. It would be better to make this a general text field with no validation. If you want to get more advanced, build a setting that allowes us to decide the validation ourselfs (much like how you validate zip codes).

 

Prices - pricelists

Every other B2B business uses pricelists in their business system. A big customer often make a deal with the supplier (us) for better prices. These prices exist in a separate pricelist that's connected to that customer or customer group in the business system. To be albe to solve this, we used a combination of specific prices and customer groups in prestashop. It works, but it's not managable on a larger scale. Limited import funcitonality, specific price not editable etc. We manage this with our own developed scripts outside of prestashop, that talks purely to the database.

 

Macros in text

In some of the other e-commerce platforms I've worked with there is the option to use macros in the product description, meta-description, meta-title etc. That way, the texts can be created dynamically and alter depending on the base information. For instance, if I where to use the product name in the description text I could do something like this:

 

"[:name:] is an awesome product."

 

[:name:] fetches the product name. If the product name is changed, the description is changed.

 

If you've read this far, hurray

Edited February 5, 2016 by Brazzan (see edit history)

[3DStudio]

Clean URLS: for me very important.  Many shops have nice clean urls but Prestashop urls are not SEO friendly, for instance 

magento:   domain.com/women/shoes/high-heels

prestashop: domain.com/women/shoes/36-high-heels  <== here google thinks this is the size of the shoe thats very poor. Remove those numbers from urls

Custom Css field like in Wordpress Themes, on an update every changes should be still there

Reduce size of Prestashop remove modules, dont make Prestashop like a milk cow, I want only install moduls, I need, languages I need, so make prestashop minimalistic and clean,  if I remove modules on the next update they re back.

[cropr]

1) clean URL

2) higher calculation precision than the display precision.  Prestahop is a mess for products with a very low unitary prices, that are ordered in high quantities

3) speed

4) better API documentation.  A least 70% of the class methods have no docstrings, and there are no generated docs from the source   

Edited February 8, 2016 by cropr (see edit history)

[josefausto]

Mas rapidez, es desesperante la lentitud, mas si trabajamos con muchísimos artículos

Un blog integrado.

Las actualizaciones mediante CSV dan mucho dolor de cabeza y errores.

[ps3z]

 

tinyMCE rich text editor should be added to new prestashop.

 

bcz theres no any section for choose font sizes on 1.6 version.

 

[videotape]

Maybe it has already been suggested but this feature would be great:

 

- Dynamic declinations

On the product page, if you choose a first declination, on Prestashop 1.6, you have to choose a second declination to be advised that this product declination is not available.

It would be better to filter the second declination in regards of the choice that been made in the first declination.

[radus]

allow svg images  https://github.com/blog/2112-delivering-octicons-with-svg 

[ajensen27]

Maybe it has already been suggested but this feature would be great:

 

- Dynamic declinations

On the product page, if you choose a first declination, on Prestashop 1.6, you have to choose a second declination to be advised that this product declination is not available.

It would be better to filter the second declination in regards of the choice that been made in the first declination.

 

If you need that functionality, here's a module I found that does this and works well on my store http://addons.prestashop.com/en/12352-advanced-display-combinations-attribute-in-stock.html

[doekia]

My wishfuls thinking regarding 1.7, sorted by importance:

1. fix all prices, taxes, orders, invoices, reimbursements calculations.
2. fix and implement the different flavor of ecotax.
3. return the stock movement without the need of advanced warehouse based stock
4. rewrite / fix / split bo Product page using ajax, been performant, usable
5. rewrite / fix cart rule condition / priority and for not to be never ending merry-go-round
6. rewrite the carrier / zone / range / fee at the light of merchant / shipping industry needs
7. Implement bulk action everywhere for every action and have list driven update-able settings
8. Everywhere checkbox list should accept shift/multi-selection
9. rethink with real merchant support team the customer support and rewrite
10. No more baseball field bootstrap unusable UI. Sexyness is against productivity.
11. Run complete regression tests before releases with yet difficult scenario
12. Have a unique roadmap, full documented API that make sense, hook-able  and a codex
13. Prune / organize GitHub branch that make sense
14. rewrite / fix the advanced stock management
15. Customization product price-able
16. virtual product combination
17. out-of-stock message on combination
18. ...

I just stop the list here, because I have already bored those fashionista of yet i-revolutions and that the other Cartesian and realist people have already realized that a life will not suffice to cover half of them with a team of only 5, not to mention with a dual brain framework. Even computation and stock management which are paramount in commerce does not fit in the time-frame.

[Guest]

My wishes for 1.7 is : do not DO THAT ! please fix 1.6 before.. once for all !

[doekia]

My wishes for 1.7 is : do not DO THAT ! please fix 1.6 before.. once for all !

 

it was already my wishes for the 1.5, but swimming against the tide is just impossible.

[bannerclick]

My wishes for 1.7 is : do not DO THAT ! please fix 1.6 before.. once for all !

 

Could not agree more!! Now we get a new, buggy 1.7 version, and then before the real issues are fixed, the Prestateam heads for the great 1.8 version...

 

FIX 1.6 FIRST!!! There are so many great commits from your community waiting to be implemented!

 

Keep ignoring your users and community, and prestashop will end up in tragedy one day..

[tdr170]

First and foremost I would like a 1.6 that functions as it should.

 

One thing I would like to see wether in an update to 1.6 or for 1.7 is the ability to include shipping with vouchers, but only for the products the voucher covers and beyond that apply shipping.

[pattuka]

I'd like to be able to set different image proportions for each category.

[tdr170]

Here is a big one back in the 1.4 days you had the ability to add counties and then enter the zip codes for that county in a string like 33462,33463,33567 and so on.

Now the only way to enter zips is a range like 33462-33678 the problem here in the US is that some zips fall into more then one county and if the ranges overlap Prestashop will add both county surcharges.

Even in 1.4 where it was much easier to add the counties and surcharges there was still the issue of zips being in more then one county that had different surcharge rates.

What I did was as I entered the zips it would give an error that this zip is already in use I would then find that zip and make sure it was added to the county with the highest surcharge rate.

Now the only way you could effectively add all the counties and zips would be to create a rule for every county and zip in the case of Florida there are 57 counties and hundreds of zips so just not practical.

So at this point we only collect State tax even though the law is that tax must be collected based on point of delivery.

 

 

I think there is a much easier way to implement county surcharges instead on adding the county surcharge by way of zip code add the surcharge by way of county.

So now in the account creation for a customer we would add county in addition to city and state.

Then in the BO would would have a county tab in the tax rules section where we could add the County and the tax surcharge for that county.

This method would not rely on zip ranges or zip strings and there would be no overlap or worry about a zip that falls into 2 different counties with different surcharge rates.

The tax surcharge would be added based on customers input of the county in witch they reside.

 

 

Does this make since, could this be implemented in future versions.

[andrecavalli]

I wish in v1.7:

1-Option to set carrier by payment type
2-Discount amount or % by payment type.

3-New fields in address form like number and complement
4-Address format need to accept labels. For example "ZIP: 123234" , "Street: xxxxxx" , "Cell Phone: 5555-5555" Today the address appears formated separated by blank space and outside Europe this looks so bad.

5-In new account include taxpayer for company and social security for persons.

 

Maybe more ;-)

Edited March 12, 2016 by andrecavalli (see edit history)

[YasinTürk]

1. Speed

2. Speed

3. Speed

[El Patron]

 

1. Speed

2. Speed

3. Speed

 

 

1.7 will have one .css and one .jss CCC'ed file for all pages.  This will make front office 'blazing' fast.  

[krismb]

Do you have any plan for better search.

 

Now search is based on word. If you type more than one word the resuld is not the best. exemple word1 word2. the serch engine search product with word1 ... and products with word2 then calculate postion.

 

but at the first position you should have the product with the name word1 word2 in the title in this order.

 

When you have many words you can't search 'word1 word2' you always have word1 or word2 not word1 and word2

 

Additionaly performance of the search should be improoved. Pleace make a try with 30 000 products not with only 100.

[ajensen27]

More integration's with 3rd party vendors such as inventory management, shipping, etc. Every time I'm wanting to sign up for one of these services, Prestashop is never a partner. It's always Magento, Shopify, BigCommerce, etc..

[happymoxa.com]

 Speed

[Chris993]

I would like to have it so that if inventory for an item is only 1, if customer A adds that item to their cart, that item is out of stock for all other customers.

 

Untill, that is, customer A removes the item from their cart or much more wanted: the time limit for someone to have an item in their cart is reached.

 

This way all other customers see an accurate inventory status.

 

At the moment all customers can put the same item in their cart and only once the fist customer to really confirm their order and pay, the other customers get a notification that the item is sold out; that's very anoying to them.

 

 

[ZMR]

My wishes are very simple-

 

1. Add option to show "Sale" on products when applying "Catalog Price Rules"

 

2. Email confirmation to sign up.

 

3. Mass product, price and category edits.

 

Hope someone listening.

 

Thank you so much in advance.

[Евгений Медведев]

Don`t use Symfony2. It`s bad idea. The best way is ZF2+Doctrine2.

[Neil Trinh]

My wish is a simple:

Module block layered could work correct! It has many bugs now! Couldn't adjust filters position! won't work correct if choosing multiple except manufacturers!

I don't need a new version, I need a new solution for all of the old errors

[7kilelr]

1.  Mass product, price and category edits. ( but thats was post many times before)...

2 . Fix price computation for product with ultra unitary low price ( ie 0.00001 e / piece).

3. Support sell by weight or length without have to use external module or many declinaison to achieve it.

4 . linked to 3 supports advanced unity suffix like €/Kg or €/m.

[LadyArch3r]

• Speed (Litespeed Support : https://www.litespeedtech.com/images/litespeed/Subpage_misc/hole-punch.png ) 
• Mass product Quantity and price update
• Auto discount system (http://i.hizliresim.com/RkvY57.png)  

                 Sample : 

                    Quantity :5-10 %50

                    Quantity :0-5 %25

• Extra Cart Rule
• Clean Url (remove link-1, link-2, link-3)

Edited April 12, 2016 by LadyArch3r (see edit history)

[ajensen27]

 

• Auto discount system (http://i.hizliresim.com/RkvY57.png)  

                 Sample : 

                    Quantity :5-10 %50

                    Quantity :0-5 %25

 

 

 

This already exists but you have to do it by product.

[colmix]

faceted navigation

 

My problem, I would use the faceted navigation as follows:

- I set filters based on categories

- I recycle some urls "filtered" as links in a menu

 

However, if I do the same manipulation to paste a url containing the manufacturer of filter in a new tab, the page starts loading, filtering is not done and manufacturer of filter (/ manufacturer-thingy) disappears from the url .

[Brazzan]

Wanted to add another wish, a very small one. 

 

In discounts, when you want to add a gift if x is in the cart. Place an option that let you decide how many gifts to be added

• Add [1] of this product (input field)
• Add the same quantity of gifts as the quantity of the product that triggers the gift

/Peace

[Trisus]

A more advanced registration form (without installing a module):

1. There should be an option for the registration form to show a radio button where the user can choose the type of account (particular / professional /..) (Goal: show different product prices for each group after registration)
2. A different registration form for each group with different fields (e.g. the field SIRET for professionals only)
3. Each field can be configured to be required or optional
4. The user will be assigned automatically or manually to the group he chose

There is currently no module available for number 2.

[Mr.SerikuS]

Hello, i think that there should be possibility to use existing products as attributes for products (bundle) as in Magento "from the box", with possibility to check if need, dropdown. and possibility to create categories and insert products. (Look at Magento Bulk for ideal variant)

[3DStudio]

Is here any Prestashop developer who reads these improvement suggestions?

it can't be a hard work to remove IDs from Urls, those ids are very poor for google. If you look to magento, shopware, oxid... they have soo beautiful clean urls,  why does prestashop not have such clean urls?

 

For me is Wordpress very intelligent designed cms system.  Prestashop Developer should look to Wordpress,  in Wordpress if I want to change Footer, I add widgets there but in Prestashop, I have to look in cms modules and if I want to remove theme, I had to search somewhere else, thats very poor.

You shoud design in the Theme like in Wordpress a widgets (Moduls) area, and drag and drop modules there

[Guest]

Is here any Prestashop developer who reads these improvement suggestions?

it can't be a hard work to remove IDs from Urls, those ids are very poor for google. If you look to magento, shopware, oxid... they have soo beautiful clean urls,  why does prestashop not have such clean urls?

 

For me is Wordpress very intelligent designed cms system.  Prestashop Developer should look to Wordpress,  in Wordpress if I want to change Footer, I add widgets there but in Prestashop, I have to look in cms modules and if I want to remove theme, I had to search somewhere else, thats very poor.

You shoud design in the Theme like in Wordpress a widgets (Moduls) area, and drag and drop modules there

 

I rarely defend prestashop team, but you are not really objective here.. first you talk about Magento and then WP.. did you try to change something in the footer in a Magento shop ?

And will you use WP with Woocommerce for your shop ?? really ?!!

 

also IDs in urls are not a problem at all for SEO and GOOGLE, read about this in details, and if you want to skip them.. buy  a module like "pretty urls", it's cheap, works fine and will give you url without any ID numbers in it,

[3DStudio]

I rarely defend prestashop team, but you are not really objective here.. first you talk about Magento and then WP.. did you try to change something in the footer in a Magento shop ?

And will you use WP with Woocommerce for your shop ?? really ?!!

 

also IDs in urls are not a problem at all for SEO and GOOGLE, read about this in details, and if you want to skip them.. buy  a module like "pretty urls", it's cheap, works fine and will give you url without any ID numbers in it,

you didnt understand my points.  I wont user wordpress with woocommerce, my points are improvement hints,  in Wordpress its very easy to manage footer with widgets, wenn the widget places defined in the theme.  If you are happy with the IDs in de Url, then use it and be happy, but I m not happy with those ids!

[Guest]

you didnt understand my points.  I wont user wordpress with woocommerce, my points are improvement hints,  in Wordpress its very easy to manage footer with widgets, wenn the widget places defined in the theme.  If you are happy with the IDs in de Url, then use it and be happy, but I m not happy with those ids!

 OK, but why are you not happy with it ?  in terms of SEO, it really doesn't matter, feelings doesn't count for google.

 IRL nice urls doesn't help at all, ask anybody who works on SEO .

 

And like I said, you can override this with a simple cheap module.

[santolla]

I would like to see improvements on the module transplants. If you check out arastta... they have a killer layout system. It's very visual and easy to understand. This is probably where my customers have the most confusion. 

 

Currently in beta 4... the theme configurator doesn't work. The theme configurator is really important... you should keep that. 

 

Maybe move banners out of the theme configurator and create a new section for this. And allow more banners into other positions. 

 

Speaking of the theme configurator... I always hated how buried it was. You had to go into the module first to open it. It would be nice fi the theme configurator had a link directly under the design button. 

 

Choose layouts... very confusing now! it was very simple before with a x tick if you wanted a left or right column. I would revert to the old system. 

 

That's it for now. I'm still playing around. 

 

[BEHNAM_RS232]

add filter ( layered block)  to manufactor page. 

improve speed in front office and in ( back office) on product page (save button)

please improve register and login page (UI and design ) and make easier for basic customer.

for security please add captcha code to login page and comment ..

improve comment layout and UI design and add a button for new comments on top on presta panel

[ssvapes]

I would like to see 2 password boxes on the registration form to verify the user password before they can complete the registration process.

 

1 in 10 people enter the wrong password during registration. They then email us asking why they can't log in. We then have to manually update their passwords, or the user has to use the change password form.

 

It's been a decade or more since I have seen a registration form with a single password box. I'm not a coder, so I do not know how difficult it would be to add a second password box for verifying that the passwords match. Nevertheless, it seems this is a needed feature in the year 2016.

 

 

[El Patron]

I would like to see 2 password boxes on the registration form to verify the user password before they can complete the registration process.

 

1 in 10 people enter the wrong password during registration. They then email us asking why they can't log in. We then have to manually update their passwords, or the user has to use the change password form.

 

It's been a decade or more since I have seen a registration form with a single password box. I'm not a coder, so I do not know how difficult it would be to add a second password box for verifying that the passwords match. Nevertheless, it seems this is a needed feature in the year 2016.

 

I hear your pain!  

 

In 1.7 template inheritance is incorporated..now developers can create 'typical' features found on 'successful' webshops.  This is what has held back PrestaShop CMS to support a 'feature' rich front office.  It does not matter if it's twig or smarty inheritance, new classic theme supports syntax for template inheritance.  Theme developers will then create their themes based on classic template....

 

Then it will be 'trivial' to create module feature to 1) replace blocks of content 2) extend blocks of content 3) delete blocks of content 4) add blocks of content.  For example one can now create a module that might incorporate nothing more than new kick-add product page, built on top of existing theme.  For your example, modern login, we can overlay existing login content with new.  

 

Let me explain like I do to my team, 1.7 is like a candy store, where the owner went home and left the door open.  

 

Happy day,  el

Edited June 12, 2016 by El Patron (see edit history)

[santolla]

We absolutely need a theme colour changer. 

 

Looks like this is being removed from 1.7 which is a step backwards. 

 

Will this be in put back in before the official launch?

[MaikelJas]

At catalog price rules I miss the option to create a quantity discount that is applied to a whole group of products instead of just 1 product within a certain group.

It should not matter if customer buys one or two per product of that group, as long as the minimum amount per product group is reached.

 

Right now discount is only applied when 1 article reaches the minimum criteria, combinations are not possible.

[zunxunz]

-

We need better support for product variants (or product attributes AKA combinations as PS calls them). Currently PS can't properly handle products that have many (like 2k or more) variants. I've had customers with products that have over 40k variants making the shop completely useless (we've had to mod the shop heavily, both back and front).

 

-

Currently the product variants and related classes have elusive names, I'd suggest naming as follows:

What are currently called 'product attributes' aka 'combinations' should be called 'variants'.

What are currently called 'attribute groups' should be called 'variant attributes' (or just 'attributes')

What are currently called 'attributes' should be called 'variant attribute values' (or just 'attribute values')

 

-

We need a way to run the shop in 'clean url mode', meaning real clean url's without 'weird' numbers (id's) in them.

My customers (without exception) always want to know why there are these 'weird numbers' (the database id's) in the url's and most of them want them gone. For cosmetic reasons, for SEO reasons and for keeping url's the same over time when products may be deleted and recreated or what not. Whatever, the customers want it.

I've written an override for the Dispatcher class (file attached, use at own risk) to achieve url's without id's, but it would be very nice if this could be a native feature. Customers are aware of 'name collision, but choose this over weird numbers in their url's every time).

 

-

I've spotted a 'id_product_attribute' parameter in 1.7 for product pages? Please drop that for the 'default' product variant so a product url can still be 'just the name'!

 

-

We need a proper way to 'extend' the core objects other than through (no disrespect, but 'oh horror' ) overrides. 

 

-

Add a 'template' (or dummy) module for developers to use to build their own modules with.

 

-

Better support for 'carriers' with different 'delivery methods'. Currently there's none at all.

 

-

Optionally replace '&' (empersand) and maybe some other tokens in url's by a '-' (dash) in stead of deleting them. (in the Tools::str2url method?).

 

-

Apart from all that, keep up the -excellent- work!

 

Dispatcher.php

[zunxunz]

also IDs in urls are not a problem at all for SEO and GOOGLE, read about this in details, and if you want to skip them.. buy  a module like "pretty urls", it's cheap, works fine and will give you url without any ID numbers in it,

 

It really does not matter if they are 'a problem' or not for SEO or for Google, but we are 2016 now, not 1996, people want 'clean' urls for all kinds of reasons, valid or not. Besides that, when we delete a product from our shop, and then recreate it with the same product name, it -is- a problem, because PS will ignore the name and look up the product by id, which obviously no longer exists so we have to revert to redirecting. And why would we want to expose db ids, which have no meaning to anyone outside of the back-end, in the first place?

 

I've had many customer's who requested this feature and I can't think of 1 reason to not allow for it.

 

Proper clean urls should be a native shop feature and we should not have to buy a mod for this.

[El Patron]

It really does not matter if they are 'a problem' or not for SEO or for Google, but we are 2016 now, not 1996, people want 'clean' urls for all kinds of reasons, valid or not. Besides that, when we delete a product from our shop, and then recreate it with the same product name, it -is- a problem, because PS will ignore the name and look up the product by id, which obviously no longer exists so we have to revert to redirecting. And why would we want to expose db ids, which have no meaning to anyone outside of the back-end, in the first place?

 

I've had many customer's who requested this feature and I can't think of 1 reason to not allow for it.

 

Proper clean urls should be a native shop feature and we should not have to buy a mod for this.

 

 

the main technical reason I see for clean url's is for those migrating from different platform whose url structure is different.  Then it would be much easier to keep 'old' URL in new ps.  

[zunxunz]

1. Speed

2. Speed

3. Speed

 

What are you running your shop on? Do you have products with many 'combinations'? I've set up multiple shops with all kinds of mods and page load speed is mostly between .4 and .8 seconds... (or do you consider that too slow?).

[zunxunz]

 

Just wanted to add something really important to the list:

 

• Feature Values should be set per combination  not per product

 

 

The combinations already have attributes. Feature values on combination level will be a complete hell to maintain.

[zunxunz]

One account, multiple contacts

More often then not in a B2B-shop, there is a need for multiple "contacts" under one customer account, and where every contact has their own login credentials. In our case we have big businesses that have businesses in multiple geografical areas, but collectivly one customer number. Each area has their own "buyers" that decide what to buy and when. The customer as a whole has some discounts, so to create multiple (sometimes up to 50) separate accounts, and manage certain discounts for these, would be an administrative nightmare.

 

We solved this by having one customer account, and then develop a module that could handle multiple contacts, all with different logins. We managed to build this and keep all the login functionality as it is, with forgot password and everything. All these contacts order under the same customer number, with the same discount, and same company details. But we have multiple addresses for the contacts to choose from.

 

This would be a fairly easy thing to implement as a standard if B2B mode is activated I believe.

 

If B2B activated - classify addresses

When we solved the above point, we also implemented a classification of the addresses connected to the customer. Addresses are classified as invoice or

delivery. Most of our customers that have the need for multiple contacts also have the need for multiple delivery adresses, but only one invoice address.

 

 

+1

[zunxunz]

the main technical reason I see for clean url's is for those migrating from different platform whose url structure is different.  Then it would be much easier to keep 'old' URL in new ps.  

This could be a reason, but in case of a migration I think I'd opt for redirecting anyway. But, this basically depends on what the url structure looks like in both the source and the target system.

[Ninja2000]

I am fairly new to Prestashop myself but I have experience with CSCart. I downloaded the beta of 1.7 and I have some feedback. Prestashop seems to suffer from the bigger picture mentality that a lot of programmers seem to have, they can't put themselves into the mind of the customer.

 

1 - If you look at the product page in Beta 1.7 and compare it to CSCarts product page, Prestashop makes some serious usability errors, in the front store if I open up a product and look at it, the additional images located below the main image should be smaller, the products description, specifications etc should then be located below that, check out how CSCart does it, http://demo.cs-cart.com/electronics/computers/tablets/apple-ipad-with-retina-display-wi-fi-32gb-white/

 

2 - The bizarre images folder structure in the shops directory itself, you have /img/i/  /img/l etc which is very counter-intuitive, for me I would have say /images/dress   /images/hats etc.

 

3 - The default template from 1.6 and 1.7 are a bit schizophrenic, everything is all over the place, when a customer hits a store he should spend less than a second looking for a button or any feature, all of the navigation should be in his field of view right away, logo and menu all nice and close, in 1.7 when I hit the template my logo is on the left, menu below but then I have to look to the right for the search, it sounds like nit picking but subconsciously it effects the customer without them realising. If you want people to buy quickly you need to look at a design that is very intuitive.

 

I think that CSCart needs a few people who really understand usability and excellent graphic design who aren't programmers. I know a little bit about usability but I always get someone who is really good at it. I am sure there are plenty of people who would help with that.

 

4 - In the admin page we have a modules section, by default this loads the marketplace modules, I think it is far better to load the installed modules first before loading the market place modules.

 

5 -  1.6 has a light box that rotates with two square advertisements right below the menu system, 1.7 has replaced this with just a rotating lightbox,. I think the 1.6 template had it right.

 

That is all I have noticed within the first few days of using the store.

[jasonbsmith]

Ok I am a complete noob on prestashop but have been working with 1.6x  Most of the improvements I would like to see have been covered.  One area I am unsure of an perhaps this group could enlighten me is regarding the Category pages.  I found this link http://digitaldisseny.com/en/blog/195-prestashop-different-layouts-per-category and felt it would be great if it was easy for user to select different templates for each category/subcategory.  It seems I seen several comments on overrides and from the comments posted on this link it seems the method used in the link no longer works?

Edited June 26, 2016 by jasonbsmith (see edit history)

[zunxunz]

Optionally load 'more' products on the category page through an ajax call in stead of through 'pagination'.

Edited June 27, 2016 by zunxunz (see edit history)