Erik Harris

This had three tags, but only one stuck (maybe because I used commas and spaces between them?) Trying to tag the thread again…
Edit: Nope, it seems that tagging might be broken in WP Forums. It worked last time I posted. ??

• This reply was modified 7 months, 1 week ago by Erik Harris.

Thanks for your suggestion, @threadi . I created a ticket for font sizes, including two proposed solution ideas within theme.json. I may do something similar for various other issues I’m finding with the theme/site editor (e.g. the colors specified for links in my 2023 child theme are completely ignored, with the “secondary” color being used instead; custom CSS isn’t displayed in the visual editor; and for text case options, the really-obvious option of “smallcaps” is missing, though I don’t use it on this site, so it doesn’t affect me).

I really like where the theme editor is going, but right now, it seems terribly limited. Most of what I want to do needs to be done by hacking theme.json or custom CSS, and I’m hardly playing with advanced concepts.

• This reply was modified 1 year, 2 months ago by Erik Harris.
• This reply was modified 1 year, 2 months ago by Erik Harris.

Font management seems… kinda broken, but not entirely. I added a font to my theme, and it showed up in the font manager, but didn’t actually add to the theme in any way I could use. I went back a few hours later, and added my font again, and now it works fine! (It’s still displaying a generic font in the Font Manager instead of the actual font, though).

Hopefully another version of this plugin will come out that works better with 6.3. It’s only listed as being compatible with up to 6.2.2.

• This reply was modified 1 year, 3 months ago by Erik Harris.

Thanks for your continued responses and for your help, @ghernkadence . I see that 3.1.9 was released, so I updated to that, and then I activated, deactivated, and successfully deleted it!

Thanks again for your kind help! Once I’ve got the hang of the base WP Theme and Block editors, I’ll start looking into how I want to extend it, and may come back to Kadence. Between the frequent updates and the quick responses to requests for help, it’s clear that you and the devs care about product quality!

@ghernkadence – thanks for the pointer. I enabled Debugging and… wow, core WordPress and some regularly-updated plugins throw a lot of debug errors for deprecated PHP calls! Anyhow, this is the block of errors I get when trying to delete Kadence Blocks 3.1.8 (where the absolute path to my WP install is replaced with “XXXXX”):

  thrown in /XXXXX/wp-content/plugins/kadence-blocks/vendor/vendor-prefixed/stellarwp/telemetry/src/Telemetry/Uninstall.php on line 64
[03-Aug-2023 21:10:11 UTC] PHP Deprecated:  strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /XXXXX/wp-includes/functions.php on line 7127
[03-Aug-2023 21:10:11 UTC] PHP Deprecated:  str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /XXXXX/wp-includes/functions.php on line 2182
[03-Aug-2023 21:10:11 UTC] PHP Deprecated:  strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in /XXXXX/wp-includes/functions.php on line 7127
[03-Aug-2023 21:10:11 UTC] PHP Deprecated:  str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /XXXXX/wp-includes/functions.php on line 2182
[03-Aug-2023 21:10:11 UTC] PHP Deprecated:  Creation of dynamic property GTmetrix_For_WordPress::$tests_page_hook is deprecated in /XXXXX/wp-content/plugins/gtmetrix-for-wordpress/gtmetrix-for-wordpress.php on line 294
[03-Aug-2023 21:10:11 UTC] PHP Deprecated:  Creation of dynamic property GTmetrix_For_WordPress::$schedule_page_hook is deprecated in /XXXXX/wp-content/plugins/gtmetrix-for-wordpress/gtmetrix-for-wordpress.php on line 295
[03-Aug-2023 21:10:11 UTC] PHP Deprecated:  Creation of dynamic property GTmetrix_For_WordPress::$settings_page_hook is deprecated in /XXXXX/wp-content/plugins/gtmetrix-for-wordpress/gtmetrix-for-wordpress.php on line 296
[03-Aug-2023 21:10:16 UTC] PHP Fatal error:  Uncaught TypeError: count(): Argument #1 ($value) must be of type Countable|array, bool given in /XXXXX/wp-content/plugins/kadence-blocks/vendor/vendor-prefixed/stellarwp/telemetry/src/Telemetry/Uninstall.php:64
Stack trace:
#0 /XXXXX/wp-content/plugins/kadence-blocks/vendor/vendor-prefixed/stellarwp/telemetry/src/Telemetry/Uninstall.php(64): count(false)
#1 /XXXXX/wp-content/plugins/kadence-blocks/vendor/vendor-prefixed/stellarwp/telemetry/src/Telemetry/Uninstall.php(50): KadenceWP\KadenceBlocks\StellarWP\Telemetry\Uninstall::maybe_remove_optin_option()
#2 /XXXXX/wp-content/plugins/kadence-blocks/uninstall.php(10): KadenceWP\KadenceBlocks\StellarWP\Telemetry\Uninstall::run('kadence-blocks')
#3 /XXXXX/wp-admin/includes/plugin.php(1245): include_once('/home/erihar47/...')
#4 /XXXXX/wp-admin/includes/plugin.php(960): uninstall_plugin('kadence-blocks/...')
#5 /XXXXX/wp-admin/includes/ajax-actions.php(4732): delete_plugins(Array)
#6 /XXXXX/wp-includes/class-wp-hook.php(310): wp_ajax_delete_plugin('')
#7 /XXXXX/wp-includes/class-wp-hook.php(334): WP_Hook->apply_filters('', Array)
#8 /XXXXX/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#9 /XXXXX/wp-admin/admin-ajax.php(188): do_action('wp_ajax_delete-...')
#10 {main}
  thrown in /XXXXX/wp-content/plugins/kadence-blocks/vendor/vendor-prefixed/stellarwp/telemetry/src/Telemetry/Uninstall.php on line 64

