Forum Replies Created

Viewing 8 replies - 1 through 8 (of 8 total)
  • njesson

    (@njesson)

    I am using the plugin on two websites. Both are WP 6.8.1 and the plugin is up-to-date. I used both successfully yesterday. I suggest that you check your installation, perhaps even remove the plugin and re-install.

    Cneu,

    When Emma refers to a “featured image”, she is using the WordPress terminology for an image used in your templates. Featured images can be set for each post. Most templates have a default image for when a featured image has not been set.

    The plugin executes at the end of the WP post process. The plugin loads the content of the post using a WP function wp_remote_retrieve_body(). It then uses preg_match to identify four <meta property> tags in the <head> of the post. Please check your post to ensure that the following tags are present:

    <meta property="og:title" content="A sample post">
    <meta property="og:description" content="A description of the post">
    <meta property="og:image" content="http://example.com/image.jpg">
    <meta property="article:published_time" content="...timestamp...">

    Look at the html code of your published post. If the og:image tag is not present, then the plugin will not execute and your post will not be posted to Bluesky. You may be able to edit your WP template to add these tags, but you will need to know what you are doing.

    Many websites have tags using the Facebook standard: fb:image, fb:title, etc… These are equivalent but non-standard. Perhaps a future upgrade to this plugin could search for these as well.

    No, not at the moment. The handle_post function of the plugin tests the post type. If it isn’t a ‘post’ then it is skipped. WP uses numerous other post types which should not be sent to Bluesky, like menus.

    If you wanted to modify the plugin to allow a custom post type, look at lines 70-75. But your changes will be written over when the plugin is updated.

    Custom post types are commonly used in WP. Perhaps this is a topic for a future upgrade. It shouldn’t be difficult to add a setting to allow the plugin to handle a specific post type. The list of registered post types can be found using get_post_types(). There could be a form with a check box for each type.

    The plugin “scrapes” the WP post to identify the image URL. It then pulls a blob of the image from the URL, and passes this blob to Bluesky. The Bluesky API doesn’t ask for an ALT field. The problem isn’t with the plugin, it is Bluesky.

    Thread Starter njesson

    (@njesson)

    OK, it isn’t really a big problem. I live in a place that doesn’t use daylight savings, so I am careful about using the correct timezones. I am surprised that WP doesn’t validate basic PHP functions.

    Frank,

    Perhaps Emma, the plugin developer, will respond to this. It may be a matter for a future development. All I can offer you is some explanation of how the plugin works, and thus why the images might not be optimal.

    The plugin uses the Bluesky API, which provides a mechanism for inserting post data directly into the Bluesky database. The key parts are the title, description, and image. These parts are retrieved as OpenGraph data from the published website, not from the WP database. This is a process known as scraping. So, it matters what your WP template is posting in the headers. (This is also the process used by Facebook and Twitter, so getting it right will affect all three.)

    Check your WP posts. Look at the source code to see what headers are being posted. If the header contains a <meta property=”og:image” …> tag, check the image to see its width and height. The plugin does not create thumbnails or modify the images posted. It pulls the image data from the published website and then passes this og:image content to Bluesky.

    The ideal post image on Bluesky is 16:9, or 1200×675 px. If you use an image with other dimensions it will be scaled to fit. I believe that width is the controlling dimension, so a 600×600 image will be scaled to 1200 wide, and cropped to 675 high.

    It is possible, but unlikely, that your WP template might not use og:image tags, but might have a fb:image, twitter:image, or X:image. See if you can modify your template to add the og:image tag.

    Note to Bluesky developers: a helpful feature would be a mechanism to force Bluesky to re-scrape a website.

    I was experiencing the same problem. So, I have temporarily disabled logging by commenting out line 54:

    // $wp_filesystem->put_contents($this->log_file, $updated_content, FS_CHMOD_FILE);

    A better solution would be to have a setting to turn on different kinds of logs. An error log can be useful, but logging successful posts may not be needed by many users.

    Has this been fixed yet?

    FILE: /home/.../public_html/wp/wp-content/plugins/broken-link-checker/includes/utility-class.php
    ----------------------------------------------------------------------------------------------------
    FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
    ----------------------------------------------------------------------------------------------------
     42 | WARNING | INI directive 'safe_mode' is deprecated since PHP 5.3 and removed since PHP 5.4
    ----------------------------------------------------------------------------------------------------

    This appears as a warning in the PHP Compatibility Checker plugin. It shouldn’t stop us upgrading to PHP 7. It would be nice to remove this warning though.

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