Jump to content

Want to know more about 1.7?


Xavier Borderie

Recommended Posts

For those who want to dive into the new major version of PrestaShop, version 1.7, this post will try to summarize the available information so far -- mostly published on the Build devblog, which you should read every week :)

 

Public releases:

In general, you really should pay a visit to the Build devblog on a regular basis: http://build.prestashop.com/

This is where we update the Community on the latest news from the Dev team!

Quick selection of articles about v1.7:

Articles about the new architecture:

Articles about the Starter Theme:

Articles about the new default theme:

Articles that go beyond the scope of v1.7:

If you have questions or articles ideas (or if you want to write for the Build devblog!), let me know!

 

Also: we're hiring in Paris (France): http://build.prestashop.com/news/prestacrew-hiring/ !

 

(cliquez ici pour la version française de cet article)

(local community members: feel free to translate this article in your local forums!)

  • Like 7
Link to comment
Share on other sites

Hi Xavier!

 

When are you planning to release the beta version of 1.7?

 

Best regards

MacRoy

 

We're deep into development, so it's hard to tell.

Currently, we expect the first beta to be released before 2016. But a lot of things are still up in the air, so let's just give the usual answer in open source project: "when it's ready" :)

Thank you for your patience!

  • Like 1
Link to comment
Share on other sites

Hy. I'm using Prestashop since 1.5. When I activate b2b option, customers are unable to register because of the following errors: SIRET is invalid and APE is invalid. Shop localization is Romania and the equivalent for SIRET and APE in romanian  has different  format. In french APE is 4 digits and a letter, in romanian is 4 digits. Not all countries have the same format for this type of information. Also some customizable fields are necessary. When a company registers on my prestashop website I need additional legal information, so more fields would be welcome. Thank you.

 

Hello Psxtavi,

 

This is a thread about PrestaShop 1.7.

Please open another thread on the main forum for your PS 1.5 issues.

 

Regards.

  • Like 1
Link to comment
Share on other sites

Hello Xavier,

I plan to redo our site on prestashop 1.7 as soon as possible... I plan to use github to synchronise my own dev with the different next releases of prestashop 1.7 (and wait that the version is stable enough to lauch in production).
You said that the first beta relase would be ready before end of 2015, please can you tell me if there will the possibility to pick up this version on the github with the possibility to update manualy our date base lauching the commande in install/upgrade/sql/1.7.0.0.sql

I don't know if i'm clear...

Thnks a lot.
Visn

Link to comment
Share on other sites

You said that the first beta relase would be ready before end of 2015, please can you tell me if there will the possibility to pick up this version on the github with the possibility to update manualy our date base lauching the commande in install/upgrade/sql/1.7.0.0.sql

 

Note: the first beta might be out before the end of 2015. For now, we're still in full development mode, so it's hard to promise anything :)

 

You can always keep up to date by upgrading to the GitHub repo, but do not that it might break from one day to another.

In any case, beta versions will be packagaged as usual, and will be available here: https://www.prestashop.com/en/developers-versions

 

Best regards.
Link to comment
Share on other sites

  • 3 weeks later...

Does PrestaShop 1.7 database will have foreign key(s) in tables?

Does PrestaShop 1.7 will be more friendly with Google Merchant Center like Bigcommerce, Google Trusted Stores Merchant like Magento, Google Content API for Shopping. ?

Does PrestaShop 1.7 will have have more native fields in product details compatible with google product data feed ?

Does PrestaShop 1.7 will remove deprecated code, hook_alias , etc

Link to comment
Share on other sites

The stock update feature of prestashop is really now time consuming. this feature is really need to change.  

I want to suggest some feature for next version of prestashop.

1. ajax edit/ Quick edit of product name , Reference, price, special price, quantity, with out leaving the page, just like on wordpress, Abante cart, Cs Cart.  Demo Pic Here http://pasteboard.co/2CyuDnwq.jpg.

2) fast loading front and back office,

3) ajax search on backup office ( searching what need, with out leaving the page)

4) Product can embed on any pages, (embed codes can be used in any website including static HTML pages.)

5) Newsletter function as core feature( from this admin can send email to customers )
6) Advance affiliate function.

The main requested feature is quick/ajax search and editing feature in back office so that admin( owner of Shop) can edit quantity, price, product name, model/ Reference number easily . Just like >>http://pasteboard.co/2CyuDnwq.jpg

Link to comment
Share on other sites

Hello,

 

I would like to know if, for instance on the product template/page,

the combinations are fully loaded with javascript selection, like it has always been in prestashop,

or if it will be at last with ajax loading, in order to soften the javascript burden

when there are many combinations on one single product, as well as make easier