• This reply was modified 1 year, 3 months ago by Erik Harris. Reason: Added plugin version for clarity, since it updated again

@ghernkadence – I copied the entire error text that appeared in the WordPress Plugins UI. It just updated to 3.1.7, so I tried deleting it again, and I get the same error:

Is there someplace else I should be looking for more verbose error text?

• This reply was modified 1 year, 3 months ago by Erik Harris.

Thank you, @writerdreamer ! I’ve been tearing my hair out over this same problem, and I finally found this thread. Evidently DreamHost’s fix for you was just for you, and I’ll have to contact them to have them fix the settings on my VPS as well, so that I can continue working on my site redesign (which I’ve been putting off for years, but have to do now that DreamHost is about to start charging accounts for using PHP 7.4. The theme I used as a basis many years ago causes the site admin login to fail if I update to PHP 8.x)

@hjogiupdraftplus – Yes, I should’ve specified that I’m using AIOS 5.1.8 on WordPress 6.2. Sorry for the omission

@aporter – Thanks, that’s good to know! I haven’t experienced any problems with AIOS, but it’s the only one of my plugins that shows up with errors under newer versions of PHP. I didn’t realize that PHP compatibility checkers don’t parse the code to look for conditional commands that execute lines only if certain versions of PHP are in use.

Oh, darn it… I didn’t dig back into the aforementioned WPMUDEV web page until prompted by this support thread, and I found my user error! I forgot to add the custom wrapper code to the live site’s custom sidebar widget. Once I did, it worked fine.

Thank you, Predrag, Kasia, and Nastia, for helping me resolve this. I was looking in the wrong places, and didn’t give you enough information to resolve the problem, but your questions prompted me to dig further and ultimately discover my error. I apologize for taking up your time with what turned out to be my own mistake, but I truly appreciate your thoughtful responses! Without them, I don’t know that I’d have figured this out.

• This reply was modified 5 years, 1 month ago by Erik Harris. Reason: tweak wording slightly

Hi Predrag ( @wpmudev-support1 ),

The front page Sidebar implementation was taken from this WPMUDEV web page, which is based on using this plugin. It’s implemented the same on both sites, but it only works on the dev site.

The one difference I can see is that I haven’t set up multiple front pages on the live site, only on the dev site. Could these edits require multiple front pages? That seems strange. The Twenty Seventeen theme only uses three page content template PHP files, and I’ve edited all of them to add in the custom sidebar.

Kasia,

I can certainly do that. They should be identical… It’s also worth noting that on https://www.harriswholehealth.com , the front page sidebar is the same as the sidebar used on the other pages (e.g. click on “Sessions”), and on anything BUT the front page, it’s styled correctly. Also, I made this child theme at the end of 2017, and have been sitting on it since then, only finally activating it on my wife’s business page a few days ago (long story; was waiting for her to make some content changes that would’ve made more use of the theme’s features, and she never did, so I just activated it as-is).

Again, they should be identical (I edited the theme mostly on the dev site, and then copied it over to the live site back at the end of 2017, and haven’t made any significant changes since then), but I zipped them both up and put them here:
https://www.eharrishome.com/harriswholehealth-2017-devsite.zip
https://www.eharrishome.com/harriswholehealth-2017-livesite.zip

Strange… The image URL above seems to bounce between showing the image and showing a 404 page. Might be related to the image hot-link protection I’ve got in .htaccess… Here’s the same image on imgur, comparing the two widgets in the admin backend: https://imgur.com/a/tbJpD6D

Nastia – That’s where I’m confused; the HTML blocks being used are definitely not identical (and therefore, neither is the CSS), but as far as I can tell, the setup is identical.

Both are Custom Sidebar widget containers, and both contain “Recent Posts” blocks. The only obvious difference was that the “Recent Posts” block is first on the live site, and second on the dev site. So I moved it to first on the dev site, and the result is the same. You can see the widget setups side-by-side here: https://www.harriswholehealth.com/WidgetCompare.png – Note that the issue existed before I added the small “Custom HTML” widget. One is called “Home” and the other is called “About” simply because the two sites have differently-named front pages.

I found the remaining explicit non-https link and changed it to a relative link, so the front page is no longer giving a mixed-content error.

I haven’t yet gone as far as creating another clone site, but the dev site does have most of the plugins I use on any of my live sites, such that if there are conflicts, they should be more common there. I did try disabling a handful of plugins on Harris Whole Health, and the result was the same. The main page sidebar still doesn’t contain the elements it should.

Brian – The thread above will help you with #2. You can hide it on other pages with some simple CSS. I haven’t had a chance to try Ionty’s JavaScript, though I intend to, because this plugin is slowing my sites WAY down. Pages that used to take 3-5 seconds to load in GTMetrix (already pretty slow) now consistently take 5-8 seconds to load. Hiding the Google banner won’t change that, but keeping the plugin from loading where it’s not needed should!

A quick web search confirms it. Those who have tested reCAPTCHA v3 show it to be quite a lot slower, by 1/3 to 1/2 second when everything is running smoothly, and even by as much as THIRTY SECONDS when one of Google’s 11-20 separate server requests (why?!?) encounters a problem.

https://pagepipe.com/how-google-no-captcha-captcha-slows-down-your-mobile-site/

Hopefully Google will address this as time goes on, but for now… reCAPTCHA v3 basically drags your website down, on every page, post, search result, etc, whether or not that page actually needs it.