Hi,

we have noticed that there still was a situation were this problem would arise, namely if you are running Tomcat on port 80 or if you are using Apache running on port 80 with mod_jk as a frontend for Jahia (same if you are accessing Jahia though the SSL port (443) ).
In that case the rewritting of the "false" url generated by the ActiveX editor would not be catched by Tidy and thus not modified.
This has been corrected in the CVS and will be part of the 4.0.5 release of Jahia.
If you wish to correct this behaviour on your Jahia, you can edit the file activex_htmleditor.jsp located in TOMCAT_HOME/webapps/jahia/jsp/jahia/htmleditors/activex/ according to the following patch :


Index: activex_htmleditor.jsp
===================================================================
RCS file: /home/cvs/repository/jahia/src/views/jsp/jahia/htmleditors/activex/Attic/activex_htmleditor.jsp,v
retrieving revision 1.20.2.1
retrieving revision 1.20.2.2
diff -u -r1.20.2.1 -r1.20.2.2
--- activex_htmleditor.jsp 6 Aug 2004 18:01:17 -0000 1.20.2.1
+++ activex_htmleditor.jsp 4 Oct 2004 17:10:14 -0000 1.20.2.2
@@ -17,10 +17,12 @@



boolean isIE = (request.getHeader( "user-agent" ).toUpperCase().indexOf("MSIE") != -1 );


- String serverURL = "http://"; + request.getServerName() + ":"
- + request.getServerPort()
- + engineUrl
- + "&screen=edit&fid=" + theField.getID();
+ String serverURL = request.getScheme() + "://" + request.getServerName();
+ String serverPort = String.valueOf(request.getServerPort());
+ if ( !"80".equals(serverPort) && !"443".equals(serverPort) ){
+ serverURL += ":" + request.getServerPort();
+ }
+ serverURL += engineUrl + "&screen=edit&fid=" + theField.getID();


(remove the lines beginning with a minus and add the ones beginning with a plus).

The file should be recompiled the next time you open a text with the ActiveX editor. Make sure that Tidy is activated in the Jahia administration for this to work.

Cheers,
Michel



Hi,

the content type is just plain text. On the "Simple" template
we are creating a new text area, enter some text, mark a word
to create a link and set the link destination using another
page id.

It seems that the ActiveX editor is causing the problem. If
I use another editor as a first choice (configuring the order
of the editors in the edit dialog) everything works fine with
this editor. If I use the SimpleText editor first, the link
is ok, if I switch to the ActiveX editor, the link gets
corrupted.

Since the ActiveX editor is the preferred editor by the users
we have to provide a solution that works with the ActiveX
editor.


Wolfram

