Should I update to 1.6.1.7 (security release)

[CrossY]

Hi there,

 

I don't really understand the patch notes for this version. It says security release, how recommended is it to install this one?
 

If it's hard to recommend whether to do it or not, maybe someone can explain what the changes entail?

Fixed bugs:
* BO : (f19ae86) Solved problem with non-unserialized filters datas

Improved/changed features:
* CORE : (e12c209) Fix a case where $context->smarty could be undefined

 

 

 

We are currently on 1.6.1.5.

 

Thanks in advance!

Best,
 

 

 

[Sathyaseelan133]

Hi CrossY,

 

Don't upgrade the prestashop site to latest version when your site is in live server because after upgrading your theme custom changes you have made in the theme files and module hook positions will changed to default. So your custom theme and hook changes will get lost.

[CrossY]

Thanks for the reply. How serious should I take the security concerns then?

[the.rampage.rado]

This release SHOULD NOT break anything! Please backup first!

[MacRoy]

Hi!

 

I've made an update of PrestaShop from 1.6.1.6 to 1.6.1.7 without any problems via 1-click update.

 

Regards

MacRoy

[Sathyaseelan133]

Hi CrossY,

 

It's better to keep the prestashop version as up to date. But before upgrading Please take backup of files and DB.

[CrossY]

That's an odd change of mind, Sathyaseelan133. I think it would be helpful if you don't post such advice unless you are certain about it.

Thanks rampage.rado and MacRoy, i'll try to update with a backup and mirror of my site first

[iyalla]

I just updated from 1.6.1.6 to 1.6.1.7 and all links to my category pages on my store stopped working, Could anyone please help me. 

This is one of such links: https://www.walfave.com/37-bags 

 

Thanks 

Iyalla Walcourt

[the.rampage.rado]

That's strange. Did you follow post update instructions correctly (clear cashe, regenerate cookies, etc.)? If so do you use some modules that may get in the way of URL rewriting?
Do you experience any other issues? Try renaming .htaccess file and check if you have such issues.

[Bill Dalton]

iyalla, try clearing your cache ... Advanced Parameters  > Performance

[JSSSX]

Wasn't flawlessly for me either, I just updated from 1.6.1.3 to 1.6.1.7 and even if I checked "NO" to all, especially for emails, all mails were changed to original ones.

Fortunately, I do have backups.

Except from this, and all the new php warning that weren't there before, this update is fine and recommended


By the way, if anyone as a clue regarding this new issue (not major), please let me know : 
PHP Warning:  htmlspecialchars() expects parameter 1 to be string, array given in C:\xxxxxxxxx\cache\smarty\compile\8f\4a\83\8f4a838f0af6b3043dbc0f97fb570e0cbabec460.file.header.tpl.php on line 105

Line 105 code : 

<link rel="stylesheet" href="<?php echo htmlspecialchars($_smarty_tpl->tpl_vars['css_uri']->value, ENT_QUOTES, 'UTF-8', true);?>

" type="text/css" media="<?php echo htmlspecialchars($_smarty_tpl->tpl_vars['media']->value, ENT_QUOTES, 'UTF-8', true);?>

" />

Edited September 8, 2016 by JSSSX (see edit history)

[iyalla]

Thanks guys for all your support. I have cleared my cashe but the problem still persists. And by the way, my store is set from the server to automatically update to minor prestashop patches. This is also the first time I am encountering this type of issue and it is the only issue I have after the update. The store is working fine  but all categories has suddenly stopped displaying on the front page. 

 

Iyalla Walcourt

[Bill Dalton]

iyalla, next turn on error reporting. Please see https://www.prestashop.com/forums/topic/224525-how-to-turn-on-error-reporting-for-debug-information-blank-page-500-internal-server-error/

[iyalla]

I got these errors after turning on error reporting as you advised:

 

Deprecated: mysql_connect(): The mysql extension is deprecated and will be removed in the future: use mysqli or PDO instead in/home/walfave4038/public_html/classes/db/MySQL.php on line 51

Warning: Cannot modify header information - headers already sent by (output started at /home/walfave4038/public_html/classes/db/MySQL.php:51) in/home/walfave4038/public_html/classes/controller/FrontController.php on line 790

Warning: Cannot modify header information - headers already sent by (output started at /home/walfave4038/public_html/classes/db/MySQL.php:51) in/home/walfave4038/public_html/classes/controller/FrontController.php on line 791

Warning: Cannot modify header information - headers already sent by (output started at /home/walfave4038/public_html/classes/db/MySQL.php:51) in/home/walfave4038/public_html/classes/controller/FrontController.php on line 793

[Bill Dalton]

Is this message only on category pages? Do you have any third party modules installed that are related to category pages?

[jetx]

That's an odd change of mind, Sathyaseelan133. I think it would be helpful if you don't post such advice unless you are certain about it.

 

Thanks rampage.rado and MacRoy, i'll try to update with a backup and mirror of my site first

 

I dunno about that CrossY, I think Sathyaseelan133 gave preeeety good advice.

[iyalla]

Yes, the message is only on the category pages, and no, I, have not installed any third party modules for categories.

[Bill Dalton]

Possible problems is that the category page for whatever reason is exceeding memory limit. But you did not install any additional modules so it may be page corruption. I would upload fresh copies of category related pages of your theme, you'll see the word category in the file names. I would also download a copy of PS and replace

 