the programmer's work when doing a module based on attributes ?

 

When there are several attributes' combinations it could easily be a burden on that page!

 

This is a killer feature in drupal commerce when having products combinations, indeed...

Edited by strapper (see edit history)
Link to comment
Share on other sites

Is it have category based product at homepage option?

 

Its necessary now a days to all online sellers. Will be great if you add that option to featured products or similar module. So that people can select how much category & from which products should be visible at frontend.

 

Thanks

Link to comment
Share on other sites

Perhaps do you mean a pluggable authentication, with a specific hook for instance ?

 

Also, the same way for the search/layered module so that it could be possible to hook in a search engine

(native search engine, addon module for sphinx, solr, elasticsearch, custom, ...)

 

 

Hi, please add this two feature natively on the new core of PrestaShop v 1.7.x.x :

 

> 1 - Native 2Fa-Two Factor Authentication (Google) + Usb Dongle Authentication (Yubikey)

 

> 2 - Auto update Maxmind Geolitecity Database

 

Sincerely, Fabio Perri.

Link to comment
Share on other sites

  • 4 weeks later...

Hey everyone!

 

I added two links to recent Build articles:

I'll try to answer a few of your questions:

 

  • Does PrestaShop 1.7 database will have foreign key(s) in tables?
    Not that I know of.
  • I want create a prestashop shop for my company from scratch. May I wait for the 1.7 version or start invest money in extensions and time in the current version?
    We're still in development mode, and hope to release a first beta in the coming weeks. Can't promise anything.
    Version 1.6 is the safe choice currently. It will be maintained and supported for several months once the stable version of PrestaShop 1.7 is released, so that should give you enough time to switch from 1.6 to 1.7 once you think 1.7 is ready for you.
  • Does PrestaShop 1.7 will be more friendly with Google Merchant Center like Bigcommerce, Google Trusted Stores Merchant like Magento, Google Content API for Shopping. ?
    I don't think these are planned evolutions.
  • Does PrestaShop 1.7 will have have more native fields in product details compatible with google product data feed ?
    The product page is being heavily reworked for 1.7, I think the team is aiming for the same features as with 1.6 in this area for now. If you want to help, let us know!
  • Does PrestaShop 1.7 will remove deprecated code, hook_alias , etc
    A lot of deprecated code is being remove, yes. I can't tell you precisely, but you can join the conversation on Gitter: https://gitter.im/PrestaShop/General !
  • I want to suggest some feature for next version of prestashop
    Please do so on the Forge.
  • Any chance you could build product dimensions into the combinations?
    I don't think this is currently planned, but please let us know on the Forge or on Gitter!
  • Is it have category based product at homepage option?
    The front office is being entirely rethought and rebuilt through the Starter Theme and Classic theme projects. I think for now they are aiming at the essential features without impacting the back office, but do let us know about your wish on Gitter: https://gitter.im/PrestaShop/General !
  • [ajax loading on product template/page]
    Ask the Starter Theme guys on Gitter: https://gitter.im/PrestaShop/General :)
  • Do you plan to extend price adjusting functionality on product combinations by adding percentage impact in the future? (default is only by value)
    I don't think this is planned for 1.7.0.
  • Native 2Fa-Two Factor Authentication (Google) + Usb Dongle Authentication (Yubikey) and Auto update Maxmind Geolitecity Database
    I don't think this is planned for 1.7.0.
  • Can I ask why Symphony 2 and not 3?
    In effect, PS 1.7.0 should be able to work with Sf3, but for now we're targetting the current LTS of Symfony. We may target Sf3 in a later version.
  • Merci d'ouvrir aussi un sujet 1.7 en FRANçAIS !
    Nous avons choisi de communique en anglais pour la 1.7, afin de cibler l'international (dont la France). PrestaShop est une société internationale, avec des bureaux à Paris mais aussi à Miami, San Francisco, Madrid, Italie, Allemagne et le Benelux.
    Je vais voir pour proposer une VF de cet article -- mais les articles liés ne seront pas traduits.
  • For Prestashop v1.7, since Symfony2.3 achieved 100% compatibility with HHVM, will this speed improvement be felt also with Prestashop 1.7 ?
    Hopefully so! :) We'll start benchmarking once we reach the beta phase.
     

Cheers!

  • Like 1
Link to comment
Share on other sites

Any reasons (explanation, justification) why new version 1.7 will not have foreign key(s) in tables?

I'm very disappointed. Anybody knows that foreign key constraint means database integrity.

MySQL 5.5 and later use InnoDB by default. It provides the standard ACID-compliant transaction features, along with foreign key support (Declarative Referential Integrity).

