badrobot

Here is a screenshot of the client area of the widget management interface that is erroneously displaying “garbage” due to inappropriate error handling.

https://drive.google.com/file/d/1j36UQ29WDCD27dvUwAG7-7tJ6ojNx65E/view

Below is the text of the “garbage” that consists of the text being displayed. Note also that the site’s background is displayed. Again, I reported these warnings to the plugin authors but I still contend that the manner in which these warning are displayed in the 5.8 version of the new block enabled widget editing interface is erroneous and inappropriate.

Warning. Invalid argument supplied for foreach() in /home/customer/www/plymouthcountybeekeepers.org/public html/wp- content/plugins/nextgen- gallery/products/photocrati nextgen/modules/nextgen_gallery_display/module.nextgen on line 108

Warning. call user func array() expects parameter 1 to be a valid callback, function ‘duplicator_global scripts’ not found or invalid function name in /home/customer/www/plymouthcountybeekeepers.org/public html/wp-includes/class- wp-hook.php on line 303

• This reply was modified 4 years, 10 months ago by badrobot.

OK but the only place the errors were visible where in the new block implementation of the widget maintenance interface. Nowhere else. When I activated the classic widget plugin my problem went away. Doesn’t that point the finger at the new functionality? Did they leave some localized debugging turned on when it went to production like the surgeon leaving the scalpel inside the patient when they sew them up?

• This reply was modified 4 years, 10 months ago by badrobot.

That may be the case but should the initial client area of the block version of the widgets interface be displaying unrelated plugin warnings? Is that not something that the core WordPress team should be aware of?

• This reply was modified 4 years, 10 months ago by badrobot.

It turns out that it is a Siteground specific issue that you might want to be aware of.

Siteground did away with cpanel and replaced it with “Site Tools” that are crap. In the process they changed the underlying directory structure. When I contacted them they gave me some bad information. The new root structure is /home/{randomly generated goobledeegook username}/www/{domainname}/public_html/ however that does not work in wordpress but they kept insisting that it was correct and that issue is with the plugin. I then stumbled upon the solution in wordpress under tools->site health->info. The directory section there reported it as /home/customer/www/{domainname}/public_html/. When I used that scheme instead the directory filters worked as expected. Apparently they are aliasing the string “customer” to the {randomly generated goobledeegook username} on a domain/customer basis under the hood and for some reason the alias “customer” works but not the real {randomly generated goobledeegook username} string.

Hopefully this will save somebody a few hours of aggravation on me…

• This reply was modified 5 years, 2 months ago by badrobot.
• This reply was modified 5 years, 2 months ago by badrobot.
• This reply was modified 5 years, 2 months ago by badrobot.
• This reply was modified 5 years, 2 months ago by badrobot.

Warning: This plugin has not been tested with your current version of WordPress.

No Longer Working
By Kevin Mason (kevinmason) on February 13, 2020

Sadly this plugin no longer works. It was great at one tie but now it seres no purpose Very disappointing.

Used to be good
By clarkehylton on January 11, 2020

This used to be the go-to plugin for making your site easily mobile. But at the time of this writing it hasn’t been updated in more than a year, and little issues have been cropping up that were never a problem before — probably because WordPress has been updated several times in the last year. Some of the problems are likely related to caching, but that never used to be an issue. So it requires a fair amount of troubleshooting. I’d like to see this updated again. It’s gone long enough that the free version appears to be abandoned.

I just noticed that a “[ Please do not bump. ]” message was added to my message above. All I did was answer the question. I don’t know what bumping is or how to do it. Apparently it is a point of order warning but I do not understand it or know what I did wrong. Can someone please explain? The explanation at https://ww.wp.xz.cn/support/guidelines/#do-not-bump-posts implies that I was somehow, nefariously attempting to raise the level of my issue in the “importance” queue. That is not the case because, as I said, I was just answering the previous question.

Also, and more importantly, I could use some help with this issue. I maintain a WordPress site where I would like to implement embedded Google Group Functionality but I can not get it to work.

• This reply was modified 6 years, 11 months ago by badrobot.

I have an ubuntu laptop as well. Is it maybe more feasible to work with an Apache/Linux sandbox?