A week ago I realized that magnolia has some critical bugs (in fact it didn't worked at all).
The bug wasn't hard to fix but I thought to make a big picture change, so I started from scratch. The new version uses ma.gnolia API and for the moment seams to be working fine (I spent about 12 hours testing it) and is waiting for approval from Firefox reviewers.
If you want to play with it before approval there's no risk involved; it's tested in Firefox 2.0.0.4 under WindowsXp and Ubuntu 7.04, and has no real bugs.
1. Click the link.
Click the install link above, click install in the Firefox dialog and reset Firefox.
2. Enable API support from ma.gnolia.
Go to your account in ma.gnolia. In the main menu select "you"->"your profile". Go to the advanced tab and select enable API support.
3. Set your username.
In Firefox, go to tools->add-ons-> magnolia options. Set the username and password (the ones used for your ma.gnolia login) and click "Save". If the username and password are correct just close the window. For this step you have a new option. If you have a ma.gnolia user&pass saved in Firefox password manager, the dropdown list (in magnolia options window) will have that user and you could simply select it and hit save.
4. Drop the button.
This stage is optional. If you want a button in Firefox main toolbar just hover the mouse near any toolbar, right click, select "Customize", drag and drop magnolia's button
wherever you like.
Two ways to do that. The simpler one: right click on the page and select "Mark it with magnolia". The "add bookmarks" page will pop. You just fill the fields and hit save.
The more simpler one: hit magnolia button and the page will pop; after that fill the fields and hit save.
If that page you want to save is already in your saved bookmarks at ma.gnolia, the "add bookmarks" page will fill the fields for you from the site. You could do any modifications to that and hit save. The bookmark will be updated.
If your API key has changed (for whatever reason), when you will try to save a page, the "invalid API key" message will apear and you will have to re save magnolia options from tools->add-ons->magnolia options, so that the add-on could get the new API key.
Copyright ©2007 RAZVAN SIMION W3c | XHTML CSS
Comments
I use OpenID to login to
I use OpenID to login to ma.gnolia (the main reason I choose ma.gnolia instead of delicious).
So how do I use OpenID with the new plugin??
Re: I use OpenID to login to
When I created this version of magnolia, I searched their API for features and I didn't found anything related with the OpenID. So this add-on doesn't allow you to add bookmarks using your OpenID. I wrote to ma.gnolia.com support team asking for a new API feature and I'm waiting for them to reply. When that wappens, and if they give me any solutions, I will update the add-on and will reply to you.
OpenID support
Ok, it's done. Now the extension allows you to add bookmarks using OpenID. After installing, go to add-on options and in the OpenID tab fill the fields with your account information. The only inconvenience is that you must get your API key from your ma.gnolia.com account.
I didn't send it to mozilla yet, but you can find it here
New version 0.8: Problem/Request
The new version (after this one) is great, one problem and one request though.
Problem, it doesn't show my username anymore it just stays stuck on Welcome: rodin? My username is jdash.
Request, can you make it pull your tags from ma.gnolia so it gives auto-suggest of tags, the bookmarklets have it and it's a feature I miss.
Thanks for your work
Hey nice work re-doing the
Hey nice work re-doing the extension against the API, and for adding the OpenID support.
We'll soon be adding an api authentication piece soon that will make signing in with third-party applications quite a lot easier and standardized, reagardless of whether users are using a Ma.gnolia password, OpenID or their Facebook ID. That will allow you to simplify signin support in the extension.
We're looking forward to seeing where you take the extension. To avoid confusion, if it's possible to coordinate with distinct naming of extensions with Nathan's branch, that would be good for people who use either one.
We're behind both projects, so if we can help please let us know.
Post new comment