Edited by lxhost (see edit history)
  • Like 1
Link to comment
Share on other sites

You are right, but honestly, about 90% of all shops would be non-upgradable and all pre-1.7 code and modules would have to be abandoned.

yes, poor shops and poor modules will not work, but this could be a criterion to keep only the best. This will increase the quality. 

Link to comment
Share on other sites

Added a link to the latest Build article:

Now, to answer a few more questions:

  • (...) about 90% of all shops would be non-upgradable and all pre-1.7 code and modules would have to be abandoned
    The themes will certainly need to be rewritten, as the Theme API is completely revamped in 1.7, in order to have a great Theming community rather than too many slight modification of the default 1.6 theme.
    A lot of 1.6 modules will still work in 1.7, most notable those which do not target the theme, the Product page or the Modules page. We've been running some tests on the Addons catalogue, we will soon publish the results on Build. But of course, there will remain modules which won't work as-is.
    Therefore, moving from 1.6 to 1.7 will not be a matter of simply clicking the Upgrade button. That is why we plan on supporting 1.6 for more than 2016 (still being decided).
  • Can someone name 3 new features (or reasons), why a PrestaShop 1.6-owner should invest time and money to upgrade his shop to 1.7?
    Upgrading will not be an easy task (see above), so we would completely understand if a merchant chose to stay with 1.6 for the time being -- at least until all modules are compatible with 1.7.
    For new stores though, 1.7 will be a treat! For merchants: the reworked UI will provide a better daily flow, the Product page has been rethought, and the Modules page as well. For developers: the Starter Theme will make it way easier to create a brand new theme, the widget system, PHP namespaces and other PHP 5.4 niceties (along with perfs), the ability to call the whole Symfony stack for you module's needs, etc.
  • Any reasons (explanation, justification) why new version 1.7 will not have foreign key(s) in tables?
    The scope of 1.7 wasn't to rework the object model, which is still full MyIsam compatibility. There was already a lot of work with the arrival of Symfony, and breaking the legacy code isn't the idea.
  • Like 1
Link to comment
Share on other sites

 

Added a link to the latest Build article:

Now, to answer a few more questions:

  • (...) about 90% of all shops would be non-upgradable and all pre-1.7 code and modules would have to be abandoned

    The themes will certainly need to be rewritten, as the Theme API is completely revamped in 1.7, in order to have a great Theming community rather than too many slight modification of the default 1.6 theme.

    A lot of 1.6 modules will still work in 1.7, most notable those which do not target the theme, the Product page or the Modules page. We've been running some tests on the Addons catalogue, we will soon publish the results on Build. But of course, there will remain modules which won't work as-is.

    Therefore, moving from 1.6 to 1.7 will not be a matter of simply clicking the Upgrade button. That is why we plan on supporting 1.6 for more than 2016 (still being decided).

  • Can someone name 3 new features (or reasons), why a PrestaShop 1.6-owner should invest time and money to upgrade his shop to 1.7?

    Upgrading will not be an easy task (see above), so we would completely understand if a merchant chose to stay with 1.6 for the time being -- at least until all modules are compatible with 1.7.

    For new stores though, 1.7 will be a treat! For merchants: the reworked UI will provide a better daily flow, the Product page has been rethought, and the Modules page as well. For developers: the Starter Theme will make it way easier to create a brand new theme, the widget system, PHP namespaces and other PHP 5.4 niceties (along with perfs), the ability to call the whole Symfony stack for you module's needs, etc.

  • Any reasons (explanation, justification) why new version 1.7 will not have foreign key(s) in tables?

    The scope of 1.7 wasn't to rework the object model, which is still full MyIsam compatibility. There was already a lot of work with the arrival of Symfony, and breaking the legacy code isn't the idea.

 

100% you must have MyIsam compatibility, but, in my opinion, you should offer a better solution for those who abandoned MyIsam.

MyIsam is a deprecated engine, and PrestaShop have a chance now to add full InnoDB in version 1.7.

 

take a look at this code:

if (_MYSQL_ENGINE_ == 'InnoDB') {

    Db::getInstance()->execute("ALTER TABLE `"._DB_PREFIX_."orders` ADD CONSTRAINT `"._DB_PREFIX_."orders_ibfk_1` FOREIGN KEY (`id_cart`) REFERENCES `"._DB_PREFIX_."cart` (`id_cart`) ON DELETE CASCADE ON UPDATE CASCADE");

}

 

 

this query

 

ALTER TABLE `ps_orders` ADD CONSTRAINT `ps_orders_ibfk_1` FOREIGN KEY (`id_cart`) REFERENCES `ps_cart` (`id_cart`) ON DELETE CASCADE ON UPDATE CASCADE

 

 

