Quantcast
Channel: PrestaShop Developers' blog
Viewing all 939 articles
Browse latest View live

Calling for user-testing volunteers (Paris, France)

$
0
0

A lot of work has been done on the new back office for PrestaShop 1.7, most notably the reworked Product page and Modules page; as well as the brand new theme. Now, we need you to tell us what you think – face to face!
As a reminder, the PrestaShop 1.7 Project FAQ is available.

A big part of the PrestaShop 1.7 project was making sure that this new version had a design that would help merchants do their daily tasks faster and with less confusion. As for any User Experience (UX) project, there comes a time when the choices which have been made have to be reviewed by real users, in order to validate them.

User testing

User-testing are the proper way to do that. We contact a user (most often a merchant, but also developers, logisticians, etc.), get them to come to our Paris office, and sit them down in front of a machine in order to see how they react to the new interface.

The user is not alone: two members of the Prestacrew will assist her/him, and the whole session is recorded for later use.

This face-to-face discovery gives invaluable feedback on what we’ve done so far, and shows us what is left to do in order to be as close to perfection as possible. From these weekly real-life feedback, we iterate between UX designers, product managers and developers, and the next batch of testers can already see our improvements.

Come on in!

And you can be a part of it! We are looking for people (ideally from the Paris region) who would be able to come to our Paris office (right next to the St Lazare station– hence the Paris region thing, see) for an hour and a half, testing the few features we have cooked for the whole community.

Ideally, you should:

  • Be at ease with managing an online store on a daily basis,
  • Be used to navigating the PrestaShop 1.6 back office (or earlier version), or the back office of any other e-commerce software,
  • Have not yet tested PrestaShop 1.7 – in order for your reaction to be genuine.

Also, you must speak either French or English, and be able to read English :)

What early testers have to say

Are you scared to be lost with the new interface? See what Clément, from renowned store Le Slip Français, had to say after his session:

Do you feel up to that (easy) challenge? Give us your details in this form, and you might be part of the next testing session!

Thank you for contributing!


PrestaShop Core Weekly - Week 11

$
0
0

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase during the last week, from Monday 14th to Sunday 20th of March 2016.

Milestones

Do you live near Paris? Are you willing to give us a couple of hours in order to test-drive the design of PS 1.7? Let us know!

The team is hard at work on PrestaShop 1.7, the next major version of the most complete e-commerce software solution there is.
You can find an up-to-date thread about it in the forum.
The 1.7 Project FAQ is always available here: http://build.prestashop.com/news/prestashop-1-7-faq/.

Please note that finishing the planned projects for 1.7 and delivering a quality beta version soon is the top priority for the PrestaShop Core developers at the moment. Merging community pull requests has therefore slowed down until then, but will be back with a vengeance once we have a first beta to release to you! So please keep testing, and keep sending patches our way: it’s the raison d’être of this community project!

Do you want to encourage us? Give us a star on GitHub! :)

Code changes in 1.7.0.0-develop

Let’s review the merged pull-requests on the ‘develop’ branch since the last Core Weekly Report!

Text changes

  • 5164: Update wording configuration.xml. Thank you @Nobodaddy!
  • 5165: Update wording order_return_state.xml. Thank you @Nobodaddy!
  • 5166: Update order_state.xml. Thank you @Nobodaddy!
  • 5167: Update wording quick_access.xml. Thank you @Nobodaddy!
  • 5168: Translated supply_order_state.xml. Thank you @Nobodaddy!

Product page

  • 5181: Product pages integration, by @Shudrum.
  • 5182: Fix Add customization button on product page, by @Shudrum.
  • 5197: product description can be saved when empty, by @mickaelandrieu.
  • 5199: Fix Online / Offline switch, by @Shudrum.

Front office (including the default theme, named “Classic” for now, based upon the Starter Theme)

  • 5020: Change structure for module assets override, by @julienbourdeau.
  • 5183: Fix block newletter display, by @nihco2.
  • 5184: Remove data from ProductController and related templates, by @julienbourdeau.
  • 5185: OrderPresenter - Rework amounts, by @julienbourdeau.
  • 5190: Fix some display troubles, by @maximebiloe.
  • 5191: Fix accessories display, by @maximebiloe.
  • 5192: Fix product cover layer, by @nihco2.
  • 5194: Fix update of delivery address, by @maximebiloe.
  • 5195: Cart widget only has link to cart if not empty, by @maximebiloe.
  • 5201: Fix delivery step display, by @nihco2.
  • 5202: Fix display ecotax, by @nihco2.
  • 5217: Fix Classic Theme README.md. Thank you @panploenes!

Back office

  • 5139: Fixed warning - no such file or directory. Thank you @true0r!
  • 5140: pack/virtual product shouldn’t be selected if variations exists, by @mickaelandrieu.
  • 5189: Module page: fix categories, by @Quetzacoalt91.
  • 5196: fixed permissions display in 1.7, by @mickaelandrieu.
  • 5203: fixed Manage tax rules link, by @mickaelandrieu.
  • 5205: click btn preview save product and redirect in window.open with target, by @cocoweb94.

Core

  • 4817: Implement Module Manager, by @Quetzacoalt91, @maximebiloe and @tchauviere.
  • 5186: Introduce the new welcome module, by @maximebiloe.
  • 5188: Fix cache dir for ModuleDataProvider, by @maximebiloe.
  • 5207: fixed getAdminLink() twig extension, by @mickaelandrieu.
  • 5208: Fix comment typo on CarrierCore. Thank you @Soullivaneuh!

Installer

  • 4140: Add check for PHP zip extension, by @Quetzacoalt91.
  • 5093: fix upgrade, by @jocel1.
  • 5179: Fix install DB query. Thank you @firstred!
  • 5200: backport tabs changes to all lang xml files, by @julienbourdeau.

See all the PRs merged into the codebase since the last Core Weekly here.

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @firstred, @Nobodaddy, @panploenes, @Soullivaneuh and @true0r! Also, thank you to the contributors whose PRs haven’t been merged yet! And of course, a big thank you to all those who contribute with tickets on the Forge!

If you want to contribute to PrestaShop with code, please read these pages first:

…and if you do not know how to fix an issue but wish to report it, please read this: How to use the Forge to contribute to PrestaShop. Thank you!

Happy contributin’ everyone!

Test PrestaShop 1.7.0.0 alpha 3 now!

$
0
0

Here it is. After two internal alpha versions, we’re happy to present to you this public alpha release of PrestaShop 1.7.0.0 – the first in a series of public alpha/beta/RC versions that we intend to release over several weeks, in order to gather feedback and make sure that the final and stable version is the best it can be!

PrestaShop 1.7 Alpha 3 Release

Here is your chance to dive into what’s coming in 1.7:

  • An improved back office interface and menu,
  • A brand new Product page and Modules page,
  • A brand new default theme and a new way of building themes,
  • An overall stronger codebase thanks to the implementation of the Symfony 2 framework and PHP 5.4.

Have a go at it!

Let’s insist on this: this is NOT the stable version of PS 1.7, and IT SHOULD NOT BE USED IN PRODUCTION. Do not create a new store with this alpha version, it is by definition not finished yet.

You SHOULD however install this alpha version as a test store, either on your machine or your web hosting, and play with it – and give us your feedback!

The release date for the stable version is not yet set, so you have a few weeks and beta/RC versions ahead of you!

Test PrestaShop 1.7.0.0 alpha 3

How to give feedback

Have you found a bug? A curious behavior? An unexpected reaction? Let us know! Create a ticket on the 1.7 Forge project, and give us as much details as possible!

Please note that we are not looking for feedback on the overall technical or design choices: Symfony2, the new theming system, the back office design and other global aspects of 1.7 are pretty much set in stone. However, do let us know about bugs or possible improvements!

What’s coming in 1.7.0.0

The 1.7 Project FAQ helpfully gives you the areas where 1.7 has seen the most work done:

  • A better way to create and maintain a theme:
    • New starter theme to help designers create a kick-ass theme in much less time than before,
    • New default theme: clean, efficient, and easy to extend.
  • Improved key user journeys in the back office:
    • Welcome first-time users with a new onboarding system,
    • Simplify the product creation workflow,
    • Easily find installed and non-installed modules.
  • An improved administration interface menu structure, focused on getting the most common tasks done faster,
  • A new architecture, based on the Symfony2 framework.

Several articles were published on this blog about the various projects surrounding 1.7. You can find a full list on this forum post.

What’s in progress

Remember that this is alpha 3: a lot of things are not ready yet, or are ready but not yet available.

We tried to gather the most important ones, so you have a clear idea of what still needs to be implemented. All of this will eventually be fixed for the stable version – and you can help with pull-requests on GitHub, and feedback of your tests!

CORE

  • If your web hosting uses PHP-FPM, some links (and images) will not work.
  • Multistore & Advanced Stock Management aren’t yet connected to the Create a Product Page.
  • The header and navigation can vary (slightly) between pages.
  • Employees permissions are not yet suited for the new navigation in place
  • If a problems occurs while uploading a theme, we may not be able to tell you why currently :) In effect, errors and warnings are not fully set yet. And in any case, your 1.5-1.6 theme will NOT work with the new theme system.

FRONT OFFICE

  • Quick view is still a work in progress and may have bugs (adding to cart for example)
  • Some links may be broken during your navigation on the shop

BACK OFFICE

  • Some images are broken for now, some buttons and tab could behave in a weird way, and you might stumble on other weird artefacts. We know about this, and they will all be fixed in time.
  • We’re still working on the responsiveness of the back-office, and 13” inches screens could particularly be affected.

MODULE PAGE

  • The “disable on mobile” option will be reintroduced in a later beta version
  • We’re improving the modules discovery page: better sorting, more information, reworked categories, etc.

CONTENT

  • Interface copywriting is not final yet. Some parts need to be written, others are waiting for a rewrite and others are in proofreading.
  • Default products are still the ones used in version 1.6. Version 1.7 should have a brand new set of products.
  • Translations are on hold for now while we’re working on improving the system: the interface is only in English for now.

DOCUMENTATION

  • Contextual help still displays 1.6 documentation as we’re updating it to 1.7. Expect it to be final during our RC period.
  • Technical documentation for modules & themes should follow the same timeline.

Final note!

So cheers for the first public glance at the brand new 1.7, made with <3 by our team and our wonderful Community. It’s not fully baked yet, but we’re very proud of the work done.

Test PrestaShop 1.7.0.0 alpha 3

We’ll closely monitor your feedback and are eager to hear from you!

Happy testing!

Release of PrestaShop 1.6.1.5

$
0
0

PrestaShop 1.6.1.5 is now available. This maintenance release closes 32 issues since version 1.6.1.4 (released on January 7th).

As the version number indicates (as per our SemVer-like versioning), this is the 5th patch release for PrestaShop 1.6.1.0.

As usual, if you are currently running promotions leading to high traffic on your website, we recommend that you wait for the promotion to end before attempting any upgrade and technical change to your store.

We hope you enjoy this new patch release!

The changes

For a full list of changes, see the list of pull requests merged into the 1.6.1.x branch since version 1.6.1.4.

Here are some of the most notable changes that this version brings:

  • Price: Fix combination price calculation with impact and reduction.
  • Order slips: Fix incorrect shipping taxes.
  • Front office: Split CSS for IE9.
  • Front office: Fix specific price.
  • Front office: Fix incorrect cart rules list in case of country restriction.
  • PDF: Re-added field note in invoice.
  • PDF: Re-added shipping box in invoice.
  • PDF: Updated b2b template.
  • PDF: Improved pagination on invoices.
  • PDF: Use address from order for invoice.
  • PDF: Update constraints on Addresses display.
  • Class: Added hook to indicate which method to use instead of deprecated methods.
  • CORE: Fixed double preg_quote() in Dispatcher.php.
  • CORE: Updated SwiftMailer to v5.2.2.
  • Security: Use Mcrypt’s CBC mode instead of the ECB mode.
  • i18n: Updated installer for Italian, Vietnamese, and Polish.
  • i18n: Updated Hong Kong localization pack.
  • i18n: Improved Dutch meta info.

Note that updating SwiftMailer is a nice step forward security-wise: most notably, it enables support for STARTTLS, making it possible for PrestaShop to work with GMail, Outlook, etc. We do advise you to update to 1.6.1.5 solely for this. However, if you cannot upgrade, contributor Michael Dekker built a free module to upgrade SwiftMailer for PrestaShop 1.5.0.0-1.6.1.4. Thank you Michael!

The PrestaShop 1.6.1.5 changelog is available.

Since version 1.6.1.5 is a “patch” update to version 1.6.1.0, upgrading from that version will be as smooth as silk for everyone: features will work better, and modules & themes which worked fine on 1.6.1.0 will work just as well with 1.6.1.5.

