rsingel

Fixed with some custom CSS.

Hi,

Thanks for the note. I looked at the post you pointed to in Chrome and Firefox on Mac and don’t see any artifacts.

Could you let us know what browser/OS you are seeing this on so we can replicate it?

If it’s easier, you can drop us a note/screenshots to [email protected].

Best,

Ryan

Hi Fisnolio,

Can you drop a note to us at info @ contextly.com with urls for both 1 and 2.

The replacement of the images does take a little time due to caching, but would like to see if something’s not working the way it should.

Thanks,

RS

Hey Matthew,

There’s two kinds of sidebars in Contextly.

The first is manually created and inserted in a specific post. These only include the stories you choose. You can also then later re-use these. You create these using the button on the Visual or Text editor. You can move them around and also edit them (simply highlight the shortcode and then press the edit button).

The “auto-sidebar” works a bit differently. When you turn this on, you’ll see a short-code whenever you start a new post. You can move this where-ever you like in a post. This will contain related stories chosen by our algorithms. The number of stories in that sidebar is controlled by the auto-sidebar settings.

Automatically adding sidebars into all posts, including older posts is something we are looking at, but it’s significantly more involved. For instance, there can be issues with older stories where existing multimedia content will be at the spot where the sidebar goes, making for an odd layout.

– RS

That error message isn’t caused by our plugin. It’s an error generated by update.php, which is a core WP file.

If you are seeing an error message you believe to be caused by Contextly, please email us at [email protected] with your site name and the error message.

RS

Hey JJNW,

Can you paste or email us ([email protected]) with the error you are seeing in the logfile?

Thanks!

RS

Hi James,

Since we only used that command to bundle two files together, we moved it server side.

The new version of the plugin without it is now live: https://www.ads-software.com/plugins/contextly-related-links/

Thanks for bringing that potential issue to our attention.

Best –

RS

Closing this.

Hi James,

Thanks for the note. So far we haven’t had any problems with any hosts over that, but I asked the team to take a look at using the filesystem API instead.

Did you run into a problem?

Best –

RS

Hi Michael,

This issue is now resolved. We now identify the featured image in each post, and for posts without featured images, use the biggest image we can find.

Best –

RS

Hi Manoj,

We identified the bug and have updated the plugin so that it won’t happen again.

Thanks for letting us know.

Best –

RS

Hi Andri,

Updating images is a bit tricky because of weird quirk in WordPress.

The secret is to change the image, then change something meaningless in the post. Add a space somewhere after a period. Then UPDATE the post. After that, we’ll figure out the new image.

We do have plans to make this automatic, but here’s the explanation of why that happens.

Our system relies on the WordPress “update” time. Basically, we constantly check if a post has been updated by looking for a timestamp that is more recent than the one we have, and if that new timestamp is there, we then look for new tags, categories, images, text, urls, etc.

But, WordPress doesn’t change the update time if you change the featured image. So basically, our system doesn’t know a change has occurred if a featured image is changed. This is a known problem and we have a few ideas on how to fix it.

Thanks for letting us know and we do plan to make this effortless in the near future.

Hi Pete,

The newest version of the plugin should fix this issue. Love to have you re-install.

Best –

RS

Michelle,

That’s so awesome. That’s exactly why we built Contextly – to help publishers of ALL sizes to build the readership they deserve.

Thank you for the kind words – they made our day!

RS