Closed Bug 247008 Opened 20 years ago Closed 18 years ago

Export as XML (compatible with ExtensionRoom)

Categories

(addons.mozilla.org Graveyard :: Administration, defect, P5)

defect

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: jedbro, Unassigned)

References

()

Details

Attachments

(1 file, 9 obsolete files)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040614 Firefox/0.9 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040614 Firefox/0.9 In light of the plans for Authors to have their own accounts for updating Extensions and Themes. It would be wonderfull if update.mozilla.org could provide a PHP script that would generate an ER XML friendly file, that we could then merge with our own database. Why: Make our lives easier. Who: I'm willing to make the code. I think the easiest way would be for me to edit the http://update.mozilla.org/rss/ script into something like a http://update.mozilla.org/xml/ where we could then generate the appropriote XML files for the apps listed (Firefox/TB/Mozilla 1.x) Secondly, this should probably be another bug, but do you need any help adding/Reviewing extension/Themes? I'd very much be willing to be an Editor for update.mozilla.org. I offered to help in the past, then was onable to do so, but I can now garantee my 100% effort as I have cleared up my time consuming issues. Cheers -Jed Reproducible: Didn't try Steps to Reproduce: 1. 2. 3.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Sure, providing an XML file for ER to grab is fine with me. There's a mozdev.org bug on this somewhere I think. If you need any help bug Alan or me. The code is a bit difficult to access, (not using a CVS server, yet.). Though I can give you access to my test server so you can grab the files you need, via ftp. As for becoming an editor, I don't have a problem with that. :-) At the moment, the site's administration functions aren't online just yet, but as soon as they are, i'll set you up an account with editor privs. In the meantime, if you want to help triage the "add this to update" bugs, feel free.
Assignee: nobody → jedbro
Great. If you could e-mail me the details for the your test server that would be great mozilla ((at)) jedbrown ((dot)) net I would love to help Alan and you with the "add this to update" bugs. What do I need to do for this to happen, and where do I add the updates? Cheers
I emailed one of your many addresses that I have. Let me know if you didn't get it.
I am willing to help code this: please email me on martinalderson@gmail.com if you want me to help :).
Status: NEW → ASSIGNED
Assignee: jedbro → jedsbugs
Status: ASSIGNED → NEW
Status: NEW → ASSIGNED
Jed - Are you abandoning this, or what?
Depends on: 264970
Depends on: 255803
Ok, I'll try to come up with something based on UMO's RSS at Jed's suggestion http://lxr.mozilla.org/mozilla/source/webtools/update/rss/
No longer depends on: 264970
Summary: Add a PHP script to generate a ER/Texturizer compatible XML file → Export as XML (compatible with ExtensionRoom)
Attached file Rough draft of php to XML formatting (obsolete) —
This is a first stab at having the php output as XML in the format ER uses. I've only tackled extensions so far, but the rough framework is set. Problems to overcome: authors categories compatible I suggest wading through http://lxr.mozilla.org/mozilla/source/webtools/update/themes/showlist.php to find how this is already done. Companion caller to be added next.
This should probably be combined with its include to reduce overhead. The Select query needs to change, but this is a start.
I've probably missed some commas. Multiple authors per theme/extension is still an issue. But this should be enough to get Jed and Clav started.
Attachment #162543 - Attachment is obsolete: true
Attachment #162544 - Attachment is obsolete: true
This is missing authors, categories, and previews. This is subject to change with the beta site. Comma separated lists such as authors and categories, are more of a pain. SELECT tM.GUID, Name, tV.Version, tM.DateUpdated, Homepage, Description, OSName, AppName FROM t_main tM INNER JOIN t_version tV ON tM.ID = tV.ID AND tM.DateUpdated = tV.DateUpdated INNER JOIN t_os tOS ON tV.OSID = tOS.OSID INNER JOIN t_applications tApp ON tV.AppID = tApp.AppID GROUP BY GUID, Name, tV.Version, tM.DateUpdated, Homepage, Description, OSName, AppName Pardon the bugspam, but I like to take notes as I work.
Attached file XML for extensions is 90% done (obsolete) —
Argh! The loops inside of loops inside of loops! Currently I'm trying to only hit the main and version tables once. While it may be more efficient, its a pain to code. I may skip the efficiency and just do lots of database hits. If perf is really bad, we can tweak later.
Attachment #162548 - Attachment is obsolete: true
Well, I figure that since I'm working on this, I'll take it.
Assignee: jedsbugs → Bugzilla-alanjstrBugs
Status: ASSIGNED → NEW
Attached file XML for extensions is 95% done (obsolete) —
I like this version much better. The flow is much better. Unfortunately, the "compatibility" section has to be very slightly different because I don't feel like doing a data model conversion. I'm pretty sure ER can handle the difference gracefully. I haven't actually tested this php, so a volunteer would be nice. I'm probably missing a few semicolons. Next on my todo list: descriptions. Feedback is always welcome.
Attachment #162658 - Attachment is obsolete: true
Attached file Extensions as XML (obsolete) —
Syntax errors fixed. Not getting any output when I do "?type=E" though.
Attachment #162660 - Attachment is obsolete: true
Attached file Extensions as XML (obsolete) —
pass in ?type=E and watch it go.
Attachment #162667 - Attachment is obsolete: true
Attached file File (obsolete) —
Per Alan's request.
Attachment #162783 - Attachment is obsolete: true
Status: NEW → ASSIGNED
Attached file DB to XML via PHP (obsolete) —
99% done. Multiple authors and multiple categories doesn't seem to want to work at the moment. But hey, what do you want for free?
Attachment #162787 - Attachment is obsolete: true
Extension long descriptions aren't CDATA, but we could have the generator slap in CDATA tags and P tags to match the current format. Author IDs are integers. Categories are the names. You wanted names, right? Extension and theme IDs are nicknames (for memorable URLs)
Moving more bugs to new component.
Component: Update → Administration
Product: mozilla.org → Update
Version: other → unspecified
Attachment #163498 - Attachment is obsolete: true
Attachment #169132 - Flags: first-review?(jedsbugs)
Mass change - bugs to be read / (re)confirmed.
Assignee: Bugzilla-alanjstrBugs → nobody
Status: ASSIGNED → NEW
Priority: -- → P5
AMO bugspam. Correcting QA contacts on OLD bugs (mozilla.update@update.bugs) -> Correct QA contact (administration@add-ons.bugs) Filtermeplzkthx
QA Contact: mozilla.update → administration
I'm going to WONTFIX this -- I don't think we need XML export, except possibly for web servicey stuff post-Remora. If you're going to re-open this, please do so with a patch against Remora!
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WONTFIX
Attachment #169132 - Flags: first-review?(jedsbugs)
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: