Extensions catalog update!

February 14, 2011 · by Torgeir Lorange Østby

Last week we released a new version of the extensions catalog! While many of the changes are under the hood and not immediately visible to the public, we do hope that you will like what you can see.

Highlights for our users

A whole bunch of styling fixes. For example, the extension names are finally displayed in full!
The front page has changed into a list of recommended extensions, maintained by Opera
The graphics on the error pages have been compressed further. You will hopefully not notice

Highlights for the extension developers

All descriptions from the config.xml can now be edited when uploading extensions
A bug was fixed regarding unsupported characters in the screenshot filenames
Screenshots can now be deleted if you accidentally upload duplicates or just too many
It is now possible to navigate from your extensions to their respective details pages. Just click the details button associated with each extension and follow the links at the top

Enjoy! (While we keep on working on the next release)

Readers' comments 14

Left under the original article, as archived.

TamilTuesday, February 15, 2011 9:52:00 AM
DaneTuesday, February 15, 2011 12:27:20 PM

I'd really love to see extension author pages...

That way you could see all the extensions made by good extension authors like whochan etc. There currently doesn't seem to be a way to do that, apart from google...
sabisanTuesday, February 15, 2011 12:43:57 PM
Any news about double popup-onConnect bug ?
ouzowtfTuesday, February 15, 2011 1:16:53 PM
Can you please put the different languages of an extension on the pages of the extension itself? When I look for new extensions I always have creeping horrors to see all the 97 translation of only one extension, where I'm not able to read or use 95 of them.
Its ok for me to see only one specific translation (the english -or optional a different- one preferred) if it exists or, if the extension is only in chinese, this one.
The search for extensions should of course still have the option to search for different languages.
Rafael LuikTuesday, February 15, 2011 6:26:22 PM
Instead of separating extensions by language (and making them to get separated by language on the catalog), you need to do like Mozilla and let extensions to detect the language being used on the browser UI. That way there won't be multiple entries for the same extension for each language, you'll get a much more organized list and consistency. *

Originally posted by d4n3:

I'd really love to see extension author pages...

That way you could see all the extensions made by good extension authors like whochan etc.
+1
Mağruf ÇolakoğluTuesday, February 15, 2011 9:13:24 PM
UsopionWednesday, February 16, 2011 1:17:09 AM
Spam removed.
Charles SchlossWednesday, February 16, 2011 3:41:54 AM
Torgeir Lorange ØstbyWednesday, February 16, 2011 9:54:27 AM
@ouzowtf: Yup. Work in progress
ouzowtfWednesday, February 16, 2011 11:37:05 AM
Originally posted by torgeilo:

@ouzowtf: Yup. Work in progress

Thanks for that information.
d4rkn1ghtWednesday, February 16, 2011 6:46:13 PM
QuHnoThursday, February 17, 2011 9:34:24 AM
Originally posted by rafaelluik:

Instead of separating extensions by language (and making them to get separated by language on the catalog), you need to do like Mozilla and let extensions to detect the language being used on the browser UI.

Is the config.xml parsing bug with multilingual descriptions on the submission page corrected and is there an option in the select box for internationalized extensions or, even better, does it allow multiple selects now?

If that is not fixed, it is not really possible to submit fully internationalized extensions because the built in description of an extension will be in one language only, even if the rest of the extension is internationalized.
Torgeir Lorange ØstbyThursday, February 17, 2011 9:59:37 AM
@QuHno: As stated in the post, "All descriptions from the config.xml can now be edited when uploading extensions".

All descriptions were parsed before as well, actually, just not editable. You could see them all listed on the final page before submitting you extension for moderation.

There are a few more bugs, though, like handling empty xml:lang attributes. We have a task on fixing all of this.
QuHnoThursday, February 17, 2011 2:48:00 PM
Fine, so we will have things like that in the config.xml in the near future:
```
...
<decription>default description</description>
<decription xml:lang="fr">description en français</description>
...
```
I'll try it with the next update of my extension, just write when it is possible