classes/db/MySQL.php

classes/controller/FrontController.php

 

with fresh copies.

 

After that, if it dosen't fix the problem you may need to give someone access to take a closer look. Or hopefully someone may post something else for you to try.

[emartinez0131]

I just updated from 1.6.1.6 to 1.6.1.7 and all links to my category pages on my store stopped working, Could anyone please help me. 

This is one of such links: https://www.walfave.com/37-bags

 

Thanks 

Iyalla Walcourt

This may seem simple - but also simple enough to miss - did you check under Preferances --> SEO & URLs - that Friendly URL is enabled? The URL you listed as non-functional looks like it would be a Friendly URL.

[Bill Dalton]

Yes Friendly is on, also the error would be 404 not 500. 

 

https://www.walfave.com/home/73-canary-yellow-engagement-ring.html

 

Keep the ideas coming all help appreciated!

[maticholic]

Yes, I have same problem after update to 1.6.1.7 please try to click https://maticholic-eshop.com/

First, Our photo catague unshown, I've try to regenerate, but it still persist

Second, If I try to click the product ( https://maticholic-eshop.com/shock-absorber-bottom-shock/68-ohlins-rear-shock-pcx-.html ), there is show message "index.php?controller=404" 

I've tried to clear cache already

 

So, I tried to restore into 1.6.1.6 but this issue still the same error and shown the message as above.

 

Anyone?

[Bill Dalton]

Your site is working fine for me, no problems.

[maticholic]

Your site is working fine for me, no problems.

I've success downgrade into 1.6.1.6, but I will update again into 1.6.1.7.

Edited September 12, 2016 by maticholic (see edit history)

[Sathyaseelan133]

Hi Maticholic,

 

After upgrading to 1.6.1.7 just turn off and turn on the friendly URL. So it will regenerate the htaccess and now all the page links will work.

[CrossY]

People are having very different experiences. I'm still wondering what the security risks/update actually mean and how necessary it is to update. Anyone has a word on that?

[maticholic]

Hi Maticholic,

 

After upgrading to 1.6.1.7 just turn off and turn on the friendly URL. So it will regenerate the htaccess and now all the page links will work.

OK. thanks. I will try to update back. Later I will also update its development after the update to 1.6.1.7

Edited September 12, 2016 by maticholic (see edit history)

[maticholic]

People are having very different experiences. I'm still wondering what the security risks/update actually mean and how necessary it is to update. Anyone has a word on that?

Yes it is a minor update. probably not much changed. but for the security and stability of the system the better we first update of its development. Moreover, version 1.7 RC is still in the stage of the RC

 

####################################

# v1.6.1.7 - (2016-09-06)

####################################

 

Fixed bugs:

 

[-] BO : (f19ae86) Solved problem with non-unserialized filters datas

 

[-] FO : (2636a31) Fix rouding error in ProductController (PSCSX-7566)

 

 

Improved/changed features:

 

[*] CORE : (e12c209) Fix a case where $context->smarty could be undefined

[iyalla]

My issue has just been resolved. What happened was that the update from 1.6.1.6 to 1.6.1.7 replaced all modifications already done on some of the shop's folders.The site started functioning well after the restoration of all such modified folders .

 

Thanks to all of you for your kind assistance, especially Bill Dalton. I really appreciate your efforts.

 

Iyalla Walcourt  

[Bill Dalton]

Fantastic. Thanks for sharing. I'm on a Windows box so the file permission thing isn't usually "a thing", but I'll keep that in mind.

[Mavenace]

You always should update but what I would do is the following:

 

setup a TEST/QA environment

Test all the upgrades, patches etc

Then have let's say an update release schedule every 3 months.

This way you are always up to date with the latest patches.

2 weeks before your patch release you freeze any update on the TEST/QA environment giving you 2 weeks time to test everything again.

 

Then put your shop in maintenance mode, copy your DB to QA, the upgrade in QA

Test again and then move all over to PROD

 

This in high level terms.

[El Patron]

I've been 'playing' with 1.6.1.7 and like it....

 

I'm considering now to recommend this release to get two year shelf life.  Which now a days is long time.

 

Happy day, ,el

[Mavenace]

My issue has just been resolved. What happened was that the update from 1.6.1.6 to 1.6.1.7 replaced all modifications already done on some of the shop's folders.The site started functioning well after the restoration of all such modified folders .

 

Thanks to all of you for your kind assistance, especially Bill Dalton. I really appreciate your efforts.

 

Iyalla Walcourt  

One question: Will these same modifications be overwritten again with the next PrestaShop update?

[Bill Dalton]

In this case it seems to be related to the host. The other problems people are having are not related to permission issues.

[jetx]

Unfortunately yeah they're all nuked on every release. Best to make a note of all modifications and use Beyond Compare or Winmerge to merge your modifications into the updated files. For minor updates it's pretty quick usually, for me always about 12 files are affected by updates.

[Mavenace]

Unfortunately yeah they're all nuked on every release. Best to make a note of all modifications and use Beyond Compare or Winmerge to merge your modifications into the updated files. For minor updates it's pretty quick usually, for me always about 12 files are affected by updates.

Are the no override folders? This leaves the core files as is, and modifications are in an override folders and you can upgrade the core software. Obvious you need to test because you might need to rewrite the modifications