Jump to content
Antoine F

PrestaShop 1.7 is now available!

Recommended Posts

At The Moment im on 1.6

 

I need

PayPal

eBay V2 2.x (IT works with 1.7)

Wire

German law / european law!

 

Anyone a idea about using 1.7 in real ?

Share this post


Link to post
Share on other sites

Yes, i saw. It is definitely great work! Alreday installed it on my server and plan to play with it enough time.

However, i meant a compiled PC app for the first place, having in mind "disconnected data model" - when you make all changes at local clone of database, and then just push final version back to server. IMHO, such bulk update could drastically increase speed and safety and also give more or less obvious advantages.

Share this post


Link to post
Share on other sites

No one with a decent IQ will go production with a 1.7 to date

Perhaps, you'll call me an idiot, but i suppose to start within 1-2 weeks. The only thing remains - to connect payment aggregator to my shop.

Share this post


Link to post
Share on other sites

Perhaps, you'll call me an idiot, but i suppose to start within 1-2 weeks. The only thing remains - to connect payment aggregator to my shop.

 

Well, seems like you are an adventurer instead of an ecommerce technician, you may not have collect enough datas before trying to use a tool wich is not meant to be used on production.

 

Now...why not ?! 

If your buisiness is starting you have nothing to loose anyway, except time maybe.

Edited by Tweb

Share this post


Link to post
Share on other sites
Hello, We are all cobayes :) through the updates of the 1.6 we participated in the 1.7 ? Some sell modules and themes while the 1.7 is not stable not serious
Edited by Soyons zen

Share this post


Link to post
Share on other sites

 

Hello, We are all cobayes :) through the updates of the 1.6 we participated in the 1.7 ?

 

 

What a frenglish, nice one Mister Be Zen :P

 

You can be a Ginea pig if you want to, isn't it a cute animal by the way ?

Share this post


Link to post
Share on other sites

Quel franglais, nice one Monsieur Be Zen :P

 

Vous pouvez être un cochon Ginea si vous voulez, est-ce pas un animal mignon par le chemin?

:P je suis nul en anglais

Edited by Soyons zen

Share this post


Link to post
Share on other sites

Little feedback on 1.7.2: during importing the a csv-file i've got wrong behavior: despite i've chose to ignore the product IDs from CSV, the import procedure actually imported that IDs - and overwrote existing products with new data. Very sad.

Share this post


Link to post
Share on other sites

I have been trying to install 1.7 from the first version. I could always complete the install, but could never reach back office. The frontend always worked fine but the backend would redirect back to frontend shop.

 

I feel a little foolish but I finally noticed an htaccess file in the admin dir. So, if anyone else out there is installing to IIS and using an htaccess module made by Helicon. The quick fix is to remove the htaccess file from admin dir.The root htaccess file works as it should no problem there. 

 

It looks like a few of the lines in the admin htaccess are for better security, so I'll put it back after I have time to figure out the line that is breaking Helicon.

 

So, here is what the default install looks like,

post-358011-0-95562900-1503784724_thumb.jpg

Share this post


Link to post
Share on other sites

I should add, this default install is not using any third party cache. Just the smarty cache and PHP 5.6 opt opcache. My server also uses Google Pagespeed modules that automatically converts images, and optimises js & css.

Share this post


Link to post
Share on other sites

I should add, this default install is not using any third party cache. Just the smarty cache and PHP 5.6 opt opcache. My server also uses Google Pagespeed modules that automatically converts images, and optimises js & css.

Well it is known that Google PageSeed is making some problems on several servers. Deinstall and try. Just with php 5.6.30 and opt cache optimized I have no problems to call and use the back-office. It must be something not common you are using on your server.

 

cache optimization I've done:

opcache.revalidate_freq=0
opcache.validate_timestamps=0 (comment this out in your dev environment)
opcache.max_accelerated_files=7963
opcache.memory_consumption=192
opcache.interned_strings_buffer=16
opcache.fast_shutdown=1

Share this post


Link to post
Share on other sites

You misunderstand, I am not posting that I have a problem with back office. I'm posting that I fixed my problem with back office. I also posted that PS 1.7 seems to work well out of the box. :)

Share this post


Link to post
Share on other sites

Well in fact I did not understand your topic #531 at all. Some wired mixing things... You are talking about IIS and .htaccess. Windows Servers do not understand .htaccess files and they will never work on Windows Servers. This is unix world. For to manage rewrites IIS need a web.config file. So you need to "translate" unix .htaccess-file into a web.config.

Share this post


Link to post
Share on other sites

lol ... :)

 

IIS can use htaccess the same way that Apache makes use of it. You install a module.

 

http://www.helicontech.com/ape/

IIS natively in fact cannot manage .htaccess. I stopped to use IIS with version 6. This module I didn't know and in principle it is doing nothing as to "translate" .htaccess which cannot be managed by windows servers. ;) 

