franky1978 / igoogle-legacy

Automatically exported from code.google.com/p/igoogle-legacy
1 stars 0 forks source link

submitted a widget twice #597

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
i unatentionally posted a widget twice, once with the "widget checker 
widget" url http://hosting.​gmodules.com/ and once with the right url 
http://www.kfz.net/. 

please delete the gmodules url'ed widget: http://www.google.com/ig/
directory?hl=de&type=gadgets&url=hosting.gmodules.com/ig/gadgets/
file/114727686795621085963/bussgeldrechner.xml

this one is the right one: http://www.google.com/ig/directory?
hl=de&type=gadgets&url=www.kfz.net/ueberuns/widgets/bussgeldrechner.xml 
please keep that.

thanx!

Original issue reported on code.google.com by s...@timewaster.de on 20 Aug 2009 at 7:27

GoogleCodeExporter commented 9 years ago
You can log into your Google account and then open the GGE: 

http://code.google.com/apis/gadgets/docs/legacy/gs.html#GGE

From there, open the xml file of the gadget you made/submitted during 
development
(the one you want deleted). This list is on the 'file' drop down menu on the 
upper
left of the GGE interface.

Now, load the xml file into the editor. Then (in another window) go here:
http://code.google.com/p/igoogle-legacy/wiki/GadgetRegistration

and register the gadget. You will be given a comment tag to be placed into your 
xml
file. once you get this tag and place it in the xml file (be sure to save the 
xml
file) you will want to click the "verify" button on the registration page.

Once your gadget is verified you will be given secret keys. You take these keys 
and
go here:

http://spreadsheets.google.com/viewform?hl=en&formkey=cEhGZVVmVUNQVmI0eFc3N3pONG
5QUEE6MA

Enter in the gadget info and secret key and go from there. Also, once this is
done...remove the xml file from your Google GGE.

I've made this error myself! 

Original comment by tropical...@gmail.com on 10 Sep 2009 at 8:18

GoogleCodeExporter commented 9 years ago
Comment 1 describes the correct procedure.

Original comment by api.dwh%...@gtempaccount.com on 17 Sep 2009 at 4:57