What do you think is missing in Prestashop 1.5?

[Rolige]

I open this thread waiting for the developer community can view and see the needs of users and create a more complete version, I will begin by giving 2 reviews.

 

Opinion 1:

I feel that Prestashop lacks an support area and customer service, there is a very popular and free software called "osTicket" which allows you to have a very organized communication with the customer through the same messages that could be seamlessly integrated. It would be great to have a new tab called "Support" in which you could easily operate in an organized and everything related to messaging, customer feedback on products, product questions, contact and E-Mail (Opinion 2).

 

Opinion 2:

Precisely related to the support and E-Mails, I think Prestashop also need a space in which you can access your mail, for example: [email protected], so you can control and monitor the emails that our employees meet our customers also in this way would be creating a professional and powerful store and manage all could go to the store without having to run programs or extra pages and could limit the computers (PC) so that employees can only open our store.

 

We could make a long list, and mentioning that each needs each of us, but the idea is to post something that really believe they would make more complete this great software.

[CraigMeade]

I love Prestashop but it's always been a little bit wobbly. Unstable perhaps. Rather than the continual race for a new version number I would prefer it if they stuck on 1.4 and kind of got the job finished for once. I think it would serve them very very well in the future if they did.

 

That said, they should find the top 20 core modifications discussed in this forum and make them manageable in the BO. Being able to scale the template layout for different screen sizes instead of wasting all that real estate would be good. Being able to specify exactly what emails are sent during checkout and exactly what they say would be great.

[indus]

Osticket is available through the free fantastico software suite in cpanel. I have installed it myself and works great. Most hosts will offer it. Due to licensing issues i dont think prestashop will integrate all these things. There are excellent third party tools available to do these things. Maybe presta can integrate their own versions if they think that is a good idea.

 

Also, the customer messages area is getting attention for 1.5 is what i read.

[Rolige]

I love Prestashop but it's always been a little bit wobbly. Unstable perhaps. Rather than the continual race for a new version number I would prefer it if they stuck on 1.4 and kind of got the job finished for once. I think it would serve them very very well in the future if they did.

 

That said, they should find the top 20 core modifications discussed in this forum and make them manageable in the BO. Being able to scale the template layout for different screen sizes instead of wasting all that real estate would be good. Being able to specify exactly what emails are sent during checkout and exactly what they say would be great.

I think I'm a bit according to your opinion, there are a lot of users who report bugs and developers will not take much importance, if things continue like this and version 1.5 is very unstable, rather than advance it would be a setback. Hopefully not lose ground against the competition, then that might be until they start taking into account the opinion of the people.

[mexique1]

I love Prestashop but it's always been a little bit wobbly. Unstable perhaps. Rather than the continual race for a new version number I would prefer it if they stuck on 1.4 and kind of got the job finished for once.

 

I often criticize PrestaShop too, but there is one thing you can't deny: it works !

It works in the real world, with real people, on even the littlest PHP shared hosting.

Non-developers can start a commercial activity in a pair of days.

 

However, evolutions seem to become more and more complicated, because of PrestaShop's architecture: this architecture seems to be here since the beginning, and it's hard to get rid of it while maintaining backward compatibility.

 

With the 1.5 version the team made a huge refactoring of the code, really.

This was really needed, and still needs lots of refactoring, but it's on the good way.

 

Maybe the 1.5 version will suffer of this... It could be an intermediary version, opening the way to a complete new architecture.

[koconborz]

I think the customer e-mail verify option with sould be a great function.

I tried many modules but I'm still not satisfied with those...

[troyrob]

This feature definitely won't be one for 1.5. But probably should be considered for 1.6.

 

I think prestashop needs to integrate a POS function.

 

 

This would really close the loop as it were and really turbocharge prestashop as a solution for both online AND physical sales.

 

It's my personal opinion that this should be the real focus of the 1.6 effort. An integrated AJAX web based POS would be an absolutely KILLER feature for this already excellent shopping cart software.

 

What do you guys think?

[Rolige]

This feature definitely won't be one for 1.5. But probably should be considered for 1.6.

 

I think prestashop needs to integrate a POS function.

 

 

This would really close the loop as it were and really turbocharge prestashop as a solution for both online AND physical sales.

 