I hate Windows, as microsoft has nothing free, which is by simple integrated natively in Unix and for free.

Share this post


Link to post
Share on other sites

IIS - lol

Windows Server - re-lol

Unfortunately at mid and big sized companies a standard....

But as I said: I hate adhesion contracts, and as you can see Microsoft is backing down with his arrogant politic for to maintain his competitive abilities and don't loose more customers. But this "sign of peace" is again not for free.... module is paid one.

Share this post


Link to post
Share on other sites

No internet has been dominated for decades by linux standards. Only "peeky" corporation refuses to have specialists for this purpose. And invent some "evangile" to support their stuborn approach.

What next? Have the database on an SQLServer, and the ServerSide script engin been dotnet?

Sounds like they want something which is not a free LAMP e-commerce solution, at least not Prestashop

Share this post


Link to post
Share on other sites

@ doekia - at least you are right. It is strange that Windows users are using a 100% Prestashop unix solution. Perhaps there is nothing suitable for Windows world ? And windows with exchange, with by the way is nothing more than a paper construct and window-dressing, dominates the network world. I hate Windows for several reasons, and exchange is only a bumpy excuse for something microsoft could not solve better. For me on these modern days with other better solutions windows has no existential reasons anymore. Their development is only looking for what others are doing better and adopting than these solutions, or creating paid modules for to build bridges. But the primary intention is to bind customers by paid adhesion contracts.

 

Prestashop will never run without any tricky solutions out of the box on a Windows Server. Unix and Windows are complete diff. worlds and standards.

Share this post


Link to post
Share on other sites

...

Prestashop will never run without any tricky solutions out of the box on a Windows Server. Unix and Windows are complete diff. worlds and standards.

The problem here is not about what solution/issues Microsoft world represent. It is the end-user company that wan't to open a web vitrine on a solution with is *nix based on a *nix dominated word but want to to this using Windows. They want to participate a truck race with a motorbike and seems not to comprehend why it will fail.

Share this post


Link to post
Share on other sites

PS 1.7.2.2 was the version that finally turned the corner for me.

 

Upgraded to PS 1.7.2.3 today no trouble. 

 

Testing on PHP version: 7.1.9

MySQL version: 10.3.1-MariaDB

Windows Server 2016

 

 

Google page speed score of 100% using PHP OpCache and Google's pagespeed modules installed.

 

With HTTP/2 on SSL no longer need CCC of CSS & JS. No need to inline CSS or JS. 

 

With more and more hosting now using HTTP/2 we really need to start thinking differently about optimisation. Prestashop needs to start encouraging best practices for current optimization in the back office.

 

I love the Classic theme and plan to stick with it. 

Share this post


Link to post
Share on other sites

Any idea for sucessful upgrade from 1.6 to any version of 1.7? That special version of autoupgrade hangs on DB upgrade...

Share this post


Link to post
Share on other sites

PS 1.7.2.2 was the version that finally turned the corner for me.

 

Upgraded to PS 1.7.2.3 today no trouble. 

 

Testing on PHP version: 7.1.9

MySQL version: 10.3.1-MariaDB

Windows Server 2016

 

 

Google page speed score of 100% using PHP OpCache and Google's pagespeed modules installed.

 

With HTTP/2 on SSL no longer need CCC of CSS & JS. No need to inline CSS or JS. 

 

With more and more hosting now using HTTP/2 we really need to start thinking differently about optimisation. Prestashop needs to start encouraging best practices for current optimization in the back office.

 

I love the Classic theme and plan to stick with it. 

 

We are having great success (fun).  We have done select projects with 1.7 all with high quality 3rd party themes..

 

for dev we see finally a sensible framework we can better work  with.  all our new dev (widgets) are 1.7 centric....we have taken old works and made better works in 1.7....

 

for me, I'm happy to see a company  burn down the house to get better frameworks....happy day from KC 

Share this post


Link to post
Share on other sites

here is a shop we upgraded from 1.3!  it was 'horrible'.

 

https://weaverstreet.prestaheroeslab.com/  we installed/configured a Leo 1.7 Theme.  Note because of the difference between 1706 and 1710, make sure theme as dev on 1710 else you  will need to upgrade some .js files.  Otherwise we were happy to take somethinig fugly and make it great again. IMHO 1706 was boo boo by PS but I love how they 'carry on' to rectify.  one thing we suggest everyone to do  is where there are phone numbers / addresses,  link these to something that calls or pulls up map, especially  important for mobile,  all our client shops do. :)

Edited by El Patron

Share this post


Link to post
Share on other sites

here is a shop we upgraded from 1.3!  it was 'horrible'.

 

 

lol ... I can image they were happy to learn that they no longer needed to dial in through AOL! :)

 

Not to mention the new color images! Much better than the old black & white

Share this post


Link to post
Share on other sites

×