Pre-release feedback for v1.5.2

[simon1066]

As with ALL upgrades, selectively picking-and-choosing isolated files is NOT the best approach. A proper upgrade is ALWAYS the best approach.
That said, the following github commits to v160 encompass the changes made for CHANGE-619: 1 2 3 4

Thank you for this info

I believe I have already incorporated some of these changes into my store - by forum suggested hacks,

I think I will take your advice and add the others via full upgrade - once past beta.

[dw08gm]

Have the following mods been fully incorporated in 152

search_configuration_keys
Fix_Cache_key utility
Keepalive Timer
time zone offset

But not COWOA.

Are there any others I may have missed.

Could a list of newly incorporated mods be appended to docs/whatsnew_1.5.2.html

Thanks

[lat9]

I noticed that /includes/functions/functions_email.php now interprets a "Gmail" transport method, but that transport method is not one of the radio buttons in Configuration->Email Options->Email Transport Method. Is this by design?

[lat9]

In /includes/templates/template_default/templates/tpl_account_default.php, shouldn't the constant used in this fragment:

<?php
  if ((int)ACCOUNT_NEWSLETTER_STATUS > 0 or CUSTOMERS_PRODUCTS_NOTIFICATION_STATUS !='0') {
?>
<h2><?php echo EMAIL_NOTIFICATIONS_TITLE; ?></h2>
<ul id="myAccountNotify" class="list">
<?php
  if ((int)ACCOUNT_NEWSLETTER_STATUS > 0) {
?>
<li><?php echo ' <a href="' . zen_href_link(FILENAME_ACCOUNT_NEWSLETTERS, '', 'SSL') . '">' . EMAIL_NOTIFICATIONS_NEWSLETTERS . '</a>'; ?></li>
<?php } //endif newsletter unsubscribe ?>

be SHOW_NEWSLETTER_UNSUBSCRIBE_LINK instead of ACCOUNT_NEWSLETTER_STATUS? The latter is the default setting for a customer's choice of newsletter sign-up (or not).

[swguy]

I am experiencing a redirect loop going to admin on a localhost installation on Apache/Fedora 16. Haven't tracked it down yet.
Works like a charm on MAMP.

[swguy]

So zen cart 1.5.2 is just for testing for now correct? I would go wrong it I use it on a live store correct?

You are correct. 1.5.2 should be considered a beta for developer testing only at this point.

[mickadoo]

Very happy to see upgrade to mysqli functions, one of the reasons I'd recently been considering other options to Zencart was the mysql reliance. I'm no expert at programming so I don't know the full implications in using mysqli over mysql functions, just that php sites always recommend using mysqli now and as a developing programmer I think it wouldn't be very helpful using deprecated functions all the time. Keep up the good work!

[lat9]

Was there a (good) reason why the selectable-countries change introduced in v1.5.2 chose to call the enable/disable field status instead of countries_active as it is in the Selectable Countries plugin? The only reason I ask is that it's going to make the upgrade to v1.5.2 more difficult for current users of the plugin since they'll need to re-disable those countries that they don't want.

[lat9]

I just started a test install on my 1and1 host and was presented with:

ERROR: date.timezone not set in php.ini. Please contact your hosting company to set the timezone in the server PHP configuration before continuing.

Is the date.timezone setting really this important?
Here's the date information that's set in a "sibling" test site running v1.5.1:

date
date/time support 	enabled
"Olson" Timezone Database Version 	2013.6
Timezone Database 	internal
Default timezone 	America/New_York

Directive	Local Value	Master Value
date.default_latitude	31.7667	31.7667
date.default_longitude	35.2333	35.2333
date.sunrise_zenith	90.583333	90.583333
date.sunset_zenith	90.583333	90.583333
date.timezone	no value	no value

[lat9]

I just started a test install on my 1and1 host and was presented with:

ERROR: date.timezone not set in php.ini. Please contact your hosting company to set the timezone in the server PHP configuration before continuing.

Is the date.timezone setting really this important?
Here's the date information that's set in a "sibling" test site running v1.5.1:

date
date/time support 	enabled
"Olson" Timezone Database Version 	2013.6
Timezone Database 	internal
Default timezone 	America/New_York

Directive	Local Value	Master Value
date.default_latitude	31.7667	31.7667
date.default_longitude	35.2333	35.2333
date.sunrise_zenith	90.583333	90.583333
date.sunset_zenith	90.583333	90.583333
date.timezone	no value	no value

FWIW, I was able to work around this restriction by changing /zc_install/includes/application_top.php (line 52) to comment out the lines associated with the restriction:

/**
 * Timezone problem detection
 */
//if (PHP_VERSION >= '5.3' && ini_get('date.timezone') == '')
//{
//  die('ERROR: date.timezone not set in php.ini. Please contact your hosting company to set the timezone in the server PHP configuration before continuing.');
/*} else*/ if (PHP_VERSION >= '5.1') {
  $baseTZ = date_default_timezone_get();
  date_default_timezone_set($baseTZ);
  unset($baseTZ);
}