This release had 19 contributors, both from PrestaShop and from the Community at large.

  • @erouvier29
  • @kelu95
  • @gwarnants
  • @mickaelandrieu
  • @kpodemski
  • @Dh42
  • @prestamodule
  • @SDF-of-BC
  • @mcdado
  • @studiokiwik
  • @AlexEven
  • @ZiZuu-store
  • @rGaillard
  • @maximebiloe
  • @nihco2
  • @firstred
  • @julienbourdeau
  • @Nobodaddy
  • @Shudrum

A huge “thank you!” to each of the 11 outside contributors, who gave their time and knowledge for the benefit of the whole PrestaShop community! You too can contribute to the next version!

Let’s go, upgrade your store(s)! Upgrading from 1.6.1.0-1.6.1.4 is completely safe, upgrades from a standard 1.6.0.x version should work just as well, and those upgrading from version 1.5, 1.4 or even 1.3 should take their time and pay attention to their modules, their theme and their custom modifications!

Download 1.6.1.5 now!

PrestaShop Core Weekly - Weeks 12-13-14

$
0
0

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase during the last few weeks, from Monday 21st to Sunday 10th of April 2016.

Milestones

Sorry for the delay! We were busy, well, you know, releasing the first public alpha version of PrestaShop 1.7, and a maintenance release for the 1.6 branch, version 1.6.1.5.

Do you live near Paris? Are you willing to give us a couple of hours in order to test-drive the design of PS 1.7? Let us know!

The team is hard at work on PrestaShop 1.7, the next major version of the most complete e-commerce software solution there is.
You can find an up-to-date thread about it in the forum.
The 1.7 Project FAQ is always available here: http://build.prestashop.com/news/prestashop-1-7-faq/.

Please note that finishing the planned projects for 1.7 and delivering a quality beta version soon is the top priority for the PrestaShop Core developers at the moment. Merging community pull requests has therefore slowed down until then, but will be back with a vengeance once we have a first beta to release to you! So please keep testing, and keep sending patches our way: it’s the raison d’être of this community project!

Do you want to encourage us? Give us a star on GitHub! :)

And with that, I’m taking two weeks off to celebrate my wedding! Cheers, good people! Don’t break the Internet while I’m away :)
(yes, that means the next Core Weekly will also be 2-3 weeks late – unless @AlexEven does something about it ;) )

Code changes in branch 1.6.1.x

Here the pull-requests that were merged on the ‘1.6.1.x’ branch since the last Core Weekly Report!

Front office (including the default theme)

  • 4438: fixed bug on payment module, check if defined $order object, by @kelu95.
  • 4444: Split css for IE9, header : add css for IE9 < only, by @kelu95.
  • 4501: Stores search didn’t work with keyboard validation. Thank you @gwarnants!
  • 4589: Removed template logic that is not needed. Thank you @Dh42!
  • 4593: bankwire / correct module name for translation. Thank you @prestamodule!
  • 4735: Fix JavaScript mistake in blocklayered.js. Thank you @macdado!
  • 4741: Fix combination price calculation with impact and reduction. Thank you @studiokiwik!
  • 5064: Fix warning if combinations are disabled, by @maximebiloe.
  • 5193: Fix specific price, by @nihco2.
  • 5221: fix parse error in AuthController.php. Thank you @kpodemski!
  • 5291: Fix incorrect cart rules list in case of country restriction. Thank you @erouvier29!

Back office

  • 3856: Incorrect shipping taxes in order slips. Thank you @erouvier29!
  • 4441: add error message on upload theme bigger than post_max_size, by @kelu95.
  • 4767: Change only active state on bulk status change. Thank you @erouvier29!
  • 5124: Fix the display of the listing filters on the toolbar, by @rGaillard.

Core

  • 4598: return false if feature is not active in aliasExists(). Thank you @prestamodule!
  • 4599: indicate which method to use for deprecated methods. Thank you @prestamodule!
  • 4717: Usage of CCB mode. Thank you @SDF-of-BC!
  • 4991: Fixed double preg_quote() in Dispatcher.php. Thank you @ZiZuu-store!
  • 5214: Update swift mailer. Thank you @firstred!
  • 5330: fix ccc for admin, by @julienbourdeau.

PDF

  • 4584: (re) added field note in invoice, by @mickaelandrieu.
  • 4586: (re) added shipping box in invoice, by @mickaelandrieu.
  • 4595: updated b2b template, by @mickaelandrieu.
  • 4608: Improved PDF pagination on invoices, by @mickaelandrieu.
  • 4621: update constraints on Addresses display, by @mickaelandrieu.
  • 5313: Use address from order for invoice. Thank you @Nobodaddy!

Installer

  • 5030: Update italian installer. Thank you @mcdado!

Localization

  • 4867: Update Hong Kong localization pack, by @AlexEven.
  • 5000: Improve Dutch meta info, by @AlexEven.
  • 5150: Adding Vietnamese installer, by @AlexEven & @dungvn1187.
  • 5222: Update Polish installer, by @AlexEven.

Code changes in branch develop (for version 1.7.0.0)

Let’s review the merged pull-requests on the ‘develop’ branch since the last Core Weekly Report!

Front office (including the default theme, named “Classic” for now, based upon the Starter Theme)

  • 5210: empty cart template redesign, by @nihco2.
  • 5224: move some templates, by @julienbourdeau.
  • 5231: client notifications redesign, by @nihco2.
  • 5236: Add some data-* attributes to the <article>. Thank you @prestamodule!
  • 5238: Fix address form, by @nihco2.
  • 5239: Add quickview feature to Classic, by @julienbourdeau.
  • 5245: Fix translation in OrderPresenter. Thank you @fojtcz!
  • 5282: Access address, by @Shine-neko.
  • 5294: Contact - fields displayed twice, by @Shine-neko.
  • 5295: Cancel search in modules, by @Shine-neko.
  • 5317: Fix errors in quick-view, by @Shine-neko.
  • 5331: Fix popin display after add to cart, by @nihco2.

Back office

  • 5206: introduced a reusable way to display a right sidebar, by @mickaelandrieu.
  • 5220: update link preview in js when product change publish, by @cocoweb94.
  • 5225: display condition should be false by default, by @mickaelandrieu.
  • 5229: use module list according to customer/employee language, by @mickaelandrieu.
  • 5234: Added ‘force deletion’ option on module uninstall, by @mickaelandrieu.
  • 5246: Set empty list on exception in module catalog, by @Quetzacoalt91.
  • 5249: Add module filter depending on their status on manage tab, by @tchauviere.
  • 5255: Module Page - Improved Ajax Loading on catalog, by @tchauviere.
  • 5261: Fix issue with add() on Tab class, altering id_parent, by @tchauviere.
  • 5262: Fix wording on “Installed Module” module tab, by @tchauviere.
  • 5263: Fix some tabs names, by @Shudrum.
  • 5264: Fix employee drop down z-index, by @Shudrum.
  • 5268: added a tag management of product categories, by @mickaelandrieu.
  • 5269: Introduce new themes catalog page, by @mickaelandrieu.
  • 5275: Fix issue with FastCGI and duplicate header “content-type”, by @tchauviere.
  • 5276: module.js fix an issue on reset category filter, by @tchauviere.
  • 5278: Fix some number formats on product page, by @Shudrum.
  • 5286: use material-icons for product status, by @Shine-neko.
  • 5287: add new ids for test, by @mgui95.
  • 5292: Themes / fix broken preview link. Thank you @prestamodule!
  • 5293: added a search input to select product categories, by @mickaelandrieu.
  • 5296: BO: open “My Shop” link on new page. Thank you @prestamodule!
  • 5298: Fixed notice Undefined index: medium, by @jtabet.
  • 5300: Don’t escape modules names. Thank you @kpodemski!
  • 5303: Fixed controller class for the “Modules” tab, by @jtabet.
  • 5323: fixed bug on product categories tree, by @mickaelandrieu.

Core

  • 5106: Improve configuration load & get performances, by @jocel1.
  • 5209: Minor fix on module actions in module page, by @Quetzacoalt91.
  • 5211: Update gitignore, by @julienbourdeau.
  • 5212: Display a warning when no payment method is available, by @maximebiloe.
  • 5226: hide deprecated msg for Module::isInstalled, by @julienbourdeau.
  • 5227: Take into account PS_CONDITIONS option, by @maximebiloe.
  • 5230: check for rights on Module installation, by @mickaelandrieu.
  • 5233: Update SwiftMailer. Thank you @firstred!
  • 5247: Fix issue on modules page when logged on addons, by @Quetzacoalt91.
  • 5248: Module manager tests, by @Quetzacoalt91.
  • 5253: Remove php -l execution on modules, by @Quetzacoalt91.
  • 5258: Remove APCu backwards compat dependency. Thank you @firstred!
  • 5279: Remove unused partner request on module page, by @Quetzacoalt91.
  • 5284: Fixed call static method on Product. Thank you @studiokiwik!
  • 5290: Fix webservice api/products/{id} for PHP7: Function name. Thank you @JoniJnm!
  • 5299: remove “autoExecuteWithNullValues” method. Thank you @prestamodule!
  • 5304: fix body_classes array shape, by @julienbourdeau.
  • 5320: Fix legacy context, by @maximebiloe.
  • 5326: Remove broken links to the SQL table modules_perfs, by @Quetzacoalt91.
  • 5329: Small fix on translation key that should’nt be capitalized, by @mickaelandrieu.
  • 5334: Remove useless files and some deprecated method, by @julienbourdeau.

Tests

  • 5281: use chrome instead of firefox for tests, by @mickaelandrieu.
  • 5297: speed up php parse error checker & precompute travis composer.lock, by @jocel1.
  • 5322: Module manager tests, by @mickaelandrieu.
  • 5332: removed call from external api in integration tests, by @mickaelandrieu.

Installer

  • 5244: Fix errors when no internet connection, by @Quetzacoalt91.
  • 5250: extract port number for parameter.yml, by @julienbourdeau.
  • 5267: regenerate parameters.yml even if mode_dev is on, by @julienbourdeau.
  • 5289: Fix creation directory on some servers, by @Shudrum.
  • 5336: Fix check about deleted folder, by @Quetzacoalt91.

PDF

  • 5315: fix address histo in orderinvoice for 1.7, by @julienbourdeau.

Localization

  • 5002: Better spelling of Dutch tab names. Thank you @firstred!
  • 5223: Fix date format in Catalan. Thank you jaumesala!
  • 5266: (Dutch) Update tabs. Thank you @firstred!

See all the PRs merged into the codebase since the last Core Weekly here.

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report!! Also, thank you to the contributors whose PRs haven’t been merged yet! And of course, a big thank you to all those who contribute with tickets on the Forge!

If you want to contribute to PrestaShop with code, please read these pages first:

…and if you do not know how to fix an issue but wish to report it, please read this: How to use the Forge to contribute to PrestaShop. Thank you!

Happy contributin’ everyone!

Do you speak PrestaShop? – March 2016 edition

$
0
0

Here is the latest report to inform you of what has been going on PrestaShop translation project on Crowdin lately (which means this last March).

Updated translations

You’ve been quite a few to report a problem when fetching the language packs: it doesn’t include the latest translations made on Crowdin.

Yes, unfortunately, we’re (still) having issues with our synchronization system. The language packs don’t include the most recent translations from Crowdin, at the moment. We’re currently working on this, as we know it’s important for a lot of merchants. Hopefully, by the end of the month the language packs will be updated to include the most recent translations on Crowdin.

Now let’s get back to our Crowdin project, and the full report of its activity in March:

A few stats

  • 78 contributors joined the project this month, for a total of 2,697 members at the end of March. Welcome to them!
  • 44 members were active on the project this month.
  • A total of 103,856 words have been translated (+138%!) and 60,155 validated.
  • All this in 28 different languages.

That’s quite some work, thank you!

Top contributors

A lot of you are working everyday on Crowdin to have PrestaShop available in many languages, and we can’t thank you enough for your dedication! Here are the most active translators and proofreaders this March.

Top 10 translators in March:

 TranslatorLanguage# Words
1.Vahur Suvi (spottraining)Estonian39,091
2.webdvl (megashopba)Slovak22,092
3.LastRhythmArabic8,108
4.BruniChinese Simp.5,273
5.Peter Schiffer (acetonik)Slovak4,265
6.Norbert Ujszigeti (unorbi)Hungarian3,488
7.Cha (cafetango)Chinese Trad.2,920
8.Martin Barfoed (MartinBarfoed)Danish637
9.Wuk (wuk_aut)German, Austria599
10.Taku (takumi412)Chinese Trad.513

