this means that we must start with one editor (BXE) and.. End with that very editor ?
2005/9/4, Joe Grist <[EMAIL PROTECTED]>:
To share my experience...
I had a lot of trouble with Kupu. For example, I could never get my document
styles to display properly. H1, H2, would always look different in Kupu to
how they looked on the live site. This really threw the non-technical
people trying to edit their sites.
Also, method of inserting an image is just way too complex for a non
technical person (having to enter a URL manually and all).
As of Lenya 1.2.4, I have cut all my sites over to BXE only and disabled
Kupu in the menu. I get the added advantage of multiple editable areas.
Also nice in-place editing, proper WYSIWYG styles, and really friendly image
management.
I have no intention of integrating any other editor (non Kupu or BXE) as I
don't want the administrative overhead of maintaining it as new Lenya
versions roll out.
Personally I'd strongly recommend BXE. It's easier to write documentation
for users on the more complex BXE than write documentation for users on
getting around Kupu's quirks.
I just thougnt others might find my experiences interesting.
Cheers all
Joe Grist
-----Original Message-----
From: Marcos Labriola [mailto: [EMAIL PROTECTED]]
Sent: Saturday, 3 September 2005 8:42 AM
To: [email protected]
Subject: Re: Problems with Kupu Editor
Hi, hope this helps:
I've been working with IE6, Lenya 1.2.4 and Cocoon 2.1.7 and all the
pictures references got broken after editing with Kupu. The host portion was
duplicated, something like http://host:port/host:port/path
After some research I found that replacing
<xsl:value-of select="@data"/>
with
<xsl:value-of
select="concat('/',substring-after(substring-after(@data,'/'),'/'))"/>
BOTH AT
line 45 of webapp/lenya/resources/kupu/apache-lenya/lenya/content2edit.xsl
AND
line 94 of webapp/lenya/pubs/your-pub/xslt/xhtml2xhtml.xsl
would do.
The practical effect is to remove that host Kupu insists to insert. I have
not tested this solution thoroughly, but so far it has been working fine.
Comments and thoughts are welcome.
Marcos
----- Original Message -----
From: "Kubiak, Thomas" < [EMAIL PROTECTED]>
To: <[email protected]>
Sent: Thursday, September 01, 2005 11:02 AM
Subject: AW: Problems with Kupu Editor
Thanks for that idea. It's the same problem you described.
Another big problem is, that all clients HAVE TO use IE6, no way to install
Firefox on them.
Any other suggestions how to solve the URL-modification from Kupu.
Thanks and regards
Thomas
-----Ursprüngliche Nachricht-----
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Gesendet: Donnerstag, 1. September 2005 06:56
An: [email protected]
Betreff: Re: Problems with Kupu Editor
On 8/31/05, Kubiak, Thomas <[EMAIL PROTECTED] > wrote:
> We have Lenya 1.2.x with visual editor Kupu.
> Now the Problem is, that Kupu translates the Doctypes samples that we
> use as templates.
> I made a template that has links that refer to the same content, like
> in a FAQ site. I mean a <a href="" that links to <a
> name="abc"> for example.
> After editing and saving it with Kupu, these <a href=""
> get changed so that they won't work anymore.
>
> Where can I modify the behavior of Kupu inside Lenya ? Does anybody
> have the same problem ? Any solutions ?
Was this the same as our issue? When editing links in Kupu with MSIE, the
URLs were completed with the protocol, servername and current document path.
Since the servername is for our secure editing server, and the document path
included "authoring", this was very bad for publishing documents.
Our workaround is to use Mozilla or Mozilla Firefox for editing.
Still wondering if this is due to MSIE-specific code in Kupu, or just a
problem with MSIE that requires MSIE-specific code in Kupu to fix.
We did not research it after realizing it was MSIE-specific.
We also had to fix Kupu so that <A NAME="ourTag"> was not removed.
That is documented at:
http://solprovider.com/lenya/kupucenter
in the ALIGN section.
solprovider
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED] For additional
commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED] For additional
commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED] For additional
commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
