[Solved] TubePress Problem communicating with Vimeo: The oauth_signature passed was not valid.

[Solved] TubePress Problem communicating with Vimeo: The oauth_signature passed was not valid.

Vimeo is a great tool for any marketer and regular joe. So why is it that things keep breaking around it? Well, simply said things change. Vimeo updates its service offering, and so does its API over time. How to combat this? Code updates! That's how. Good news is, that when you use TubePress, it eliminates a lot of your WordPress related stress when it comes to Youtube and Vimeo videos. The down side? They also need to update their code regularly AND you as the consumer need to make sure everything is 100% correct. If not, you could potentially get a dreaded message from TubePress like this one: Problem communicating with Vimeo: The oauth_signature passed was not valid. Oh noes! What to do! The horror! As the best life guide book said: “Don't Panic” (in big letters on the cover). You're in luck, because I have a (potential) solution for you! The best part, it's extremely easy. Click over to Page 2 to find out how! To be honest there are two steps to this. Both are very trivial.

First and foremost: **make sure your TubePress plugin version is up-to-date. That usually helps eliminate a lot of issues. **The super easy fix: Head over to your TubePress Options onto the “FEED” tab. TubePress Feed Tab         Now check both the Vimeo API “Consumer Key” and the Vimeo API “Consumer Secret” for any trailing spaces. What does that mean? Put your cursor at the END of either key/secret and if there is a ” ” (a space) right after either one, delete that space (or spaces if you had more than one). Let me repeat there in another way: THERE SHOULD BE NO SPACE AFTER EITHER THE KEY OR SECRET. If there is, it'll cause problems. Sadly the screenshot doesn't show it, but in that shot there is a space right after the “95” in the key. So I simply put my cursor after it, selected the space (just to make sure my eyes weren't deceiving me) and deleted the space. And like magic TubePress worked perfectly again and the error was completely gone! Rejoice everyone! Let us all know if this worked for you (or not … but preferably if it did).