Top 10 proofreaders in March:

 ProofreaderLanguage# Words
1.webdvl (megashopba)Slovak36,954
2.Vahur Suvi (spottraining)Estonian14,713
3.Cha (cafetango)Chinese Trad.3,662
4.Peter Schiffer (acetonik)Slovak4,265
5.Jesús Ruiz (jruiz)Spanish644
6.DaoKakaoRussian212
7.Danoosh Miralayi (danoosh)Persian160
8.Morten Borg (mortenborg)Danish120
9.fariorBulgarian35
10.KoralPolish30

A big applause to them! And welcome to our new top contributors!

Complete translations

Fully translated languages

At the end of March, PrestaShop 1.6.1 was fully available (= 100% translated and validated) in 15 languages. That’s two more languages compare to last month, Persian and Russian. Great! :)

  • Bulgarian
  • Croatian
  • Dutch
  • English
  • French
  • German
  • Italian
  • Lithuanian
  • Norwegian
  • Persian
  • Polish
  • Russian
  • Slovenian
  • Swedish
  • Vietnamese

98-99% translated languages

PrestaShop was also almost fully translated (and/or validated) in these 6 languages:

  • Czech
  • Indonesian
  • Portuguese
  • Portuguese, Brazilian
  • Romanian
  • Slovak
  • Spanish

We’re happy to welcome Romanian in this category! A little bit of work and these languages can be 100% translated and validated too! If you feel like you want to help, join the project!

(Note: since the end of March, Slovak has been fully validated, so things move fast!)

Languages with the best evolution

In comparison with February 2016, the following languages had the best progress in March:

  • German, Austria (+50% to reach 3% translated)
  • Estonian (+21% to reach 91% translated)
  • Slovak (+19% to reach 100% translated - yay!)
  • Romanian (+17% to reach 99% translated - another yay!)
  • Arabic (+15% to reach 55% translated)
  • Chinese simplified (+12% to reach 66% translated)

March 2016 best translation progress

Languages that need (more) proofreaders

A translated string will not be available in PrestaShop as long as it is not validated. For this reason, it’s important we should keep a good level of validated strings vs. translated strings, to make sure everyone benefits from the latest translations!

This month also brought a good news as Slovak has been fully approved! We’re down to 3 languages that require in priority some proofreading at the end of March:

  • Turkish (96% translated vs 0% validated)
  • Ukrainian (99% vs 53%)
  • Galician (49% vs 11%)

March 2016 best translation progress

If you wish to help proofreading what has been translated, please contact me on Crowdin with the language you’d like to proofread. We need your help!

If you haven’t joined us on Crowdin yet, it’s never too late!

If you want to gather your fellow translators to work towards a better harmonization, start a glossary, or anything else, do let us know: we’ll include a word about it in the next monthly report.

Do you have a question, a remark? Don’t hesitate to leave a comment. See you next month!

Here comes PrestaShop 1.7.0.0 alpha 4!

$
0
0

Three weeks ago we released PrestaShop 1.7.0.0 alpha 3. Since then, and with the help of the community, we’ve been working on it to fix the bugs you’ve reported and to keep improving this new version. We’re now releasing PrestaShop 1.7.0.0 alpha 4 version, so we can keep gathering feedback and make sure that the final and stable version will be the best it can be!

Let’s insist on this: this is NOT the stable version of PS 1.7, and IT SHOULD NOT BE USED IN PRODUCTION. Do not create a new store with this alpha version, it is by definition not finished yet.

You SHOULD however install this alpha version as a test store, either on your machine or your web hosting, and play with it – and give us your feedback!

The release date for the stable version is not yet set, so you have a few weeks and beta/RC versions ahead of you!

Test PrestaShop 1.7.0.0 alpha 4

How to give feedback

Have you found a bug? A curious behavior? An unexpected reaction? Let us know! Create a ticket on the 1.7 Forge project, and give us as much details as possible!

Please note that we are not looking for feedback on the overall technical or design choices: Symfony2, the new theming system, the back office design and other global aspects of 1.7 are pretty much set in stone. However, do let us know about bugs or possible improvements!

Updates since alpha 3

You’ll find more details about the previous alpha 3 in this previous article.

Here are the main improvements this new alpha version brings:

Front office

  • Fix invoice address not being asked in checkout #5305 by @jtabet
  • Checkout - displays voucher value in the shopping cart #5312 by @Shine-neko
  • Fix warnings in the quick-view #5317 by @Shine-neko
  • Fix Prices drop, Best sales & New products display #5351 by @maximebiloe
  • Display tax in shopping cart by default #5353 by @maximebiloe
  • Display product image in confirmation order #5361 by @Shine-neko
  • Fix checkout behavior when simplified URLs are disabled #5376 by @maximebiloe
  • Form error messages are now displayed in the website language (only English for now), instead of browser language #5399 by @maximebiloe
  • Improved the legal compliancy #5394, #5445. Thank you @paeddl!
  • Fix shipping tax when proportionate is enabled in AEU #5325 by @maximebiloe

Back office

  • TinyMCE improvements on style and loading perfs #5420 by @tchauviere
  • Added a features to be able to remove birthdate in subscription form #5343. Thank you @firstred!

Product page

  • The bottom bar for the product page has been redesigned #5391 by @nihco2
  • Introduced a Category management system on Page product #5293, #5323, and #5401 by @mickaelandrieu
  • Introduced tooltips and improved wording #5424 by @julienbourdeau

Modules page

  • The ‘enable/disable on mobile’ action is back! #5319 by @Quetzacoalt91
  • Improve the loading time of the module catalog #5368 by @Quetzacoalt91
  • Modules to be configured are now displaying #5395 by @Quetzacoalt91
  • Improved Module class to handle more potential issues #5397 by @Quetzacoalt91
  • Fix zip module installation for complex modules #5380 by @mickaelandrieu
  • Improved list display #5371. Thank you @ShepherdV8!
  • Modules scoring is now displayed #5405 by @Quetzacoalt91

Core

  • Added PHP 7 tests on Travis CI #5439. Thank you @firstred!
  • Introduced a new dump function from Symfony VarDumper component #5381 by @Shine-neko
  • Disallow indexing of admin pages #5357. Thank you @firstred!
  • Updated SwiftMailer to the latest version #5233. Thank you @firstred!

This alpha 4 version was made possible by the hard work of the PrestaShop Core Team, with additional commits by the following contributors: @firstred (responsible for no less than 8 contributions already accepted the last 3 weeks, thank you!), @paeddl and @ShepherdV8. Thank you!

What’s (still) in progress

Remember that this is alpha 4: a lot of things are not ready yet, or are ready but not yet available.

We tried to gather the most important ones, so you have a clear idea of what still needs to be implemented. All of this will eventually be fixed for the stable version – and you can help with pull-requests on GitHub, and feedback of your tests!

Core

  • If your web hosting uses PHP-FPM, some links (and images) will not work.
  • Multistore & Advanced Stock Management aren’t yet connected to the Create a Product Page.
  • The header and navigation can vary (slightly) between pages.
  • Employees permissions are not yet suited for the new navigation in place
  • If a problem occurs while uploading a theme, we may not be able to tell you why currently :) In effect, errors and warnings are not fully set yet. And in any case, your 1.5-1.6 theme will NOT work with the new theme system.

Front office

  • Some links may be broken during your navigation on the shop

Back office

  • Some images are broken for now, some buttons and tab could behave in a weird way, and you might stumble on other weird artefacts. We know about this, and they will all be fixed in time.
  • We’re still working on the responsiveness of the back-office, and 13” inches screens could particularly be affected.

Modules page

  • We’re improving the modules discovery page: better sorting, more information, reworked categories, etc.

Content

  • Interface copywriting is not final yet. Some parts need to be written, others are waiting for a rewrite and others are in proofreading.
  • Default products are still the ones used in version 1.6. Version 1.7 should have a brand new set of products.
  • Translations are on hold for now while we’re working on improving the system: the interface is only in English for now.

Documentation

  • Contextual help still displays 1.6 documentation as we’re updating it to 1.7. Expect it to be final during our RC period.
  • Technical documentation for modules & themes should follow the same timeline.

Final note!

So cheers for the second public glance at the brand new 1.7, made with <3 by our team and our wonderful Community. It’s not fully baked yet, but we’re very proud of the work done.

Test PrestaShop 1.7.0.0 alpha 4

We’ll closely monitor your feedback and are eager to hear from you!

Happy testing!

PrestaShop theme documentation first draft is out

$
0
0

With PrestaShop 1.7 we completely rewrote the way shop theme works. Along with these changes, we intended to publish a full documentation that would help you create an amazing and creative new theme or adapt your theme to PrestaShop 1.7.

Throughout the development process we wrote many articles to keep you up-to-date with our progresses on the StarterTheme. We talked about the introduction of new features and also deprecation/removal of existing features.

With the Starter Theme, we introduce many new ways of developing themes, we reorganized the whole directory, moved templates, changed module override folders and deleted assets. Hence there is no backward-compatibility with PrestaShop 1.5/1.6 themes.

Obviously we had to provide documentation since all you already knew about theme development with prestashop might have changed. Don’t worry, there is nothing crazy about it, it still relies on Smarty and (pretty much) the same front controller list. After 15 minutes you will feel at home again.

Read PrestaShop Theme Documentation

The state of the documentation

We wanted to publish the documentation as soon as possible, so today we made the GitHub repository public. We hope you’ll read it through and tell us what’s missing and what else you’d like to find in it.

Please keep in mind that the content is far from being finished (is a documentation ever finished?).

As of today, the documentation is a collection of text files, without any rendering system (see below).

It includes JSON files, which hold an example of the data passed to the templates like: $customer, $page, $breadcrumb, $cart… These data will be irrevocable when PrestaShop 1.7 final is released, and they will be maintained during the whole 1.7 life cycle. Trust these datasets.

Adopting Sphynx and reStructuredText

We decided to move from Atlassian Confluence to Sphynx (at least for the developer documentation), and use reStructuredText files, available on our GitHub repository.

reStructuredText is a lightweight markup language designed to be both (a) processable by documentation-processing software such as Docutils, and (b) easily readable by human programmers. – Wikipedia)

We now have a bunch of nice reStructuredText files, so we can enjoy the power of Git for our documentation: compared to the Confluence system, it’s much more flexible.

Sphinx converts reStructuredText files into HTML websites and other formats including PDF, EPub and man.

reStructuredText is extensible, and Sphinx exploits its extensible nature through a number of extensions – for autogenerating documentation from source code, writing mathematical notation or highlighting source code, etc. – Wikipedia

Then, of course, anyone can contribute through pull-requests on the GitHub repository. That is another big advantage compare to Confluence.

Finally, this stack is also used for Symfony documentation, so if you’re already a Symfony contributor: there is nothing new to learn. Easier for everybody, as we’re using Symfony in PrestaShop 1.7.

How to contribute

Contribution guidelines can be easily summarized: Use the power of GitHub!

The documentation is fully managed on GitHub (exactly like this blog) so don’t hesitate to open an issue or a pull-request.

If you want more details about something

Open an issue here and detail as much as possible what you are trying to do. You can also join us on Gitter.

If you want to edit the doc

If you want to modify content or fix a typo, please do it through a pull-request. We will soon publish the guidelines for writing the doc :)

Don’t use “workarounds”

If you are trying to do something in particular with your theme or module, please, please, please don’t try to find a workaround on your own! Tell us about it on Gitter (ping us) or open a GitHub issue where we can have a conversation about it. You are probably not the only one in the community who need this feature or this change of behavior.

Enjoy!


How we reorganized the main menu in PrestaShop 1.7

$
0
0

Did you think everything had been said about PrestaShop 1.7 version? In our quest towards a simpler interface, the main menu was reorganized, mostly to make it easier for you to navigate in PrestaShop. So here are a few things you should be aware of.

In short:

  • New sections were created
  • A new wording has been introduced
  • The location of some pages was changed
  • Other pages were gathered as tabs of a main page

The method behind the new menu

Here’s our recipe to come up with this updated menu:

  • A game of card-sorting with the User Club
  • A little bit of intuition
  • A pinch of logic
  • and, well, some of our secret sauce :)

We hope you’ll like it!

More seriously, the aim of the reorganization was simply to make the navigation easier in the software. We haven’t reduced the menu, it still has the same number of first-level options, however we did reorder it to what we hope is a logical way of navigating and working with your shop.

So we conducted a card-sorting experience with the help of the User Club members: 113 users gave us their feedback on which pages they were using the most in PrestaShop. It turns out “Orders”, “Products” and “Customers” were the big winners. Who’d have thought?