It's my personal opinion that this should be the real focus of the 1.6 effort. An integrated AJAX web based POS would be an absolutely KILLER feature for this already excellent shopping cart software.

 

What do you guys think?

thats will be perfect, but as there are now extra modules that do something like POS, I doubt that it integrates by PS, but definitly would be perfect.

[Fabien Serny]

Hi aQs,

 

I'm not sure I understand you, in one post you said we should stuck with 1.4 and take care of bugs and another post you said you want us to add major features.

 

First of all, I think 1.4 is now very stable and we take care of reported bugs. You said that we don't care of bugs. Look at our bug tracker and then look to others open source solution bug tracker, you'll see that we are very active on it. Yes they are still bugs, and you will probably be able to find one or two old bugs not resolved yet, but look at the number of bugs we resolved each week, you'll understand

 

For the new features resquests, we won't add new features for 1.5 (we already added a lot of functionnalities), we're only working on bugs now to have a very stable 1.5. New major features will be for 1.6 now. As @Mexique1 said, we did a huge refactoring of the code. Merchant won't see that changement but developers will =)

 

For new features in 1.6, don't just say that we HAVE to add a new features. If you're the only one asking for it, we probably won't add it (if we added every features that everyone asked, PrestaShop will be full of non used functionnalities ).

Discuss with others members, make a topic and ask if others members are interested and how do they see it. If many members are interested, that's how you will convince us to develop it

[Rolige]

Hi aQs,

 

I'm not sure I understand you, in one post you said we should stuck with 1.4 and take care of bugs and another post you said you want us to add major features.

 

First of all, I think 1.4 is now very stable and we take care of reported bugs. You said that we don't care of bugs. Look at our bug tracker and then look to others open source solution bug tracker, you'll see that we are very active on it. Yes they are still bugs, and you will probably be able to find one or two old bugs not resolved yet, but look at the number of bugs we resolved each week, you'll understand

 

For the new features resquests, we won't add new features for 1.5 (we already added a lot of functionnalities), we're only working on bugs now to have a very stable 1.5. New major features will be for 1.6 now. As @Mexique1 said, we did a huge refactoring of the code. Merchant won't see that changement but developers will =)

 

For new features in 1.6, don't just say that we HAVE to add a new features. If you're the only one asking for it, we probably won't add it (if we added every features that everyone asked, PrestaShop will be full of non used functionnalities ).

Discuss with others members, make a topic and ask if others members are interested and how do they see it. If many members are interested, that's how you will convince us to develop it

I totally agree with your comment, this thread I did intend to see if some agreed with me about some things that could be included in PS 1.5, I fully understand that it is not possible to meet every need you have each person, that's what addons or if necessary a programmer, I’m sorry if I mentioned above can affect you, but believe me I understand perfectly your comment.

 

Regards

[Fabien Serny]

No problem, what you said did not affect me

I think communication with the community is very important for us.

So if you think that some features should be added for 1.6, do not hesitate to open a topic, discuss with other community members and send me the link to participate.

[OC2PS]

I think integration with support could be useful. But the issue then would be which programs to integrate with...there are so many out there. We can look at integrating only with the most popular 2-3 opensource scripts.

 

But really, what do we mean by integration? In case of support, I think integration would mostly incorporate

1. Outgoing info from Prestashop to support software (customer info, order info, etc)

2. Single sign on.

 

I think the proper way to go about this is for Prestashop to expose an API. And for module(s) to take care of "integration" and SSO with different software.

[yondo]

Hello,

I am only a beginner in prestashop. But I think the easiest way to see what is missing is to look onto the modules. Which modules are popular? So they are popular because the user needs them and this function is missing in prestashop.

 

We work in 80% with dropshipping, so I wish a better import function. But what I really miss is a export funktion.

All shops need marketing. And a big part of the marketing is the integration in marketplaces and

 

Price comparison websites. But for this you need a export function.

 

At the moment I try to install the beta of 1.5 to see a bit of the future. So I will tell a bit about it in a few days.

[pmfjoe]

I would personally love to see a POS function. I have not seen any modules which provide this, are there any? Working ones that is.

[guest*]

@pmfjoe

You can realize this with Prestashop Store Manager from Add-Ons - fourth slide. With an extra module QuickBooks POS you can connect a point of sale/cash system.

 

@yondo - as I already mentioned on German Forum, you can Import/Export your catalog very easily and variable (making own lists/templates) also with the mentioned tool.

