Skip to content.

Etria Lists

 

[quills-dev] [Collective-checkins] r49551 - quills.remoteblogging/trunk/quills/remoteblogging/browser

Sasha Vincic sasha.vincic at valentinewebsystems.se
Wed Sep 19 09:36:42 UTC 2007


On 19 sep 2007, at 11.25, Tim Hicks wrote:

> Tom Lazar wrote:
>> On Sep 19, 2007, at 10:58 AM, Tim Hicks wrote:
>>
>
>> this uid
>> however never existed in any of the cases that i tested.

I had this problem too and I am not sure of the cause :) but I think  
it was that the UID of my blog changed after migrating it to Plone 3.  
I will keep this in mind next time I see it.

I use scribefire and it just stopped working so I had to readd my  
blog with new UID, that is what I remember.

/Sasha

>
> That's very strange.  I thought that we were, everywhere, returning  
> UIDs
> for the appkey, and even instructing (logged-in) users to use a string
> that is the UID of the weblog that they are viewing if they want to  
> use
> remote blogging.  How was ecto getting hold of the appkey in your
> testing?  It sounds like this is where the real bug is.
>
>> as per
>> specification of metaweblog API this mechanism is intended to  
>> discover
>> *all* blogs (of a given user) at a given url.
>
> Yes.  The implementation that I was going for was that, with the  
> appkey
> being the UID of a particular weblog, then that weblog is effectively
> the 'app', meaning it makes sense for it to only return itself as the
> available weblog for the user.
>
> However, that's just a particular implementation specific to Quills  
> (and
> specific to an appkey that corresponds to a particular weblog).  The
> metaWeblog view could be declared against a plone site root, in which
> case it would need to be able to return *all* available weblogs for  
> the
> user.
>
> With your change, the flexibility of the metaweblogapi  
> implementation -
> which is supposed to be generic, and not quills.app-specific - is  
> lost.
>  My suspicion is that your change skirts around a bug, rather than
> fixing it.
>
>> actually, i'm not sure, what the previous implementation did. i also
>> don't know how the client acquires the 'appkey' that it provides.
>
> That would seem to be the source of the problem.
>
> Are you able to look at this again?
>
>
> Tim
> _______________________________________________
> quills-dev mailing list
> quills-dev at lists.etria.com
> http://lists.etria.com/cgi-bin/mailman/listinfo/quills-dev



More information about the quills-dev mailing list