is it possible that it makes an invalid JSON / XML-RPC call when the
> virtual hosting is in place? Can you see anything in Firebug about a failed
No, everything looks fine.
What does render at that point in the page?
The page renders completely fine with those actions missing.
I stepped into the code a bit and the "plone.contentactions" viewlet isn't
even called when repoze.vhm is used.
On Sun, Dec 27, 2009 at 9:01 PM, Tres Seaver <tsea...@palladion.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Nathan Van Gheem wrote:
> > I'm having some very odd behavior with using repoze.zope2. The site is
> > served using repoze.vhm#vhm_xheaders filter. The correct site is served;
> > however, it seems that content editors can not see the content actions
> > down menus(Actions, Display, Add new..., etc). More specially, when using
> > repoze.vhm, the "plone.contentactions" viewlet will *NOT* be called on
> > page except the home page.
> > If I remove the repoze.vhm filter, the issue does not occur. I have not
> > too deep into the issue yet. I kind of wanted to post here and see if
> > else has seen this issue and if there is something simple I may be doing
> > wrong.
> I don't have ay idea how that viewlet is implemented: is it possible
> that it makes an invalid JSON / XML-RPC call when the virtual hosting is
> in place? Can you see anything in Firebug about a failed request? What
> does render at that point in the page?
> - --
> Tres Seaver +1 540-429-0999 tsea...@palladion.com
> Palladion Software "Excellence by Design" http://palladion.com
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> -----END PGP SIGNATURE-----
Repoze-dev mailing list