There is a yet one issue in this blog linking plugin.
Error log gives me the next error:
file: ccomhr/public_html/igranje_novo/wp-content/sp-resources/forum-plugins/blog-linking/library/sp-linking-blog.php
line: 224
function: sp_show_blog_link
Notice | Trying to get property of non-object
Can you do something with this?
Woo hoo!!! Just updated and everything’s working on the test site. Will update the live site later on this evening and let you know. Great job guys. Thanks so much 
we fix these harmless notices as we, or our users, find them… slowly but surely getting them all…
ozgirl57: I don’t know if you updated the linking plugin via the updater or through svn but there are some further changes for this in the svn repository that I only made yesterday. It would be great iof you could try them out. Er… maybe save off a copy of the plugin first just in case… 
If you don’t want to do that now then they will be available via the updater soon of course.
Just updated everything using the latest svn and everything is looking good! You guys do a great job and I love the new version of the forum – it’s very lightweight and looks super. Thanks again 🙂
I’m getting a similar error and warnings after updating my plugins. The only way I can get the error to go away is if I deactivate my blog-linking plugin.
I noticed after updating my plugins that there was a warning about the blog linking plugin and that it had been deactivated. It wasn’t available to reactivate on my on my list of plugins so I tried to reinstall it. The first time it wouldn’t reinstall because it said the folder already existed. I tried a second time and it appeared to install just fine. But that’s when the error and warnings showed up below.
The website is ProjectsInMetal.com/forum – but the plugin is currently inactive.
Warning: include_once(/problem-with-post-edit-buttonome/content/77/7671077/problem-with-post-edit-buttontml/projectsinmetal/wp-content/sp-resources/forum-plugins/blog-linking/template-tags/sp-linking-show-link.php) [function.include-once]: failed to open stream: No such file or directory in /problem-with-post-edit-buttonome/content/77/7671077/problem-with-post-edit-buttontml/projectsinmetal/wp-content/sp-resources/forum-plugins/blog-linking1/sp-linking-plugin.php on line 454 Warning: include_once() [function.include]: Failed opening '/problem-with-post-edit-buttonome/content/77/7671077/problem-with-post-edit-buttontml/projectsinmetal/wp-content/sp-resources/forum-plugins/blog-linking/template-tags/sp-linking-show-link.php' for inclusion (include_path='.:/usr/local/php5/lib/php') in/problem-with-post-edit-buttonome/content/77/7671077/problem-with-post-edit-buttontml/projectsinmetal/wp-content/sp-resources/forum-plugins/blog-linking1/sp-linking-plugin.php on line 454 Fatal error: Call to undefined function sp_do_TopicHeaderShowBlogLink() in /problem-with-post-edit-buttonome/content/77/7671077/problem-with-post-edit-buttontml/projectsinmetal/wp-content/sp-resources/forum-plugins/blog-linking1/sp-linking-plugin.php on line 455
It looks like you have the number 1 after the folder blog-linking. Try removing the 1 in the folder name using either FTP or your CPanel file manager.
FTP showed that I indeed had bloglinking and bloglinking1 folders. I backed up both folders and then deleted them. Then reinstalled the plugin. Oddly it re-created a folder named bloglinking1 (instead of bloglinking). And it broke both the front end (blog portion), backend (dashboard), as well as the forum. I quickly deleted the folder via FTP and it’s back to normal.
So … how might I go about re-installing the blog linking plugin properly?
I looked at my backed up folders. blog-linking seemed to have missing files while blog-linking1 didn’t have anything missing. Should I try to re-upload blog-linking1 and rename it to blog-linking or is there a better/safer way? I don’t want to brick my site.
I was able to get it sorted. I uploaded the folder that didn’t seem to be missing any files (blog-linking1) and renamed it to blog-linking. All is working now. Thanks!
Good deal. Glad you figured it out. That problem with the ‘1’ added to the folder name has been something that has turned out to be tricky in trying to figure out. It could be anything from a WP problem to people downloading the same file twice. We have been looking at some ways to eliminate both WP and user errors and have implemented a few changes recently but it is still happening occasionally on certain installs.