will guaranties that you will have in table ps_orders only real id_cart, you will not be able to add some nonexistent id_card.

This will increase the database integrity and security.

Link to comment
Share on other sites

For everyone who asking:

"If PrestaShop will add *here is some feature from module*"?

 

No, this feature will probably not be available, why? Because it is also business, and there are hundreds of great modules, there are better search modules, modules for buying products with measurements etc. 

 

1.7 is huge change on front-end, pretty big changes in back-office but those are changes more for UX, Usabillity etc. it doesn't mean that new version = new features, probably 1.7 will have "a few" new features but overall it is simply version to provide better quality catalog managament, and better architecture for theme developers.

  • Like 1
Link to comment
Share on other sites

Hi!

 

What are system requirements for v1.7?

One of the strongest point for me is that 1.6 version can run at cheap shared hostings with easy installation process (unpack zip and step-by-step installation).

 

What about system requirements and installation process of 1.7 version? 

Link to comment
Share on other sites

Hi!

 

What are system requirements for v1.7?

One of the strongest point for me is that 1.6 version can run at cheap shared hostings with easy installation process (unpack zip and step-by-step installation).

 

What about system requirements and installation process of 1.7 version? 

 

I'm afraid that you'll need more than that in the nearest future because for example it will be good to have access to SSH to do some task by developer working on Symfony.

 

http://symfony.com/doc/2.7/reference/requirements.html

Link to comment
Share on other sites

I'm afraid that you'll need more than that in the nearest future because for example it will be good to have access to SSH to do some task by developer working on Symfony.

 

http://symfony.com/doc/2.7/reference/requirements.html

 

 

That's ok in general. Or even that is great news!

 

On other hand there are some promising e-commerce solutions based on Symfony already.

And PrestaShop now enter their market.

Symfony is now everywhere.

Link to comment
Share on other sites

Further questions? Further answers, yay!

 

  • 100% you must have MyIsam compatibility, but, in my opinion, you should offer a better solution for those who abandoned MyIsam. MyIsam is a deprecated engine, and PrestaShop have a chance now to add full InnoDB in version 1.7.
    In an ideal world with enough manpower to dive into all the subprojects we want and where we don't have to worry with legacy code, yes, I'm sure we'd do that. But pragmatically, it's not going to happen in 1.7.
  • What are system requirements for v1.7?
    Nothing is set in stone yet (and we won't have proper benchmarks before the first beta version), but as Krystian said, you can bet it will at least be the same as for Symfony 2.8. Also, we announced that PrestaShop was moving to PHP 5.4. As for server configuration, well, let's just say "the more the better" for now, but in any case, it will most probably be higher than for 1.6.
  • Like 1
Link to comment
Share on other sites

I have a problem with ps 1.7 installation from github.

 

Step I did

1. downloaded dev zip from github

2. when I access to site i have info about composer

3. so i dit

composer install
npm install -g grunt-cli
npm install
 

then i have installer visible but i can not proceed due 

  • Not all files were successfully uploaded on your server"
Link to comment
Share on other sites

@Xavier Borderie

 

In the old version of Prestashop it was so easy for any beginner to install the Prestashop version. just download and install. What i saw that in 1.7 it need to do some extra work. Before install. install composer. and other things, Which is little bit complicated for new user to install windows  PC. But it is easy to install composer and other things in mac.

 

If there is any special guide for new user that will be good for them.

Link to comment
Share on other sites

Hey there, good people!

 

I got a few more answers for you :)

  • Can you tell us when the PrestaShop 1.7 beta is ready?
    Not yet. We hope to have it out verrrrry soon, but I cannot give a precise date. "When it's ready" is the most common answer in Open Source projects :)
  • Any plans to add some mails template system in 1.7?
    Not at this time. Maybe in a later version.
  • is anywhere available prestashop 1.7 version for download?
    The development code is available here: https://github.com/PrestaShop/PrestaShop/tree/develop
    To install, read the instructions here: https://github.com/PrestaShop/PrestaShop/blob/develop/README.md
  • In the old version of Prestashop it was so easy for any beginner to install the Prestashop version. just download and install. What i saw that in 1.7 it need to do some extra work.
    This is only while we're developing it -- and while developers are testing it and contributing to it. The stable version will be packaged in such a way that any user will be able to just upload and install, just like they did with previous versions.

Cheers!

  • Like 3
Link to comment
Share on other sites

Added two recent Build articles to the list in the first post of this discussion:

  • Like 1
Link to comment
Share on other sites

Hello Xavier!

 

I like new default theme features and its general approach!

 

By the way, what about tutorials and documentation specific for 1.7 version?

 

 

With best wishes,

Mikhail

 

P.S. I forget to ask about blog features previously. Any plans to have it natively?

Edited by Mixa_RU (see edit history)
  • Like 1
Link to comment
Share on other sites

Added one article:

 

 

About your questions, Mixa_RU:

  • Documentation will be worked on once feature are fully ready and stable enough -- probably during the beta phase, then.
  • There is no plan to have a native blog feature. I'm tempted to say that, on the contrary, since 1.7 is way for us to focus on business features (managing a cart, handling orders, calculating prices and taxes, generating invoices, etc.), there is less chance to see a native blog feature happen. Either use a module, or use a dedicated tool, such as WordPress.
  • Like 3
Link to comment
Share on other sites

  • 2 weeks later...

 

Those installation instructions are for a Linux environment. They are not very useful for a Windows environment. 

 

Can you provide Windows instructions too?

Link to comment
Share on other sites

Those installation instructions are for a Linux environment. They are not very useful for a Windows environment. 

 

Can you provide Windows instructions too?

 

It works for Windows too, install localhost(xampp for example), then install composer https://getcomposer.org/ and then run in cmd

composer install

In past i had an error about bash command from linux, so installation failed, So instead of cmd you can use some linux terminal for Windows Cygwin https://www.cygwin.com/

Link to comment
Share on other sites

 

 

If we want to keep this thread serious... I think that if they want to use php 5.4, they have no intention to modernize prestashop codebase. I'm writing this at march 10 on a nov 3 post but... We need a prestashop based on php 7.x. 

Prestashop is slow by nature and we need this upgrade.

 

Regards.

Link to comment
Share on other sites

I've told this to the development team before and I'm not the only one thinking that PHP 5.4 isn't a good choice.

PHP 5.4 has reached end of life on 3 September 2015.

Installing a LAMP stack on Ubuntu 14.04 comes with PHP 5.5.9 and on Debian 8 with 5.6.9. As a developer, to ensure that my code runs well with PrestaShop I will have to find a way to downgrade the PHP version or use an older linux distribution.

PHP 5.5 would have been a good choice if the presta team doesn't feel so bold yet for 5.6.

  • Like 1
Link to comment
Share on other sites

Today, my module was declined by addons.prestashop.com because: "Your module will crash on PHP 5 < 5.5"

Now, I should spend time to install on my server a old version of php, that php.net do not support long time ago.

from my point of view, this is a very stupid situation.

my question is, if php.net do not support php 5.4 why prestashop support 5.4

I'm very disappointed in your attitude.

 

php.net always support 3 versions, now are 5.5, 5.6, 7.0, and all respectable companies go in step with php developers

 

does prestashop support php 7?

another question: what is

Downshifting?
Link to comment
Share on other sites

It's sightly faster, specially if you have a good hosting with latest CPanel and well configured.

We have some prestashop installed in a VPS for each one and they are slow as ****. By the other way, the epic fail of almost all 1.5.x versions and the 1click upgrade errors from 1.4.x, 1.5.x, and 1.6.x to 1.6.x latest versions seems incredible, even unabling all modules and deleting cache...

 

I need to find another way to create an online shop, or find an explicit config where ps run well in harmony (if there is some)...

 

Link to comment
Share on other sites

  • 2 weeks later...

If they want to support php 5.4 that's fine with me, however going to the time and effort to put out a major upgrade and not supporting php 7 is just ridicules. At the very least i think we deserve to know what future version will fully support php 7

Link to comment
Share on other sites

If they want to support php 5.4 that's fine with me, however going to the time and effort to put out a major upgrade and not supporting php 7 is just ridicules. At the very least i think we deserve to know what future version will fully support php 7

 

Both Prestashop 1.6.1.4 and 1.7.0.x work fine already using PHP 7.

 

This was mentioned as one of the main reasons behind the 1.6.1.4 release, and of course will not be removed for 1.7.0.x.

Link to comment
Share on other sites

Both Prestashop 1.6.1.4 and 1.7.0.x work fine already using PHP 7.

 

This was mentioned as one of the main reasons behind the 1.6.1.4 release, and of course will not be removed for 1.7.0.x.

Yes it should run fine in a php 7 environment, but has it been specifically optimized for php 7? Joomla 3.4 ran fine with php 7 however joomla 3.5 was specifically set up to take full advantage of php 7. The speed increase was dramatic.

Link to comment
Share on other sites

The first public test version was released yesterday! Test PrestaShop 1.7.0.0 alpha 3 now!

The 1.7 Project FAQ has been updated too!

 

