lat9

How about, as an alternate solution, we just plunk the following code ```php if (IS_ADMIN_FLAG === false && !isset($data['lang'][$_SESSION['languages_code']])) { $data['lang'][$_SESSION['languages_code']] = [ 'language_id' => $_SESSION['languages_id'], 'products_name' => '', 'products_description'...

> @lat9 I support your proposed alternative. It's cleaner insomuch as it simply prevents the empty-array situation that was triggering the PHP warnings. > > It does make it possible...

At which point is the zc_install supposed to report? I've got a very foobared zc154 database whose default collation is latin1_swedish_ci and an assortment of latin1-collated tables. The zc_install allowed...

I've also got a base install of zc155 (using `latin1_general_ci` throughout). No collation message on the zc_install upgrade. When the upgrade was completed, the newly-added tables (e.g. `plugin_groups`) have a...

Looking good for various databases that 'identify' as `latin1`, but I've found an issue with a 'utf8' installation. All collations in the database are `utf8_unicode_ci` and the configure.php files report...

Would a similar issue be present on the storefront where an order's history is displayed, e.g. `account_history_info`?

> OK in 2.0, the order class does a query on TABLE_ORDERS_STATUS LEFT JOIN TABLE_ORDERS_STATUS_HISTORY to build the list of order statuses, so this entry is not included in the...

Any idea what impact this change will have on `USU`?

Noting that this behavior is present in `/includes/auto_loaders/paypal_ipn.core.php` 70: init_sessions.php 71: init_paypal_ipn_sessions.php 95: init_languages.php

Unit test suites need updating to remove the check for the zenid/zenAdminID parameters (beyond my ken).