Dan,

Weird: I copied the link with %2550 right from the Google Directory.
It should be 
http://www.xs4all.nl/~mackaaij/Google%20Gadgets/Portfolio/Portfolio.xml
as the old location indeed.

For the second one I see I made a type in the filename. The first
letter of the XML should be a capital P, as in:
http://postcodekilometerdeclaratie.googlecode.com/svn/tags/PROD/Postcodekilometerdeclaratie.xml

Thanks for looking into this,

Patrick Mackaaij

On Jan 8, 6:38 pm, "Dan (Google Employee)" <[email protected]> wrote:
> Hi again,
>
> It appears that both of the aliases you submitted have errors in the
> URLs. The first, issue 
> 356http://code.google.com/p/igoogle-legacy/issues/detail?id=356,
> has %2520 instead of what should just be a %20. This prevents the
> source URL from redirecting properly. The second, issue 
> 357http://code.google.com/p/igoogle-legacy/issues/detail?id=357, has a
> destination URL that returns a 404. The alias looks to be in effect
> for this gadget, but it won't display anything because there isn't a
> gadget at that URL.
>
> I'd like to implement both of these corrections simultaneously, so
> please let me know what URL I should use for the destination in alias
> 357.
>
> Thanks,
> Dan
>
> On Jan 8, 9:27 am, "Dan (Google Employee)" <[email protected]> wrote:
>
>
>
> > Hi Patrick,
>
> > The alias should have gone through by now, I will investigate.
>
> > Thanks,
> > Dan
>
> > On Jan 7, 1:51 pm, Mackaaij <[email protected]> wrote:
>
> > > I received a response on monday evening telling me the relocation
> > > should be active at the end of the day. This URL still shows the old
> > > location though. Does anybody have a clue whether things go wrong or
> > > am I just impatient?
>
> > >http://www.google.nl/ig/directory?type=authors&url=patrick%40mackaaij...
>
> > > @Jerome: Do you also have a tip about overwriting the gadget.xml in
> > > the PROD tag of SVN with a new version from the trunk? What I do now
> > > is remove the PROD tag using repo browser and then re-tag the trunk to
> > > PROD. I've also switched from trunk to PROD but then you have to re-
> > > apply changes... I'm hoping for a faster way :-)
>
> > > Regards,
>
> > > Patrick Mackaaij
>
> > > On 30 dec 2008, 14:26, Mackaaij <[email protected]> wrote:
>
> > > > I updated the repository for all my gadgets and submitted the alias
> > > > requests (and directory requests). Very anxious to see how this
> > > > goes...:http://code.google.com/p/igoogle-legacy/issues/list?can=2&q=mackaaij&;...
>
> > > > Thanks for the info and happy new year,
>
> > > > PatrickMackaaij
>
> > > > On 30 dec, 10:49,Mackaaij<[email protected]> wrote:
>
> > > > > Jerome,
>
> > > > > Ok thanks for the SVN advice as well. I guess I'll tag a PROD as
> > > > > well :-)
>
> > > > > Regards,
>
> > > > > PatrickMackaaij
>
> > > > > On Dec 29, 11:19 pm, "Jerome (Guru)" <[email protected]> wrote:
>
> > > > > > Hi Patrick,
>
> > > > > > Regarding your first question, yes, aliasing (relocating) a gadget 
> > > > > > is
> > > > > > transparent to the user. I have not aliased any of my gadgets, but
> > > > > > from what I've seen and read, your end users will keep their user
> > > > > > prefs.
>
> > > > > > Tagging versions in SVN to keep track of major revisions is a good
> > > > > > idea, but I would strongly suggest you do not submit a revision tag 
> > > > > > of
> > > > > > your gadget in the directory, otherwise, as you commented, you would
> > > > > > end up aliasing your gadget for each major revision. I would think
> > > > > > that the best option would be to submit a version with a tag you 
> > > > > > move
> > > > > > to the production version (a "prod" tag). I personally serve my 
> > > > > > gadget
> > > > > > from my hosting servers, so I have not experimented much with the
> > > > > > different options to use SVN tagging to identify the production
> > > > > > version of the gadget.
>
> > > > > > Jerome
>
> > > > > > On Dec 29, 9:58 pm,Mackaaij<[email protected]> wrote:
>
> > > > > > > Jerome,
>
> > > > > > > I don't like loosing my rating though it's more important that 
> > > > > > > the end
> > > > > > > user settings are retained. Are the end user settings retained?\
>
> > > > > > > Another question you, as a guru, might also know (if you know 
> > > > > > > about
> > > > > > > SVN as well). I tagged a version with SVN since I thought it 
> > > > > > > would be
> > > > > > > appropriate for a release. If I update a iGadget in the future, a 
> > > > > > > new
> > > > > > > tag would be applicable and I'd have to file an alias change 
> > > > > > > again.
> > > > > > > This would vote for submitting the SVN trunk, right? What would be
> > > > > > > your advise on this?
>
> > > > > > > Regards,
>
> > > > > > > PatrickMackaaij
>
> > > > > > > On 22 dec, 17:30, "Jerome (Guru)" <[email protected]> wrote:
>
> > > > > > > > Hi Patrick,
>
> > > > > > > > As you can see on top of this group, there is a sticky thread 
> > > > > > > > which
> > > > > > > > explains the procedure to make the changes you are need done. 
> > > > > > > > The
> > > > > > > > issue though is that this change will loose your ranking, user
> > > > > > > > comments, etc. which does not seem what you are looking forward
> > > > > > > > to. :-)
>
> > > > > > > > Please see this previous thread about this issue of aliasing 
> > > > > > > > causing
> > > > > > > > lost of ranking and 
> > > > > > > > comment:http://groups.google.com/group/Google-Gadgets-API/browse_thread/threa...
> > > > > > > > and visit the link to the iGoogle issue tracker where you can 
> > > > > > > > star the
> > > > > > > > related issue. The more developers on the issue, the better 
> > > > > > > > chances to
> > > > > > > > get a workable solution put in place.
>
> > > > > > > > Thanks,
>
> > > > > > > > Jerome
>
> > > > > > > > On Dec 21, 5:04 pm,Mackaaij<[email protected]> wrote:
>
> > > > > > > > > Hi,
>
> > > > > > > > > Since I've switched to Google code as a host (using 
> > > > > > > > > Subversion). Is it
> > > > > > > > > possible to change the location for my Gadget users while 
> > > > > > > > > retaining
> > > > > > > > > their settings? It concerns the following iGoogle Gadgets:
>
> > > > > > > > > WEATHERNEWS 
> > > > > > > > > NEDERLAND:http://www.xs4all.nl/~mackaaij/Google%2520Gadgets/Weathernews/Weather...
> > > > > > > > > to:http://weathernews.googlecode.com/svn/tags/REL-1.0/Weathernews.xml
>
> > > > > > > > > POSTCODEROUTEPLANNER:
> > > > > > > > > (seems not to be listed in the directory but I do get 
> > > > > > > > > requests from
> > > > > > > > > the location google.com for this 
> > > > > > > > > gadget)http://www.xs4all.nl/~mackaaij/Google%20Gadgets/Postcoderouteplanner/...
> > > > > > > > > to:http://postcoderouteplanner.googlecode.com/svn/tags/REL-1.0/Postcoder...
>
> > > > > > > > > POSTCODEKILOMETERDECLARATIE:http://www.xs4all.nl/~mackaaij/Google%20Gadgets/Postcodekilometerdecl...
> > > > > > > > > to:http://postcodekilometerdeclaratie.googlecode.com/svn/tags/REL-1.0/po...
>
> > > > > > > > > PORTFOLIOhttp://www.xs4all.nl/~mackaaij/Google%20Gadgets/Portfolio/Portfolio.xml
> > > > > > > > > to:http://portfoliogadget.googlecode.com/svn/tags/REL-1.0/Portfolio.xml
>
> > > > > > > > > Best regards,
>
> > > > > > > > > PatrickMackaaij- Tekst uit oorspronkelijk bericht niet 
> > > > > > > > > weergeven -
>
> > > > > > > > - Tekst uit oorspronkelijk bericht weergeven -- Hide quoted 
> > > > > > > > text -
>
> > > > > > - Show quoted text -- Tekst uit oorspronkelijk bericht niet 
> > > > > > weergeven -
>
> > > > > - Tekst uit oorspronkelijk bericht weergeven -- Tekst uit 
> > > > > oorspronkelijk bericht niet weergeven -
>
> > > > - Tekst uit oorspronkelijk bericht weergeven -- Hide quoted text -
>
> - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"iGoogle Developer Forum" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/Google-Gadgets-API?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to