From there, we tried to rearrange the sidebar to reflect both what merchants would use the most, while injecting some logic in all this. For instance, to manage your contact information, you previously had to go on both the “Store Contacts” and the “Contacts” page. Hence, two different sections for a single action. Now it’s together in one place!

So hopefully you’ll see what we tried to do here: make it easier to find what you want to do. And when I say we, the whole team took part in this debate (for yes, there were debates!): UX designers, content and product managers too.

Introducing a new wording

In addition to actually reorganizing the menu, we thought some menus deserved a better labeling. This is why some names have changed to be more explicit or easier to understand for first-time users. So new concept were introduced as well. Here are the details:

Renaming

1.61.7Comment
ManufacturersBrandsWe believe merchants would rather advertise brands on their shops, instead of manufacturers; and from what we’ve seen, merchants were using the “manufacturer” entity more in the sense of “brands”.
AttachmentsFilesAttachments aren’t always well understood. With a renaming and proper indications within the software, we hope this is now clearer (= adding files to your product page).
Price RulesDiscountsWe’re not really getting rid of price “Rules” as you’ll still find “Catalog Price Rules” and “Cart Rules”, but we wanted to give it a name easier to grasp for first-time users.
ThemesTheme & LogoIt’s not much, but the way to change the logo wasn’t easy to find, and it’s something merchants want to do as soon as they start their shop. Now it should be even quicker to customize it!
CMSPagesWell… We’re not exactly WordPress, or Drupal — and we don’t plan to be. What this feature allows you to do is to create pages for your static content (About, T&C, etc.). So here you go, that’s where you can create and manage your pages.
EmployeesTeamIf you work with employees, then you’re a team :) A little renaming to give it a friendlier touch.
CSV ImportImportGood news! In version 1.7 you can import more formats - no need to be CSV-specific anymore!

New labels or menus

Design

We’re aware that it’s not very easy to know where to go when you want to change the look of your shop. In previous versions, it was split between various menus in various sections. In PrestaShop 1.7, we’ve created a “Design” section, gathering the main front office sections. From now on, this is where you’ll find the theme settings, the pages (“CMS”), the modules’ positions page, and the image settings. All in one handy place, at last!

International

We haven’t invented anything here, we simply tried to rationalize the “Localization” menu, by reorganizing it, and giving it this new name, “International”. Because that’s what it is mostly about: you want to grow your business internationally, and PrestaShop helps you reach that goal. New markets, with new languages, new currencies and taxes, customized translations, etc.

Traffic

We created this new section to gather everything you need to manage in order to bring more visitor traffic to your online store. It means SEO management, but it also means how you deal with specific search engines, as well as the referral programs which you may have. These pages aren’t new, but we decided to put them all together in order to improve your workflow.

Now that you know most of what’s strictly “new”, let’s dive into how it’s all been reorganized — in other words, the “why” of these evolutions.

Reorganization

Introducing tabs

One of ideas behind this reorganization was to lighten the menu, at least its first level. To do this, and in line with the new 1.7 design, we’ve introduced tabs within various pages. This way we could gather related topics in one page only:

Main sections: Sell, Improve, Configure

The most visible change to the back office menu is probably that we introduced three main sections, thus dividing the menu into three logical parts, based on how often merchants use each menu (as per our research). These sections are “Sell”, “Improve”, and “Configure”.

Sell

It’s all about your day-to-day activity. Orders, customers, catalog, etc. This section presents the essence of your business, where you go each day to get your business going.

Submenus: Orders, Catalog, Customers, Customers Service, Stats.

Improve

Here you will find everything to customize your shop and take your business further. Set up the look of your front office, adapt your payment methods to your target markets, expand internationally or enhance your shop with new modules and features!

Submenus: Modules, Design, Shipping, Payment, International

Configure

It is divided in two submenus. The first one is your shop parameters. You’ll find here all the settings you need to configure when you launch your activity. Once you made your initial choices, you won’t go there very often. The second menu can be seen as the technical section, with more advanced settings that aren’t used often either.

Submenus: Shop Parameters, Advanced Parameters

Now let’s dive into each of these three sections to see what’s underneath.

New positions and subsections

// SELL //

Orders

Orders now come first, as it’s THE most important concern of your daily activity.

RemovedMerchandise ReturnsNow in “Customer Services” (see below).
 StatusesNow in “Shop Parameters” > “Order Settings”, as it’s not related to your daily operations but rather to the global settings for your orders.
 Order MessagesNow in “Customer Service”. Order messages are pre-written messages you can send to your customers via the “Order” page. We thought it made sense to have it under the “Customer Service” section, where you can manage your communication with your clientele.
AddedShopping CartsPreviously in “Customers”, is now in “Orders”. We think it’s key to monitor your abandoned carts, and moving it to this major section made sense. It’s not yet an order, but could soon become one, so it deserves all this attention.
Submenus Orders, Invoices, Credit Slip, Delivery Slips, Shopping Carts

Catalog

This is where the first pages using tabs were introduced as we grouped several pages here. We added or removed others pages to make sure this is the one place where you go to manage your offer and what is available on your shop.

RemovedTagsWent to the new “Search” pages as they are used to guide your customers through their product search on your shop.
AddedPrice Rules (now Discounts)Has been moved in this section as pricing is as important as your products in defining your catalog and adjusting your offer.
MergedProduct Attributes + Product Features= Attributes & Features
 Manufacturers + Suppliers= Brands & Suppliers
Submenus Products, Categories, Monitoring, Attributes & Features, Brands & Suppliers, Files, Price Rules
Customers

This menu has been stripped down to keep the essential: your listing of customers, and their addresses. Everything else, which is considered as settings (groups, titles, etc.), is now in more relevant sections.

RemovedGroupsNow to be found as a tab in “Shop Parameters” > “Customers”.
 Shopping CartsNow in “Orders”, as already mentioned.
 Customer ServiceHas been promoted as a first-level menu, to make it easier to follow-up with your customers.
 ContactsHas been moved to “Shop Parameters”: once it’s filled-in, you don’t often use this page.
 TitlesNow in “Shop Parameters” > “Customers”.
Submenus Customer Settings, Addresses, Outstanding (in B2B mode)

Customer Service

With more visibility, the “Customer Service” menu now includes the previously separate “Customer Service” page as you know it, the “Order Messages” page and the “Merchandise Returns” page.

This is where you can manage interactions with your customers once an order has been placed.

And finally, the Stats menu hasn’t changed a bit: same page, same position.

// IMPROVE //

Modules

You’re aware we’ve revamped the Modules page. We also stripped down this menu to its bare essence:

RemovedPositionsNow in “Design”, as part of the improved way of customizing your front office.
 PaymentIn the “Improve” section, so that it is treated on equal footing with “Shipping”.
SubmenusModules & ServicesRedesigned, as you’ve seen in this previous article.
 Modules CatalogWhich now only displays modules from Addons Marketplace (and no longer themes, which you will find in “Theme Catalog”).

Design

I’m not going to dwell much on this one, the why of this section has been explained above.

  • Submenus: Theme & Logo, Theme Catalog, Pages, Positions, Image Settings
Shipping

Stays the same, we kinda liked it this way :)

  • Submenus: Carrier, Preferences

Payment

The former “Payment” page has been divided into two new pages: “Payments Methods” and “Preferences”. It has been organized to look like the Shipping page.

In the Payment Methods page, you’ll find all the payment methods available in your shop, active or inactive, while the Preferences page (formerly at the bottom of the Payment page, thus less visible), allows you to decide which country or which currency to support for each payment method. Nothing new here, just a quick reorganization.

  • Submenus: Payment Methods, Preferences
International

You can view it as the former “Localization” menu, where pages have been merged to give a better overview. Nothing new either, only a few merges and an addition.

AddedGeolocationPreviously in “Preferences”, the “Geolocation” page is now a tab of the “Localization” page. It seemed logical, as it’s where you define in which countries your shop is accessible (or not).
MergedStates + Zones + Countries= “Locations”. We grouped under one page everything related to the shipping zone and locations.
 Taxes + Tax Rules= became two tabs of a general “Taxes” page.
Submenus Localization, Locations, Taxes, Translations

// CONFIGURE //

The Configure section is mostly a reorganization of the former “Preferences”, “Advanced Parameters” and “Administration” tabs.

Shop Parameters

This section is about settings that will impact how your shop works. Most of these pages were previously found under the “Preferences” menu.

RemovedGeolocationMoved to “International”.
AddedStatusesNow in “Order Settings”.
 GroupsNow in “Customer Settings”.
 TitlesAlso in “Customer Settings”.
 Tagsin “Search”.
MergedGeneral + Maintenance= General
Submenus General, Order Settings, Product Settings, Customer Settings, Contact, Traffic, Search

Advanced Parameters

Here you’ll find advanced and technical settings. Most of these pages are for one-time use: once you’ve set everything up, you’re not supposed to go there very often, but merely for checkups or a few updates.

AddedAdministrationFormerly a first level tab, it’s been moved here. The “Employees” page was extracted and moved to the same level (as the “Team” page).
MergedEmployees + Profiles + Permissions= Team. Everything to manage your employees (at least, in PrestaShop :)
 SQL Manager + DB Backup= Database
Submenus Information, Performance, Administration, E-mail, Import, Team, Database, Logs, Webservice

That’s it, you know all about it. Let us know what you think! :) We’re still in the alpha phase for PrestaShop 1.7, so this new navigation isn’t fully implemented yet if you’re testing it (yes, we need you to test it!). But most of it is already there!

PrestaShop Core Weekly - Weeks 15-16-17

$
0
0

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase during the last few weeks, from Monday 11th of April to Sunday 1st of May 2016.

Milestones

Since the last Core Weekly Report, we released alpha 4 of PrestaShop 1.7. Give us your feedback!

We also recently released a maintenance version for the 1.6 branch, version 1.6.1.5.

Do you live near Paris? Do you want to come test-drive the design of PS 1.7? Let us know!

The team is hard at work on PrestaShop 1.7, the next major version of the most complete e-commerce software solution there is.
You can find an up-to-date thread about it in the forum.
The 1.7 Project FAQ is always available here: http://build.prestashop.com/news/prestashop-1-7-faq/.

Do you want to encourage us? Give us a star on GitHub! :)

And, indeed, she said “yes”! (I did too) :)

Code changes in branch 1.6.1.x

Here the pull-requests that were merged on the ‘1.6.1.x’ branch since the last Core Weekly Report!

Tests

  • 5440: Fix PHP 7 tests. Thank you @firstred!

Code changes in branch develop (for version 1.7.0.0)

Let’s review the merged pull-requests on the ‘develop’ branch since the last Core Weekly Report!

Front office (including the default theme, named “Classic” for now, based upon the Starter Theme)

  • 5210: Empty cart template redesign, by @nicoh2.
  • 5245: Fix translation in OrderPresenter. Thank you @fojtcz!
  • 5305: Fix invoice address not being asked in checkout, by @jtabet.
  • 5312: Checkout - displays more details, by @Shine-neko.
  • 5335: Improve page cms style, by @nicoh2.
  • 5346: Add display after carrier list hook. Thank you @firstred!
  • 5351: Fix Prices drop, Best sales & New products display, by @maximebiloe.
  • 5361: Display product image in confirmation order, by @Shine-neko.
  • 5362: Fix hook location for AEU, by @maximebiloe.
  • 5363: admin header - Add missing components, by @nicoh2.
  • 5365: Add anchor to email subscription, by @julienbourdeau.
  • 5366: Extract product add to cart for ajax refresh, by @maximebiloe.
  • 5372: Fix hook called twice, by @maximebiloe.
  • 5387: update required file list for theme, by @julienbourdeau.
  • 5394: ps_legalcompliance, Added new hook for tax-label in listing, by @paeddl.
  • 5399: Fix mixed up language in form feedbacks, by @maximebiloe.
  • 5402: Revert change on “display_tax_label” forced to true, by @tchauviere.
  • 5432: Fix products total amount in order details, by @Quetzacoalt91.
  • 5433: Added new hooks for AEU, by @paeddl.
  • 5445: ps_legalcompliance layout, by @paeddl.
  • 5447: Classic: Remove slashed for self-closing tags, by @julienbourdeau.
  • 5450: Categories menu integration, by @nicoh2.
  • 5451: added delete buttons for brand & related products options, by @mickaelandrieu.
  • 5461: Fix DOM not closed, by @maximebiloe.
  • 5464: Clean up form validation, by @julienbourdeau.
  • 5466: Fix amount format in order confirmation, by @maximebiloe.
  • 5468: Fix some warnings on search result, by @maximebiloe.
  • 5474: Product Image Cover and Layer Hover. Thank you @ShepherdV8!
  • 5485: CSS-class when showing tax-label; global Template-Var, by @paeddl.
  • 5488: Improved some webpack config, by @julienbourdeau.
  • 5489: Fix error on Best sales page. Thank you @fojtcz!
  • 5490: Fix variable name in product-prices.tpl. Thank you @fojtcz!
  • 5506: Fix some element attributes. Thank you @fojtcz!

