Jump to content
magali ferber

1.6.0.11 Upcoming Release

Recommended Posts

Hi there!

 

As many of you Beta testers noticed, the cloud version of PrestaShop runs on v1.6.0.10. When we launched this beta program on the cloud, there had been many improvements to the 1.6 branch of PrestaShop since 1.6.0.9. It seemed natural that we would merge them and have this new program run on the latest version of PrestaShop, which we identified as 1.6.0.10.

 

Since then, we’ve fixed many bugs and improved many features. Which is why next version of PrestaShop is going to be version 1.6.0.11, for both projects. Public release of 1.6.0.11 and upgrades of the stores hosted by PrestaShop with the Beta program will be happening during the first week of January.

 

Here is the package for PrestaShop 1.6.0.11, which we invite you to test it in the upcoming week. Keep in mind that the codefreeze deadline is scheduled for Monday, December 15th.

 

We highly encourage you to explore this new version, try it and bring back your feedback, which is extremely valuable to us. Please do so through the PrestaShop 1.6 Project on the Forge.

 

You can find the changelog doc inside the package, but here are the most significant changes that we have made:

 

  • Localization pack for Costa Rica

  • Order creation and management through the Back Office, even in catalog mode

  • Improvement of specific price reductions and price management, before and after tax

  • Improvement of Wishlist module

  • Update of taxes and states in Canada

  • Huge improvement in taxes and number rounding

  • More than 200 bugs fixed

 

All of this was made possible thanks to you! You are the essence of our company’s improvements, and we trust you to help us bring our Community the very best. Thank you for your time and dedication, for your feedback, for your collaboration and for being the most valuable element of our amazing Community.

 

If you have any questions, do not hesitate to contact us. We are here for you!

Cheers!

  • Like 9

Share this post


Link to post
Share on other sites

Thanks for the information.

 

I read through the docs/CHANGELOG.txt in the zip and the number of fixes and improvements is *huge*. You guys have really been busy.

 

This will be the best Prestashop release ever :)

 

Cheers, Robert

  • Like 1

Share this post


Link to post
Share on other sites

That sounds great Good Job Team.

 

 

Comment: I  didn't see any changes made to the one page checkout, I thought that there was going to be improvements to the OPC in the next release. I was hoping that users did not need to click "save" in the OPC..This has now more than 800 votes and is one of the top 3 most requested feature for PS here :  http://feedback.prestashop.com/forums/124931-general

 

Are any of the top 3 requested features in .11 ? I don't see them being added in the release notes.

 

Also still no change in the BO to remove the DOB, Salutation & "Receive Email from partners", As well as adding customized fields.  This still painstakingly needs to be done in code.  If anything this small feature or fix,  I hope is taken care of in the coming release.

 

Thanks for all your hard work.

 

RICKY

Edited by ricky11 (see edit history)
  • Like 2

Share this post


Link to post
Share on other sites

Parsifal and Roband, we are pleased to see you are excited about our new release!! Keep the cheers! Great things are coming soon too!!!

 

Ricky regarding your comments of the feedback.prestashop, I have consulted specifically those improvements that you mentioned with our dev team, and they told me that for this release they had strictly focused on the Taxes issue suggested by the community, which at the time seemed to be the most critical one. Our team has noted all of your feedback from the "Vote to improve PrestaShop" program, and we thank you very much for your suggestions. We are incorporating older and critical requests first, but we will take your suggestions into consideration for our future improvements. As for the second part of your message, we didn't quite understand what you mean by: Also still no change in the BO to remove the DOB, Salutation & "Receive Email from partners", As well as adding customized fields.  This still painstakingly needs to be done in code.  If anything this small feature or fix,  I hope is taken care of in the coming release.

If you could please elaborate further, that will help us a lot!

 

Thank you all!!!

 

Cheers!

Share this post


Link to post
Share on other sites

Hi,

 

Please make a provision in the coming release to add delete fields in customer registration field as this is very common problem of most of the people who are managing there own websites and not having an experience of writing codes.

 

Thanks 

Share this post


Link to post
Share on other sites

Hi!

 

Preview of CMS pages does not work.

 

Prestashop 1.6.0.11

 