Now, for your latest questions:

  • Please dont forget some important seo improvement.
    Please check out the new default theme, bundled with PS 1.7 alpha 3! If you see something that could be improved, do not hesitate to suggest it with a pull request on Github!
  • can I know if there will be seo differences ?
    The default themes for 1.6 and 1.7 are completely different, so yeah, I'm pretty sure there are SEO differences baked in :) Now, the Theme team had done its best to use current best practices -- but won't go as far as full-fledged SEO option, which are module territory. It's also up to the theme creator to work on its theme's SEO capabilities: the 1.7 default theme is a solid theme, but not a theme that does everything under the sun.
  • Please care about the social login.
    I do not think this is planned for Core.
  • Could a shipping countdown be added as standard similar to this
    Including this module feature in Core is not planned, as far as I know.
  • We need a prestashop based on php 7.x.
    does prestashop support php 7?
    going to the time and effort to put out a major upgrade and not supporting php 7 is just ridicules

    Several key parts of version 1.7.0.0 have been updated to work with PHP 7.0.
  • PHP 5.4 isn't a good choice.
    We recommend the use of PHP 5.6+, for obvious security and performance reasons. PrestaShop 1.7 will also work with PHP 5.4, just as WordPress does for work with PHP 5.2.
  • "Your module will crash on PHP 5 < 5.5"
    A majority of PrestaShop installations are made on cheap shared hosts, which are mostly still relying on PHP 5.4. We cannot abandon these users.
  • Will be Prestashop 100% symfony? And obviosly Symfony 3, not 2
    That's the idea: upgrade the code base to use modern Symfony framework instead of the old custom architecture. We are currently working with Sf 2.8, and I'm sure eventually we'll move to Sf 3, once it is stable enough.
Link to comment
Share on other sites

Thank you for the update Xiavier! Any news on an upgrade path to 1.7?

 

As the FAQ says, upgrading from 1.6 to 1.7 can be done, but it won't be easy, if only because the theme system was completely rewritten.

 

So, in short, if you want to upgrade from 1.6 to 1.7, you will have to:

  • Have the theme rewritten.
  • Have the modules updated (the vast majority will work as-is, with only a need to adapt the CSS code. Use the UI Kit!)
  • Test your overrides thoroughly.

Hence, we tend to advise NOT to upgrade directly from 1.7 to 1.6. We advise to keep 1.7 for new stores, and upgrade the 1.6-1.5-1.4-etc. stores to the latest version of 1.6 (currently 1.6.1.4), because the 1.6 version of PrestaShop will be supported (with bugfixes) for several months once the stable version of 1.7 is out.

Link to comment
Share on other sites

I'm waiting to moove an active prestashop with 20k/week users, but i have to make a clean install (because one click upgrade from 1.5.4 to 1.6.0 was catastrofic) and i prefere to wait till 1.7.x version to make all that creepy job. 

Do you know, more or less, when will a stable tested version avaible to download?

 

It will be fine if a second stable version appears at may :P (first one is always a lottery lol)

 

Thanks. =)

Link to comment
Share on other sites

Is the first final realease date of 1.7 still in June ?

 