Back office

  • 5220: update link preview in js when product change publish, by @cocoweb94.
  • 5255: Module Page - Improved Ajax Loading on catalog, by @tchauviere.
  • 5263: Fix some tabs names, by @Shudrum.
  • 5276: module.js fix an issue on reset category filter, by @tchauviere.
  • 5324: Fix module sort by name, by @maximebiloe.
  • 5350: Fix module card when spinner displayed, by @Quetzacoalt91.
  • 5354: improvement on adding ip on maintenance, by @maximebiloe.
  • 5357: Disallow robots. Thank you @firstred!
  • 5370: Wording update for module part, by @maximebiloe.
  • 5371: Module page enhance list view display mode. Thank you @ShepherdV8!
  • 5375: Fix theme preview, by @maximebiloe.
  • 5380: fix module installation by zip on complex modules, by @mickaelandrieu.
  • 5391: tab bar redesign, by @nicoh2.
  • 5401: added category default selection on category tree, by @mickaelandrieu.
  • 5405: Add scoring on the module cards in the catalog, by @Quetzacoalt91.
  • 5420: TinyMCE improvements on style and loading perfs, by @tchauviere.
  • 5423: Improve product page header, by @nicoh2.
  • 5424: Add tooltips to admin product page, by @julienbourdeau.
  • 5426: Change placeholder search module page, by @julienbourdeau.
  • 5436: Update product page layout in the BO, by @maximebiloe.
  • 5437: product-header - Change placeholder text, by @julienbourdeau.
  • 5438: add a product category on the fly, by @mickaelandrieu.
  • 5446: Update “Exit to addons” module card, by @Quetzacoalt91.
  • 5448: product-header - Fix tooltip width, by @nicoh2.
  • 5452: Small fixes related to the design of the module page, by @Quetzacoalt91.
  • 5459: Add ids on ‘Add a brand’ and ‘Add a related product’ buttons. Thank you @mgui95!
  • 5463: Add UI-kit on dropdowns in modules page, by @Quetzacoalt91.
  • 5475: Fix theme preview. Thank you @fojtcz!
  • 5479: added missing delete confirmation poppin on product page form, by @mickaelandrieu.

Core

  • 5106: Improve configuration load & get performances, by @jocel1.
  • 5233: Update SwiftMailer. Thank you @firstred!
  • 5319: Bring back “enable / disable on mobile” action, by @Quetzacoalt91.
  • 5325: Fix shipping tax when proportionate is enabled in AEU, by @maximebiloe.
  • 5343: Toggle birthdate field with one click. Thank you @firstred!
  • 5358: remove useless “;” after a try-catch. Thank you @PifyZ!
  • 5368: Add some perfs in the module catalog / repository, by @Quetzacoalt91.
  • 5376: Force POST method for payment options, by @maximebiloe.
  • 5381: Introduce dump function, by @Shine-neko.
  • 5393: Fix modules sent to twig, by @Quetzacoalt91.
  • 5395: Fix filters on installed modules, by @Quetzacoalt91.
  • 5397: Move require of module class to handle more potential issues, by @Quetzacoalt91.
  • 5403: Add logger on module class checks, by @Quetzacoalt91.
  • 5413: ModuleRepository must keep in cache a broken module too, by @Quetzacoalt91.
  • 5415: Module page tooltips and theme modules, by @Quetzacoalt91.
  • 5431: Fix Smarty SQL Cache. Thank you @firstred!
  • 5435: hide available date if 0000-00-00, by @julienbourdeau.
  • 5453: Upgrade render syntax, by @Shine-neko.
  • 5465: Remove old PS1.4 admin files, by @julienbourdeau.
  • 5470: remove functions.php. Thank you @fojtcz!
  • 5478: Re added global getPath() admin function into Tools and display it as deprecated to avoid crashes, by @tchauviere.
  • 5491: Adding missing method to make method HookExtension::renderHooksArray work. Thank you @FabienSerny!
  • 5494: Remove useless Addons filter on modules list. Thank you @FabienSerny!
  • 5502: Improve DisplayOverrideTemplate hook to get more details, by @maximebiloe.

Tests

  • 5297: speed up php parse error checker & precompute travis composer.lock, by @jocel1.
  • 5386: upgrade travis to trusty to fix google chrome version issue, by @jocel1.
  • 5388: Make tests less dependants from addons website, by @mickaelandrieu.
  • 5396: Improved the tests architecture, by @mickaelandrieu.
  • 5439: Enable PHP 7 tests (failure = allowed). Thank you @firstred!
  • 5441: Fix PHP 7 unit tests. Thank you @firstred!
  • 5477: Fix travis composer, by @Quetzacoalt91.
  • 5481: Separate two tests to avoid timeout, by @Quetzacoalt91.

Installer

  • 5267: regenerate parameters.yml even if mode_dev is on, by @julienbourdeau.
  • 5353: Display tax in shopping cart by default, by @maximebiloe.
  • 5400: fix default tax display value, by @jocel1.

Localization

  • 5266: (Dutch) Update tabs. Thank you @firstred!

See all the PRs merged into the codebase since the last Core Weekly here.

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @FabienSerny, @firstred, @fojtcz, @mgui95, @PifyZ, and @ShepherdV8! Also, thank you to the contributors whose PRs haven’t been merged yet! And of course, a big thank you to all those who contribute with tickets on the Forge!

If you want to contribute to PrestaShop with code, please read these pages first:

…and if you do not know how to fix an issue but wish to report it, please read this: How to use the Forge to contribute to PrestaShop. Thank you!

Happy contributin’ everyone!

Evolution of the PrestaShop Coding Standards

$
0
0

Working on an open source project as massive as the PrestaShop codebase, a few ground rules have long been established in order to ease the participation of developers, be they from the PrestaShop Core team or the Community at large.

For long, we used our own coding standards. We then switched to PSR-2 last year.

Because we want to have an always better codebase, clearer, easier to read and to maintain, we have decided to follow some more established standards for the languages used in PrestaShop.

This means that we are updating our current standards requirements for languages that already have some, or selecting a standard for the languages which did not have any in use yet. This means that we now have clear standards and norms for PHP, JavaScript, HTML, CSS, pull requests and commits.

We already see your face, don’t panic :smile: These standards are pretty common and natural.

Below, you’ll find a little overview of these standards and some examples of the most significant points. Do not hesitate to look at our documentation to see all the details.

At the same time, to make it easier for you to contribute, we also updated our commit and pull-requests norms. Read all about it below.

Coding standards

PHP

As you already know if you have read this article, we chose to integrate the Symfony framework into PrestaShop. So, what’s more natural than to follow their coding standards? It comes as a complement of the PSR standards (PSR-0, PSR-1, PSR-2 and PSR-4).

Some noteworthy rules:

  • Use camelCase, not_underscores, for variable names, function names, method names, and arguments names.
  • Yoda conditions you should use.
  • Add a comma after each array item in a multi-line array, even after the last one.
<?php$defaultOptions=array('some_default'=>'values','another_default'=>'more values',);if(true===isset($defaultOptions['some_default'])){return;}

More details and a complete example can be found in the Symfony documentation.

JavaScript

For our JavaScript code, we chose to follow the well-detailed and documented Airbnb JavaScript Style Guide. Code should be written in ECMAScript 6 and Babel will transpile it into ECMAScript 5 for a wider browser compatibility.

Some noteworthy rules:

  • Always use semicolons at the end of an instruction.
  • Use soft tabulations with two spaces to indent.
  • Use braces with all multi-line blocks.
(function(){if(test){returnfalse;}}());

Do not hesitate to look at their complete documentation.

CSS & HTML

Regarding the CSS and HTML codebase, because we have integrated Bootstrap 4 both in the back office and front office, we have decided to follow their coding standards, maintained by @mdo.

When you are writing HTML code, if your line is longer than 120 characters, we have chosen to do a line break after each attributes with an indentation. For example, it will look like this:

<imgclass="test"id="..."name="..."data="..."src="..."title="..."alt="..."role="...">

Some noteworthy rules:

  • HTML
    • Use soft tabulations with two spaces to indent.
    • Avoid superfluous HTML markup.
    • No more self-closing tag.
  • CSS
    • Use soft tabulations with two spaces to indent.
    • When grouping selectors, keep individual selectors to a single line.
    • End all declarations with a semicolon, even the last one.
