Sovrn

Hello,

I apologize for the inconvenience you are experiencing. Unfortunately, a code push broke a line of code on the WordPress Related Posts by Sovrn. The problem has been diagnosed, and code is being reverted.

I would like to thank you for your patience in resolving this issue. We have detailed the solution below, and unfortunately, it entails removing the plugin entirely, and reinstalling to version 3.6.1.

Option 1:
1. Contact your web hosting company, and have them delete the “wordpress-23-related-posts-plugin” folder from the “wp-content/plugins/” folder.

Option 2 (for those comfortable managing files):
1. Log into your site’s files using the File Manager provided by your web hosting company or by using an FTP program (such as Filezilla).
2. Browse to “wp-content/plugins/” folder for your WordPress site.
3. Delete “wordpress-23-related-posts-plugin” folder.

Once you have completed option 1 or 2, “Reinstall “wordpress-23-related-posts-plugin”. The latest plugin version should be 3.6.1”

Again, apologies for the inconvenience.

Sovrn Support

Hello,

Thank you for your inquiry. Please see the detailed directions below to setup custom field ‘image’ for your Related Posts thumbnails.

First, go to your create-new-post page or one of your previous already-published-posts. On the top right corner you should see the ‘Screen Options’ button; click on it for the drop-down menu to open. After that, select the box next to ‘Custom Fields’.

Now you should be able to see a new box below the editor called ‘Custom Fields’. Create a new custom field, name your image that you would like to use as a thumbnail for the specific post (something like “My thumbnail”), enter the URL of the image you would like to use and finish by selecting “Add Custom Field”. Remember to save this draft, or publish the post when you’re ready.

After that, go to ‘settings’ on your plugin and scroll down to the bottom. The option called “Use custom field for thumbnails” should now be available, select the box next to it, and select the value you’ve set up before (if you used “My thumbnail”, select that one).

Now, the important thing is this: the value of the Custom Field stays the same for every new post, while the URL of the image changes. In other words: the name of the Custom Field stays the same, images change. That’s because once you set up your settings in the plugin settings (when you choose which value our the Custom Field our plugin should use for the thumbnails), you won’t have to change it again in the future. This way you save yourself a lot of time.

Once you have set this up, you just add a Custom Field with every new post, set the image you want to use for the thumbnail, while the name stays the same. Also worth noting is that you should keep the images you want to use for thumbnails as square as possible and that they’re not too big. The perfect size would be 151×151 pixels (or bigger), but that is not that crucial. Just don’t use the biggest images you can find, because this can return you some problems.

I hope this information helps!

Meghan
Sovrn Support

Hello Maja,

Thank you for your inquiry and information you provided in your post. I will pass this information along to our engineering / development team to potentially develop a ‘translation option’ in a subsequent release of the plugin.

Happy Blogging ??

Meghan
Sovrn Support

Hello,

Thank you for your inquiry. If you have not yet registered the plugin, start writing a post in the top of the Editorial Assistant (EA) widget. Once you starting typing you will see in sign in button. Click the sign in button and it will open the preferences application where you will find a link to register near the bottom left of the preferences page. If, however, you have registered your plugin, start writing a post in the top of your EA. Once the EA widget starts, you can click the highlighted ‘preferences’ link, at which point you should be able to recommend links from your own page.

I hope this information helps!

UPDATE: For those that have already downloaded the 3.6.2 update and it has caused issues, the best solution is as follows:

Option 1

1. Contact your web hosting company, and have them delete the “wordpress-23-related-posts-plugin” folder from the “wp-content/plugins/” folder.

Option 2 (for those comfortable managing files):

1. Log into your site’s files using the File Manager provided by your web hosting company or by using an FTP program (such as Filezilla).
2. Browse to “wp-content/plugins/” folder for your WordPress site.
3. Delete “wordpress-23-related-posts-plugin” folder.

<p>
Again, we apologize for this inconvenience. We are currently conducting a postmortem meeting to make sure this problem is not repeated. I will provide our conclusions here.

Thank you.

UPDATE: For those that have already downloaded the 3.6.2 update and it has caused issues, the best solution is as follows:

Option 1

1. Contact your web hosting company, and have them delete the “wordpress-23-related-posts-plugin” folder from the “wp-content/plugins/” folder.

Option 2 (for those comfortable managing files):

1. Log into your site’s files using the File Manager provided by your web hosting company or by using an FTP program (such as Filezilla).
2. Browse to “wp-content/plugins/” folder for your WordPress site.
3. Delete “wordpress-23-related-posts-plugin” folder.

<p>
Again, we apologize for this inconvenience. We are currently conducting a postmortem meeting to make sure this problem is not repeated. I will provide our conclusions here.

Thank you.

UPDATE: For those that have already downloaded the 3.6.2 update and it has caused issues, the best solution is as follows:

Option 1

1. Contact your web hosting company, and have them delete the “wordpress-23-related-posts-plugin” folder from the “wp-content/plugins/” folder.

Option 2 (for those comfortable managing files):

1. Log into your site’s files using the File Manager provided by your web hosting company or by using an FTP program (such as Filezilla).
2. Browse to “wp-content/plugins/” folder for your WordPress site.
3. Delete “wordpress-23-related-posts-plugin” folder.

Again, we apologize for this inconvenience. We are currently conducting a postmortem meeting to make sure this problem is not repeated. I will provide our conclusions here.

Thank you.

• This reply was modified 8 years, 1 month ago by Sovrn.

UPDATE: For those that have already downloaded the 3.6.2 update and it has caused issues, the best solution is as follows:

Option 1

1. Contact your web hosting company, and have them delete the “wordpress-23-related-posts-plugin” folder from the “wp-content/plugins/” folder.

Option 2 (for those comfortable managing files):

1. Log into your site’s files using the File Manager provided by your web hosting company or by using an FTP program (such as Filezilla).
2. Browse to “wp-content/plugins/” folder for your WordPress site.
3. Delete “wordpress-23-related-posts-plugin” folder.

<p>
<p>

Again, we apologize for this inconvenience. We are currently conducting a postmortem meeting to make sure this problem is not repeated. I will provide our conclusions here.

Thank you.

• This reply was modified 8 years, 1 month ago by Sovrn.

Our apologies for this inconvenience. We used a new process for updating code for the plugin and it clearly failed. We are in the process of fixing the issue right now and have an ETA of 30-90min. If you have the ability to deactivate the plugin, that would be the most immediate solution.

I will provide updates here every 30min.

Going forward, we are definitely reverting back to our proven process for code updates to ensure this situation does not happen again.

Again, our apologies for the inconvenience.

Our apologies for this inconvenience. We used a new process for updating code for the plugin and it clearly failed. We are in the process of fixing the issue right now and have an ETA of 30-90min. If you have the ability to deactivate the plugin, that would be the most immediate solution.

I will provide updates here every 30min.

Going forward, we are definitely reverting back to our proven process for code updates to ensure this situation does not happen again.

Again, our apologies for the inconvenience.

Our apologies for this inconvenience. We used a new process for updating code for the plugin and it clearly failed. We are in the process of fixing the issue right now and have an ETA of 30-90min. If you have the ability to deactivate the plugin, that would be the most immediate solution.

I will provide updates here every 30min.

Going forward, we are definitely reverting back to our proven process for code updates to ensure this situation does not happen again.

Again, our apologies for the inconvenience.

.

• This reply was modified 8 years, 2 months ago by Sovrn.