One of our shops is 100% drop-shipping. The csv is imported daily automatically (you can manage it also variable, each hour, each day, and so on), and you have your catalog always actual.

[troyrob]

@cd2500

 

While the quickbooks module would connect it to a point of sale system it's not really a seamless system. For instance do customers accrue loyalty points from purchases made at the POS?

 

Is stock maintained realtime? How about warehouses? Are they supported?

 

Not really a knock on the product, It's just there are logistical hurdles that a 3rd party POS product will likely never account for.

[guest*]

@troyrob - Loyalty points are not supported, as the orders aren't made with prestashop front-office. The problem is the routine of Prestashop. No extra tool will support loyalty points.

 

Yes stock is maintained in realtime, because PM connects directly to Pretashop Database.

 

Sorry but I don't know any OS-System which has POS integrated for free and this fully integrated without 3rd party connection. There are several solutions, but all paid. I think this is also a too much for a simple shopsystem, blowing it up unnecessary. Users needing such solution can have it, because it is already available.

 

With 1.5. we are having blowing up problems (parse, BO not working because of low memory, etc..). If prestashop integrates also a POS with loyalty, so on my feeling I can say, that it will loose many users, because PS will not run on small webspaces. 1.4. is just running with several problems on small webspaces. I don't think that prestashop needs to be perfect and reaches the status "expert software for big wallets".

[troyrob]

Please don't consider this me arguing with you, but i simply disagree.

 

@troyrob - Loyalty points are not supported, as the orders aren't made with prestashop front-office. The problem is the routine of Prestashop. No extra tool will support loyalty points.

 

This is precisely my point, loyalty points, order history, customer info. All of this stuff will now be in a seperate database not integrated with presta.

 

Sorry but I don't know any OS-System which has POS integrated for free and this fully integrated without 3rd party connection.

 

There's a term we use for this in business school. We call this a market opportunity. However to be fair, i never explicitly stated that this functionality has to be free. I would be perfectly content paying for this as a prestashop PRO or whatever.

 

There are several solutions, but all paid. I think this is also a too much for a simple shopsystem, blowing it up unnecessary. Users needing such solution can have it, because it is already available.

 

None of the solutions that i have seen work terribly well.

 

With 1.5. we are having blowing up problems (parse, BO not working because of low memory, etc..). If prestashop integrates also a POS with loyalty, so on my feeling I can say, that it will loose many users, because PS will not run on small webspaces. 1.4. is just running with several problems on small webspaces. I don't think that prestashop needs to be perfect and reaches the status "expert software for big wallets".

 

Couldn't (and shouldn't it) it be run as a module? Therefore if a user doesn't need the functionality they can simply not enable it thus no extra strain on the webserver.

 

Also i am not very technical but i'm not convinced a POS interface (which is essentially just a different front office interface) would add any extra strain to the webserver. My cheap $4 a month webhost services upwards of 50 simultaneous users and more than 200GB of traffic a month (we use lots of 2000x2000 images).

 

There are FAR more physical stores than on-line ones, Prestashop could be a solution that services BOTH needs

[Paul / 01media]

I would like to request quite basic feature on BackOffice: settings for ordernr. At lest to be able to enter next ordernr, but more optimal settings coudl be like this:

 

- how many digits, example 12345, or 00001

- add one for each new order OR random

- enter next order nr

- auto prefix: a) none fixed text ____ c) date yymmdd c)

- prefix divider a) none -

- auto suffix: a) none fixed text ____ c) date yymmdd c)

- suffix divider a) none -

I should also be possible to make those settings individually for each shop (in multishop scenario)

 

What do you think about this ?

[Paul / 01media]

Link item id and name on stock managemnet page

 

/index.php?controller=adminstockmanagement&token=22e8968f60a53d1407fe22c22ae1acdc&conf=1

 

to item edit page

 

/index.php?controller=adminproducts&id_product=1&updateproduct&token=db13883a60714c27e1c4730c6b063fe1

 

Easy to fix, this makes the work a lot easier and faster. You should also put link on the item edit page to stock management page.

 

I feel this is really good idea to make it more usefriendly.

[Paul / 01media]