<imgclass="test"src="...">
img,a,input[type="text"]{display:block;padding:15px;margin-bottom:15px;background-color:rgba(0,0,0,.5);box-shadow:01px2px#ccc,inset01px0#fff;}

Smarty / Twig

PrestaShop 1.7 uses both the Smarty and Twig template engine. Since those are mostly used to generate HTML, we expect the Smarty/Twig code to comply with the HTML standards above – as well as the one used by SensioLabs for Twig.

Some noteworthy rules:

  • Use soft tabulations with two spaces to indent.
  • Use single quotes to surround strings.
  • Use snake case (underscores) to name your blocks.
{% block my_block_name %}
   {% set foo = 'foo' %}
{% endblock %}

Commits & Pull-requests

Commits

In the past, we used to have only one commit by pull request. This was a bad habit. We now require contributors to make atomic commits, so you will surely have more than one commit in a single pull request. This will be helpful to review, cherry-pick or revert (we hope to never have to do that :wink: ) the changes.

What’s an atomic commit? It means that the commit’s purpose is one, and only one, complete fix or change. Typically, ask yourself if what you are doing is one or several tasks. Do not hesitate to use “git add -p …” (details here) if you have made several changes in the same file but not all those changes are meant to be in the current commit.

When you are modifying CSS and/or JavaScript files, we invite you to make a separate commit for the compiled files. If you want to know more about compiling assets, you can look at our documentation.

The commit name should also give an idea of the context or of the file that is being changed. The more details, the better! The commit name should be as unique and recognizable as your commit itself.

To make the commits context easier to read and hassle-free, we have chosen to prefix them with two letters depending on the modification scope:

CodeScope
FOif the changes impact the front office
BOif the changes impact the back office
INif the changes impact the installer
WSif the changes impact the web service
COif the changes impact the core
TEif the changes impact the tests

Examples:

  • CO: Retrieve all required data for notifications
  • BO: JS for notifications in new BO theme
  • FO: Fix voucher layout in cart
  • TE: PHP 7 is now mandatory

Pull Requests

Now that you have made atomic commits, you surely have a lot of commits for one pull request. A pull request answers to a given issue. Do not ever make a single pull request for many purposes. Do not hesitate to split your big commit into several subprojects. It will be easier and quicker to review.

As all your commits messages are well-formated, just make a summary of your pull request’s purpose in its GitHub title. A summary does not mean it can not be explicit. Please describe what your pull request does in details (avoid “Fix product page” or “Category page improvement”). Then, just fill the PR template table to answer some questions which will help the team make a decision faster.

Please note that all the pull requests must follow those guidelines. If the commit messages are not well-formatted, the pull request’s title is not correct, or the table is not properly filled, we will not be able to accept your pull request.

Find more information and all the details on our documentation.

FAQ

When will these standards be mandatory?

You can (and should :wink:) already use these standards. We will not reject your contributions for now if you do not respect them, there will be a transitional phase. We will ask you to respect these standards from 1st July, 2016 onward.

You don’t have to rewrite all your code! We simply ask you to respect these standards for your next contributions.

Don’t worry, during that transition phase, we will gladly help you and indicate you what you could be improved next time you contribute.

In which cases do I have to use those standards?

All the new files and new contributions will have to respect them. You will not have to change the entire file to the new standards, but you must not submit new contributions with old standards.

You are now ready to contribute and to help us to improve PrestaShop. If you have any questions about a pull request you want to make, or need help to contribute, do not hesitate to contact us on our dedicated Gitter channel.

How can I use these in my IDE of choice?

We created an EditorConfig file to help you! It is located at the root of the PrestaShop repository: you can download it here.

It’s particularly useful when having to handle different tab sizes depending on the file type.

Several IDEs (WebStorm, BBEdit, etc.) have native support for EditorConfig files. Most other IDEs (Eclipse, Atom, SublimeText, PhpStorm, etc.) can support EditorConfig files through a free plugin. See here for more information.

PrestaShop Core Weekly - Week 18

$
0
0

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase during the previous week, from Monday 2nd to Sunday 8th of May 2016.

Milestones

The work being done on version 1.7.0.0 is still going strong (even though last week was a short one in France, due to Ascension Day on Thursday).

Want to help things go faster? There are several ways:

You can find an up-to-date thread about the 1.7 development in the forum.
The 1.7 Project FAQ is always available here: http://build.prestashop.com/news/prestashop-1-7-faq/.

Do you live near Paris? Do you want to come test-drive the design of PS 1.7? Let us know!

Code changes in branch develop (for version 1.7.0.0)

Let’s review the merged pull-requests on the ‘develop’ branch since the last Core Weekly Report!

Front office (including the default theme, named “Classic” for now, based upon the Starter Theme)

  • 5462: Fix voucher layout in cart, by @maximebiloe.
  • 5507: Fix undefined label when using facet filters, by @maximebiloe.
  • 5513: Remove backslash from BR tag in formatted address. Thank you @fojtcz!
  • 5515: Hide H1 if page has no title. Thank you @fojtcz!
  • 5517: ps_legalcompliance BOOM-198 : hook for unit_price added, by @paeddl.

Back office

  • 5215: Enable debug mode from BO. Thank you @firstred!
  • 5486: Add placeholder for product summary, by @maximebiloe.
  • 5492: precise delivery time, by @paeddl.
  • 5496: Module page remove notifications to install, by @Quetzacoalt91.
  • 5520: Update node-sass version, by @maximebiloe.
  • 5526: improved performances of renderfield action, by @mickaelandrieu.

Core

  • 5389: Simplified configuration, by @Shine-neko.
  • 5518: Ensure () after new Class;, by @julienbourdeau.
  • 5524: Fix Exception-ception, by @Quetzacoalt91.

Tests

  • 5519: PHP 7 is no longer an option, by @Shudrum.

Installer

  • 5449: Installer optimizations, by @Shudrum.

See all the PRs merged into the codebase since the last Core Weekly here.

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @firstred, and @fojtcz! Also, thank you to the contributors whose PRs haven’t been merged yet! And of course, a big thank you to all those who contribute with tickets on the Forge!

If you want to contribute to PrestaShop with code, please read these pages first:

…and if you do not know how to fix an issue but wish to report it, please read this: How to use the Forge to contribute to PrestaShop. Thank you!

Happy contributin’ everyone!

Do you speak PrestaShop? – April 2016 edition

$
0
0

Here is the latest report to inform you of what has been going on PrestaShop translation project on Crowdin lately (which means this last April).

Some news first

Updated translations: it happened!

Good news! Last week we updated the 1.6 language packs, so they now include the newest translations from Crowdin. This means that when you update the languages in your shop, you can now benefit from some recent translations from Crowdin. That’s big news for Estonian, Greek, Slovak, and Vietnamese for instance, as they made some huge progress recently.

The not-so-good news is that the automatic update process is still not working… For now we’ll update the language packs manually, so the updates won’t be regular for a while. We’re fully aware that this NOT ideal, but our resources are dedicated to the development of a whole new system, working for both PrestaShop 1.6 and 1.7 versions. It should be implemented once the 1.7 strings are imported to Crowdin, so expect more news about this in the coming months.

What about that 1.6.1.4 folder I saw?

You might have noticed a 1.6.1.4 folder for some time… it was added when we updated the translation packs. It turned out the folder wasn’t complete (admin file was missing for instance, which is a big part of the project) and in the end it did not bring much to the project: all the 1.6.1.4 and 1.6.1.5 strings are already in the “next-version” folder. For this reason, the 1.6.1.4 folder is no longer. You can keep on working as usual in the “next-version” folder!

Translator guide

We’re currently working on a translator guide so that we can:

  • better welcome new translators to the project
  • answer any question you may have when translating PrestaShop

It will soon be available as a downloadable PDF and a dedicated page on Build. In the meantime, if you want to help us in giving you the right information, we need your feedback:

Answer our translator survey

Thank you!

Now let’s get back to our Crowdin project, and the full report of its activity in April:

A few stats

  • 60 contributors joined the project this month, for a total of 2,757 members at the end of April. Welcome to them!
  • 42 members were active on the project this month.
  • A total of 21,958 words have been translated and 13,067 validated.
  • All this in 28 different languages.

That’s quite some work, thank you!

Top contributors

A lot of you are working everyday on Crowdin to have PrestaShop available in many languages, and we can’t thank you enough for your dedication! Here are the most active translators and proofreaders this April.

Top 10 translators in April:

 TranslatorLanguage# Words
1.rebi8akiGreek9,962
2.webdvl (megashopba)Slovak2,980
3.Peter Schiffer (acetonik)Slovak1,987
4.Jesús Ruiz (jruiz)Spanish1,167
5.Andrus (Askeldaja)Estonian1,085
6.Дмитрий Жашкевич (SupportPS)Ukrainian893
7.Tomáš Prskavec (shawik)Czech695
8.Janne Wikman (vetoveljet)Finnish405
9.Jorge Vargas (jorgevrgs)Spanish, Colombia403
10.N1n7aXIII (ninja_xiii)Thai346

Top 10 proofreaders in April:

 ProofreaderLanguage# Words
1.webdvl (megashopba)Slovak6,536
2.Peter Schiffer (acetonik)Slovak2,623
3.Jesús Ruiz (jruiz)Spanish1349
4.Janne Wikman (vetoveljet)Finnish619
5.greenchTurkish438
6.N1n7aXIII (ninja_xiii)Thai423
7.lolypop000Slovenian330
8.M. Mirena (mmirena)Albanian194
9.Cha (cafetango)Chinese Trad.183
10.Stanislav Yordanov (StanProg)Bulgarian169

A big applause to them! And welcome to our new top contributors!

Complete translations

Fully translated languages

At the end of April, PrestaShop 1.6.1 was fully available (= 100% translated and validated) in 16 languages. That’s even better than last month, with Slovak and Indonesian making it to the top! Congrats! :)

  • Bulgarian
  • Croatian
  • Dutch
  • English
  • French
  • Indonesian
  • Italian
  • Lithuanian
  • Norwegian
  • Persian
  • Polish
  • Russian
  • Slovak
  • Slovenian
  • Spanish
  • Swedish

Again, Slovak in now fully translated: this is quite a progress since it was 78% translated and 24% validated at the beginning of the year! Well done to the Slovak team!

98-99% translated languages

PrestaShop was also almost fully translated (and/or validated) in these 6 languages:

  • Czech
  • German
  • Portuguese
  • Portuguese, Brazilian
  • Romanian
  • Vietnamese

A little bit of work and these languages can be 100% translated and validated too! If you feel like you want to help, join the project!

Languages with the best evolution

In comparison with March 2016, the following languages had the best progress in April:

  • Greek (+12% to reach 100% translated - woohoo!)
  • Chinese traditional (+1.5% to reach 75% translated)
  • Spanish, Colombia (+1.3% to reach 77% translated - yay!)
  • Estonian (+1.1% to reach 92% translated)
  • Czech (+1% to reach 99% translated!)

April 2016 best translation progress

Languages that need (more) proofreaders

A translated string will not be available in PrestaShop as long as it is not validated. For this reason, it’s important we should keep a good level of validated strings vs. translated strings, to make sure everyone benefits from the latest translations!

At the end of April, 3 languages required in priority some proofreading:

  • Turkish (96% translated vs 1% validated)
  • Ukrainian (100% vs 53%)
  • Galician (49% vs 11%)

April 2016 best translation progress

If you wish to help proofreading what has been translated, please contact me on Crowdin with the language you’d like to proofread. We need your help!

If you haven’t joined us on Crowdin yet, it’s never too late!

If you want to gather your fellow translators to work towards a better harmonization, start a glossary, or anything else, do let us know: we’ll include a word about it in the next monthly report.

Do you have a question, a remark? Don’t hesitate to leave a comment. See you next month!

PrestaShop Core Weekly - Week 19

$
0
0

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase during the previous week, from Monday 9th to Sunday 15th of May 2016.

Milestones

The work being done on version 1.7.0.0 is still going strong, working towards a proper first Beta!
In the meantime, the 1.6 branch is being supported, as expected, and you should soon see 1.6.1.6 land :)

Want to help things go faster? There are several ways:

You can find an up-to-date thread about the 1.7 development in the forum.
The 1.7 Project FAQ is always available here: http://build.prestashop.com/news/prestashop-1-7-faq/.

Do you live near Paris? Do you want to come test-drive the design of PS 1.7? Let us know!

Code changes in branch develop (for version 1.7.0.0)

Let’s review the merged pull-requests on the ‘develop’ branch since the last Core Weekly Report!

Front office (including the default theme, named “Classic” for now, based upon the Starter Theme)

  • #5544: Some cleanup in Classic folder, by @maximebiloe.
  • #5548: Update wording in Classic theme according to mockups, by @maximebiloe.
  • #5552: Fix z-index to display navigation over the header in new theme, by @maximebiloe.
  • #5555: Highlight selected attributes in Classic, by @maximebiloe.
  • #5559: Custom text block margin change. Thank you @shepherdv8!

Back office

  • #5508: add category by default field, by @mickaelandrieu.
  • #5522: .gitinore now ignore the parameters.old.php, by @shudrum.
  • #5523: combinations improvements, by @mickaelandrieu.
  • #5528: Implements new notifications in back-office header, by @maximebiloe.
  • #5536: Improved Product related search action, by @mickaelandrieu.

Core

  • #5487: simplify logic expression. Thank you @zizuu-store!
  • #5527: Fix install, by @shine-neko.
  • #5535: Improved installation, by @shine-neko.
  • #5538: Updated Symfony framework to prevent CVE issue, by @mickaelandrieu.
  • #5539: Missing Core in classname. Thank you @raphael-homann!
  • #5542: Fix travis errors during CLI installation, by @shine-neko.
  • #5547: A module can now return more than one termsAndConditions object, by @paeddl.
  • #5551: Fix typo and warning in ConditionsToApproveFinder.php, by @maximebiloe.
  • #5553: Travis cache is now used, by @quetzacoalt91.
  • #5554: Fix call to undefined method for PDF generation, by @shudrum.
  • #5558: Use symfony level for php-cs-fixer, by @julienbourdeau.

Localization

  • #5257: add some Czech translations. Thank you @fojtcz!

See all the PRs merged into the codebase since the last Core Weekly here.

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @fojtcz, @raphael-homann, @shepherdv8, and @zizuu-store! Also, thank you to the contributors whose PRs haven’t been merged yet! And of course, a big thank you to all those who contribute with tickets on the Forge!

If you want to contribute to PrestaShop with code, please read these pages first:

…and if you do not know how to fix an issue but wish to report it, please read this: How to use the Forge to contribute to PrestaShop. Thank you!

Happy contributin’ everyone!

Contributor Night & barcamp: Community Events around the PrestaShop Day

$
0
0

The yearly PrestaShop Day event is coming to Paris, France on Thursday June 2nd, and contributors are invited to join in on the fun with two events: a Contributor Night in the PrestaShop office on the day before, and a Community Barcamp within the event’s walls. Let’s meet and exchange!

Because the PrestaShop Day event happens in France and is primarily in French, this article is written in both French and English. The English version can be found after the French one.


Le PrestaShop Day est LA journée pour les professionnels de l’e-commerce, avec de nombreuses conférences, ateliers et masterclasses permettant à chaque visiteur d’améliorer son approche de la vente en ligne.

Nous avons décidé de profiter de cette grande journée et de la venue exceptionnelle de nombreux membres de la communauté à Paris pour organiser deux évènements destinés à se rencontrer, échanger, et faire progresser le projet.

La soirée des contributeurs

La veille du PrestaShop Day (soit le mercredi 1er juin 2016), l’équipe de PrestaShop accueillera dans ses locaux les contributeurs afin de faire progresser le projet PrestaShop 1.7 ensemble, pendant 3 heures (19h00-22h00).

Rejoignez-nous pour une soirée où vous pourrez apprendre à contribuer au code, à la documentation ou la traduction, par le biais de contributions open source !
Une partie de l’équipe PrestaShop sera présente pour vous accompagner en tant que mentor, avec encouragements et bons conseils.

Tout le monde peut participer à la documentation ou à la traduction – tant que vous savez écrire correctement ;)
Côté code, il faudra bien sûr déjà s’y connaître en PrestaShop 1.7 (et donc en PHP/MySQL et autres technologies), et idéalement avoir déjà contribué au code. Chaque contribution compte, même la plus petite !

Les mentors de PrestaShop seront présents pour vous accompagner :

  • Correction de bugs ;
  • Vérification de pull requests / tickets Forge ;
  • Écriture/correction de la documentation utilisateurs/développeurs/designers ;
  • Traduction du logiciel ou de la documentation.

Inscrivez-vous à cette première soirée de contribution !

