Hi there @westcoastradio
Thanks for your report.
You can download 1.7.4.4 here https://downloads.wordpress.org/plugin/wonderm00ns-simple-facebook-open-graph-tags.1.7.4.4.zip
But before you do, can you please set WP_DEBUG to true or check your error_log so we can find the reason why you’re getting a blank screen. We do not have other complaints so far, so it’s important to find out what specific problem you’re having so we can fix it for you.
This happened also on a site I’ve been working on. Pages with the card tag image field blank did not render and the source on those pages had only the head tag up until the part where the <!– START – Facebook Open Graph, Google+ and Twitter Card Tags 2.0.1 –> should appear (but it doesn’t and <head> is left open too).
For my part switching WP_DEBUG on is a bit tricky as the WP installation is running multiple unrelated sites and I couldn’t reproduce this on my local WP installation.
Hi there @kimmokurola
When you say “card tag image field blank”, you’re referring to the option “Include Image” on the Twitter Card section?
Can you please try our latest version and get back to us on either the problem persists or not?
Thanks for the quick reply.
When editing a page, there’s a “Facebook Open Graph, Google+ and Twitter Card Tags” settings box (div id webdados_fb_open_graph) with only field being “Use this image” with buttons “Upload/Choose” and “Clear field”.
I pasted an URL to an image file to see if the problem was caused by some missing field and this solved the problem for all of the broken pages. There were no problems on pages where this field was already set before.
I’m already running 2.0.1 and according to WP that’s the latest release. Correct?
-
This reply was modified 7 years, 6 months ago by
kimmokurola. Reason: Added version info
@kimmokurola
That field can be left empty. There shouldn’t be any problem with that.
To fix the problem you had to fill that field on ALL the pages? Or you filled it in one page and the problem disappeared on all the website?
This is very odd…
We’ve just made some small fixes and updated to 2.0.2, but it shouldn’t affect your problem at all.
Three pages that didn’t have this field set displayed as blank and filling the field fixed them again. Each of these three pages had to be edited separately to fix them. I tried updating other fields on the pages first and that didn’t have any effect. Other pages with this field filled or as blank worked just fine from the start. There are still pages that don’t have this field set and they render just fine.
I’m not much of an expert on this matter as I work mostly with Node+Mongo. I do just a little bit of WordPress on the side so unfortunately I don’t really have any good guesses why this happened.
Do you have access to the account error_log so we can check it out?
Sorry, I don’t have direct access to the error_log, but my colleague checked it as we noticed the problem. Oddly enough according to him there’s nothing there.
We cannot help if there’s nothing on the error_log or you can’t use WP_DEBUG = true momentarily.
Apologies for the late reply, I’ve been away.
Thanks for the link to the old version of the plugin. I’ll try and set WP_DEBUG to true later today and see what the output is. I’ll have to copy the website over to our dev server though, as I don’t want debugging output on our live site 🙂
It seems to only render the page code up until where the start of the plugin code should be. Not sure if that helps.
Is there anything on the error_log?
I’ve enabled debug mode on a copy of the website on my dev server and got this error message:
Fatal error: Call to a member function current_view_object() on a non-object in /home/blah/public_html/blah/wp-content/plugins/wonderm00ns-simple-facebook-open-graph-tags/public/class-webdados-fb-open-graph-public.php on line 160
Is this on the last version?
Line 160 reads:
$default_options = $this->default_options();
There’s no call to current_view_object() anywhere on the plugin.
Have you tried to disable other plugins, one by one, and use the default theme (Twenty 16 or Storefront)?
Maybe this is some incompatibility, that we’ll need to sort out.
Yes, this is on the latest version (2.0.4).
Found the culprit, the Business Directory Plugin. When I deactivate it, the problem goes away.
I’ll do some more investigating…
