#28 — Kupu in Ploneboard is klugy
by Marshall Mayer — last modified Feb 21, 2009 10:18 PM
|Submitted by||Marshall Mayer|
|Submitted on||May 11, 2006|
While Kupu works with other content types in Plone 2.1.2, it's stripped down iteration in Ploneboard 1.0alpha really does not. The problem is most notable in the internal and external internet link buttons. Nothing happens. A new window comes up but you can't interact with it. No browsing for internal documents nor entering an external URL. No amount of canceling dismisses the window, let alone an OK. The only way you can recover is by refreshing the page. No end user in their right mind would find this acceptable. I've tested this in Firefox on a Mac as well as IE on Windows XP SP@, all with the latest updates.
Added by Edward Muller on May 11, 2006 10:34 PMremoving the lines that say:
Target release: 1.0 → None
Responsible manager: wichert → (UNASSIGNED)
fixes the problems for me.
Although I don't know if it causes any others.
Added by Marshall Mayer on May 11, 2006 10:59 PMI have a followup question about Kupu in Ploneboard: why are you including a stripped down version of Kupu rather than just using Kupu out of the box. There might be some good reason, but it seems like it will open a whole can of worms that you don't want to address/maintain over time.
Added by Edward Muller on May 11, 2006 11:39 PMWell, I;m not a ploneboard developer, just an interested party with mostly the right skill set to understand most of what's going on.
The kupu included is the same kupu as in the rest of plone, but they've just had it display itself with a few of the bells and whistles of hte full kupu disabled. If you remove the lines like I said kupu works, or at least it does for me.
I assume the developers are not displaying the full kupu because it's just not necessary for a forum product.
And having kupu display itself without those extras doesn't induce a maintenance burden AFAICT.
Added by Marshall Mayer on May 12, 2006 12:16 AMYour solution seems to have worked, though I do not know if it has introduced other problems (I'll keep testing). It would be great if the developers gave us a read on this by committing your solution to the trunk (after testing themselves).
I'm not sure they are reading this, however. You're the first person to respond to any of my issues.
Added by Wichert Akkerman on May 12, 2006 01:36 PM
Issue state: unconfirmed → open
Target release: None → 1.0
Responsible manager: (UNASSIGNED) → wichert
Issue state: open → resolved
No responses can be added.
If you can, please log in before submitting a reaction.