Bugs and crashes with version 2.1.7

Hello aThemes team,

we just updates our six Sydney Pro installations to your current version 2.1.7 and had problems in every single installation of it. We use completely different servers in different data centers, so it cannot be a question of the server. Also all plugins and WordPress itself are on the most current versions.

With Sydney Pro 2.1.6 all was running fine. With 2.1.7 we had two separate problems, four installations had the first variation, two installations had the second one:

1.)
In this variation the WordPress website basically continued functioning, but in all four installations there were the same errors in the console.

In Firefox the console errors said the following:
functions.js:391:19

Uncaught TypeError: form is null

  • init https://[URL]/wp-content/themes/sydney-pro-ii/js/functions.js?ver=20210917:391*
  • https://[URL]/wp-content/themes/sydney-pro-ii/js/functions.js?ver=20210917:612*
  • sydneyDomReady https://[URL]/wp-content/themes/sydney-pro-ii/js/functions.js?ver=20210917:601*
  • https://[URL]/wp-content/themes/sydney-pro-ii/js/functions.js?ver=20210917:604*

While in Chrome the console error said this:
functions.js?ver=20210917:391

Uncaught TypeError: Cannot read properties of null (reading ‘getElementsByClassName’)

  • at Object.init (functions.js?ver=20210917:391)*
  • at HTMLDocument. (functions.js?ver=20210917:612)*
    init @ functions.js?ver=20210917:391
    (anonymous) @ functions.js?ver=20210917:612

After we deleted the new updated theme directory manually and uploaded the old directory from yesterday’s backup, all was running again in all four installations without these errors.


2.)
In this problems variation, that was the same in two different websites / installations, the whole websites nearly crashed and showed a “destroyed” looking homepage.
Here we had the following console errors in Firefox:
GET https://[URL]/ [HTTP/2 500 Internal Server Error 808ms]

  • Fatal error: Uncaught Error: Call to undefined function wc_get_cart_url() in /[SERVER-PATH]/wp-content/themes/sydney-pro-ii/inc/legacy.php:29 Stack trace: #0*
  • /[SERVER-PATH]/wp-includes/class-wp-hook.php(303): sydney_nav_cart(’<li id="menu-it…’, Object(stdClass)) #1*
  • /[SERVER-PATH]/wp-includes/plugin.php(189): WP_Hook->apply_filters(’<li id="menu-it…’, Array) #2*
  • /[SERVER-PATH]/wp-includes/nav-menu-template.php(259): apply_filters(‘wp_nav_menu_ite…’, ‘<li id="menu-it…’, Object(stdClass)) #3*
  • /[SERVER-PATH]/wp-content/themes/sydney-pro-ii/inc/classes/class-sydney-header.php(580): wp_nav_menu(Object(stdClass)) #4*
  • /[SERVER-PATH]/wp-includes/class-wp-hook.php(303): Sydney_Header->header_legacy(’’) #5*
  • /[SERVER-PATH]/wp-includes/class-wp-hook.php(327): WP_Hook->apply_filters(NULL, Array) #6*
  • /[SERVER-PATH]/wp-includes/plugin.php(470): WP_Hook->do_action(Array) in /[SERVER-PATH]/wp-content/themes/sydney-pro-ii/inc/legacy.php on line 29*

In Chrome the console error said this:
Uncaught TypeError: Cannot read properties of null (reading ‘classList’)

  • at Object.init (front.min.js?ver=2.1.4:1)*
  • at front.min.js?ver=2.1.4:1*
    init @ front.min.js?ver=2.1.4:1
    (anonymous) @ front.min.js?ver=2.1.4:1
    load (async)
    (anonymous) @ front.min.js?ver=2.1.4:1
    (anonymous) @ front.min.js?ver=2.1.4:1

After we deleted the new updated theme directory manually and uploaded the old directory from yesterday’s backup, all was running again in all two installations without these errors.

We are a professional web agency working with WordPress for many years, and with Sydney Pro, too. We didn’t ever encounter such grave problems. We had quite some shocking moments after the update and quite a bit of work, too, to get all back to the previous versions and running again and testing all.

Please fix these bugs and release a new update. Of course we cannot re-update to this theme version again before something happened.

If you have any questions to us that can help you in tracking down the problems, feel free to ask. We are happy to help you if we can - at least with some information if necessary.

Greetings,
Matthias

Hello Mathias,

First thanks for using our theme!

We already replied to the email you sent through our priority support contact form. So, please kindly check your email inbox and let’s continue from there. I will close this topic for now.

Kind Regards,

Rodrigo.

aThemes Support