WWDay3

I would say the site where I had the plugin installed is not larger than yours, perhaps a bit smaller.

The issue presented itself when I updated the plugin from the repository. Before the update, no problem. As soon as I updated, the error occurred. I manually moved the plugin to a “plugins2” directory, the error went away, I submitted the ticket, and looked for a replacement.

Later, I deleted the plugins2 directory, so I can’t even check now what version it was.

Sorry I’m not more help.

By the way, @webtemyk, after the original response 2 months ago, I tried what you suggested and disabled every other plugin on the site, and still got the error. I had no time to pursue the issue further, so I removed your plugin and found another plugin I could work with. I forgot to report the results back here (sorry about that).

I’m sorry, I don’t understand what you mean.

I am trying to post remotely from MS Word (which I do frequently).

MS Word fails while WPFC is active. It works when WPFC is disabled.

Does your plugin do something that would affect XMLRPC?

After some digging into the scripts, I found the solution.

In jetpack/modules/contact-form/admin.php the button is added using an add_action function at the top. Then, later, in jetpack/modules/contact-form/grunion-editor-view.php the button is removed from init and then re-added to admin_head with array( __CLASS__, ‘grunion_media_button’ ). I “fixed” it (for now) by adding

remove_action( ‘media_buttons’, array(‘Grunion_Editor_View’, ‘grunion_media_button’), 999 );

in my function.

My function is now being added to both init and admin_head (just in case).

This approach seems like questionable coding to me.

And, the lack of comments in the scripts is really annoying. A couple of simple comments added to the code changes could have saved me a bunch of time. (But then, when I write code, I’m a comment freak. Mainly because of situations like this).

I hope this helps someone else.

This is not resolved (and I didn’t receive an email even though I checked the box).

No, it is not resolved. It has happened with a completely “fresh” site nothing but the default plugins and Jetpack installed. But, it does not always do it. I’ve tried “forcing” the error to occur a couple of times, and the results vary.

Ah, never mind. I’m getting confused here between the slug for the news category and the slug for the corresponding page. I got things figured out now. Great plugin!

Thanks. Changed it to /thenews and it worked great.

I copied and pasted [sp_news limit=”10″ show_full_content=”true”] from the post/page editor.

I can do a screen shot, but it doesn’t look like I can post it here. Where do I send it?

I’m trying out Front End Publishing. Seems OK so far

Ah ha. I finally found the button that moves the cache directory. Hidden at the bottom of the http rules page. ** Probably should move it to a more noticeable place. ** Thanks for the help.

Thanks for the tip. However…

I am not seeing gator_cache anywhere in the install for this particular website. Gator Cache seems to think it’s working, but the directory is not there.

No debug info is written to the page source.

Here is the config file

<?php exit;?>
lifetime = 1209600
cache_dir = “/var/chroot/home/content/99/9999999/gator_cache”
group = “xxxxxxxxxx.com”
enabled = 1
gzip = 1
skip_user = 1
last_modified = 0
cache_warm = 1
pingback = “https://xxxxxxxxxx.com/xmlrpc.php&#8221;
debug = 1
skip_ssl = 1
host = “xxxxxxxxxx.com”
dir_slash = 1
jp_mobile = 1
content_type = “Content-Type: text/html; charset=UTF-8”
rss2_type = “Content-Type: text/xml; charset=UTF-8”
atom_type = “Content-Type: application/atom+xml; charset=UTF-8”
rdf_type = “Content-Type: application/rdf+xml; charset=UTF-8”
default_feed = “rss2”
jp_mobile_cache = 1

The wordpress install is NOT at the level listed above. If it was, it should be at “/var/chroot/home/content/99/9999999/xxxxxxxxxx.com/gator_cache” (if I understand what you’re trying to do)

Aha. Figured out where it’s getting the post url. It’s picking up the url from the ‘latest posts’ widget in the sidebar. It may be that widget is coded incorrectly (not resetting the loop correctly).

I think you need to change your plugin to detect the current ‘active’ post. You really have to keep in mind that other plugins and widgets may not do things correctly, and your plugin should keep that in mind.

Additional info. Now, it seems to be stuck with a different post. Oddly enough, I tracked it down by doing some experimentation. It always seemd to be the ‘5th’ post in the blog index. In other words – whatever post shows up in the 5th position in the blog index is what the plugin is picking up to post rather than whichever post is currently being viewed. What the heck is causing this, and how can I fix it? My share buttons are worthless right now and I may have to switch plugins.

I think the PHP code suggestion was intended to be added to the plugin script. I may be wrong, but that’s how I read it. It would have to be added where the plugin is rendering HTML, if that’s what it does. Kinda depends on the plugin. FWIW

Odd though – the only table that had the failure was wp_posts.