jkatinger

I got some feedback from the ThinkUPThemes support team. They verified that this is intended behavior and not nefarious…

“It’s not malicious script. It’s a verification script. You can remove with the help of this knowledge base article: https://www.thinkupthemes.com/docs/remove-fallback-verification-script/ “

I implemented this in my sub-theme functions.php file as suggested and it works perfectly. Less involved than a plugin-based solution.

Same issue here but with the Minamaze Pro theme from the same provider.

The Shortcode was the issue! Not sure why that didn’t make sense last night. I did not need to make the code change recommended here to get this to work, but is this something I should do for security reasons?

Michael,

Appears that CMB2 is being used in the theme I’m using on this site (Minamaze Pro from Think Up Themes). I bought the theme WAY back in 2014, and I do not see anything allowing me to update the theme via the WP admin area so that lines up with your assumptions. So perhaps my best next step is to attempt to work with Think Up on getting my theme updated. Does that sound like the right move to you?

Secondarily, if Think Up can’t be reached (I say that because I see some notes online about them being very slow to reply of late, etc) – do you think simply replacing the cmb.js file in the theme could be a fix, or is that asking for more trouble in your experience?

Thanks so much for sticking with me on this!

-Josh

Hello Michael and thanks for responding. I am indeed familiar with console in Chrome, but not so much with fully understanding the errors I’m seeing. Here’s a screen grab: https://rrdc.org/wp-content/uploads/2020/10/rrdc-console.png

Do any of these make any sense to you?

I guess I should also point out that the other widgets on the right sidebar of the admin screen also do not seem to work (expand, collapse, etc). Fields like Featured Image and Excerpt. Don’t think it’s a JS related issue as I’ve tried in Chrome and FireFox on Mac and I’ve not disabled or otherwise mucked with JS settings on either browser and the issue is the same in both.

Nobody? Nothing?

Sweet…thanks.