As said on main thread, there is no needed important feature and no real improvement (sorry but backend Modules isn't used so often by clients) that proves the utility to drive tests and make changes to all shops we manage. Still we will make it, but where is the interest ?

As previously said in this current thread, making huge frontend performance improvement shall be a milestone for new good version.

 

I mean, there is some things you really can do without spending lots of time :

- Making a static cache by defaut when user are note logged. Exception made of some hooks, lots of modules do that. Which prouves there is something missing.

- Easy DB backup with Prestashop Cloud. Would be a great feature, for ridiculus cost and a great security for shops owners.

- Upgrading Compressors quality and usability (like Autoptimize do it for Wordpress for example).

- PHP 7 real compatibility, forcing owners to switch to this version would be a great things for the future.

- Adding more hooks on key features (Page preloading, Carts update, , we nearly always need an override when we made a module.

- Force native Modules and Legacy code to use Objects and not hardcoded requests.

 

Sure we can help on this :)

 

Still, I think you are doing great, but you need to be more ambitious, or this version will be looked as a minor upgrade.

 

M.

Link to comment
Share on other sites

As Matthieu Malttt says, it will be "the one" osCommerce application, but you need to deprecate php 5> <5.6 users in a new version. Those users need to upgrade their hosting or make changes in config to use 5.6+ or 7.x. If you want to support deprecated versions of php, you'll never get an optimized version of prestashop. Better said, WE never get it. Users with those "cheap hostings" that not allow php 7, may choose another option of "cheap hosting" too. I've a prestashop in a 4,95 US$ / month, and i don't think this is expensive... and know worse hostings at 3,5US$/month that allow php7 too. It's not an excuse (remember that we are talking about online shopping, where it's supposed that you are earning some money with it...).

Another good change (and easyest as possible) for 1.7 is to change search funcitons to get better results. I made a tutorial about that (in spanish) on there: https://www.prestashop.com/forums/topic/517757-tutorial-mejora-de-las-b%C3%BAsquedas/

It's a need, not a caprice. It's annoying to get thousands of results about a search that you know there are only 3 or 4. It happens in backend (searching users for example) and in front end, where prestashop search every word you put separated by spaces, and merge results ordered by product id (WTF?). In brief, more words = more restrictive search (everybody knows that usually search have to work like that). But prestashop is still making the opposite.

 

 

Regards!

Link to comment
Share on other sites

  • Do you know, more or less, when will a stable tested version avaible to download?

    Nope. For real, man: we want to release it when it's ready. We have a rough idea of when we'd like it to be ready, but if it's not, we do not want to be constrained by a public date announcement.

  • Is the first final realease date of 1.7 still in June ?

    When was it every said it would be released in June?

  • there is no needed important feature and no real improvement

    Have a look at the Product page, maybe? Or the default theme system? Or the fact that the architecture is switching to an solid and thriving Open Source framework (Symfony2) rather than a codebase that is getting older by the year?

  • Sure we can help on this :)

    Yeah, great, that's the spirit! Give us feedback, ideas, or even better: pull requests! :)

  • Another good change (...) is to change search funcitons to get better results

    Forwarding that to the Core team -- but creating a detailed Forge ticket directly would be better! :)

Link to comment
Share on other sites

  • Please dont forget some important seo improvement.

    Please check out the new default theme, bundled with PS 1.7 alpha 3! If you see something that could be improved, do not hesitate to suggest it with a pull request on Github!

  • can I know if there will be seo differences ?

    The default themes for 1.6 and 1.7 are completely different, so yeah, I'm pretty sure there are SEO differences baked in :) Now, the Theme team had done its best to use current best practices -- but won't go as far as full-fledged SEO option, which are module territory. It's also up to the theme creator to work on its theme's SEO capabilities: the 1.7 default theme is a solid theme, but not a theme that does everything under the sun.

Hi Xavier, I want to take this into discussion. I don't doubt on the efforts made for SEO improvement, but did you ever analyzed PS 1.7. with one SEO tool like GTMETRIX.

 

Although I have A grade on performance (more than a server task!), there are some not really satisfied points Prestashop 1.7. is not covering:

 

  • ERROR: offers field missing or empty
  • Google fonts and cache validator Problem: Grade F = 0 points from 100
  • Image dimensions problem: Grade F = 39 points from 100
  • Some JS could not be minified yon NGNIX (this is not a server problem, compression is activated and working for other pages running for ex. on WP) Grade E = 56 from 100 points
  • Than minor problems like landing pages redirects, css @imports and banner images scale on the new theme.
  • Furthermore there are 7 errors on microdata for all 7 available products ?! WARNING: price field not specified in http://schema.org/Product and
  • Besides that there are no opengraph meta-tags available as per default on the new theme.

 

Don't know who is working on that, but he should also test what he is coding. Delivering bugged data is not really what users without any knowledge of SEO needs. ;)

Link to comment
Share on other sites

Hi Xavier,

 

I am a bit puzzled by your statement that PS 1.7 is for new shops and that upgrading is not recommended. As I understand 1.7 has new themes so you need to install a new theme. And modules that address the products pages in the back office need to be upgraded. But there are lots of shops that don't use that much modules and that want a new theme anyway. So what should be the problem for them?

 

As related question: if that new theme is so flexible, isn't it possible to build a wraparound so that old themes can be used? It would help a lot of people. 

Link to comment
Share on other sites

Is it possible to at least import the orders, customers, products and categories from 1.6 to 1.7?

Why import ? PS 1.6. is not discontinued, and I'm sure when PS 1.7. is released they will find a way for to upgrade (at least your database, if themes and modules not possible due to the new structure).

  • Like 1
Link to comment
Share on other sites

Why import ? PS 1.6. is not discontinued, and I'm sure when PS 1.7. is released they will find a way for to upgrade (at least your database, if themes and modules not possible due to the new structure).

 

Why import? Because I might want to upgrade my shop to 1.7 in the near future and from everything I'm reading, there is no easy upgrade option from 1.6 to 1.7. So if I create a new store using 1.7, I want to know if I'm able to import my orders, customers, products and categories from my 1.6 store. 

  • Like 1