When editing prices and discounts, it shoudkl be possible to edit "specific prices for clients belonging to different groups, different countries...". Right now I must delete teh discount and enter again, when having many qty disconts adjusting the prices for all dicsounts is very time consuming. If there is no other way ofg course I missed...

[vlatko]

One thing I've noticed; the back end is not as easy to navigate as v1.4. In 1.4 i could go to any sub category and add products there. In the new version I have to edit associations for each new product from scratch. The interface is also more intuitive in the old one.

I also like the 1.4 default theme better, and would like to have it as an option in 1.5.

 

Actually, the only thing that would even make me go from 1.4 to 1.5 at this moment is the ability to modify orders, which 1.4 is lacking.

[Rolige]

One thing I've noticed; the back end is not as easy to navigate as v1.4. In 1.4 i could go to any sub category and add products there. In the new version I have to edit associations for each new product from scratch. The interface is also more intuitive in the old one.

I also like the 1.4 default theme better, and would like to have it as an option in 1.5.

 

Actually, the only thing that would even make me go from 1.4 to 1.5 at this moment is the ability to modify orders, which 1.4 is lacking.

Well in this case I think the most people like the new BO interface, i think is most intuitive, clearly, this is my viewpoint.

[vlatko]

Well in this case I think the most people like the new BO interface, i think is most intuitive, clearly, this is my viewpoint.

 

it is too segmented and I have to make too many clicks to change something. Also, when changing themes, in the 1.4 version I had thumbnails to preview a theme; i did not see that here.

seems to me while some things have become better, others have taken a turn for the worse. Hopefully most of this will be solved until the final version.

[absolutic]

I've noticed that the product_lang table size is equal to number of products*number of shops*number of languages. It would be great if there could be possibility to associate product lang with group of stores optionally, this will reduce the table on the number of shops when we know exactly that products descriptions will be the same for all members of the group. That point is important for shops with large number of products.

[Andreas Maurer]

Drop ship still missing.

[Andreas Maurer]

I've noticed that the product_lang table size is equal to number of products*number of shops*number of languages. It would be great if there could be possibility to associate product lang with group of stores optionally, this will reduce the table on the number of shops when we know exactly that products descriptions will be the same for all members of the group. That point is important for shops with large number of products.

Perhaps you could use just one store with multiple languages. And have domains or subdomains point to different languages? That will keep your table light while giving the appearance of "multistore"

[nortom]

Prestashop needs a function that's allow the admin to create a new order and invoice for your customer and that you can change every product manually on the order like in Magento.

[Rolige]

Prestashop needs a function that's allow the admin to create a new order and invoice for your customer and that you can change every product manually on the order like in Magento.

That function is implemented in 1.5, you need test the alpha version

[vshaa]

Shopping Cart is Hidden now.

[Guest]

I want improvements to free shipping. Currently if I set free shipping to 100.00, the tax is included in that 100.00. And what I want is the customer to actually purchase 100.00 before tax.

 

Also to give free shipping to Canadians and not to the USA I need to create shipping zones. That is ok because I need to charge different shipping rates. But it means I can't use the free shipping feature because it will give USA free shipping and I only want to give free shipping within Canada.

 

So then I set up Price Ranges - for the Canadians I'll set a price range to 0.00 so they will get free shipping if they reach that point. However, because tax is included in the calculation I have to set up a Carrier and zone and price range for each province that has a different tax rate, because I need to set each Price range to allow for the tax.

[TWDesign]

Better handling of attributes - as per the PrestoChangeo Attributes Wizard module.

 

Ability to handle multiple shipping addresses for a single order

 

Ability to add an extra fee for different payment types e.g. C.o.d. payment (most shippers charge an extra fee for this).

 

WYSIWYG editor in the category editing page.

 

 

That would be a good start.

[screentekdesignsltd]

Hi aQs,

 

I'm not sure I understand you, in one post you said we should stuck with 1.4 and take care of bugs and another post you said you want us to add major features.

 

First of all, I think 1.4 is now very stable and we take care of reported bugs. You said that we don't care of bugs. Look at our bug tracker and then look to others open source solution bug tracker, you'll see that we are very active on it. Yes they are still bugs, and you will probably be able to find one or two old bugs not resolved yet, but look at the number of bugs we resolved each week, you'll understand

 

