I know that adding link in Editor brings up a form that is somewhat messed-up, some times more messed up than others. I found that the Editor resize utility, while is kind-of cool and I like it, cases the problem with the link form and also with image form (we don't have image tool right now but I tested it)
So the solution would be to either get rid of resize utility in Editor or use simple prompts to enter url for link and url for image.
The Editor will still be auto-resizable, meaning when you keep typing longer posts and need more height, the Editor will just auto-expand.
We now have an option to post Question or Answer to user's blog on Blogger via bloggerAPI.
Just like our Tumblr module it uses OAuth authentication.
Use can "connect" blogger blog from their profile page or from the "Ask" or "Answer" form when they click the "Post to blogger" check box and their account is not yet connected to Blogger.
More social features means more traffic for your site. Imagine a user with popular blog decides to share a question on a blog. That would mean a lot more new visitors to your Q&A site.
In the future we may also be able to monitor that post on blogger an any comments made on blogger will be imported as comments to that question or answer.
Also comments added to Question or Answer or an answer to a question made on the site may be posted to blogger's post as comments. This of cause is pretty dangerous feature because if someone posts a spam on your site we sure don't want to propagate that spam to someone else's blog.
This is my answer to a Question on Support site for LampCMS project
There are some posts with images on this site. I am not sure how they did it. There is no support to actually save an image to the server but there is a way to just include an img tag that points to image hosted somewhere else.
I finished the TumblrAPI module.
User can now send Question or Answer to their Tumblr blog at the time of posting.
It uses OAuth authentication, just like Twitter API.
So source is on github.
I will work on few minor changes next like not including deleted items in views even for administrators
Instead there will be a separate controller to view deleted items and only administrator will be able to use it.
After getting Oauth token and secret from Google for blogger
Check out this "playground" http://googlecodesamples.com/oauth_playground/index.php
it's so hard to even find the details of how to register your app with Google, what
url to use to request Oauth Token for blogger API.
When I find it again (takes a lot of wasted time to just find the correct url for documentation as Google scattered the blogger API documentation all over their sites - some in Oauth data related pages, some on Blogger API related pages...)
Some piece meal bits of data for Google OAuth API developers:
You will need to register your domain with Google. This included downloading some lame html file from Google then uploading it to root dir of your site and then clicking "verify" button, basically proving to Google that you are the admin of that domain.
and enter some string that you must create yourself - some type of long secret string, into the
"Target URL path prefix"
That will become your app's OAuth Consumer Key and Google will generate the OAuth Consumer Secret value for you. This is the lamest and most unintuitive way I"ve seen in any APIs to get your OAuth Consumer API key and OAuth consumer secret. But that's how it is with Google, it's because they don't really care about the developers(about schmucks like you)
Now you will probably be able to use OAuth protocol, but of cause nothing is "easy" when it comes to Google's implementation of OAuth - remember this kids - Google does not care about developers and does not want to provide clear and easy-to-understand or even easy-to-find documentation.
can use this url to get list of user's blogs: https://www.blogger.com/feeds/default/blogs
It will be in the superbly fucked-up format written by incompetent fools at Google.
Even though it's in XML format, there is no entry for "blogID" and you must extract it from the tag using regex.
The url for the POST - to post your entry to blogger using api is also not easy to extract. It's buried in the Why the fuck the type="html"? This is an XML file - supposed to be pure data, why html?
That's not even the worst part.
To extra the url for post you need to find an entry in the "summary" tag that looks like this:
There is no easy way to extract this entry because there are a bunch of other very similar entries. Your only clue to use is that the "rel" attribute must end with #post How do you extract this entry? Is there a way to use XPATH when the only condition you have is that value of an attribute ends with #post?
Maybe if you can be certain that value will be "http://schemas.google.com/g/2005#post" then yes, it's possible to find this entry easily and then use the value of href
But it's probably easier to just extract and store the blog-id by extracting it out of the tag.
An awesome site for Android developers and Android enthusiasts has been launched recently.
It's straight to the point - Questions and Answers, mailing lists and Videos, all about Android phones, tips and tricks and development of Android apps.
If you are interested in learning or trying to develop your Android app, you've got to join it. Here is the link: http://www.androidportal.info
You can use existing Twitter or Facebook or Google account to join.