Link to comment
Share on other sites

  • 3 weeks later...

Added a few more Build articles:

Link to comment
Share on other sites

 

Added a few more Build articles:

 

 

Good job, i will install p1.7 at my home. I will try give you feedback.  :)

Link to comment
Share on other sites

Questions! Answers!

  • Will the symfony bring an other file/image system or will you try to keep  the existing one ?
    As far as I know, the existing one is still valid.
  • Will PrestaShop 1.7 always require URL rewriting? I'm asking because product and module page are using the "new" request routing f.e. /backoffice/module/catalog
    The new back office pages will work even if URL-rewriting is not activated -- but that will require a small modification to your virtual host or .htaccess file.
    Here's how to do it for nginx.

  • did you ever analyzed PS 1.7. with one SEO tool like GTMETRIX.
    We're working on performance and accessibility right now. As far as I know, SEO is more of a module-territory thing (same with WordPress), but the basics should be there. If not, please make a pull request in GitHub!

  • Is it possible to at least import the orders, customers, products and categories from 1.6 to 1.7?
    Yes. The database scheme remains globally the same, and entities will be compatible between 1.6 and 1.7.

Link to comment
Share on other sites

If there are changes on database (i supposed that it changed between 1.6.x.x and 1.7.x) can you, please, specify those changes? I think developers or users need those info explained as easy as possible to take it like referrence, cause if theres any explanation of that type we have to search for hours or read unsmokable blocks of info. I need it for dummies to not waste my time on it (and it's supposed that you have that change log for yourselves)

 

f.e. table ps_images (id, img, id_product) has changed to ps_product_images (id, img, id_product) and ps_img has been set to store global imgs with cols (id, img, id_block).

 

I know there is a change.log with all info in official page, but it's very very hard to know those changes, and it's being harder when there are more than one update between actual and latest. official change.log need a category (database changes). 

 

 

Thanks

Link to comment
Share on other sites

What would be nice is if Prestashop could not only include the minimum configuration to run, but also a recommended configuration, which would have been tested by the PS team. That way the merchants among us, who don't feel comfortable experimenting with tech settings, could take this to their hosting company and say "here, can I get this on my VPS / dedicated account?

Link to comment
Share on other sites

hello,

I installed today 1.7 alpha 4.0 in a directory (ex. http://myname.domain/prestashop17) . 2 links from back office are not working.

 

http://myname.domain/prestashop17/admin123/module/catalog not working

also http://myname.domain/prestashop17/admin123/product/catalog

 

it redirect me to http://myname.domain/index.php

 

I use php-fpm with nginx.

Any help is appreciate.

 

thank you

Link to comment
Share on other sites

Hello,

since Prestashop 1.6.1.1. when I want to install a clean app, the installation process is stopped by a bug when creating demo data in czech language. Now I tried this alpha version and it still the same bug (screen 1). When I change install language to English it is installed without any issue, but everything is in english and must be changed to CZ. Could you look at this problem? I would say it is something with czech language, but the database language is UTF-8 (screen 2; "znaková sada=character set", "porovnání=collate"). Thanks a lot.

Link to comment
Share on other sites

Please, improve the creation of CMS pages!! Now cms pages are so basic.....I think that is the most weak point of prestashop in comparison to wordpress. Indeed that is one point that is making me deciding to use wordpress in my next proyect as corporative part is very important. Any news about cms pages?

Link to comment
Share on other sites

Please, improve the creation of CMS pages!! Now cms pages are so basic.....I think that is the most weak point of prestashop in comparison to wordpress. Indeed that is one point that is making me deciding to use wordpress in my next proyect as corporative part is very important. Any news about cms pages?

 

Hi Xavier,

I just wanted to let you know as a simple user that indeed the 2 big milestones of Prestashop are:

1. CMS pages (creating, insertion of content, styling and so on)

2. Checkout process (please look at Magento 2, Woocommerce or Shopify, you can take the good things from there and make the best checkout process on Presta), OPC has to be a default feature, not a module thing.

 

p.s. OPC i mean a real One page checkout, not the one that is now in ps1.6

Edited by Leo Ce (see edit history)
  • Like 1
Link to comment
Share on other sites

Hi Xavier,

I just wanted to let you know as a simple user that indeed the 2 big milestones of Prestashop are:

1. CMS pages (creating, insertion of content, styling and so on)

2. Checkout process (please look at Magento 2, Woocommerce or Shopify, you can take the good things from there and make the best checkout process on Presta), OPC has to be a default feature, not a module thing.

 

p.s. OPC i mean a real One page checkout, not the one that is now in ps1.6

 

Totally agree

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...