BeckyTech

For those who follow, the Sparkling theme developer said they would fix their error. Did not indicate when. In the meantime, revert to default font settings:
https://colorlib.com/wp/forums/topic/undefined-index-errors-extras-php/

I know the errors don’t go away, but there are situations where it looks to me like they are a show stopper and I don’t want my show stopped. 🙂 Let me explain why masking a problem is just fine as a temporary solution.

It looked to me like the only way around this error was to create a new child theme, copy all the files from my old child-theme directory to my new one, etc. (Maybe that was user error, but updates to my css file didn’t seem to be working and after I did this the updates to the css worked fine). It was a hassle, it created some ripple effects in other areas and it was just kind of messy to recover from. Altogether, it took me over an hour to get my site back correctly.

Remember that when I originally ran into this I was just innocently going along updating my plugins. Since I knew I had not made any changes to any files or code, I really didn’t want to have to stop, Google a few different ways to see if this problem had been encountered before and had an existing resolution. If not, now I have to go find the developer’s forum, register, login, and create a succinct post of the problem. We are talking a good hour and a half because as I’m Googling I’m trying to get a handle on just what the problem is.

You responded right away, which is great. (BTW, I got sick and had to table this problem for awhile. Now I’m back at it.) But now I have to take a significant side trip along a path that I really didn’t want to have to pursue at the moment. And right now the developer’s response is it will be fixed later. I have no idea when the developer will come out with an update.

Now the option to mask the debug output is really needed because the theme developer responded that I have to change the font in order to not get the error. So now when it’s time to do the CTC update on my sites, I have to change the font, run the CTC update, then go back and change the font.

I hope I’ve explained this and you can see why just being able to say “skip the errors, do the CTC update” would be a helpful option.

And let me say once again that the quality of your tech support is just stellar. Thank you!

Things just got worse. Although you helped me with one site, I never did go back to the Sparkling developer and tell them of the problem. I need to get back on this and resolve this issue, so today I logged into one of my sites and discovered that the author had updated his theme. Great, maybe it fixed the undefined index errors.

No such luck. This time when I ran the analyzer I was hit with several pages of the following error:
————
Notice: Indirect modification of overloaded element of WP_Hook has no effect in /home/content/p3pnexwpnas04_data02/02/2906402/html/wp-content/object-cache.php on line 709
————–

When I did the debug thing you told me about: turn on debug, activate the master theme and call up the home page, the home page would not load. All I got was a page full of these errors instead. I re-upload the non-debug wp-config.php and the site is back up, but I’m no closer to resolving the Child Theme Configurator problem.

I would like an option to update my child theme configurator software without running in debug mode. My only other option is to create a new child theme (child-them.01, .02) each time you issue an update.

The original error and this error references a directory that I cannot see in FTP:

Undefined index: size in /home/content/p3pnexwpnas04_data02/02/2906402/html/wp-content/themes/sparkling/inc/extras.php on line 304
PHP Notice: Undefined index: style in home/content/p3pnexwpnas04_data02/02/2906402/html/wp-content/themes/sparkling/inc/extras.php on line 304

Judging by some other messages to the developer about this problem, they were caused by an add-on. The problem is that I have no idea what is in the content directory and what these other directories hold. I have a call in to GoDaddy to try to find out. My add-ons are very minimal and I know I shared those with you in my first message.

I’m wondering if you could replicate this problem by loading the old version of your software on a version of the theme before this very latest update. Then updating your software starting with mid-year last year when this problem started appearing?

I don’t want to debug the theme, I don’t know how to fix the errors, I just want to use your software and proceed, that’s why I would like the option not to run in debug mode, just use the current child theme and update your software.