Tous les participants seront remerciés avec une invitation au PrestaShop Day, le lendemain.

Vous aurez besoin :

  • D’un esprit Open Source ;
  • De votre propre ordinateur portable ;
  • De votre propre compte GitHub (code) ou Crowdin (traduction) ;
  • D’être disponible à Paris de 19h à 22h le 1er juin.

L’équipe de PrestaShop se charge de fournir nourriture et boissons pour la soirée, ainsi que la musique pour animer la soirée :)

Le barcamp au sein du PrestaShop Day

Le PrestaShop Day comprendra un espace dédié au déroulement de discussion dans le style barcamp : un espace de non-conférence, ouvert, avec des discussions participatives où chacun peut s’exprimer sur le sujet en cours. L’idée directrice : “pas de spectateur, que des participants”.

Le tout se déroule dans une ambiance non-commerciale : il n’est pas ici question de faire de la promotion de votre produit ou votre service, mais de partager vos connaissances et expériences, afin que chacun sorte grandi de la conversation, sans rétroprojecteur ni présentation Power Point.

Suggérez dès à présent votre sujet de discussion.

Nous établirons un premier programme des interventions, qui pourra également être complété le jour J s’il reste du temps.

Chaque discussion durera 40 minutes, avec 20 minutes de battement et questions/réponses informelles.

Vous aurez besoin :

  • D’un esprit ouvert ;
  • D’une volonté de partager vos connaissances ;
  • De questions permettant de faire progresser le sujet.
  • D’être inscrit au PrestaShop Day, bien sûr !

Venez à la rencontre de la communauté PrestaShop !


PrestaShop Day is THE for e-commerce professionals, with numerous conferences, workshops and masterclasses, allowing visitors to get a better knowledge of online sales.

We have decided to take advantage of this great event and the presence of many community members in Paris: we are organizing two events destined to meet, discuss, and improve the project.

The contributor night

The day before PrestaShop Day (so on Wednesday 1st of June), the PrestaShop team will welcome contributors within our Paris office, so that we can improve PrestaShop 1.7 together, for 3 hours (19:00-22:00).

Join us for the evening, and you will learn how to contribute to the code, the documentation or the translation, all this thanks to the power of Open Source!
Part the PrestaShop team will be there to get you onboard as mentors, with encouragements and best practices.

Anyone can participate to the documentation or the translation, as long as you know how to write ;)
As for code contribution, you should already know about PrestaShop 1.7 (and therefore, PHP/MySQL and other technologies), and at best you would have already contributed code. Each contribution counts, even the smallest!

The PrestaShop mentors will be there to help you:

  • Correct bugs.
  • Check pull-requests / Forge tickets.
  • Write/correct the User/Developer/Designer guides.
  • Translate the software or the documentation.

Register for our first Contributor Night !

All participants will be thanked with an invitation to the next day’s PrestaShop Day event.

You will need:

  • An Open Source mindset.
  • Your own laptop.
  • Your own GitHub account (code) or Crowdin account (translation).
  • To be available in Paris from 7 PM to 10 PM on June 1st.

We will take charge of food and beverages for the evening, as well as proper music :)

The barcamp within PrestaShop Day

PrestaShop Day will feature an area dedicated to barcamp-style conversations: a non-conference space, open, with exchanges where everyone can participate to the topic. The main idea: “No spectators, only participants”.

The whole things takes place in a non-commercial environment: this is not a place to promote a product or service, but a place to share knowledge and experience, so that everyone leaves a better person, with no overhead projector and no PowerPoint presentation.

Suggest a discussion topic right now.

We will build a first schedule of the suggested topics, which can be completed during the D if there are slots left.

Each discussion is 40 minutes long, with 20 minutes of informal Q&A and downtime.

You will need:

  • An open mindset.
  • The will to share your knowledge.
  • Questions ready in order to make the discussion keep on.
  • Have a PrestaShop Day ticket, of course !

Come and meet the PrestaShop community!


PrestaShop Core Weekly - Week 20

$
0
0

This edition of the Core Weekly report highlights changes in PrestaShop’s core codebase during the previous week, from Monday 16th to Sunday 22th of May 2016.

Milestones

Come and meet us in Paris on June 1st & 2nd!
We’re organizing two events along the PrestaShop Day:

  • June 1st: a contributor night in our Paris office. Want to contribute or learn how to contribute? Register here!
  • June 2nd: a community barcamp within the walls of the PSDay. Have something to share about PrestaShop or e-commerce? Let us know here!

See you there!

The work being done on version 1.7.0.0 is still going strong, working towards a proper first Beta!
In the meantime, the 1.6 branch is being supported, as expected, and you should soon see 1.6.1.6 be released :)

Want to help things go faster? There are several ways:

You can find an up-to-date thread about the 1.7 development in the forum.
The 1.7 Project FAQ is always available here: http://build.prestashop.com/news/prestashop-1-7-faq/.

Do you live near Paris? Do you want to come test-drive the design of PS 1.7? Let us know!

Code changes in branch 1.6.1.x

Let’s review the merged pull-requests on the ‘1.6.1.x’ branch since the last Core Weekly Report!

Front office (including the default theme, named “Classic” for now, based upon the Starter Theme)

  • 4392: Broken pagination links in loyalty, by @maximebiloe.
  • 5410: Fix CSS 404 when using subdirectory. Thank you @firstred!
  • 5588: Fix blockwishlist utf8 entities, by @rgaillard.

Back office

  • 4434: fixed bug when toggle status product not logged, by @kelu95.
  • 4439: fixed bug parent tab list wont show if admin tab class is invalid, by @kelu95.
  • 4440: add user shop origin in autocomplete cart rule, by @kelu95.
  • 4619: Improved Customer Back Office display, by @mickaelandrieu.
  • 5563: fixed bug when no results with address and map does not exist. Thank you @idnovate!
  • 5569: Display all carriers in Dashbord Configuration. Thank you @okom3pom!

Core

  • 5240: Check for displayPaymentEU to fix advanced checkout restrictions. Thank you @firstred!
  • 5242: Fix fatal error on classes/stock/StockAvailable.php, by @xborderie.
  • 5314: Return empty string when module is not installed. Thank you @alexsegura!
  • 5392: Update shopping-cart-advanced.tpl. Thank you @nobodaddy!
  • 5455: fixed mysql 5.7 “virtual” is a reserved keyword. Thank you @raphael-homann!
  • 5500: Sending mail fail with invalid Id given. Thank you @hiousi!

Webservice

  • 5216: Fix for PHP 5.2, 5.3 and 7.0 compatibility. Thank you @firstred!

PDF

  • 5411: Fix generation of PDF files. Thank you @firstred!

Installer

  • 5482: All key must not be nullable, by @julienbourdeau.

Code changes in branch develop (for version 1.7.0.0)

Let’s review the merged pull-requests on the ‘develop’ branch since the last Core Weekly Report!

Front office (including the default theme, named “Classic”, based upon the Starter Theme)

  • 5232: Avoid the deletion of still used address in order history, by @julienbourdeau.
  • 5516: Redesign checkout personal information step, by @julienbourdeau.
  • 5564: Re-implement minimum purchase amount, by @maximebiloe.
  • 5565: Add confirmation checkbox to ps_emailsubscription, by @quetzacoalt91.
  • 5572: Move cms link generation in module controller, by @quetzacoalt91.
  • 5576: Open newsletter privacy policy in a new page, by @quetzacoalt91.
  • 5586: Fix html errors on Home Page, by @mickaelandrieu.
  • 5587: Fixed invalid HTML list on Category Page, by @mickaelandrieu.
  • 5597: Fixed HTML errors on Cart Page, by @mickaelandrieu.

Back office

  • 3630: Email patches: fix encoding + add possibility to use pop3. Thank you @freedayko!
  • 3729: Fix AdminSearch customer count. Thank you @firstred!
  • 3833: Customer message should be private. Thank you @djbuch!
  • 5534: Improve product page layout according to mockups, by @nihco2.
  • 5537: Friendly URL are fixed on the Product page, by @quetzacoalt91.
  • 5568: Rename tabs in navigation an make an ellipsis for too long tabs name, by @maximebiloe.
  • 5578: Fix CSV import on PHP 7, by @quetzacoalt91.
  • 5581: Add .editorconfig rule to avoid trimming Markdown. Thank you @mcdado!
  • 5585: refacto trans twig, by @julienbourdeau.
  • 5590: Fixed bug when changing impact on price. Thank you @antho-girard.
  • 5596: The broken links on the navigation are fixed, by @shudrum.
  • 5603: Avoid PHP notices in the old template. Thank you @brunojunior!
  • 5609: use Tools::getCurrentUrlProtocolPrefix(). Thank you @zizuu-store!

Core

  • 5525: Legal compliancy code enhancement on mails, product presenter and install fixture data, by @tchauviere.
  • 5556: Make Symfony routes working even without URL rewriting, by @quetzacoalt91.
  • 5599: Remove unused $order_creation_failed var. Thank you @prestamodule!
  • 5601: get carrier by reference using specific language. Thank you @prestamodule!
  • 5602: Fixed invalid path to PEAR in Archive_Tar library, by @mickaelandrieu.

Installer

  • 5567: Install first available theme (sort alphabetically), by @julienbourdeau.
  • 5574: Better installation performances, by @quetzacoalt91.

Tests

  • 5566: Introduced dump() helper function, by @mickaelandrieu.

Webservice

  • 3745: Adding Message to the API. Thank you @gleseur!

See all the PRs merged into the codebase since the last Core Weekly here.

Thank you to the contributors whose pull requests were merged since the last Core Weekly Report: @alexsegura, @brunojunior, @djbuch, @firstred, @freedayko, @gleseur, @hiousi, @idnovate, @mcdado, @nobodaddy, @okom3pom, @prestamodule, @raphael-homann, and @zizuu-store! Also, thank you to the contributors whose PRs haven’t been merged yet! And of course, a big thank you to all those who contribute with tickets on the Forge!

If you want to contribute to PrestaShop with code, please read these pages first:

…and if you do not know how to fix an issue but wish to report it, please read this: How to use the Forge to contribute to PrestaShop. Thank you!

Happy contributin’ everyone!

Barcamp conversations: Symfony, PHP performance, Cloud e-commerce, SEO, Customer Returns and more!

$
0
0

We’d like to thank for the numerous suggestions we received: we were able to build a fantastic program for the barcamp in just a few days!

(Because the PrestaShop Day Paris event (and thus the barcamp) will be entirely in French, so will the rest of this article. Thank you for your understanding.)

Quelques jours seulement après avoir lancé un appel à suggestions, voici le programme des discussions du barcamp lors de la PrestaShop Day Paris 2016 :

HeureSujetDiscussion menée par
11h00 - 12h00SymfonyFabien Potencier, de Sensio Labs
créateur de Symfony
12h00 - 13h00Cloud et e-commerce côté business et techniqueJean-François Gomez, de Microsoft
13h00 - 14h00Les points à ne surtout pas négliger pour un SEO performantNicolas, de CreaNico
ambassadeur PrestaShop
14h00 - 15h00Performances PHPChristophe Dujarric, de Sensio Labs
CPO de Blackfire.io
15h00 - 16h00Mieux gérer les retours clientsOlivier Bally, de velo-perso.com
16h00 - 17h00Comment contribuer à PrestaShopXavier Borderie & Mickaël Andrieu, de PrestaShop
Open Source Advocate et développeur Core
17h00 - 17h30Échanges libres 

Vous voulez participer à ces sessions de discussions ouvertes et de partage de connaissances ? Il est encore de prendre votre billet pour la PrestaShop Day Paris !

Consultez également le programme très complet de cette journée dédiée à l’e-commerce (ici au format PDF).

Et souvenez-vous que vous pouvez toujours vous inscrire pour la soirée de contribution chez PrestaShop à Paris, la veille de la PrestaShop Day Paris !

À la semaine prochaine !

How to contribute to PrestaShop

$
0
0

Hey, welcome! If you landed here, it means that you’re interested in participating, testing, improving or giving your thoughts about PrestaShop.

We <3 feedback! They are greatly appreciated: they help us improve the software and make the best e-commerce solution for all types of people/businesses.

As we want to be sure that your contributions don’t get lost and are quickly understood and taken into account by our team, we’ve decided to create this exhaustive guide, with tips and guidelines on how to contribute. Here you will find a list of information and tools about the several ways to get involved.

Thank you for your interest in contributing: let’s make PrestaShop the best solution out there all together!

Download the PDF guide

PrestaShop 1.7.0.0 Beta 1 is open for feedback!

$
0
0

The first Beta version for PrestaShop 1.7.0.0 is now ready for you to test!