For the new features resquests, we won't add new features for 1.5 (we already added a lot of functionnalities), we're only working on bugs now to have a very stable 1.5. New major features will be for 1.6 now. As @Mexique1 said, we did a huge refactoring of the code. Merchant won't see that changement but developers will =)

 

For new features in 1.6, don't just say that we HAVE to add a new features. If you're the only one asking for it, we probably won't add it (if we added every features that everyone asked, PrestaShop will be full of non used functionnalities ).

Discuss with others members, make a topic and ask if others members are interested and how do they see it. If many members are interested, that's how you will convince us to develop it

 

I think the solution to having features put in that most people won't use is understandable, but thats wat the modules are for, so people can have different features and some don't.

[Dh42]

The biggest feature I would add currently would be an alerter. So when you log into the back office Prestashop can actually post security alerts other than telling you your version needs to be updated. If there ever is a bug that affects old versions or security problems you will be able to get the message out to everyone.

[Scotty501]

Restore function!!

 

It's been asked for since 1.2x - you can export a back-up but cannot restore from a backup in the back office - what???!!

 

With all the update issues people have it would be far easier if it was a BO function - certainly for migration, updates it is a must.

[Dh42]

Its a hard functionality to make. Its like trying to change your shoe while you are standing on it.

[Scotty501]

Its a hard functionality to make. Its like trying to change your shoe while you are standing on it.

 

I understand the process - it is something many would like to see - hard or not

 

If it was all easy things we wanted we would be a happy community with nothing to wish for

Edited June 18, 2012 by Scotty501 (see edit history)

[Dh42]

You can just import it in phpMyadmin. To me it just adds bloat to the program.

[Scotty501]

You can just import it in phpMyadmin. To me it just adds bloat to the program.

 

You miss the point. I know how to do that, you know how to do that. But many do not - and have requested it - that's the point.

[DeepVoid]

Prestashop absolutely needs a feature to manage separately different couriers. I would like to setup free delivery for courier A and normal paid delivery for courier B. This is very important when a merchant starts a promotion with free delivery for orders above a certain cart amount, but only for customers in country X, while foreign customers continue to pay their usual delivery fees.

 

General advice: why doesn't the development team hire a true merchant, in order to obtain valuable hints about new features in Prestashop? Not a programmer, a true merchan, one who knows how TO SELL, not how to write good code.

 

Coding is absolutely secondary, ideas and good architecture are the only things that really matter in software development.

[Fiuncho]

Hey. This message is a Google translation, because my English is not the best. I searched a lot for several weeks in the forums, modules, I downloaded different versions of Prestashop, but have not found anything like what I seek:

I'ma Photographer freeland. I need Prestashop solely and exclusively to enable downloadable products. I need also to unregistered visitors can pay by entering your email only, to send a link andthe payment confirmation from Paypal.

And finally, I need a module that handles the bulk upload graphics files (png and jpg), so as to show in galleries with categories, but always with a watermark, then, as it is now thought Prestashop, there to enter one by one the attributes, characteristics and prices of each product. Can you imagine doing every evening with 500 products?

Fotolia style or any other bank of images.

Is there anything even similar in Prestashop?

Nevertheless, Prestashop has an advantage over the rest of the stores (which do not have these possibilities), and is a magnificent and intuitive operating system, both in Front and in Back oficce.

 

 

