WordPress throws error when trying a page with a gdoc query shortcode

[fabacab]

WordPress throws error when trying a page with a gdoc query shortcode

[martijn19811]

This is the stacktrace:
Een fout van het type E_ERROR werd veroorzaakt op regelnummer 1171 van het bestand /var/www/roosendaalsbiergilde.nl/site2/wp-content/plugins/inline-google-spreadsheet-viewer/inline-gdocs-viewer.php. Foutmelding: Uncaught Error: Call to a member function has_cap() on boolean in /var/www/roosendaalsbiergilde.nl/site2/wp-content/plugins/inline-google-spreadsheet-viewer/inline-gdocs-viewer.php:1171 Stack trace: #0 /var/www/roosendaalsbiergilde.nl/site2/wp-content/plugins/inline-google-spreadsheet-viewer/inline-gdocs-viewer.php(1105): WP_IGSV\InlineGoogleSpreadsheetViewerPlugin->canQuerySqlDatabases() #1 /var/www/roosendaalsbiergilde.nl/site2/wp-content/plugins/inline-google-spreadsheet-viewer/inline-gdocs-viewer.php(1025): WP_IGSV\InlineGoogleSpreadsheetViewerPlugin->getSqlOutput(Array, '') #2 /var/www/roosendaalsbiergilde.nl/site2/wp-includes/shortcodes.php(325): WP_IGSV\InlineGoogleSpreadsheetViewerPlugin->displayShortcode(Array, '', 'gdoc') #3 [internal function]: do_shortcode_tag(Array) #4 /var/www/roosendaalsbiergilde.nl/site2/wp-includes/shortcodes.php(199): preg_replace_callback('/\\[(\\[?)(gdoc)(...', 'do_shortcode_ta...', '\nDe belangri...') #5 /var/www/roosendaalsbiergilde.nl/site2/wp-includes/class-wp-hook.

Oddly enough, things do seem to go well when disabling the Yoast SEO plugin. I am not sure which plugin is to 'blame'.

[fabacab]

Oddly enough, things do seem to go well when disabling the Yoast SEO plugin. I am not sure which plugin is to 'blame'.

One day, a patient came to their doctor and said, "Doctor, it hurts when I do this."

"Hmm," the doctor said. "Well, don't do that."

[martijn19811]

I've been a developer for quite some years now. I've submitted a few issues to different kind of repositories. The feedback I received was always great. People showing interest in how their plugin can actually be improved.

That's why I'm baffled by the response above. Not only does this metaphor feels very condescending, but basically stating: "well, if it doesn't work with this plugin, simply stop using it", feels like a complete lack of interest.

If you've looked through the stacktrace and quickly decided that this is not the fault of the inline gdocs viewer, then great. Please state so in a clear manner and we're all good :). Then I do know I should bother other people.

I'm a fan of your work itself. The viewer is pretty good. But please understand this is just an honest attempt to sort out bugs and get them fixed, in order to improve the plugin. I've clearly stated the problem, I've even added a stacktrace and thereby I hope I've showed you enough respect. All I ask is the same from your side.

[fabacab]

This issue seems to be the same issue as this one posted on the Support forum I no longer monitor. This posting was made exactly one day after that original one.

You're trying to get me to support a plugin that I explicitly and vocally no longer support. I don't feel like that's showing me any respect, and therefore I don't feel like I owe you any, either.

If you want the bug fixed, send me a patch. Otherwise, don't waste any more of my time.

[martijn19811]

Wow. Alright, if you really feel this way: consider transferring the ownership of this repository to someone else. By not supporting this plugin in any way possible, you're not making things easier for people actively using this tool. I'm sure we can agree on that, right? :)

Again, despite what you're saying to me, I am a fan of your work and I do not think this work should go to waste this way. If we, as the WordPress community, can keep this plugin alive and kicking by handing this repository to someone else, then we should consider that.

[fabacab]

As the readme of this plugin clearly describes, it is the "WordPress community" that made me so fucking bitter about spending my time trying to support this plugin for them in the first place. ¯\_(ツ)_/¯ Fork at will.

[martijn19811]

No, I will not do that. It's clear to me that this plugin cannot receive the attention it should have. Without anyone else being able to take care of this repository, I should know better and look elsewhere. Thanks for your time.

[fabacab]

All right then. Good luck.