We are happy to announce that the development branch of version 1.7 has reached the Beta state, and we can’t wait to receive your feedback as a merchant, a service provider, a module developer or a theme designer.

Test PrestaShop 1.7.0.0 Beta 1 now!


PrestaShop 1.7.0.0 is still in development, which means that this Beta release is a great opportunity for you to start working with it before we release a stable version!
Go download and install this Beta version as a test store, either on your machine or your web hosting, then play with it – and give us your feedback!

The release of this first Beta version starts a period of intensive testing and debugging for the PrestaShop developers, with the help of the whole community: we need YOU to test this new version of PrestaShop. Change the settings, browse the default theme, check if the modules that you created still work as-is (or with tiny design adaptations), etc. And most importantly, let us know about your findings!

Test PrestaShop 1.7.0.0 Beta 1 now!

Subsequent beta and RC versions will be released as needed, and we will post on this blog when this happens.

What you need to know about PrestaShop 1.7.0.0

Regular readers of this PrestaShop Build devblog probably already know everything about the forthcoming 1.7 version, but here’s the gist of it, straight from the 1.7 Project FAQ:

Version 1.7.0.0 is the next major release of PrestaShop, following version 1.6.1.0. This major version aims at simplifying the creation of a shop and product, and to facilitate the path to your first sale. It consists of four main projects:

  • A better way to create and maintain a theme:
    • A new default theme (classy and efficient).
    • A starter theme to help designers create a kick-ass theme in half the time it took with PrestaShop 1.6.
  • Improved key user journeys in the back office:
    • A new onboarding for beginners.
    • A simplified product-creation workflow.
    • Easily find installed and non-installed modules.
  • An improved administration interface menu structure, focused on getting the most common tasks done faster.
  • A new architecture, based on the Symfony2 framework.

There is no release date to announce for the stable version right now, other than “when it’s ready”.

If you have more questions, the answer might just be in the FAQ already!

How to give feedback about Beta 1

Have you found a bug? A curious behavior? An unexpected reaction? Let us know! Create a ticket on the 1.7 Forge project, and give us as much details as possible!

Please note that we are not looking for feedback on the overall technical or design choices: Symfony2, the new theming system, the back office design and other global aspects of 1.7 are pretty much set in stone. However, do let us know about bugs or possible improvements!

Updates since alpha 4

Here are the main changes since the last public alpha version:

Front office / default theme

  • 4310: Bots can now crawl the modules’ images. Thank you @gskema!
  • 5433: Added displayCMSDisputeInformation and displayCMSPrintButton hooks. Thank you @paeddl!
  • 5564: Implemented the minimum purchase amount.
  • 5621: FO performance are now up to 20% faster than with v1.6.1.4!
  • 5644: Customized products are now displayed as distinct products in shopping cart. Thank you unlocomqx!

Back office

  • 3729: Added possibility to use POP3 server. Thank you @fredayko!
  • 3833: Customer messages are now private. Thank you @djbuch!
  • 4446: Role, Aria and Data HTML attributes are allowed in the editor. Thank you @mcdado!
  • 5528: Brand new notification system!
  • 5568: Price Rules tab is now called Discounts!
  • 5573: Introduced a default section for modules attached to a deprecated hook.
  • 5605: Attributes list are displayed in a combination tab.
  • 5612: Added an easier way to go to the Maintenance page while shop is turned off. Thank you @kpodemski!
  • 5645: The final price is now dynamically updated according to impact on price.

Product page

  • 5436: Product page layout has been improved.
  • 5438: Product category can now be added on the fly.
  • 5451: Brand and Related Products options now have a delete button.
  • 5523: You can now make the selection of default combination of a product easier and see the impact on price.
  • 5549: Added bulk edit on combinations.

Modules page

  • 5283: Modules can be sorted by last access date.
  • 5405: Module cards new display the module’s Addons score.

Core

  • 5215: Debug Mode can now be enabled from the back office. Thank you @firstred!
  • 5381: Symfony’s dump() function now replaces ppp(), ddd(), etc.
  • 5502: displayOverrideTemplate now displays more details.

Webservice

  • 3745: Added Order Messages to the API. Thank you @gleseur!

What’s (still) in progress

Remember that this is the first Beta release of version 1.7.0.0: a lot of things are not ready yet, or are ready but not yet available. We are aware of it, and we are working on it right now.

We tried to gather the most important ones below, so that you have a clear idea of what still needs to be done. All of this will eventually be fixed for the stable version – and you can help with pull-requests on GitHub, and feedback of your own tests!

Core

  • If your web hosting uses PHP-FPM, some links (and images) will not work.
  • Multistore & Advanced Stock Management aren’t yet connected to the Create a Product Page.
  • The header and navigation can vary (slightly) between pages.
  • Employees permissions are not yet suited for the new navigation in place
  • If a problem occurs while uploading a theme, we may not be able to tell you why currently :) In effect, errors and warnings are not fully set yet. And in any case, your 1.5-1.6 theme will NOT work with the new theme system (see the FAQ).

Front office

  • The Classic theme needs to be made responsive.

Back office

  • Some images are broken for now, some buttons and tab could behave in a weird way, and you might stumble on other weird artifacts. We know about this, and they will all be fixed in time for the stable release.
  • We’re still working on the responsiveness of the back office, and 13” screens could particularly be affected.
  • CSV Export can take up a lot of memory, and thus not work on some shared hosting.

Product page

  • Entry-level shared hosting can get performance issues, sometimes culminating to a blank page. We are working on it, and are committed to address the issue.

Modules page

  • We’re improving the modules discovery page: better sorting, more information, reworked categories, etc.

Content

  • Interface copywriting is not final yet. Some parts need to be written, others are waiting for a rewrite and others are in proofreading.
  • Default products are still the ones used in version 1.6. Version 1.7 should have a brand new set of products.
  • Translations are on hold for now while we’re working on improving the system: the interface is only in English for now.

Documentation

  • Contextual help still displays 1.6 documentation as we’re updating it to 1.7. Expect it to be final during our RC period – once the 1.7 User Guide will be online!.
  • Technical documentation for modules & themes should follow the same timeline.

Final note!

So cheers for this glance at the brand new 1.7, made with <3 by our team and our wonderful Community. It’s not fully baked yet, but we’re very proud of the work done.

Test PrestaShop 1.7.0.0 Beta 1 now!

We’ll closely monitor your feedback, and are eager to hear from you!

Happy testing!

Designing the new PrestaShop default theme

$
0
0

When merchants use PrestaShop for the first time, they’re offered a basic shop with demo products and a default theme. This basic theme is essential for the merchants to have a clear insight of what their new shop will look like. For the 1.7 version of the software, we’ve decided to revamp this default theme which we called “Classic”.

Main goals of the Classic theme

With around 600 free native features, PrestaShop is the ideal software for anyone wishing to get started with e-commerce. But the task is not an easy one when you’re not familiar with all the standards of e-commerce nor a web professional.

  • The major aim of the default theme is to allow any merchant to meet the Web and e-commerce best practices.
  • The second aim is to be entirely adjustable and customizable, to allow every online shop to be singular. Do you have any specific requirement? The modules from the Addons marketplace are here to allow you to improve your website using as many features as you like.

Design challenges

Don’t judge a book by its cover. If the final result of the Classic theme might lead you to think it was easy to implement, it was actually a real challenge in terms of graphic design and user experience. To make it accessible to everyone, our Product team had to face several challenges, such as:

  • Offering a theme compatible with any kind of business from the textile industry to the food one, ranging from technology, luxury or wholesale outlets).
  • Implementing the standard best practices of e-commerce for any merchant at any level.
  • Offering a design of interfaces that is sleek enough so that merchants can imagine their products in it, and see how easily they can adapt the design to their graphic identity.
  • Allowing an optimal user experience, with a graphic design focused on the products on show as well as a simplified and smoother buying journey.
  • Offering adjustable blocks compatible with the overall graphic design of the shop allowing merchants to choose whatever modules they need.
  • Allowing merchants to fulfill any visual identity at an affordable price for an esthetic and clear website.
  • Creating international interfaces, compatible with e-commerce all around the world, in the 165 countries where Prestashop is being used.
  • Being responsive, to meet with the ever-increasing e-commerce market on mobile phones around the world.

The choices of this theme’s revamp were not only based on graphic criteria but on our promise to put e-commerce at everyone’s reach.

Graphic choices

The product constraints described above were used as a common thread for the graphic choices of the theme.

Imagine that you should sell a house. If your potential buyers see it with furnitures, frames, porcelain figurines and other wooden duck collections, they will have more difficulties to project themselves into it and to have an idea of its volume and potential rather than if it was painted in white with very minimal furnishing. The same applies for the Classic theme. The idea was not to create the perfect visual identity for the next womenswear store to come but on the contrary to offer a neutral framework, where products could be easy to identify, as well as a faceted navigation, a fluid purchase funnel and easy-to-identify call to actions. These choices answer some specific project needs:

  • The background colors (white and grey) allow to focus on the products and to simplify the reading process of the interfaces.
  • The blue calls to action contrast with the background and are more easily viewable and identifiable.
  • The Open Sans typography is a Google font that has three major benefits: it is very easy to read, very complete (897 characters), and it allows you to translate in a maximum of Latin alphabet-based languages that are used by a large majority of our merchants.
  • The minimum size of the paragraphs meets readability criteria.
  • The flat design combined with shadow effects allow to have light interfaces while preserving the meaning of dynamic elements.
  • The alert colors (orange and red) answer the standards of most of the merchants and are clearly identifiable by their customers as alert messages.
  • The icons are taken from Google Material, an Open Source library, just like our software. This aspect is very important to us and the advantage of this library is that our merchants will be able to add icons to their websites for free without leaving the graphical universe.
  • The demo products from the shop are being created. As a matter of fact, we’re aware that our catalog of demo products is mainly about woman clothing. But this is going to change! Our Product team is working on a new products catalog that is more up-to-date and that will allow our merchants to better see how their products can fit in their new store. Merchants will then be free to customize their theme’s interfaces, to change all the elements and to add their graphic identity to it.

One-page checkout

The purchase funnel is essential for an e-commerce website. A well-built checkout process facilitates the conversion and customer loyalty. On the other way round, if it is not well designed, it can lead to cart abandonments. This additional revamping challenge of the basic theme is huge, since here, more than anywhere else, the impact on the success of our merchants will be decisive. You don’t buy pizzas the same way as handbags. And a lot of themes are based on the default PrestaShop theme, so if the conversion is not good enough, that’s the whole ecosystem that might suffer from it.

So the main goal of the purchase funnel for the Classic theme is to propose the best possible user experience. This funnel is intended to:

  • Convert as efficiently as possible.
  • Present steps identifiable at a glance.
  • Have a speedy buying process.
  • Put the best practices of online shopping at the merchant’s disposal.
  • Better integrate the necessary modules (payment, delivery, etc.).
  • Be compatible with foreign languages.
  • Be easy to maintain and debug.

All this while complying with the same design constraints as those mentioned above (interface readability, adjustable blocks, international compatibility, etc.).

This purchase funnel is built on one page, with unfolding blocks. This choice is not a random one. To reach this conclusion, we have:

  • Tested tens of shops and numerous different online selling styles.
  • Followed the Design thinking methodology.
  • Performed user tests with 25 merchants coming from all backgrounds.
  • Iterated the production of those interfaces according to those test results.

One-page checkout vs. Five steps

The methodology followed for this kind of purchase funnel allowed us to realize that a one-page checkout process (or OPC) presents a lot of benefits for a shop:

  • It is considered by customers to be quicker than a funnel with 5 distinct steps on different pages.
  • It allows the customers to anticipate the steps to follow before the payment.
  • It allows the customer to check its cart at any time during the checkout process.
  • Returning to the previous step to make a change appears more reassuring, since the information will not be lost.
  • The page structure is responsive (to allow for payments on mobile phones).

Standard vs. specific

One thing we must keep in mind is that PrestaShop is a free and Open Source software designed to meet the needs of all merchants, whether they are small or big. That’s the reason why the Classic theme should meet all standard needs and not only specific ones. For customization purposes, Open Source offers all the necessary tools (modules, access to source code, etc.) to have a unique shop.

Alpha vs. Release (work in progress)

We’re not quite ready! The Product team is currently working on the 1.7 version. So the Classic theme is not final, and more user tests and iterations should follow. The demo products inherited from version 1.6 will be replaced by an enriched catalog. The site behavior will also be fully responsive… Exciting challenges are still to come, with the will to place the best of e-commerce at everyone’s reach.

Prestashop is hiring

At PrestaShop, we have a mantra: “Work like a Captain, Play like a Pirate”. If you want to join the community and take part in the adventure, remember that:

Viewing all 939 articles
Browse latest View live