A few months ago, LinkedIn opened up their companies API. It’s been a busy few months, but this weekend I took the time to get this implemented in leenk.me. One of the many things on my to-do list for leenk.me.
If you have a company in LinkedIn, you’ll need to reauthenticate your token between LinkedIn and leenk.me, so we can access your companies. To do this, just remove the LinkedIn account from your leenk.me dashboard and readd it. You should see a new permission being request, “Company Pages”.
Once, you approve the new permissions from LinkedIn, go to manage your API keys, click the API key you’re using to edit it and you should see a new drop down selection for LinkedIn Companies.
Save your settings, and head on over to your WordPress dashboard. Make sure you’re using at least version 2.0.0 of the leenk.me plugin (check for the update). Edit the LinkedIn settings for the leenk.me plugin and make sure you have “Share to Company?” checked.
Save those settings and the next time you publish a post, it should send to your LinkedIn Company page.
This is fairly new, so if you run into any trouble, contact us immediately.
Special thanks to Andrew Kurtis from Webhosting Hub for supplying us with a Spanish translation of the leenk.me plugin for WordPress. If you’re interesting in translation the plugin, check out the files in the i18n directory. This file doesn’t get updated too often, but check with us first to make sure we generate a new one, in case something changes and we forget.
Hey Everyone. Last night I updated the LinkedIn API leenk.me was using. This was required by LinkedIn, they are turning off their old oAuth 1.0 API and have recently brought up a new oAuth 2.0 API.
Facebook did this last year (if you don’t remember). This will require you to log into your account at http://leenk.me/ and remove your LinkedIn account, then re-add it. You should not need to do anything else, but you may want to visit the “manage your API keys” section to verify that your API key(s) have the proper LinkedIn settings.
Sorry for any convenience, unfortunately it was a requirement from LinkedIn. As always, let me know if you have any trouble. Also, I have been getting a few requests to update to LinkedIn Company pages. Unfortunately, this is not currently allowed with LinkedIn. As soon as it is allowed, I will add it to the plugin.
I am in the process of rebuilding the leenk.me site and the leenk.me plugin. It is going to be even easier to manage your connections! I hope to have the website finished in the next couple months and leenk.me 3.0 out by the end of the year. I am also planning on adding Tumblr to the plugin and I have been considering removing Friendfeed (I do not know anyone who actually uses Friendfeed). So, please tell me what you think!
The second most requested thing I have received from leenk.me users is to create a leenk.me affiliate program. Well, guess what, I have finally gotten around to setting up the leenk.me Affiliates program. The leenk.me service was created as an affordable solution to solving the problem of publicizing your WordPress content to your social networks, automatically and instantly. The primary reason I had to ask for money was to cover the cost of server upkeep and to subsidize future upgrades and improvements to the plugin.
The leenk.me Affiliates program has one tier, you get 50% of every sale and payment made by each new customer you refer to leenk.me. Each leenk.me account will continue to get their 1 month free trial, if they decide to keep the service and pay for it after the first month is over, you will get 50% of their payment. If they continue to use and pay for the leenk.me service, you will get 50% for each future payment they make. I plan on approving any pending commissions throughout the month and will payout the commissions on or around the first weekday of every month. Also, you must have a PayPal account to sign up for the leenk.me Affiliates program.
We are using iDevAffiliate to manage all of the affiliate information.
Now you can get paid for referring new users to the leenk.me service!
Let me know if you have any questions!
Posted in Affiliates, News
I just submitted version 2.0.0 of the WordPress plugin for leenk.me to WordPress. You should see an update in your WordPress dashboards any moment now. There are a few pretty great new features in this version… check out the run down in this video:
If you have any trouble, please contact me.
Hey Everyone, I just submitted version 1.4.0 of the leenk.me plugin, which uses the new version of the leenk.me API. As I have mentioned over the past few posts, Facebook has made some changes to their API which will affect leenk.me. Namely, tomorrow, May 2nd, Facebook is removing the “offline access” token which is what leenk.me uses to post on your behalf without you needing to be logged into Facebook. They have replaced this with a 60-day expiring token, which means you will most likely need to refresh your Facebook account on leenk.me every 60 days. Hopefully Facebook will make this a little less annoying before the next 60 days. If not, I apologize, but it is completely out of my control.
If you have updated to leenk.me 1.4.0 it will not work unless you update your account settings. I’ve made a short video explaining what you need to do. Basically, you should only need to “click the big red button”. If you have been using the BETA, you should upgrade to version 2.0.0b5 which includes the new API.
I know there are many users out there who have had to create multiple leenk.me accounts. With this new Account Settings page, you will probably be able to switch to a single account. This is where things could get confusing. The new way Facebook handles this is that it will change the access token every time you connect it to a different leenk.me account, breaking your other leenk.me accounts. So if you have three Basic accounts that all use the same Facebook account, two of them will most likely stop working sometime in the future. My solution fixes this, it allows you to create multiple API keys in a single account. So you simply add your Facebook to one account and create multiple API keys in that account depending on your needs. Each API can use the same Facebook account if you want it to, it just can’t be used in separate leenk.me accounts.
Also, if you had a Basic account, you will be able to add up to 3 API keys. If you had a Plus account, you will be able to add up to 10 API keys. I also renamed the plans to Personal and Business.
I tried to test this out as much as I could in the short time that I had, so if you have any problems, contact me and I will help you as soon as possible.
The last few days have been pretty crazy, trying to get things in place for the upcoming Facebook changes has forced my hand into making some changes to the leenk.me service. These changes were already planned for the near future, but now they’re becoming a reality. I’ve also had to place the 2.0 BETA version of the plugin on hold while I update the site/account options.
Here are a couple of screenshots of the new account setting pages that I’ve been working on:
Each account will be able to create multiple API keys!
If you have a single Basic account, you won’t have to worry about any of these things. Due to the changes that Facebook is going to make on May 2nd, this will severely affect how people with multiple Basic or Plus accounts use the service. In many cases, if you had 2 or 3 separate Basic accounts, all using the same Facebook profile, you’ll be able to go down to 1 Basic account!
I haven’t nailed everything down yet, but I am currently thinking that Basic accounts will get 3 APIs, Plus accounts will get 10 APIs, and I’ll probably discontinue the Basic account option for future customers.
Also, one last thing, when the new account settings pages are live, I’ll release a new version of the plugin which will use a new version of the leenk.me API. To use this, you’ll need to go through an “account conversion” process to convert your existing leenk.me settings to the new account methodology. This will be true for everyone, but it should be pretty straight forward and not very difficult to deal with.
I’ll let you all know as I finalized these details! Until then, happy blogging!
A few weeks ago one of my great leenk.me customers, Dr. Walt emailed me because he was having trouble with leenk.me not automatically publishing to his social networks. It took about a week to test what was happening, but eventually I discovered (with the help of my WordPress developer friend Alan Knox) that the Subscribe2 plugin was causing the issue. Basically, Dr. Walt had so many subscribers to his blog that the Subscribe2 was overloading his MySQL instance. Then leenk.me would run and it couldn’t contact the MySQL server. I wasn’t able to reproduce this but my friend Alan started to have the same exact problem on his personal blog. Alan’s solution was easy, he switched to the free version of MailChimp. But that solution wasn’t going to work for Dr. Walt because Dr. Walt posts twice a day to his blog, Alan only posted once a day (which is the smallest increment supported by MailChimp’s RSS reader).
Well, once we figured out exactly what was happening, I tried to raise the priority of the leenk.me plugin (so it would fire before the Subscribe2 plugin). And to everyone’s pleasure, it worked! leenk.me and Subscribe2 did exactly what they were suppose to do. Dr. Walt was so happy with the out coming and the level of support he got, he offered to send me one of his books!
Thanks Dr. Walt!
I wanted to give you all a head up that Facebook is making some changes that will (and for some people already have) affect leenk.me. I’ve notice a few people who have had an “expiration” time attached to the access token that Facebook give leenk.me. The access token is what allows leenk.me to send content on your behalf when you publish a new post. The way Facebook use to work is 3rd party developers like myself could request an access token with “offline access”, which basically meant it worked forever (or until the user changed their password or remove the app from their profile). Facebook is now planning on removing the offline access ability from their API. So, in preparation for this change (which is coming May 2nd, 2012), I have been testing their new requirements and have already made a few changes to leenk.me to start to deal with what Facebook is requiring. Over the next week I will continue to make changes until I have a solution in place that will cause YOU the least amount of pain.
So far it is going well though. I’ve removed the request for the “offline access” and have set my app in Facebook to disable that feature altogether. Facebook is handle these access tokens in two ways, it will hand out a token that expires in 2-hours or a token that will expire in 60-days. I am still testing the 60-day tokens to make sure they will work as I expect them to. It looks like I will be able to “renew” the 60-day tokens before they expire to get a new 60-day token. Basically replicating the previous “offline access” token I was able to use. However, in the case that I am unable to do this, it may require you to reset your Facebook connection to leenk.me every 60 days.
While I am working on this, I have also started implement some new error reporting within the beta version of the leenk.me plugin. Ultimately, this change by Facebook is pushing back the development of the plugin, but I think in the end we’ll all be better off. There will be better error reporting and more helpful messages.
Facebook is by far that social network that I end up having to do the most support for. Let’s just say that they do not handle the oAuth standard in a “traditional” manner. As I said, my goal here is to make this as simple as possible and not require you to do any extra work. Hopefully that goal will be accomplished. If you have any questions or need any support, as always, feel free to contact me.
Hey Everyone, We’re getting closer to a new version of leenk.me. Just made some more fixes to the 2.0.0 beta, thanks to everyone who has helped me test. You can download the new version here. I’m still getting questions about Google+, and trust me, I haven’t forgotten about it. Google still hasn’t opened up their API for writes (it’s read-only). As soon as they open it up, I’ll be working to add it. I’ve been hearing a lot of chatter on the internet from Google+ developers. They’re all just waiting for Google to open up the API so they can start writing their apps.
So, if I don’t get any bug reports about this BETA, it’ll become the official version of leenk.me. Thanks again for all the testing!