Best regards

 

MacRoy

Share this post


Link to post
Share on other sites

Hi!

 

Preview of CMS pages does not work.

 

Prestashop 1.6.0.11

 

Best regards

 

MacRoy

I have tested , it work for me. Do you have any pop up blocker in your browser :)

Share this post


Link to post
Share on other sites

Hi!

 

You actually right!

 
It was my browser that blocked the page without informing me about it.
 
The case resolved.  :D
 
Regards
 
MacRoy
  • Like 1

Share this post


Link to post
Share on other sites

Hello

I'm looking for list of effected files+folders for price round up. Round up was built great for this version; actually only version that it works.

Edited by bitpixel (see edit history)

Share this post


Link to post
Share on other sites

Is 1.6.0.11 stable for production ? I'm starting a new project today and was wondering if it would be better to start at 1.6.0.9 and wait for public release to upgrade. Thanks.

Share this post


Link to post
Share on other sites

 As for the second part of your message, we didn't quite understand what you mean by: Also still no change in the BO to remove the DOB, Salutation & "Receive Email from partners", As well as adding customized fields.  This still painstakingly needs to be done in code.  If anything this small feature or fix,  I hope is taken care of in the coming release.

If you could please elaborate further, that will help us a lot!

 

 

 

He is talking about an option to remove those items on registration or checkout. The date of birth, the mr / ms /mrs and the email sign up for the partners.

  • Like 2

Share this post


Link to post
Share on other sites

Hi ringerce,

 

1.6.0.11 is a beta version for now. I advise you start with a 1.6.0.9 and update to 1.6.0.11 when it's out.

 

Thank you for your reply.

Share this post


Link to post
Share on other sites

Hi, i'm on testing

 

