Blocksy 1.8.17 Beta Version – Issue in Customizer Screen Refresh

UPDATE: Just checked my admin email. The below error is thrown for our production site when Blocksy Companion is updated with Blocksy ver 1.8.17 beta installed (did not get error on test site). The site looked fine on customer-end/live-end/whatever-it’s-called-end…
FYI, I did downgrade Blocksy Companion to previous version of 1.8.17, and the issue I described above still persisted.

Error Details
=============
An error of type E_ERROR was caused in line 65 of the file /home/dewingsc/public_html/siteres/wp-content/plugins/blocksy-companion/plugin.php. Error message: Uncaught Error: Class "Blocksy\CacheResetManager" not found in /home/dewingsc/public_html/siteres/wp-content/plugins/blocksy-companion/plugin.php:65
Stack trace:
#0 /home/dewingsc/public_html/siteres/wp-includes/class-wp-hook.php(303): Blocksy\Plugin->init()
#1 /home/dewingsc/public_html/siteres/wp-includes/class-wp-hook.php(327): WP_Hook->apply_filters()
#2 /home/dewingsc/public_html/siteres/wp-includes/plugin.php(470): WP_Hook->do_action()
#3 /home/dewingsc/public_html/siteres/wp-settings.php(578): do_action()
#4 /home/dewingsc/public_html/siteres/wp-config.php(83): require_once('/home/dewingsc/...')
#5 /home/dewingsc/public_html/siteres/wp-load.php(50): require_once('/home/dewingsc/...')
#6 /home/dewingsc/public_html/siteres/wp-admin/admin.php(34): require_once('/home/dewingsc/...')
#7 /home/dewingsc/public_html/siteres/wp-admin/themes.php(10): require_once('/home/dewingsc/...')
#8 {main}
  thrown

Hey @wardencenter

We’re investigating this internally and will get back to you asap.

Thanks.

Hi @wardencenter,

It seems like we have two issues here:

1. About Customizer not displaying properly with WordPress 5.8.3
2. About updating Blocksy Companion from 1.8.17 -> 1.8.18 on WP 5.8.3

—

Issue #1

I tried installing our Floreo starter site on WP 5.8.3 with our latest versions of Blocksy Theme & Companion and the customizer is displayed properly.
Can you please enable WP_DEBUG and WP_DEBUG_LOG on that site as described here and try to reproduce the problem again?
If there are any errors in the “wp-content/debug.log” file, please attach them here and we’ll try to understand what’s happening there for you. Otherwise, without being able to reproduce the problem, it’s hard to understand what’s going on here.

—

Issue #2

The issue that you saw happens when the “framework/cache-reset-manager.php” file is not present in your plugin install, and thus the autoloader fails to laod that class.
Can you please check if this file was copied properly for you during the update process? This might be the reason for the problem.

I tried to update from 1.8.17 -> 1.8.18 on WP 5.8.3 and everything was smooth…
Please try to reproduce this problem on another install and provide us the exact steps for the reproduction. This way we’ll understand if this is something caused by your setup or if it’s a general issue from our end.

—

Waiting for your reply.

Sincere thanks to you both.

I’ll create another clone of our production site and will do as instructed, though it will likely not be until tomorrow.

Just FYI, I updated my Blocksy companion through the normal method of clicking on “update” on the Dashboard Plugin screen. That is, I didn’t update the companion via an upload.

Hey @wardencenter,
No rush, take your time.

Please let us know in case you observe something weird.

Have a wonderful day/evening.

FYI – As I’m sure you’ve already figured out, issue appears to be related to Global Header. I had a good report written up of my findings, but with each Blocksy and Companion update the trigger(s) (that is, the action(s) within the customizer that causes Live Preview to refresh and then show incorrect header) within the Customizer changes.
There’s only one trigger and “untrigger” that have remained consistent:
Trigger – What will always cause “Live Preview” to refresh and then show wrong version of header:
Goto, Header>Headers tab>Global Headers, and toggle the “Sticky Header” option.
“Untrigger” – What will always make the “Live Preview” refresh again and then show the correct version of header (besides a complete browser page refresh):
Goto, Header>Elements tab>Menu> General tab. Move the slider, “Item Spacings”.