I would like this new version (which I'm testing and also lacks all these things that indicated), think of all those who only use downloadable products, and for which the options related to delivery, returns, countries, transport, etc, will not do.

And if possible simplificasen the guest register, leaving NO binding most of the fields. And an exclusive management (or module) for image management, as the project "Gallery3".

Thanks, and again, apologize if anything I said has not been translated from the convenient way. I appeal to your imagination.

[TWDesign]

I think the solution to having features put in that most people won't use is understandable, but thats wat the modules are for, so people can have different features and some don't.

 

In general I agree BUT....

 

sometimes the modules fill a functional need that is obvious AND those same modules require core file modifications.

NOT a good situation.

[Dh42]

Scotty501,

That is the whole learning curve. You cannot have powerful and easy, it just doesn't work that way. Think windows and linux. Linux ships stripped down and relies on the community for a lot of features that windows users think should be included. Prestashop is keyed at being a professional solution, not a one size fits all, everything included.

 

I have complained about it needing features in the past, but in light of recent developments, I would prefer it to be stripped down with a better module interface. I have shops that don't ship, that is just code overhead for me. A lot of the features are just code overhead in a lot of situations. I do not want to rely on a ccs display:none, I would prefer it not be there.

 

At the same time you have to take the software for what its worth too. It doesn't work for every situation. Before I have mentioned that I have a client that runs a catalog in prestashop, but all of the cart function is handled by WHMCS. I took 2 softwares that are strong in certain areas and made a solution, because neither was a good standalone solution. Sometimes you have to hack things out, that is why we are developers. Personally I do not mind it, that is what keeps us in jobs.

[epatxi]

define the type of unit for sale in each product, grams, square meters, ... without using attributes

[Bill Dalton]

CSS Image Sprites

 

An image sprite is a collection of images put into a single image.A web page with many images can take a long time to load and generates multiple server requests. Using image sprites will reduce the number of server requests and save bandwidth.

http://www.w3schools.com/css/css_image_sprites.asp

[wingover]

Dear PrestaShop Team,

 

first of all - thank you for this great software.

 

Here some suggestions for PrestaShop 1.5 or the next versions...

 

Create snippets:

The opportunity for the admin to create snippets (text, html, wysiwyg, code...) in the backend and place them in templates, cms-pages, product specification, translations, hooks, etc.

 

Hook list on module page:

Information about available hooks for every module on the module page.

 

Extend hooks of a module:

Extend the available hooks of a module.

It would be nice to have a checkbox 'ignore' (for example), to insert a module everywhere and ignore the limitation of hooks set by the module developer.

 

Filter by hook on module position page:

Filter by hook to find modules and hooks faster.

 

Insert modules:

To insert a module directly in a template, without using the module positions page.

 

Select templates:

To select individual templates for products, categories and cms-pages.

 

Installation Profiles:

Like suggested in this post, it would be a great feature to save module positions and configurations.

http://www.prestasho...-profile-files/

http://forge.prestas...owse/PSCFV-2855

 

Clear caches:

Clear all caches without starting a ftp-software. Like 'clear all caches' in TYPO3 (for example). http://forge.prestas...owse/PSCFV-1919

 

Smarty vs. php:

As a php developer, like many others, I think it's better to use pure php in templates. More flexibility for php developers and no need to learn another 'language'...

[Carl Favre]

Hi everyone,

 

Thanks for all these suggestions.

 

Do not forget to also post them on the bug tracker (official place for everything related to PrestaSop bugs/improvements/suggestions reports).

 

There is already a list of popular suggestions/improvements. You can also vote for your favorite one.

 

http://forge.prestas...larissues-panel

[mexique1]

wingover > Most of the issues you are pointing (snippets, insert modules, extend hooks) are fixed by {pan}

 

https://github.com/alexsegura/pan

[wingover]

Hi mexique1,

 

thanx for the link to {pan} - first time I read about it. It looks very interesting.

Do you plan to make it usable for version 1.5?

I'm new to PrestaShop and I like to start with 1.5, because 1.4 is different in some things.

 

It seems, that a lot of (free) PrestaShop modules and themes are spread over the internet. Sometimes not easy to find, sometimes registration needed. For example:

http://www.presto-ch...op-free-modules

http://www.prestaliv...stashop-modules

http://prestashop-module.de

 

Why is not everything on http://addons.prestashop.com

Like TYPO3 for example - most extensions you can find here: http://typo3.org/ext...ons/repository/

[mexique1]

I haven't tested yet, but it should work out of the box in 1.5

 

If not, report an issue, I'll be happy to fix it

[graffeli]

Can use external picture link from a central picture repository instead of uploading every product picture again in prestashop main system. Example:

[ember1205]

How about much more flexibility with taxes?

 

Every item in the store, including handling fees, shipping fees, and any other costs need to be able to be identified as taxable or not. Also, we need a way to identify that items are taxable based on shipping OR pickup address. Ship an item from a state with sales tax to a state without, and you don't pay the tax (usually). However, picking it up in store requires the payment of tax.

 

We also need a way to identify shipping containers / packaging and what combinations of items go in them. Then, we can send along weight (combined weights of items in the box) and package dimensions (after PS chooses the right box to ship everything in) to FedEx and the like for shipping rate costing.

[ember1205]

REMOVED

 

Their own versions of what?

[vekia]

it's was a spam, don't worry