Forum Replies Created

Viewing 15 replies - 1 through 15 (of 15 total)
  • Is there a way to fix this without using shell commands? I don’t know how to access that kind of thing.

    Thread Starter adum

    (@adum)

    Found this: http://wordpress.org/support/topic/294547?replies=23

    Things are back to normal. I am happy. 🙂

    Thread Starter adum

    (@adum)

    I get this error below posts when I am editing them and WP tries to save a drafte, after I deactivated GZip Output and left Robots on:

    WordPress database error: [Unknown column ‘robotsmeta’ in ‘field list’]
    UPDATE wp_posts SET robotsmeta = ” WHERE ID = 139

    Warning: Cannot modify header information – headers already sent by (output started at /wp-includes/wp-db.php:615) in /wp-includes/classes.php on line 1586

    I’m having this problem when I try to install Robots Meta on one of my new blogs (WP 2.9.1).

    I’m an idiot…I now realize that Facebook stores the link info for a certain amount of time, so I needed to create new posts to really check if it was working or not.

    It turns out there is some kind of conflict with WP Ajax Edit Comments. When I turn it off, Facebook is able to recognize <link rel="image_src" href="http://www.mysite.com/image.jpg" />. When it is the plugin is on, Facebook doesn’t pick up the image.

    I’ll contact the makers of the plugin and let them know the issue. I am 90% sure it’s the problem. I didn’t try every single combination of disabling plugins to confirm it’s Ajax Edit Comments, but I did try ones I thought may be the problem, namely WP Super Cache and WP Minify.

    I’m happy to at least know the problem…now I’m not sure if the upgrade to 2.9 causes an issue with the plugin or if Ajax Edit Comments had to be upgraded and they changed their code or what.

    I really appreciate your helping Ipstenu, thanks so much. 🙂

    I don’t think it’s actually the hosts anymore. Both are now getting the correct <link rel="image_src" href="http://www.mysite.com/image.jpg" /> in the <head>, but now neither is supplying that image to Facebook.

    I thought the blog on HostGator was working before because I only had 1 picture in the post and no comments (w/ avatars), whereas my blog on BlueHost has multiple pictures in the post and lots of comments (w/ avatars), so when I posted the link to Facebook, it only gave me one picture option (which is what it did when it was working, gives you only 1 option, the picture I specify).

    (For all of this testing I’ve been posting the link to Facebook by hand rather than through Twitter btw.)

    So what I did was disable all plugins on both blogs and switch the themes to default (kubrik). I added the function into the default themes functions to get the Facebook image, and checked the page source to make sure it came up on both blogs, which it did.

    I still had no luck when I posted those links to Facebook. Facebook is not recognizing the <link rel="image_src" href="http://www.mysite.com/image.jpg" /> for whatever reason.

    I’m looking back through my Facebook updates and it looks like the last time things worked for sure was December 18th. December 21st and onward is when things haven’t been working. I think that may have been when I upgraded to 2.9, I just didn’t realize the problem was occurring at the time (holidays going on etc…).

    SOOOO I think it’s something on the WordPress end. I find it unlikely both BlueHost and HostGator acquired issues at the same time, and like you said if it was a FB issue then like you said, a lot more people would be complaining.

    I guess I’ll send something to the WP guys, hope they can look into it. 🙂 Just not sure where the best place to file this…

    Uggg what a bummer. I guess I get what I pay for, right? 😉

    I might try disabling all my plugins to see if that has any effect, I’ll report back if I have any success.

    Do you really think it’s a problem with my hosting rather than being a problem with Facebook?

    Ok well I fixed the blog that wasn’t working…this is the right code for the function:

    function get_social_img() {
    global $post;
    if ( is_single ()){
    $image = "";
    $image = get_post_meta($post->ID, 'fb_img', $single = true);
    ?>
    <link rel="image_src" href="<?php echo $image; ?>" />
    <?
    }
    }

    I was missing: $image = "";

    So now all the blogs DO have the correct meta tags for Facebook…it just isn’t being read for whatever reason.

    <head> is the place you want this, right?

    I just checked CPanel and it says HotLink protection is disabled (which is what I want, right?).

    My Facebook images are having problems on my other host too now. My function just doesn’t seem to be working there either. (My two hosts are Bluehost and HostGator btw).

    It’s an issue because my Fan Page is synchronized with my Twitter, and so when I Tweet that there is a new blog post, it gets sent to the fan page and the first image that is chosen is my header (which looks bad).

    I am now looking at the source code of the my sites…on the ones hosted on HostGator is looks like

    <link rel="image_src" href="http://www.mysite.com/image.jpg" />

    is getting passed on to the header. It’s not really nestled along with all the other link rels but it gets in before the </head>. HOWEVER Facebook is not picking this image up anymore (maybe it needs to be higher up?).

    My one blog stopped picking up the image for whatever reason. This is what came up in the source code:

    <link rel="image_src" href="" />

    I have the same function set up in this blog that is set up in the others…not sure what to make of this. :/

    I appreciate all the help Ipstenu. 🙂

    Ipstenu: I didn’t know what hotlinking was before you mentioned it, but I don’t think I have it disabled. How would I check this type of thing? What would I ask my host?

    btw, this is the function I use within WP for specifying the FB image:

    function get_social_img() {
        global $post;
        if ( is_single ()){
           $image = get_post_meta($post->ID, 'fb_img', $single = true);
           ?>
           <link rel="image_src" href="<?php echo $image; ?>" />
           <?
        }
    }
    add_action('wp_head', 'get_social_img');

    fb_img is metadata I give each post, I specify the image URL there.

    Man I thought this was something I messed up, didn’t realize other people were having trouble too.

    I use a function in my blog which is supposed to specify the image for each post I want to use for the FB thumbnail, but it stopped working after I upgraded and it keeps showing the wrong image now.

    HOWEVER my blogs that are hosted by HostGator are cool, they still work. It’s my blog that is hosted on BlueHost that’s the issue.

    Not sure who’s fault it is, but I hope this gets fixed.

    Thread Starter adum

    (@adum)

    So far “Simple Tags” causes a totally blank screen when I activate it and “Yet Another Related Posts Plugin YARPP” causes just the plugins screen to show nothing.

    EDIT: “HeHeHunter’s Infolinks” and “WordPress Mobile Edition” also cause a blank plugins sreen.

    Simple Tags looks like it was the main problem, but those other 3 seem to have some issues too.

    Everything seems to be good now and my site is back up and running, so I am pretty relieved!

    Thread Starter adum

    (@adum)

    I renamed both at separate times, but currently themes is the default “themes” and I am copying each plugin from plugin.hold to the new plugin folder to see if I can tell if there is a plugin causing the problem.

    Is this the right thing to do?

    Thanks for you help. 🙂

    Thread Starter adum

    (@adum)

    I got this error when I tried to open the list of plugins:

    Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 7680 bytes) in /home1/mysite/public_html/blog/wp-includes/kses.php(401) : runtime-created function on line 1

    So I did a search on that and the solution for that was to change wp_settings.php from 32 to 64 M of memory, and voila my general settings page was fixed too!

    Maybe that will help some other people out.

    Thread Starter adum

    (@adum)

    ugg nevermind I just deleted and reinstalled so it seems to be working fine now.

Viewing 15 replies - 1 through 15 (of 15 total)