On 7/3/10 2:09 AM, in article [email protected], "Suresh V."
<[email protected]> wrote:

> Alex Clark wrote:
>> Folks, 
>> 
>> I'm trying to create a "simple" browser view method e.g. @@view/method that
>> I can call via XML-RPC, but I notice browser views don't seem to possess the
>> Zope 2 "goodness" that "regular" objects/methods do.
> 
> I found a related problem while integrating the contentratings product.


I'm not sure how your problem is related, but mine turned out to be "user
error". I had protected the view with the cmf.ManagePortal permission but I
wasn't authenticating.

Once I fixed that, as long as I returned a dict then the publisher was happy
and I got my XML-RPC reply :-)


> 
> In Plone 4, a url of the form:
> 
> http://localhost:8080/Plone/obj/@@editor_rating_set/rate
> 
> was producing a 404 error. This used to work in Plone 3.
> 
> "rate" used to be a allowed_attribute of the view.
> 
> As a work around, I had to create a new browser:view with rate as the name.
> 
> Anyone knows what happened?

Actually, I don't think that ever worked, unless you do something like this:

http://www.teamrubber.com/blog/cookin-with-traverse_subpath/


If you specify "allowed_attributes" in zcml then you can at least call the
method in a page template.

Although, I've been seeing an "attribute" parameter in zcml lately, maybe
that exposes it TTW? I'm not sure.


Alex




> 
> <snip>
> 
> 
>> 
>> 
>> I found this post from this list which seems to indicate that browser views
>> should provide XML-RPC:
>> 
>> http://www.mail-archive.com/product-developers-g3yhmj00slolbbk5bon...@public.
>> gmane.org/msg01169.html
> 
> This link seems to have expired.
> 
> <snip>
> 
>> 
>> Anyone know what's going on here? What do I need to do to make this work?
>> 
> 
> Suresh

-- 
Alex Clark · http://aclark.net
Author ‹ Plone 3.3 Site Administration · http://aclark.net/admin



_______________________________________________
Product-Developers mailing list
[email protected]
http://lists.plone.org/mailman/listinfo/product-developers

Reply via email to