But when i want to update a native module (bankwire for example) ->  Error: the archive is corrupted... :(

If  i load a module from my bo, it's ok.

Share this post


Link to post
Share on other sites

Hi!

 

Will PrestaShop 1.6.0.11 be released this week?

 
I hope and believe so.  :rolleyes:
 
 
Best regards
 
MacRoy

Share this post


Link to post
Share on other sites

Hi!

 

Do you have any updates before then?

 

 

Regards

 

MacRoy

Share this post


Link to post
Share on other sites

I work with PS 1,5 years now.
I started as a novice, being annoyed by all the small errors, because my webshop is my lifeline and primary income.
During the 1,5 years of experience, i've met other people online through the community.

Where i got help at first, i'm starting to give help to others now, on a starter level.
I'm leveling up, and i like it.

Thank you Prestashop, for giving me direction and advice. Thanks to you, i moved from PS 1.5.x to PS 1.6.x and am helping others in starting their PS webshop too.

Looking forward to all the fixes. I'm a big fan of PS today. Thanks!!

Edited by pandorrah (see edit history)
  • Like 3

Share this post


Link to post
Share on other sites

Hi there,

 

I have just test it, and there is some problem with theme installations. When i click add new theme, it shows that the theme is installed, however only the modules folder from the theme archive is uploaded, the theme folder itself is missing from the /themes/newtheme

This result in error 500 on the front page.

 

I have tried several themes from 1.6.0.9, same result with all of them. As this is 1.6.0.11 can it be reported to the forge?

  • Like 1

Share this post


Link to post
Share on other sites

Hi there,

 

I have just test it, and there is some problem with theme installations. When i click add new theme, it shows that the theme is installed, however only the modules folder from the theme archive is uploaded, the theme folder itself is missing from the /themes/newtheme

This result in error 500 on the front page.

 

I have tried several themes from 1.6.0.9, same result with all of them. As this is 1.6.0.11 can it be reported to the forge?

I got similar results with my testings. I disabled seo and/or regenerated .htaccess and product pages started showing up. Please let me know if you find a solution to this.

Share this post


Link to post
Share on other sites

Hi there,

 

I have just test it, and there is some problem with theme installations. When i click add new theme, it shows that the theme is installed, however only the modules folder from the theme archive is uploaded, the theme folder itself is missing from the /themes/newtheme

This result in error 500 on the front page.

 

I have tried several themes from 1.6.0.9, same result with all of them. As this is 1.6.0.11 can it be reported to the forge?

 

Hi guys! Thanks for the report, this bug was fixed a few days ago, you won't have the issue on the public release :)

  • Like 1

Share this post


Link to post
Share on other sites

Hi Xavier.

 

Do you happen to know if there are any reported but unresolved showstopper/critical bugs in the current 1.6 Github branch?

 

Thanks.

Share this post


Link to post
Share on other sites

Hi guys! Thanks for the report, this bug was fixed a few days ago, you won't have the issue on the public release :)

Hi,

 

Please, where I can download a 1.6.0.11 functional release?

 

 
I downloaded from github and installation works fine but no installed modules and products.

Share this post


Link to post
Share on other sites

I downloaded from github and installation works fine but no installed modules and products.

 

Check this: http://www.prestashop.com/forums/topic/369702-is-1609-already-fixed/?do=findComment&comment=1834323

 

If you are not familiar with git and you are on Windows OS, you can make your life easier by using Github's desktop client:

https://windows.github.com/

This program will also register itself as the default handler for github-windows: // type of URIs.

 

Then, from PrestaShop's main repo page:

https://github.com/PrestaShop/PrestaShop

you just click on the "Clone in Desktop" button and the GitHub client will take charge from there and clone the repo on your local hard drive (including a proper recursive clone to include all modules).

 

 

If all of the above sounds too much, you can try this 7-zip package I made some hours ago from GitHub (GMT+3):

https://drive.google.com/file/d/0B2yXNy5NehB2VXBLRWktZHlpMGM/view?usp=sharing

Edited by parsifal (see edit history)

Share this post


Link to post
Share on other sites

Perhaps this is theme related error:

Fatal error: Uncaught --> Smarty: Missing template name <-- thrown in /home/********public_html/tools/smarty/sysplugins/smarty_internal_template.php on line 678

 

occurs in 1.6.0.11

 

Am I correct? Because default theme works just great.

Share this post


Link to post
Share on other sites

Hi there,

 

I have just test it, and there is some problem with theme installations. When i click add new theme, it shows that the theme is installed, however only the modules folder from the theme archive is uploaded, the theme folder itself is missing from the /themes/newtheme

This result in error 500 on the front page.

 

I have tried several themes from 1.6.0.9, same result with all of them. As this is 1.6.0.11 can it be reported to the forge?

 

Hi I believe this has been fixed since in 

 

https://github.com/PrestaShop/PrestaShop/commit/bdec19ea174a07325927007cc43aeee4e239cb06

 

and https://github.com/PrestaShop/PrestaShop/commit/78adec942bbbf9026c5d25f76c2f93834e6ad061

 

https://github.com/PrestaShop/PrestaShop/commit/c80647195587289b3620738f702385a63ce353ef

 

Please @DreamTheme do not hesitate to post on the forge if needed.

 

Regards

Share this post


Link to post
Share on other sites

Little side question - is there a fix for the dashboard (nearly all of the modules don't work and the new order since the update from 1.5.6.2 to 1.6.0.9 don't appear there).

Is something fixed in v.1.6.0.11?

Share this post


Link to post
Share on other sites

@dambie This error is really unfixable with the current bootstrap theme, it was written incorrectly. 

Share this post


Link to post
Share on other sites

Comment: I  didn't see any changes made to the one page checkout, I thought that there was going to be improvements to the OPC in the next release. I was hoping that users did not need to click "save" in the OPC..This has now more than 800 votes and is one of the top 3 most requested feature for PS here :  http://feedback.prestashop.com/forums/124931-general

 

Agree. The checkout process is the worst part of Prestashop - and it's the most important part of a webshop! Was really hoping for improvements :-(

  • Like 3

Share this post


Link to post
Share on other sites

hi there 

 

i hope you will fix the modules for ssl padlock problems and hope to see that will be solved with new version of prestashop

 

 

 

 

 

Regards

Matt

Share this post


Link to post
Share on other sites

Can I ask if we can do little modification on product image add - can we automatically upload the images after we select them from the dialog window (as it was in 1.5). This will really speed up the manual product upload time.

Edited by the.rampage.rado (see edit history)
  • Like 1

Share this post


Link to post
Share on other sites

Hi!

 

Have found a bug.

 
When I go to the translations and choose for example the translation of installed modules, it shows the total lacked expression = 0
But when I scroll down, there are lots of expressions that are marked in red, not at all translated!
 
I have done a new clean installation of the latest Prestashop 1.6.0.11 (December 12.)
 
 
Best regards
 
MacRoy

Share this post


Link to post
Share on other sites

Hi MacRoy,

 

Which language are you talking about please?

Share this post


Link to post
Share on other sites

Hi!

 

Sorry I forgot to write it.

 
Swedish!
 
Best regards
 
MacRoy
  • Like 1

Share this post


Link to post
Share on other sites

Partial refund is totally messy.

 

1/ Order = 1 x 18 + 1 x 23.80 - 5% voucher(2.09) = 39.71 paid

2/ Partial refund per quantity (1) the product at 23.80 + create a voucher

 

=> No order-slip created

=> Voucher created at 23.80 (should be 22.61)

     because 18 - 5%(0.9) = 17.10 and 39.71 - 17.10 = 22.61 !!

Share this post


Link to post
Share on other sites

Partial refund is totally messy.

 

Hi,

 

Sorry fixes for that will be included in 1.6.0.12, not 11. Did you test a current git version about this matter ?

 

Regards

  • Like 2

Share this post


Link to post
Share on other sites

Hi,

 

Sorry fixes for that will be included in 1.6.0.12, not 11. Did you test a current git version about this matter ?

 

Regards

 

Is there any dead line for 1.6.0.12 or is this a diplomatic way of saying in some incertain (far away) future.

 

This problem that was not present in 1.4 emerged during 1.5 and been reported since ages marked either no fix, no changes, no reproduce:

 

http://forge.prestashop.com/browse/PSCSX-3709 marked no changes, but comment let assume it been fixed

http://forge.prestashop.com/browse/PSCFV-11428 marked fixed

http://forge.prestashop.com/browse/PSCSX-3622

http://forge.prestashop.com/browse/PSCFV-11413

http://forge.prestashop.com/browse/PSCFV-12507

http://forge.prestashop.com/browse/PSCSX-3511

 

http://www.prestashop.com/forums/topic/353083-remboursement-partiel/

 

 

Those issues should be mark critical amongst the critical - this is the core purpose of the solution to provide the basic of commerce daily action and return/refund are really THE tasks for which the solution should be unquestionable, reliable and stable.

  • Like 1

Share this post


Link to post
Share on other sites

Those issues should be mark critical amongst the critical - this is the core purpose of the solution to provide the basic of commerce daily action and return/refund are really THE tasks for which the solution should be unquestionable, reliable and stable.

 

Fully agree! The 100+ PrestaShop-customers we support often have problems with this function because it does not work correctly or or it's confusing ( http://forge.prestashop.com/browse/PSCFV-11483 ). Our general workaround since PS 1.5: cancel the order and create a new one in BO. Then go to PayPal or whatever site and correct the amount manually (reimbursement).

  • Like 1

Share this post


Link to post
Share on other sites

Lets be frank here people. The issue is that the last two major versions were pushed out the door so fast without input of merchants and very little outside developer input. There are bugs that are not fixed that have been around since version 1.4. There are a whole host of features that 1.4 had that none of the later version had. IE, renaming of images, custom htaccess directives, and better voucher product exclusion rules. 

 

The issue is the focus, it is no longer driven by the community, it is driven by the internal team to be what they want it to be. 

  • Like 11

Share this post


Link to post
Share on other sites

Lets be frank here people. The issue is that the last two major versions were pushed out the door so fast without input of merchants and very little outside developer input. There are bugs that are not fixed that have been around since version 1.4. There are a whole host of features that 1.4 had that none of the later version had. IE, renaming of images, custom htaccess directives, and better voucher product exclusion rules. 

 

The issue is the focus, it is no longer driven by the community, it is driven by the internal team to be what they want it to be. 

 

Which ... means ...?

 

In a nutshell, maybe as a sort of provocative intervention ;) :

  • That the damage done by an insular developers team already has passed the point of no return after focusing on less important issues over a period of at least two major releases?
  • Or that there's enough substance and innovational potential left for a successful reconception of Prestashop?

Assumed, of course, the French developers (or whoever) are willing and determined for a turnaround.

Edited by eleazar (see edit history)

Share this post


Link to post
Share on other sites

Official translations in version 1.6.0.10 has not been communicated to version 1.6.0.11
https://crowdin.com/project/prestashop-official/pl

 

1.6.0.11 = 1.6.0.9 an error
Translations, corrections 1.6.0.10 loss for all countries.

 

Please translation version 1.6.0.10 to version 1.6.0.11
Translation version 1.6.0.9 to version 1.6.0.11 is a mistake.
The loss of many translations and corrections.

 

Best Regards
Karol

Share this post


Link to post
Share on other sites

@karolwild:

Install locally a github version of PS in your language. Go to Localisation / Translation, then export your language for the theme default-bootstrap. This should generate a zip you'll be able to re-import within your 1.6.0.11. If the crowin archive matches it may well be a better candidate to import.

 

The language archive has not been yet published since the release is not yet published per say.

While migrating from release n to n+1 translations are not updated since this can cause customized ttranslations to be lost. This action is at shop owner discretion to update the language pack. (but the pack is not yet at 1.6.0.11 since the team may still need to change some strings until the release date)

 

If 1.6.0.9 matches with a good translation archive, let start with that and do an upgrade. This normally should left the good translation intact - the new strings will be missing however. But only thoses will need special attention.

 

 

Hope this answers your question

  • Like 2

Share this post


Link to post
Share on other sites

This is not a good solution.
It is the loss of all translations from version 1.6.0.10
Future Translations 1.6.0.11, 1.6.0.12 you have to do it again.

 

 

It is not a problem to my shop.
The problem is the official translation.
We need to unnecessarily repeat.

Edited by karolwild (see edit history)

Share this post


Link to post
Share on other sites

Hi karolwild,

 

In theory translations should be ported automatically from 1.6.0.10 to 1.6.0.11 (and from any version 'n' to any version 'n+1' when we publish it).

In practice you're unfortunately right: it seems Crowdin sometimes makes a "mix" of versions when porting the translations.

 

I'm looking at the options to fix this, and hopefully nobody will need to do the translations again.

 

Please give us some time to try and find the best solution, and thank you for reporting the issue!

  • Like 3

Share this post


Link to post
Share on other sites

Hi, to anyone interested in the translation thing:

  • we've removed version 1.6.0.9 from Crowdin (it was getting old anyway), seems like it was the only way to clean things up
  • in the future, we'll try to have at MOST 2 versions on Crowdin to make things easier for the system: most of the time there will be only the latest stable version, and during release periods, we'll add the upcoming version too

We'll switch to this new workflow right after 1.6.0.11 is out, which means we will remove 1.6.0.10, leave only 1.6.0.11 for a while, and then add the next version a while before the next release.

 

The should be much less opportunities for translations to propagate to the wrong version :)

  • Like 1

Share this post


Link to post
Share on other sites

Perfect, François! ;)

 

Anyway, from my experience a decision to normally provide just a single translation seems to be the best way to prevent trouble. I'd suggest to totally abstain from adding the upcoming version, even during release periods.

 

Wouldn't it be easier to start a new project like it was before Crowdin? The baseline should always be the former translation release so that nobody would be forced to start from the beginning. This would help to avoid automatic changes of previous releases due to identical translation-IDs. Shit happens, and iIt's a simple fact that most of the guys volunteering in translation at Crowdin pick up random items while ignoring context and release.

  • Like 1

Share this post


Link to post
Share on other sites

Hi!

 

Will PrestaShop 1.6.0.11 be released next week?

 

I hope and believe so.

 

 

Best regards

GEORGE

Share this post


Link to post
Share on other sites

No, the next release will be the 1.6.0.12 :)

  • Like 1

Share this post


Link to post
Share on other sites

Hi, to anyone interested in the translation thing:

  • we've removed version 1.6.0.9 from Crowdin (it was getting old anyway), seems like it was the only way to clean things up

 

Makes no sense! 1.6.0.9 is the current, official version! You can't remove that - well, you have, but you shouldn't.

 

Now my changes will not have effect until you release 1.6.0.11 and I - and other shop owners - update to that version.

 

You must always keep the current, official version.

 

Regards,

Morten, Danish proofreader

Edited by Morten Borg (see edit history)

Share this post


Link to post
Share on other sites

No, the next release will be the 1.6.0.12 :)

Where did you get this information ?

Share this post


Link to post
Share on other sites

"We do not have time to include this fix in 1.6.0.11 release" is not the same as saying "The next official release will not be 1.6.0.11 but 1.6.0.12"... :)

Share this post


Link to post
Share on other sites

First post in this topic says it will be released this week.

  • Like 1

Share this post


Link to post
Share on other sites

 

No, the next release will be the 1.6.0.12 :)

Where did you get this information ?

 

This information is not correct. As I said, next version is 1.6.0.11, out this week.

  • Like 5

Share this post


Link to post
Share on other sites

This information is not correct. As I said, next version is 1.6.0.11, out this week.

 

Yay! Finally. It will be really nice to have some road map for next releases... if you plan to do only bugfixes or some new features etc.

  • Like 1

Share this post


Link to post
Share on other sites

What's the interest to publish an already obsolete version ?

Share this post


Link to post
Share on other sites

What's the interest to publish an already obsolete version ?

 

This is not "obsolete" version IMO. Check their Github and "Release" branch and how it works.

Edited by Krystian Podemski (see edit history)

Share this post


Link to post
Share on other sites

I know how works a release, but I do not still understand the interest to publish a version about which we know that it contains bugs which are corrected. The next version being planned to go out in 2 months.

  • Like 1

Share this post


Link to post
Share on other sites

save button process always running, please fix this

 

im indonesian

The same problem was reported here

Share this post


Link to post
Share on other sites

is safe to migrate the previous version to this new version, is that I have a store up and running in version 1.6.0.9 ?

 

 

I have those Link1   Link2  two problems, so make backups.

Edited by Dreamtheme (see edit history)

Share this post


Link to post
Share on other sites

There is a big issue with prestashop 1.6 CSS compile. seriously, still not fixed?

 

http://forge.prestashop.com/browse/PSCSX-2043

 

It is fixed: http://forge.prestashop.com/browse/PSCSX-2043?focusedCommentId=103077&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-103077 :)

 

@dambie This error is really unfixable with the current bootstrap theme, it was written incorrectly. 

 

Not true, problem was with css compiler > http://forge.prestashop.com/browse/PSCSX-2043?focusedCommentId=103077&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-103077

  • Like 1

Share this post


Link to post
Share on other sites

Hmm, the release was delivered on January 7th, It had to be a very big foie gras...

Edited by Eolia (see edit history)

Share this post


Link to post
Share on other sites

Come on Eolia, you know that the 1.6.0.11 was code frozen long before the holidays. You're a competent developer and you know how versioning works, trolling is unnecessary.
 

Keep in mind that the codefreeze deadline is scheduled for Monday, December 15th.

  • Like 4

Share this post


Link to post
Share on other sites

Even though you don't merge new, external development after a codefreeze, you still can (and must) apply internal fixes. 

 

Again, I know that you're highly competent and that you know very well how that works :)

Share this post


Link to post
Share on other sites

Ha, the code is frozen... http://scm.prestashop.com/changelog/~br=1.6,startDate=2014-12-15,endDate=2015-01-07/PrestaShop_v.1.5

 

An example: AdminStatsController.php is different and has been edited between december the 15th and the official release.

 

No doubt I'm stupid.

 

Have a nice day.

 

Your link is for ps 1.5 not for ps 1.6. My solution for IE issue still need some improvements to fits prestashop standards(older php version) so they need time to apply it in realase, Please by patient they doing great job

  • Like 1

Share this post


Link to post
Share on other sites

Even though you don't merge new, external development after a codefreeze, you still can (and must) apply internal fixes. 

 

Again, I know that you're highly competent and that you know very well how that works :)

OK Xavier I keep silent and I wait for the following release.

 

Your link is for ps 1.5 not for ps 1.6. My solution for IE issue still need some improvmants to fits prestashop standards(older php version) so they need time to apply it in realase, Please by patient they doing great job

No, consider good and do not trust the title. The 1.5 version died.

Share this post


Link to post
Share on other sites

In prestashop 1.6.0.11 one client inform us that the product page left or right column is not able to change form theme configuration page. After investigate in database i saw that Prestashop add shop column but product page and some other page are missing from that table meta. 

 

It is prestashop 1.6.0.11 new architecture or missed that.

  • Like 1

Share this post


Link to post
Share on other sites

Thanks to iqit-commerce, not only have the best theme for prestashop but they also have solved a really important bugs (the fix is not an easy one)

  • Like 2

Share this post


Link to post
Share on other sites

Hi!

 

Thank you! It looks promising!

 

Best regards

 

MacRoy

Share this post


Link to post
Share on other sites

Hi to all,
I would like to open a new store with PrestaShop, with version 1.6.0.9 I have always been happy even if I do not have great technical skills I had developers (type ThemeFuse and iqit-commerce) that they have been able to solve every problem I've had.
You recommended to install the version 1.6.0.11 or continue to use version 1.6.0.9 for a few months? :)

I would not have problems like these:
 

....It is prestashop 1.6.0.11 new architecture or missed that.

Edited by framarfre (see edit history)

Share this post


Link to post
Share on other sites

Hi!

 

I recommend you to install the latest PS version 1.6.0.11!

 
It looks to be very stable and bug free, which you can not say about 1.6.0.9.
 
Best regards
 
MacRoy
  • Like 1

Share this post


Link to post
Share on other sites

In prestashop 1.6.0.11 one client inform us that the product page left or right column is not able to change form theme configuration page. After investigate in database i saw that Prestashop add shop column but product page and some other page are missing from that table meta. 

 

It is prestashop 1.6.0.11 new architecture or missed that.

 

Hi,

 

Try to apply this commit, https://github.com/PrestaShop/PrestaShop/commit/998f8a828934567cf4a3d95d56b9d051e1fd65ff and https://github.com/PrestaShop/PrestaShop/commit/3047ee0b3246cb1270a8fbfc51a19de2563da7ad

 

you should see theses pages again.

 

Regards

Edited by Gregory Roussac (see edit history)

Share this post


Link to post
Share on other sites

I have this problem with prestashop 1.6.0.11 when customer management gives me this error when I enter a customer
:

 

yulia perxxxxxxxxx [000004] - xxxxxxxxxxxxx

Modifica
Titolo Sociale

Mrs.

Età

Di 34 anni (data di nascita: 18/02/1985)

Data Registrazione

24/12/2013 21:39:29

Ultima Visita

Mai

Lingua

Italiano (Italian)

Registrazioni

Newsletter   Opt-in

Ultimo Aggiornamento

24/12/2013 21:39:29

Stato

Attivo

Ordini 0

yulia perxxxxxxx non ha ancora fatto ordini

Carrelli 0

Nessun carrello disponibile

Aggiungi una nota privata
Questa nota sarà mostrata a tutti i dipendenti ma non al cliente.
Ultimo Aggiornamento

24/12/2013 21:39:29

Stato

Attivo

Ordini 0

yulia perxxxxxxxxxx non ha ancora fatto ordini

Carrelli 0

Nessun carrello disponibile

Aggiungi una nota privata
Questa nota sarà mostrata a tutti i dipendenti ma non al cliente.

Gruppi 1 Modifica

Id Nome 3 Customer

 
 
Fatal error

Share this post


Link to post
Share on other sites

Hi Angelica,

 

Would you mind posting your issue on a separate topic so that we keep this thread organized? Many thanks!

 

Maggie

Share this post


Link to post
Share on other sites

...Età

 

Di 34 anni (data di nascita: 18/02/1985)

....

I'm sorry, excuse my but how is possible that she's born in 1985 and have 34 years?
  • Like 1

Share this post


Link to post
Share on other sites

×
×
  • Create New...

Important Information

Cookies ensure the smooth running of our services. Using these, you accept the use of cookies. Learn More