I’ve been diligently updating Blocksy and Companion and am now on ver 1.8.19 on both.

I messed up and did some content updating, and then updated Blocksy and Companion before making a clone, so a clone would do me no good right now. My apologies. I’m marketing, not really web development. I’ll try to find time this evening to restore one of my old site versions and let y’all have at it.

Thank you again for your continued support and for this fantastic theme.

Ok – I cloned the site. The issue did not manifest. The only difference between production and cloned site: The “Site Address (URL)” field.

For production site, this field is different than the “WordPress Address (URL)”. The The “Site Address (URL)” field does not include my WP installation folder name. So, it is just “https://dewingscenter.org/” But, the “WordPress Address (URL)” has my WP installation folder name appended to it. So, it’s https://dewingscenter.org/myinstall — example, not my real install folder name

For the cloned site, the two fields are the same.

Stick with me.

When I remove the WP installation folder name from “Site Address (URL)” field on the cloned site, I get the same symptoms in the customizer that I’m getting on the production site. Clear as mud?

Thoughts? Advice? Keep in mind that I had no Customizer “Live Preview” Header display issues with Blocksy ver 1.8.14.

• This reply was modified 2 years, 9 months ago by wardencenter.

@wardencenter just to recap, you have only one issue now: the proper preview of the header in the Customizer. I would assume you are dealing with one or more custom headers that have conditions attached to them, is that so?

Even if so, I really don’t see how this could’ve been related to the site being placed in a folder or being served from the root of the server… These seem to be totally unrelated to be honest.

Also, have you managed to encounter again the error related to Blocksy\CacheResetManager class that you showed previously? It never showed up on our end…

Please confirm the above with me.

Hello and thank you.

I do not understand what you’ve written here, because I don’t know what you mean by “custom headers” or “conditions” (sorry):
“I would assume you are dealing with one or more custom headers that have conditions attached to them, is that so?”

There are other issues within Customizer since upgrading Blocksy/Blocksy Companion.
I also am unable to load the “design tab” for any elements in the footer rows – but I can in the header rows. Also, the Customizer will lockup and only a page refresh can bring it back. Thankfully, I’m slow and I save my work often.

I agree that it does not make sense that any of the issues would be related to the site being served from the root. I only know that changing the “Site Address URL” on a clone of my site will cause the issues to appear. The problem, of course, is that leaving a cloned site with the same Site Address URL of my production site (with the site being served from the root) will cause issues on my production site.

Have you tried removing the trailing install folder from the Site Address URL from within the WP dashboard on your test site?

Have not had the Blocksy Cache issue since upgrading to Blocksy .19

• This reply was modified 2 years, 9 months ago by wardencenter.

Hi @wardencenter,

Yes, we have tried to change install folders for our installs and frankly this made no difference in the behaviour.

Glad to hear you have no issues with upgrades so far. But please let us know if this changes.

—

Now, the issues about “Design” tab for elements seems like something that is a problem.

Can you please gives us two things:

1. Customizer export from your site as described here: https://creativethemes.com/blocksy/docs/general-options/manage-options/
2. Browser console.log output as described here: https://support.shortpoint.com/support/solutions/articles/1000222881-save-browser-console-file#Google-Chrome

Waiting for your reply so that we can debug this further.

Thank you and sorry for my delayed reply.

How do I get these items to you, please?

Hello @wardencenter

You can send us these files at [email protected] ?? I’ll pass them on to our devs asap.

Thanks!

Got it – thanks, Eduard!

Thanks @wardencenter
Got the files and directed them towards our software engineer, who will analyse and get back to you asap.

Thanks again!

Resolved in newest version, ver 1.8.20, of Blocksy and Blocksy Companion