-----Original Message-----
From: Serge Huber [mailto:[EMAIL PROTECTED]
Sent: Thu 23.09.2004 16:21
To: [EMAIL PROTECTED]
Subject: Re: AW: AW: AW: AW: Problem with automatic linking


A bigtext field in Jahia is a text field where an editor appears. Could you send here an example of the type of content that you insert that causes problems ?

Regards,
  Serge Huber.

Wolfram Sorg wrote:

>What do you mean with "bigtext"?
>
>Wolfram
>
>________________________________
>
>Von: Serge Huber [mailto:[EMAIL PROTECTED]
>Gesendet: Do 23.09.2004 15:37
>An: [EMAIL PROTECTED]
>Betreff: Re: AW: AW: AW: Problem with automatic linking
>
>
>
>
>Hi Wolfram,
>
>Strange... that stack trace you give doesn't seem related to the content
>of the field but rather to the popup engine URL itself. Maybe somebody
>put an editing link into a bigtext and that is causing your problem ?
>
>Regards,
> Serge Huber.
>
>Wolfram Sorg wrote:
>
>
>
>>Hi Stephane,
>>
>>I think we nearly tried everything that is possible to do in the editor.
>>Everything we enter is plain text, version of Jahia is 4.0.4.
>>
>>We are always getting a error screen whose page source contains the
>>following exception:
>>
>><!--
>>Error :
>>Error in parameters, Error in parameters : cid (null) cannot be converted in int
>>
>>Exception StackTrace: Cause level : 0 (level 0 is the most precise exception)
>>org.jahia.exceptions.JahiaException: Error in parameters, Error in parameters : cid (null) cannot be converted in int
>>at org.jahia.engines.updatecontainer.UpdateContainer_Engine.initEngineMap(Lorg.jahia.params.ParamBean;)Ljava.util.HashMap;(UpdateContainer_Engine.java:612)
>>at org.jahia.engines.updatecontainer.UpdateContainer_Engine.handleActions(Lorg.jahia.params.ParamBean;Lorg.jahia.data.JahiaData;)V(UpdateContainer_Engine.java:146)
>>at org.jahia.operations.OperationManager.handleOperations(Lorg.jahia.params.ParamBean;Lorg.jahia.settings.SettingsBean;)V(OperationManager.java:279)
>>at org.jahia.bin.JahiaAction.execute(Lorg.apache.struts.action.ActionMapping;Lorg.apache.struts.action.ActionForm;Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)Lorg.apache.struts.action.ActionForward;(JahiaAction.java:50)
>>at org.apache.struts.action.RequestProcessor.processActionPerform(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;Lorg.apache.struts.action.Action;Lorg.apache.struts.action.ActionForm;Lorg.apache.struts.action.ActionMapping;)Lorg.apache.struts.action.ActionForward;(RequestProcessor.java:484)
>>at org.apache.struts.action.RequestProcessor.process(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(RequestProcessor.java:274)
>>at org.apache.struts.action.ActionServlet.process(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(ActionServlet.java:1482)
>>at org.jahia.bin.Jahia.process(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(Jahia.java:1467)
>>at org.jahia.bin.Jahia.service(Ljavax.servlet.http.HttpServletRequest;Ljavax.servlet.http.HttpServletResponse;)V(Jahia.java:792)
>>at javax.servlet.http.HttpServlet.service(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(HttpServlet.java:853)
>>at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(ApplicationFilterChain.java:247)
>>at org.apache.catalina.core.ApplicationFilterChain.doFilter(Ljavax.servlet.ServletRequest;Ljavax.servlet.ServletResponse;)V(ApplicationFilterChain.java:193)
>>at org.apache.catalina.core.StandardWrapperValve.invoke(Lorg.apache.catalina.Request;Lorg.apache.catalina.Response;Lorg.apache.catalina.ValveContext;)V(StandardWrapperValve.java:256)
>>at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(Lorg.apache.catalina.Request;Lorg.apache.catalina.Response;)V(StandardPipeline.java:643)
>>at org.apache.catalina.core.StandardPipeline.invoke(Lorg.apache.catalina.Request;Lorg.apache.catalina.Response;)V(StandardPipeline.java:480)
>>at org.apache.catalina.core.ContainerBase.invoke(Lorg.apache.catalina.Request;Lorg.apache.catalina.Response;)V(ContainerBase.java:995)
>>at org.apache.catalina.core.StandardContextValve.invoke(Lorg.apache.catalina.Request;Lorg.apache.catalina.Response;Lorg.apache.catalina.ValveContext;)V(StandardContextValve.java:191)
>>at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(Lorg.apache.catalina.Request;Lorg.apache.catalina.Response;)V(StandardPipeline.java:643)
>>at org.apache.catalina.core.StandardPipeline.invoke(Lorg.apache.catalina.Request;Lorg.apache.catalina.Response;)V(StandardPipeline.java:480)
>>at org.apache.catalina.core.ContainerBase.invoke(Lorg.apache.catalina.Request;Lorg.apache.catalina.Response;)V(ContainerBase.java:995)
>>at org.apache.catalina.core.StandardContext.invoke(Lorg.apache.catalina.Request;Lorg.apache.catalina.Response;)V(StandardContext.java:2416)
>>at org.apache.catalina.core.StandardHostValve.invoke(Lorg.apache.catalina.Request;Lorg.apache.catalina.Response;Lorg.apache.catalina.ValveContext;)V(StandardHostValve.java:180)
>>at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(Lorg.apache.catalina.Request;Lorg.apache.catalina.Response;)V(StandardPipeline.java:643)
>>at org.apache.catalina.valves.ErrorDispatcherValve.invoke(Lorg.apache.catalina.Request;Lorg.apache.catalina.Response;Lorg.apache.catalina.ValveContext;)V(ErrorDispatcherValve.java:171)
>>at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(Lorg.apache.catalina.Request;Lorg.apache.catalina.Response;)V(StandardPipeline.java:641)
>>at org.apache.catalina.valves.ErrorReportValve.invoke(Lorg.apache.catalina.Request;Lorg.apache.catalina.Response;Lorg.apache.catalina.ValveContext;)V(ErrorReportValve.java:172)
>>at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(Lorg.apache.catalina.Request;Lorg.apache.catalina.Response;)V(StandardPipeline.java:641)
>>at org.apache.catalina.core.StandardPipeline.invoke(Lorg.apache.catalina.Request;Lorg.apache.catalina.Response;)V(StandardPipeline.java:480)
>>at org.apache.catalina.core.ContainerBase.invoke(Lorg.apache.catalina.Request;Lorg.apache.catalina.Response;)V(ContainerBase.java:995)
>>at org.apache.catalina.core.StandardEngineValve.invoke(Lorg.apache.catalina.Request;Lorg.apache.catalina.Response;Lorg.apache.catalina.ValveContext;)V(StandardEngineValve.java:174)
>>at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(Lorg.apache.catalina.Request;Lorg.apache.catalina.Response;)V(StandardPipeline.java:643)
>>at org.apache.catalina.core.StandardPipeline.invoke(Lorg.apache.catalina.Request;Lorg.apache.catalina.Response;)V(StandardPipeline.java:480)
>>
>>-->
>>
>>
>>Hopefully the stack trace can give you some more inforamtion.
>>
>>
>>Wolfram
>>
>>________________________________
>>
>>Von: St�phane Croisier [mailto:[EMAIL PROTECTED]
>>Gesendet: Di 21.09.2004 11:58
>>An: [EMAIL PROTECTED]
>>Betreff: Re: AW: AW: Problem with automatic linking
>>
>>
>>Hi,
>>
>>I just tried on a fresh Jahia 4.0.4 installation with Tidy activated and it
>>works fine for me (both in add and update mode - for example just enter the
>>pid of the linked page - for example "4" in the adquate icon in the activeX
>>and if you then switch in the simple text editor, save your container or
>>reopen it, my link is still relative). Of course the links are each
>>rewritten in the ActiveX editor with something like:
>>http://localhost:8080/jahia/Jahia/engineName/updatecontainer/op/edit/pid/12
>>because the ActiveX editor forces the use of a complete absolute url... but
>>when you save the engine (the pop-up), Jahia should filter this content and
>>automatically replace the "bad ActiveX links" by new relative urls. But
>>perhaps your links are part of a larger complex HTML fragment (e..g a cut
>>and paste from Word) that Tidy could not successfully parse. Have you tried
>>with a basic block of text?
>>
>>St�phane
>>
>>At 11:31 21/09/2004, you wrote:
>>
>>
>>
>>
>>>Hi Stephane,
>>>
>>>we are running Jaia 4.0.4. Using Tidy and/or markup cleanup did not
>>>help. As mentioned before, using those options will corrupt the other
>>>content as well.
>>>
>>>I'm not shure if the editor is causing the problem itself. Maybe there
>>>is an issue with passing the data to the editor.
>>>
>>>
>>>Wolfram
>>>
>>>
>>>________________________________
>>>
>>>Von: St�phane Croisier [mailto:[EMAIL PROTECTED]
>>>Gesendet: Di 21.09.2004 10:58
>>>An: [EMAIL PROTECTED]
>>>Betreff: Re: AW: Problem with automatic linking
>>>
>>>
>>>
>>>
>>>Hello,
>>>
>>>Which version of Jahia are you using? Please try to upgrade to the 4.0.4 if
>>>you are not running the last version. This is a bug in the MS ActiveX
>>>control we should have fixed by a workaround with Tidy in our latest stable
>>>release.
>>>
>>>Cheers
>>>St�phane
>>>
>>>At 10:47 17/09/2004, you wrote:
>>>
>>>
>>>
>>>
>>>>Hi Philippe,
>>>>
>>>>actually activating those options make everything worse.
>>>>
>>>>- the links stay broken or are getting corrupted after editing
>>>>- the text itself is changed to a bunch of special characters
>>>>
>>>>For now the only thing of interest is the linking functionality.
>>>>Let me describe again what happens.
>>>>
>>>>- I create new content
>>>>- I select one word of the text to be a link (ActiveX editor) an
>>>> enter only a valid page id as target
>>>>- I save the changes made
>>>>
>>>>So far everything is working fine, the text is shown propperly,
>>>>the link is working and the link is pointing to the desired page.
>>>>
>>>>BUT:
>>>>
>>>>If I edit the text again, the link gets corrupted upon entering
>>>>the editor. Upon opening the editor the original link
>>>>
>>>>http://localhost:8080/jahia/Jahia/op/edit/pid/12
>>>>
>>>>is changed to
>>>>
>>>>http://localhost:8080/jahia/Jahia/engineName/updatecontainer/op/edit/p id/12
>>>><http://localhost:8080/jahia/Jahia/engineName/updatecontainer/op/edit/ pid >>>>
>>>>
>>>>
>>>>
>>>/12>
>>>
>>>
>>>
>>>
>>>>.
>>>>
>>>>(switch to HTML perspective to see it). This renders the link
>>>>invalid after saving the changes, because it is pointing to an
>>>>non existing page.
>>>>
>>>>Using Tidy and cleanup does not help (but produces additional
>>>>issues as described above).
>>>>
>>>>Any other suggestions?
>>>>
>>>>
>>>>Wolfram Sorg
>>>>
>>>>
>>>>
>>>>________________________________
>>>>
>>>>Von: Philippe Vollenweider [mailto:[EMAIL PROTECTED]
>>>>Gesendet: Do 16.09.2004 17:09
>>>>An: [EMAIL PROTECTED]
>>>>Betreff: Re: Problem with automatic linking
>>>>
>>>>
>>>>
>>>>Hello,
>>>>
>>>>Did you active "Html Cleanup" (with Tidy) and "Markup Filtering" for your
>>>>current website in Server administration -> Html Editors -> Manage site
>>>>setting?
>>>>
>>>>If not, try to do this, then add a link to another page. When it's done,
>>>>try to remove the linked page. You will get an alert.
>>>>
>>>>Philippe
>>>>
>>>>At 16.09.2004 16:52, you wrote:
>>>>
>>>>
>>>>
>>>>
>>>>>Hi,
>>>>>
>>>>>we faced a problem with the automatic page linking funtionality of Jahia.
>>>>>
>>>>>If we are using a link (created using any of the existing editors)
>>>>>
>>>>>
>>>>>
>>>>>
>>>inside an
>>>
>>>
>>>
>>>
>>>>>ordinary textblock, pointing the link to an existing page id, everything
>>>>>
>>>>>
>>>>>
>>>>>
>>>>works
>>>>
>>>>
>>>>
>>>>
>>>>>fine in the first place.
>>>>>
>>>>>The problem arises if the container is edited another time, in this
>>>>>
>>>>>
>>>>>
>>>>>
>>>case the
>>>
>>>
>>>
>>>
>>>>>link gets changed upon entering the editor (it seems that the editor
>>>>>
>>>>>
>>>>>
>>>>>
>>>is not
>>>
>>>
>>>
>>>
>>>>>causing the problem). Even if no changes are made (simply open the edit
>>>>>view and say save afterwards) the links are changed.
>>>>>
>>>>>Now the links are broken and do not work anymore. Since we are having
>>>>>a large number of links reentering the page ids of all of them again
>>>>>
>>>>>
>>>>>
>>>>>
>>>is not
>>>
>>>
>>>
>>>
>>>>>an option.
>>>>>
>>>>>Ist this a known issue?
>>>>>Are there any fixes available yet?
>>>>>Is there any kind of workaround?
>>>>>
>>>>>
>>>>>Thanks in advance
>>>>>
>>>>>Wolfram Sorg
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>-------=[ pvollenweider at jahia dot com ]=---------
>>>>Jahia : A collaborative source CMS and Portal Server
>>>>www.jahia.org Community and product web site
>>>>www.jahia.com Commercial services company
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>>
>
>
>
>
>







Reply via email to