taylorjohnson Posted October 28, 2011 Share Posted October 28, 2011 Hi I've written an article outlining some major shortcomings I feel Prestashop has in terms of developer and site builder friendliness. The article may seem harsh, but the motive is to provide valid feedback to the Prestashop team on what I feel a lot of site developers and builders want to see, especially if they build a lot of sites in Prestashop. http://taylorjohnson...time-to-step-up Link to comment Share on other sites More sharing options...
OC2PS Posted November 2, 2011 Share Posted November 2, 2011 Regarding sentence 1 of your article, PS claim to have more than 100k live websites, so your assertion of 40k seems unfair Do you have reason to disbelieve the PS claim? Link to comment Share on other sites More sharing options...
OC2PS Posted November 2, 2011 Share Posted November 2, 2011 Regarding the rest of the article, I disagree with you when you talk about core and site separation. Coming from larger and more general CMS platforms such as Drupal and WordPress, the idea of separating the core files from any data (be it images, config, or other) related to the individual website seems only natural, however this is not the case in Prestashop. Something so fundamental and trivial as this can be the difference between a successful and failed product. I'll try my best to break down Prestashop's structure: /modules/ - Both core and contributed modules are placed in this folder /themes/ - Both core and custom themes are placed in this folder I don't believe the software should differentiate the *default* modules and themes (calling them core is erroneous) shipped with the package from those added during customization. A theme is a theme, and a module is a module. You mentioned Wordpress, and yet, WP works exactly like PS...their default theme is placed in same folder as other themes. Same goes for their modules. High-level roadmap is surely something PS lacks sorely, and I hope this is addressed soon. I also agree on the email template issue and highly recommend that the development team have a serious look at Mailchimp templates for inspiration. Link to comment Share on other sites More sharing options...
El Patron Posted November 8, 2011 Share Posted November 8, 2011 I didn't see it mentioned maybe it was, but I would love to see the URL removed from the db...i.e. PS_DOMAIN This causes untold problems (see installation form). As for mentioning wordpress in your article, it is by far the worse offender of embedding url's in it's db. Link to comment Share on other sites More sharing options...
taylorjohnson Posted November 9, 2011 Author Share Posted November 9, 2011 Sorry, at the time I was unaware of the statistics posted by the Prestashop team. I've updated my article to reflect this. I don't believe the software should differentiate the *default* modules and themes (calling them core is erroneous) shipped with the package from those added during customization. A theme is a theme, and a module is a module. You mentioned Wordpress, and yet, WP works exactly like PS...their default theme is placed in same folder as other themes. Same goes for their modules. I understand where you're coming from in terms of WordPress, however I wouldn't go as far to say their structure works the same. First of all, having the default theme in the same folder does not worry me, as you'll usually only have a few themes. WordPress does include one plugin by default, Akismet, which is somewhat out of place I feel, but that is the only exception. I understand what you mean by a module being a module, however, my point is one of efficiency not definition of what a module is. You rarely want to keep the same version of a Prestashop included module when manually upgrading a Prestashop site. It is very much the case of scrolling through the modules directory, locating and selecting each contributed module you wish to transfer and backing them up before upgrading. When managing more than a handful of sites, each with different modules, this can become very time consuming and inefficient. One of my main issues is with the /img directory. Separating the images that are included with Prestashop and the ones that are added by the site admin/user would make upgrading a lot easier. It becomes time consuming when upgrading manually, and the autoupgrade module has a tendency to delete custom favicons for example. As the autoupgrade module matures it should largely fix this issue. In the end these are just my opinions. I am more than happy for others to tell me why my ideas are wrong, better ways to go about it or why the current system is as it is. Link to comment Share on other sites More sharing options...
OC2PS Posted November 9, 2011 Share Posted November 9, 2011 WP ships with several modules apart from Akismet - Jetpack, Hello Dolly, etc. Eitherway, I see what you are getting at, and I think a large part of the problem will be resolved once PS implements a "one-click upgrade from admin panel" system for upgrading modules (scheduled for 1.5.0). Autoupdate for the core (+ default modules) is already operational. Hopefully teething troubles shall be resolved soon and the process will become as smooth as Wordpress's. I agree with you on the images folder issue - I wonder if ANY images should be part of the software itself. Arguably, images could be only either i) part of themes, or ii) associated with the store (e.g. products, categories, manufacturers, etc) Link to comment Share on other sites More sharing options...
.png.022b5452a8f28f552bc9430097a16da2.png)
Recommended Posts