Feature #1716


Plugin Request: Blogger Importer

Added by scott voth over 10 years ago. Updated over 10 years ago.

Priority name:
Category name:
WordPress (misc)
Target version:
Start date:
Due date:
% Done:


Estimated time:
Deployment actions:


QUESTIONS FOR THE PERSON REQUESTING THE PLUGIN/THEME [generally this means Matt or a community facilitator]
- What's the name of the plugin/theme? Blogger Importer
- [plugins] In a few words, what does it do? Allows user to import xml file created by Blogger export process
- How is the plugin/theme different from what's already provided on the Commons? The Commons currently has only one importer (WordPress Importer) which is WP->WP. This one does Blogger->WordPress
- What's the potential impact? Who will use it? I don't think there will be any potential impact. Members wanting to move their content from Blogger to the Commons would use it.
- Who initially made the request? [sometimes Matt is passing along requests from members, sometimes suggesting something he found himself] Priscilla Stadler asked about how to get her content into the Commons from Blogger
- Who is the plugin author?*I am a little unclear - it seems like it is actually a tool within WordPress - and maybe part of the code set? On a non-Commnons WP site, a list of importers is presented when you go to Tools>>Import. I selected Blogger, and this plugin was automatically added and worked perfectly.*
- Say a little bit about the release history and popularity of the plugin. How many times has it been downloaded? When was it last updated? [The idea behind these last two questions is that I'm more likely to look favorably on plugins that are less likely to be abandoned]In, some people report that the Blogger Importer is broken for 3.3, and yet it worked fine for me. Boone - maybe you have some insight on this. Are there importers that come with WP, or are they all separately written plugins? The plugin seems to be popular - 189,000 downloads - and has gone through three releases - most current is 0.4.

- Maintenance: Given the data above, how likely is it that the plugin is going to be abandoned by the developer?
- Security: Scan for XSS and DB vulnerabilities [How? Is there a better way than doing it by hand? Anyone have a script that greps for things like 'echo $' and "INSERT "? I chatted a bit with Mark Jaquith in Phoenix and it sounds like he just has a list of things he searches for. Maybe we should invest in writing something.]
- Redundancy: If this plugin/theme does something that plugins/themes on the site already do, is there enough reason to put it on anyway? Maybe we should migrate users from the older plugin/theme to the new one? How hard would that be?
- Themes: What are the results of the Theme Check? Many of the 'required' warnings I don't care much about - they are nitpicks. But consistent calls to deprecated functions, for instance, could indicate something about the quality of the theme.

Actions #1

Updated by Matt Gold over 10 years ago

  • Category name set to WordPress (misc)
  • Status changed from New to Assigned
  • Assignee set to Boone Gorges
  • Target version set to 1.3.9
Actions #2

Updated by Boone Gorges over 10 years ago

  • Status changed from Assigned to Resolved

Also available in: Atom PDF