You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@lenya.apache.org by Gaurav Kalia <ga...@techblue.co.uk> on 2009/09/23 12:10:45 UTC

Firedocs Editor Problem

Hi All

I am facing a problem with Firedocs editor on the server.

The problem is when i try to edit a page on the website which is 
deployed on the server with Firedocs editor, it hung up at status 
"Setting up XML Editor..." although its working absolutely fine on my 
local machine with the same publication.

Please let me know if anything is not clear.

Regards
Gaurav

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: New Firedocs version (1.2.4) supporting FF 3.5 available

Posted by Rudolf Korhummel <ru...@korhummel.de>.
Am 28.09.2009 um 19:10 schrieb Richard Frovarp:

> Rudolf Korhummel wrote:
>> Hi Richard,
>>
>> after a build you can find the file in firedocs module at dist/ 
>> firedocs-lenya-full.xpi
>> You can also use the downloadlink from my website:
>>
>> http://kursunterlagen.cmskurse.com/cmsgrundlagen/ubersicht/firedocslenyafull.xpi
>>
>> It's an other filename but the same content.
>> I'll try to find out what's the difference of the original and the  
>> dowloaded file.
>>
>> Rudolf
>>
>> P.S. I have a date now and will be back in about 2 hours
>>
>
> So, it will corrupt for you, it will corrupt for me. I tried  
> gzipping it and that resulted in corruption, but the same file size.  
> I uploaded a large image, and that was corrupted as well. I uploaded  
> a small image, and that one came out okay. I suppose I'll file a  
> ticket with infra.
>
Thanks very much. So I known It's not  a local problem from me.

Rudolf 

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: New Firedocs version (1.2.4) supporting FF 3.5 available

Posted by Richard Frovarp <rf...@apache.org>.
Rudolf Korhummel wrote:
> Hi Richard,
>
> after a build you can find the file in firedocs module at 
> dist/firedocs-lenya-full.xpi
> You can also use the downloadlink from my website:
>
> http://kursunterlagen.cmskurse.com/cmsgrundlagen/ubersicht/firedocslenyafull.xpi 
>
>
> It's an other filename but the same content.
> I'll try to find out what's the difference of the original and the 
> dowloaded file.
>
> Rudolf
>
> P.S. I have a date now and will be back in about 2 hours
>

So, it will corrupt for you, it will corrupt for me. I tried gzipping it 
and that resulted in corruption, but the same file size. I uploaded a 
large image, and that was corrupted as well. I uploaded a small image, 
and that one came out okay. I suppose I'll file a ticket with infra.

Richard

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: New Firedocs version (1.2.4) supporting FF 3.5 available

Posted by Rudolf Korhummel <ru...@korhummel.de>.
Am 28.09.2009 um 19:23 schrieb Richard Frovarp:

> Rudolf Korhummel wrote:
>>
>>
>> Nevertheless I would propose to move the firedocs documentation   
>> and the plugin file from the wiki to the lenya Website.
>>
>> WDYT ?
>>
>> I tried to access the authoring environment, but I got a bad  
>> gateway response.  So I think lenya at the zones server is down.  
>> Since I have no acces to the server I can't restart it. Can  
>> somebody help ?
>>
>> Is http://lenya.apache.org/docu/website-update.html still valid ?
>>
>> Rudolf
>
> I don't know what the official policy is, but offering binary  
> downloads off of our main site is probably a big no-no. I'm not sure  
> what the official policy is regarding providing third party  
> offerings like this. If we slip it into our libs with proper  
> attribution, it probably won't be a problem.
>
At the moment firedocs-1.2.4.xpi is downloaded from firedocs.org  
during the build process and packed together with firedocs-lenya.xpi   
to firedocs-lenya-full.xpi (xpi files are zip files) The files are  
stored in the  dist directory of the firedocs module.

> Maybe someplace in SVN would be a better place for it?

If it's a problem to download the file from firedocs.org we can copy  
it to the firedocs module and keep it up to date manualy.

>
> The docu site is still valid. Something took the zone down and docu  
> didn't come back up. I've restarted it.

Thanks very much.

At the moment we have the documentaton on the wiki. There is no place  
for the contributions documentation on the website at the moment.
Schould we do further  documentation on the lenya website ?

WDYT ?

Rudolf
>
> Richard
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: New Firedocs version (1.2.4) supporting FF 3.5 available

Posted by Richard Frovarp <rf...@apache.org>.
Rudolf Korhummel wrote:
>
>
> Nevertheless I would propose to move the firedocs documentation  and 
> the plugin file from the wiki to the lenya Website.
>
> WDYT ?
>
> I tried to access the authoring environment, but I got a bad gateway 
> response.  So I think lenya at the zones server is down. Since I have 
> no acces to the server I can't restart it. 
> Can somebody help ?
>
> Is http://lenya.apache.org/docu/website-update.html still valid ?
>
> Rudolf

I don't know what the official policy is, but offering binary downloads 
off of our main site is probably a big no-no. I'm not sure what the 
official policy is regarding providing third party offerings like this. 
If we slip it into our libs with proper attribution, it probably won't 
be a problem.

Maybe someplace in SVN would be a better place for it?

The docu site is still valid. Something took the zone down and docu 
didn't come back up. I've restarted it.

Richard

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: New Firedocs version (1.2.4) supporting FF 3.5 available

Posted by Rudolf Korhummel <ru...@korhummel.de>.
Hi all,
> I'll try to find out what's the difference of the original and the  
> dowloaded file.

I uploaded the file from my pc at and work and form my mac at home.
If I download the files afterwads I got the following results using  
the cmp command.

upload form my windows pc at work:
original and uploaded files are different between byte 63777 and 69168  
= 5391 bytes

upload from my mac at home
original and uploaded files are different between byte 62852 and 68643  
= 5791 bytes

all other bytes are identical.

I don't know what's going wrong. Since I use different operating  
systems I think a virus can't be the reason.

Nevertheless I would propose to move the firedocs documentation  and  
the plugin file from the wiki to the lenya Website.

WDYT ?

I tried to access the authoring environment, but I got a bad gateway  
response.  So I think lenya at the zones server is down. Since I have  
no acces to the server I can't restart it.
Can somebody help ?

Is http://lenya.apache.org/docu/website-update.html still valid ?

Rudolf
>
>
>> rudolf.korhummel@uniklinik-freiburg.de wrote:
>>> Hi Vik,
>>>
>>> a strange problem. I could install the original file.
>>> If I upload it, and download afterward I'm also getting this error.
>>>
>>> Anybody an idea what's going wrong ?
>>>
>>> Regards
>>>
>>> Rudolf
>>>
>>>
>>
>> I know next to nothing about this. It seems like firedocs-1.2.4.xpi  
>> inside of the wrapper xpi is not extracting correctly. However,  
>> firedocs-lenya.xpi is extracting correctly.
>>
>> $ unzip firedocs-lenya-full-1.2.4.xpi
>> Archive:  firedocs-lenya-full-1.2.4.xpi
>> inflating: firedocs-1.2.4.xpi      error:  invalid compressed data  
>> to inflate
>> inflating: firedocs-lenya.xpi      inflating: install.rdf
>>
>> Do you have another place to put the file so others can try the  
>> upload to see what is going on? There was a recent MoinMoin  
>> upgrade, that may be affecting this.
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
>> For additional commands, e-mail: user-help@lenya.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
>


Re: New Firedocs version (1.2.4) supporting FF 3.5 available

Posted by Rudolf Korhummel <ru...@korhummel.de>.
Hi Richard,

after a build you can find the file in firedocs module at dist/ 
firedocs-lenya-full.xpi
You can also use the downloadlink from my website:

http://kursunterlagen.cmskurse.com/cmsgrundlagen/ubersicht/firedocslenyafull.xpi

It's an other filename but the same content.
I'll try to find out what's the difference of the original and the  
dowloaded file.

Rudolf

P.S. I have a date now and will be back in about 2 hours


> rudolf.korhummel@uniklinik-freiburg.de wrote:
>> Hi Vik,
>>
>> a strange problem. I could install the original file.
>> If I upload it, and download afterward I'm also getting this error.
>>
>> Anybody an idea what's going wrong ?
>>
>> Regards
>>
>> Rudolf
>>
>>
>
> I know next to nothing about this. It seems like firedocs-1.2.4.xpi  
> inside of the wrapper xpi is not extracting correctly. However,  
> firedocs-lenya.xpi is extracting correctly.
>
> $ unzip firedocs-lenya-full-1.2.4.xpi
> Archive:  firedocs-lenya-full-1.2.4.xpi
> inflating: firedocs-1.2.4.xpi      error:  invalid compressed data  
> to inflate
> inflating: firedocs-lenya.xpi      inflating: install.rdf
>
> Do you have another place to put the file so others can try the  
> upload to see what is going on? There was a recent MoinMoin upgrade,  
> that may be affecting this.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: New Firedocs version (1.2.4) supporting FF 3.5 available

Posted by Richard Frovarp <rf...@apache.org>.
rudolf.korhummel@uniklinik-freiburg.de wrote:
> Hi Vik,
>
> a strange problem. I could install the original file.
> If I upload it, and download afterward I'm also getting this error.
>
> Anybody an idea what's going wrong ?
>
> Regards
>
> Rudolf
>
>   

I know next to nothing about this. It seems like firedocs-1.2.4.xpi 
inside of the wrapper xpi is not extracting correctly. However, 
firedocs-lenya.xpi is extracting correctly.

$ unzip firedocs-lenya-full-1.2.4.xpi
Archive:  firedocs-lenya-full-1.2.4.xpi
  inflating: firedocs-1.2.4.xpi     
  error:  invalid compressed data to inflate
  inflating: firedocs-lenya.xpi     
  inflating: install.rdf     


Do you have another place to put the file so others can try the upload 
to see what is going on? There was a recent MoinMoin upgrade, that may 
be affecting this.

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: New Firedocs version (1.2.4) supporting FF 3.5 available

Posted by ru...@uniklinik-freiburg.de.
Hi Vik,

a strange problem. I could install the original file.
If I upload it, and download afterward I'm also getting this error.

Anybody an idea what's going wrong ?

Regards

Rudolf



Vik Tara <vi...@propco.co.uk> schrieb am 25.09.2009 11:06:30:

> Hi Rudolf,
>
> I just downloaded from the wiki but it wouldn't install:
>
> > Firefox could not install the file at
> >
> > file:///firedocs-lenya-full-1.2.4.xpi
> >
> > because: Not a valid install package
> > -207
> Regards
>
> Vik
>
> rudolf.korhummel@uniklinik-freiburg.de wrote:
> > Hi Lenya Users,
> >
> > there is a new version (1.2.4) of Firedocs supporting FF 3.5
available.
> > (Thanks to Thomas Comiotto).
> > You can download a precompiled version from:
> > http://wiki.apache.org/lenya/HowToInstallFiredocs.
> > You'll also get the new version if you  checkout the Firedocs module
and
> > rebuild.
> >
> > Best
> >
> > Rudolf
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> > For additional commands, e-mail: user-help@lenya.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
>
>



---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: New Firedocs version (1.2.4) supporting FF 3.5 available

Posted by Vik Tara <vi...@propco.co.uk>.
Hi Rudolf,

I just downloaded from the wiki but it wouldn't install:

> Firefox could not install the file at
>
> file:///firedocs-lenya-full-1.2.4.xpi
>
> because: Not a valid install package
> -207
Regards

Vik

rudolf.korhummel@uniklinik-freiburg.de wrote:
> Hi Lenya Users,
>
> there is a new version (1.2.4) of Firedocs supporting FF 3.5  available.
> (Thanks to Thomas Comiotto).
> You can download a precompiled version from:
> http://wiki.apache.org/lenya/HowToInstallFiredocs.
> You'll also get the new version if you  checkout the Firedocs module and
> rebuild.
>
> Best
>
> Rudolf
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
>
>   


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


New Firedocs version (1.2.4) supporting FF 3.5 available

Posted by ru...@uniklinik-freiburg.de.
Hi Lenya Users,

there is a new version (1.2.4) of Firedocs supporting FF 3.5  available.
(Thanks to Thomas Comiotto).
You can download a precompiled version from:
http://wiki.apache.org/lenya/HowToInstallFiredocs.
You'll also get the new version if you  checkout the Firedocs module and
rebuild.

Best

Rudolf



---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: Firedocs Editor Problem

Posted by Vik Tara <vi...@propco.co.uk>.
Actually it's all documented here"
http://www.firedocs.org/development/docs/addons

:-)

Vik Tara wrote:
> Just to add to this, we are trying to debug this problem - does anyone
> know where to get the source code for firedocs?
>
> Gaurav Kalia wrote:
>   
>> Hi All
>>
>> I am facing a problem with Firedocs editor on the server.
>>
>> The problem is when i try to edit a page on the website which is
>> deployed on the server with Firedocs editor, it hung up at status
>> "Setting up XML Editor..." although its working absolutely fine on my
>> local machine with the same publication.
>>
>> Please let me know if anything is not clear.
>>
>> Regards
>> Gaurav
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
>> For additional commands, e-mail: user-help@lenya.apache.org
>>
>>     
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
>
>   


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: Firedocs Editor Problem

Posted by sac sha <sa...@gmail.com>.
Hi Vik

I havent tried editing proxy configuration file yet. Will try and let you
know.

The confusing thing to me is when I append the url with
"mycontext/mupub/authoring" like cms.example.co.uk/mycontext/mupub/authoring,
it starts looking into the directory "80"(means it automatically adds 80 to
the file path) and it works fine. But when I try accessing through
cms.example.co.uk it does not add "80" to the path of file.

Regards
Sac

On Sun, Oct 4, 2009 at 12:31 PM, Vik Tara <vi...@propco.co.uk> wrote:

>  When I append 80 to the url it automatically converts it into 'without
> 80' url by removing ":80" from the url.
>
>
> What happens if you put :80 at the end of your url in the proxy
> configuration?
>
>
> On 04/10/09 12:14, sac sha wrote:
>
> Hi Vik
>
> When I append 80 to the url it automatically converts it into 'without 80'
> url by removing ":80" from the url.
>
> Regards
> Sac
>
> On Sun, Oct 4, 2009 at 9:33 AM, Vik Tara <vi...@propco.co.uk> wrote:
>
>>  And when I put the path into my browser it says no such file. But when I
>> insert 80 to the path it shows the proper file. So I am sure that the
>> problem is due to that '80' figure.
>>
>>
>>  So if you append :80 to your proxy url - does firedocs then work?
>>
>> Vik
>>
>>
>> On 04/10/09 01:33, sac sha wrote:
>>
>> Hi All
>>
>> I have put some alerts to the javascript(includeURI.spec) and find out
>> that the path to the file is coming incorrect. The path to the rngs stored
>> in my system is having a directory for port 80 with the name '80', but the
>> javascript alert is giving me the path omitting this directory.
>>
>> And when I put the path into my browser it says no such file. But when I
>> insert 80 to the path it shows the proper file. So I am sure that the
>> problem is due to that '80' figure.
>>
>> file:///tmp/firedocs/schema/uk/co/example/cms/lenya/schemas/lenya.rng ->
>> Gives error (file not found)
>> file:///tmp/firedocs/schema/uk/co/example/cms/80/lenya/schemas/lenya.rng-> (shows proper file)
>>
>> Not sure but can this be because of url proxying?
>>
>> Adding to this...
>> the lenya.rng on the wrong path(as above) is an xml file having wrong data
>> i.e page not found data of lenya. And also no dublincore directory and
>> dublincore.rng present :-)
>>
>> Regards
>> Sac
>>
>> On Thu, Oct 1, 2009 at 3:39 PM, Thomas Comiotto <
>> thomas.comiotto@id.uzh.ch> wrote:
>>
>>>
>>>> I can call each of the urls and get a page returned using the proxy url.
>>>>
>>>>
>>>  You really need to follow *all* the links, including cross-references
>>> within schema files.
>>> The line below basically says that a schema import directive is pointing
>>> to the void.
>>>
>>> Error: uncaught exception: [Exception... "Component returned failure
>>> code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIXMLHttpRequest.send]"
>>> nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame ::
>>> chrome://firedocs/content/validation/RNGSchemaParser.js :: anonymous ::
>>> line 121" data: no]
>>>
>>>  If you want to know which file can't be found without having to do all
>>> the handy work, add something like this to RNGSchemaParser.js (located
>>> somewhere below your firefox profile):
>>>
>>> 113: dump(includeURI.spec)
>>>
>>> and restart firefox from console.
>>>
>>> Don't forget to disable xul caching and enable console dumps as described
>>> here for instance
>>> http://www.yulup.org/developers.html
>>>
>>>
>>>  The only strange thing I can see is calling the last url:
>>>>
>>>>  <edit:uri-resolver protocol="lenya-document"
>>>>>> href="solutions.html?lenya.usecase=atom.uuid2url&url="/>
>>>>>>
>>>>>
>>> This returns:
>>>>
>>>> /staticfiredocs
>>>>>
>>>>
>>>> Which is the publication name - but we hide this with the proxy. Could
>>>> that be an issue?
>>>>
>>>>
>>>  That's for resolving lenya:document links. Should be ok.
>>>
>>>
>>> Best
>>> Thomas
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
>>> For additional commands, e-mail: user-help@lenya.apache.org
>>>
>>>
>>
>>
>> --
>> Regards
>> Sachin Sharma
>>
>>
>>
>
>
> --
> Regards
> Sachin Sharma
>
>
>


-- 
Regards
Sachin Sharma

Re: Firedocs Editor Problem

Posted by Vik Tara <vi...@propco.co.uk>.
> When I append 80 to the url it automatically converts it into 'without 
> 80' url by removing ":80" from the url.

What happens if you put :80 at the end of your url in the proxy 
configuration?

On 04/10/09 12:14, sac sha wrote:
> Hi Vik
>
> When I append 80 to the url it automatically converts it into 'without 
> 80' url by removing ":80" from the url.
>
> Regards
> Sac
>
> On Sun, Oct 4, 2009 at 9:33 AM, Vik Tara <vik@propco.co.uk 
> <ma...@propco.co.uk>> wrote:
>
>>     And when I put the path into my browser it says no such file. But
>>     when I insert 80 to the path it shows the proper file. So I am
>>     sure that the problem is due to that '80' figure.
>
>     So if you append :80 to your proxy url - does firedocs then work?
>
>     Vik
>
>
>
>     On 04/10/09 01:33, sac sha wrote:
>>     Hi All
>>
>>     I have put some alerts to the javascript(includeURI.spec) and
>>     find out that the path to the file is coming incorrect. The path
>>     to the rngs stored in my system is having a directory for port 80
>>     with the name '80', but the javascript alert is giving me the
>>     path omitting this directory.
>>
>>     And when I put the path into my browser it says no such file. But
>>     when I insert 80 to the path it shows the proper file. So I am
>>     sure that the problem is due to that '80' figure.
>>
>>     file:///tmp/firedocs/schema/uk/co/example/cms/lenya/schemas/lenya.rng
>>     -> Gives error (file not found)
>>     file:///tmp/firedocs/schema/uk/co/example/cms/80/lenya/schemas/lenya.rng
>>     -> (shows proper file)
>>
>>     Not sure but can this be because of url proxying?
>>
>>     Adding to this...
>>     the lenya.rng on the wrong path(as above) is an xml file having
>>     wrong data i.e page not found data of lenya. And also no
>>     dublincore directory and dublincore.rng present :-)
>>
>>     Regards
>>     Sac
>>
>>     On Thu, Oct 1, 2009 at 3:39 PM, Thomas Comiotto
>>     <thomas.comiotto@id.uzh.ch <ma...@id.uzh.ch>> wrote:
>>
>>
>>             I can call each of the urls and get a page returned using
>>             the proxy url.
>>
>>
>>         You really need to follow *all* the links, including
>>         cross-references within schema files.
>>         The line below basically says that a schema import directive
>>         is pointing to the void.
>>
>>
>>         Error: uncaught exception: [Exception... "Component returned
>>         failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND)
>>         [nsIXMLHttpRequest.send]" nsresult: "0x80520012
>>         (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame ::
>>         chrome://firedocs/content/validation/RNGSchemaParser.js ::
>>         anonymous :: line 121" data: no]
>>
>>         If you want to know which file can't be found without having
>>         to do all the handy work, add something like this to
>>         RNGSchemaParser.js (located somewhere below your firefox
>>         profile):
>>
>>         113: dump(includeURI.spec)
>>
>>         and restart firefox from console.
>>
>>         Don't forget to disable xul caching and enable console dumps
>>         as described here for instance
>>
>>         http://www.yulup.org/developers.html
>>
>>
>>             The only strange thing I can see is calling the last url:
>>
>>                     <edit:uri-resolver protocol="lenya-document"
>>                     href="solutions.html?lenya.usecase=atom.uuid2url&url="/>
>>
>>
>>             This returns:
>>
>>                 /staticfiredocs
>>
>>
>>             Which is the publication name - but we hide this with the
>>             proxy. Could
>>             that be an issue?
>>
>>
>>         That's for resolving lenya:document links. Should be ok.
>>
>>
>>         Best
>>         Thomas
>>
>>
>>
>>         ---------------------------------------------------------------------
>>         To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
>>         <ma...@lenya.apache.org>
>>         For additional commands, e-mail: user-help@lenya.apache.org
>>         <ma...@lenya.apache.org>
>>
>>
>>
>>
>>     -- 
>>     Regards
>>     Sachin Sharma
>>
>
>
>
>
> -- 
> Regards
> Sachin Sharma
>


Re: Firedocs Editor Problem

Posted by sac sha <sa...@gmail.com>.
Hi Vik

When I append 80 to the url it automatically converts it into 'without 80'
url by removing ":80" from the url.

Regards
Sac

On Sun, Oct 4, 2009 at 9:33 AM, Vik Tara <vi...@propco.co.uk> wrote:

>  And when I put the path into my browser it says no such file. But when I
> insert 80 to the path it shows the proper file. So I am sure that the
> problem is due to that '80' figure.
>
>
> So if you append :80 to your proxy url - does firedocs then work?
>
> Vik
>
>
>
> On 04/10/09 01:33, sac sha wrote:
>
> Hi All
>
> I have put some alerts to the javascript(includeURI.spec) and find out that
> the path to the file is coming incorrect. The path to the rngs stored in my
> system is having a directory for port 80 with the name '80', but the
> javascript alert is giving me the path omitting this directory.
>
> And when I put the path into my browser it says no such file. But when I
> insert 80 to the path it shows the proper file. So I am sure that the
> problem is due to that '80' figure.
>
> file:///tmp/firedocs/schema/uk/co/example/cms/lenya/schemas/lenya.rng ->
> Gives error (file not found)
> file:///tmp/firedocs/schema/uk/co/example/cms/80/lenya/schemas/lenya.rng-> (shows proper file)
>
> Not sure but can this be because of url proxying?
>
> Adding to this...
> the lenya.rng on the wrong path(as above) is an xml file having wrong data
> i.e page not found data of lenya. And also no dublincore directory and
> dublincore.rng present :-)
>
> Regards
> Sac
>
> On Thu, Oct 1, 2009 at 3:39 PM, Thomas Comiotto <thomas.comiotto@id.uzh.ch
> > wrote:
>
>>
>>> I can call each of the urls and get a page returned using the proxy url.
>>>
>>>
>>  You really need to follow *all* the links, including cross-references
>> within schema files.
>> The line below basically says that a schema import directive is pointing
>> to the void.
>>
>> Error: uncaught exception: [Exception... "Component returned failure code:
>> 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIXMLHttpRequest.send]" nsresult:
>> "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame ::
>> chrome://firedocs/content/validation/RNGSchemaParser.js :: anonymous ::
>> line 121" data: no]
>>
>>  If you want to know which file can't be found without having to do all
>> the handy work, add something like this to RNGSchemaParser.js (located
>> somewhere below your firefox profile):
>>
>> 113: dump(includeURI.spec)
>>
>> and restart firefox from console.
>>
>> Don't forget to disable xul caching and enable console dumps as described
>> here for instance
>> http://www.yulup.org/developers.html
>>
>>
>>  The only strange thing I can see is calling the last url:
>>>
>>>  <edit:uri-resolver protocol="lenya-document"
>>>>> href="solutions.html?lenya.usecase=atom.uuid2url&url="/>
>>>>>
>>>>
>>  This returns:
>>>
>>>  /staticfiredocs
>>>>
>>>
>>> Which is the publication name - but we hide this with the proxy. Could
>>> that be an issue?
>>>
>>>
>>  That's for resolving lenya:document links. Should be ok.
>>
>>
>> Best
>> Thomas
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
>> For additional commands, e-mail: user-help@lenya.apache.org
>>
>>
>
>
> --
> Regards
> Sachin Sharma
>
>
>


-- 
Regards
Sachin Sharma

Re: Firedocs Editor Problem

Posted by Vik Tara <vi...@propco.co.uk>.
> And when I put the path into my browser it says no such file. But when 
> I insert 80 to the path it shows the proper file. So I am sure that 
> the problem is due to that '80' figure.

So if you append :80 to your proxy url - does firedocs then work?

Vik


On 04/10/09 01:33, sac sha wrote:
> Hi All
>
> I have put some alerts to the javascript(includeURI.spec) and find out 
> that the path to the file is coming incorrect. The path to the rngs 
> stored in my system is having a directory for port 80 with the name 
> '80', but the javascript alert is giving me the path omitting this 
> directory.
>
> And when I put the path into my browser it says no such file. But when 
> I insert 80 to the path it shows the proper file. So I am sure that 
> the problem is due to that '80' figure.
>
> file:///tmp/firedocs/schema/uk/co/example/cms/lenya/schemas/lenya.rng 
> -> Gives error (file not found)
> file:///tmp/firedocs/schema/uk/co/example/cms/80/lenya/schemas/lenya.rng 
> -> (shows proper file)
>
> Not sure but can this be because of url proxying?
>
> Adding to this...
> the lenya.rng on the wrong path(as above) is an xml file having wrong 
> data i.e page not found data of lenya. And also no dublincore 
> directory and dublincore.rng present :-)
>
> Regards
> Sac
>
> On Thu, Oct 1, 2009 at 3:39 PM, Thomas Comiotto 
> <thomas.comiotto@id.uzh.ch <ma...@id.uzh.ch>> wrote:
>
>
>         I can call each of the urls and get a page returned using the
>         proxy url.
>
>
>     You really need to follow *all* the links, including
>     cross-references within schema files.
>     The line below basically says that a schema import directive is
>     pointing to the void.
>
>
>     Error: uncaught exception: [Exception... "Component returned
>     failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND)
>     [nsIXMLHttpRequest.send]" nsresult: "0x80520012
>     (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame ::
>     chrome://firedocs/content/validation/RNGSchemaParser.js ::
>     anonymous :: line 121" data: no]
>
>     If you want to know which file can't be found without having to do
>     all the handy work, add something like this to RNGSchemaParser.js
>     (located somewhere below your firefox profile):
>
>     113: dump(includeURI.spec)
>
>     and restart firefox from console.
>
>     Don't forget to disable xul caching and enable console dumps as
>     described here for instance
>
>     http://www.yulup.org/developers.html
>
>
>         The only strange thing I can see is calling the last url:
>
>                 <edit:uri-resolver protocol="lenya-document"
>                 href="solutions.html?lenya.usecase=atom.uuid2url&url="/>
>
>
>         This returns:
>
>             /staticfiredocs
>
>
>         Which is the publication name - but we hide this with the
>         proxy. Could
>         that be an issue?
>
>
>     That's for resolving lenya:document links. Should be ok.
>
>
>     Best
>     Thomas
>
>
>
>     ---------------------------------------------------------------------
>     To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
>     <ma...@lenya.apache.org>
>     For additional commands, e-mail: user-help@lenya.apache.org
>     <ma...@lenya.apache.org>
>
>
>
>
> -- 
> Regards
> Sachin Sharma
>


Re: Firedocs Editor Problem

Posted by sac sha <sa...@gmail.com>.
Hi All

I have put some alerts to the javascript(includeURI.spec) and find out that
the path to the file is coming incorrect. The path to the rngs stored in my
system is having a directory for port 80 with the name '80', but the
javascript alert is giving me the path omitting this directory.

And when I put the path into my browser it says no such file. But when I
insert 80 to the path it shows the proper file. So I am sure that the
problem is due to that '80' figure.

file:///tmp/firedocs/schema/uk/co/example/cms/lenya/schemas/lenya.rng ->
Gives error (file not found)
file:///tmp/firedocs/schema/uk/co/example/cms/80/lenya/schemas/lenya.rng ->
(shows proper file)

Not sure but can this be because of url proxying?

Adding to this...
the lenya.rng on the wrong path(as above) is an xml file having wrong data
i.e page not found data of lenya. And also no dublincore directory and
dublincore.rng present :-)

Regards
Sac

On Thu, Oct 1, 2009 at 3:39 PM, Thomas Comiotto
<th...@id.uzh.ch>wrote:

>
>> I can call each of the urls and get a page returned using the proxy url.
>>
>>
> You really need to follow *all* the links, including cross-references
> within schema files.
> The line below basically says that a schema import directive is pointing to
> the void.
>
> Error: uncaught exception: [Exception... "Component returned failure code:
> 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIXMLHttpRequest.send]" nsresult:
> "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame ::
> chrome://firedocs/content/validation/RNGSchemaParser.js :: anonymous :: line
> 121" data: no]
>
> If you want to know which file can't be found without having to do all the
> handy work, add something like this to RNGSchemaParser.js (located somewhere
> below your firefox profile):
>
> 113: dump(includeURI.spec)
>
> and restart firefox from console.
>
> Don't forget to disable xul caching and enable console dumps as described
> here for instance
> http://www.yulup.org/developers.html
>
>
>  The only strange thing I can see is calling the last url:
>>
>>  <edit:uri-resolver protocol="lenya-document"
>>>> href="solutions.html?lenya.usecase=atom.uuid2url&url="/>
>>>>
>>>
>  This returns:
>>
>>  /staticfiredocs
>>>
>>
>> Which is the publication name - but we hide this with the proxy. Could
>> that be an issue?
>>
>>
> That's for resolving lenya:document links. Should be ok.
>
>
> Best
> Thomas
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
>
>


-- 
Regards
Sachin Sharma

Re: Firedocs Editor Problem

Posted by Vik Tara <vi...@propco.co.uk>.
Hi All,

We have still not managed to get firedocs to work when using our ajp proxy.

Are any other users working with firedocs in this way?

Regards


Vik

Thomas Comiotto wrote:
> Hi Sac
> 
> 
>>
>> Can you let me know from where the javascripts get the path? Right now
>> the heirarchy which firedocs is creating in the /tmp directory is
>> different than the heirarchy it javascript alert shows for
>> "includeURI.spec" in RNGSchemaParser.
> 
> That should be ok. The default port gets substituted by 80 when storing
> the local copy of the Uri.
> 
> However you can put some alerts to URICache.js:171 and see what port
> information you get for the remote schema files (not the local copy).
> 
> Make sure to clear the cached files first (remove the whole local schema
> folder structure).
> 
> 
> 
>>
>>
>> The heirarchy made by firedocs in /tmp is having directory "80"(for
>> http port) in it but javascript alert shows path without "80"
>> directory in it. And also the lenya.rng produced is an lenya error
>> file with error-404. There is no dublincore produced.
> 
> 
> This looks like the interesting part. Is lenya.rng (the remote file)
> actually accessible from the server?
> 
> I am not sure if this is a Lenya or a Firedocs issue, so let's move this
> discussion to a private channel and post a summary to the list when
> we're finished.
> 
> Cheers
> Thomas
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: Firedocs Editor Problem

Posted by Thomas Comiotto <th...@id.uzh.ch>.
Hi Sac


>
> Can you let me know from where the javascripts get the path? Right  
> now the heirarchy which firedocs is creating in the /tmp directory  
> is different than the heirarchy it javascript alert shows for  
> "includeURI.spec" in RNGSchemaParser.

That should be ok. The default port gets substituted by 80 when  
storing the local copy of the Uri.

However you can put some alerts to URICache.js:171 and see what port  
information you get for the remote schema files (not the local copy).

Make sure to clear the cached files first (remove the whole local  
schema folder structure).



>
>
> The heirarchy made by firedocs in /tmp is having directory "80"(for  
> http port) in it but javascript alert shows path without "80"  
> directory in it. And also the lenya.rng produced is an lenya error  
> file with error-404. There is no dublincore produced.


This looks like the interesting part. Is lenya.rng (the remote file)  
actually accessible from the server?

I am not sure if this is a Lenya or a Firedocs issue, so let's move  
this discussion to a private channel and post a summary to the list  
when we're finished.

Cheers
Thomas



---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: Firedocs Editor Problem

Posted by sac sha <sa...@gmail.com>.
Hi Thomas

Can you let me know from where the javascripts get the path? Right now the
heirarchy which firedocs is creating in the /tmp directory is different than
the heirarchy it javascript alert shows for "includeURI.spec" in
RNGSchemaParser.

The heirarchy made by firedocs in /tmp is having directory "80"(for http
port) in it but javascript alert shows path without "80" directory in it.
And also the lenya.rng produced is an lenya error file with error-404. There
is no dublincore produced.

Regards
Sac

On Thu, Oct 1, 2009 at 3:39 PM, Thomas Comiotto
<th...@id.uzh.ch>wrote:

>
>> I can call each of the urls and get a page returned using the proxy url.
>>
>>
> You really need to follow *all* the links, including cross-references
> within schema files.
> The line below basically says that a schema import directive is pointing to
> the void.
>
> Error: uncaught exception: [Exception... "Component returned failure code:
> 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIXMLHttpRequest.send]" nsresult:
> "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame ::
> chrome://firedocs/content/validation/RNGSchemaParser.js :: anonymous :: line
> 121" data: no]
>
> If you want to know which file can't be found without having to do all the
> handy work, add something like this to RNGSchemaParser.js (located somewhere
> below your firefox profile):
>
> 113: dump(includeURI.spec)
>
> and restart firefox from console.
>
> Don't forget to disable xul caching and enable console dumps as described
> here for instance
> http://www.yulup.org/developers.html
>
>
>  The only strange thing I can see is calling the last url:
>>
>>  <edit:uri-resolver protocol="lenya-document"
>>>> href="solutions.html?lenya.usecase=atom.uuid2url&url="/>
>>>>
>>>
>  This returns:
>>
>>  /staticfiredocs
>>>
>>
>> Which is the publication name - but we hide this with the proxy. Could
>> that be an issue?
>>
>>
> That's for resolving lenya:document links. Should be ok.
>
>
> Best
> Thomas
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
>
>


-- 
Regards
Sachin Sharma

Re: Firedocs Editor Problem

Posted by sac sha <sa...@gmail.com>.
Hi All

I looked into the issue and find out some thing interesting:

The first thing I noticed is the dublincore directory with the
dublincore.rng is missing in case I use the direct url. I dont know why but
all other files are being copied but not this one.

Second: If I put /pubname/area in front of the url all works fine.

My URLs and directory structure in the tmp are :

*Case 1: http://cms.example.co.uk/test.html*
/tmp/firedocs/schema/uk/co/example/cms/80/lenya and
/tmp/firedocs/schema/uk/co/example/cms/80/modules

In this case firedocs says file not found.

*Case 2: http://cms.example.co.uk/lenya/mypub/authoring/test.html*
/tmp/firedocs/schema/uk/co/example/cms/80/mycontext/lenya and
/tmp/firedocs/schema/uk/co/example/cms/80/mycontext/mypub/modules

In this case firedocs works fine.

Obviously two different file structures here. Any suggestions.

Regards
Sac


On Thu, Oct 1, 2009 at 3:39 PM, Thomas Comiotto
<th...@id.uzh.ch>wrote:

>
>> I can call each of the urls and get a page returned using the proxy url.
>>
>>
> You really need to follow *all* the links, including cross-references
> within schema files.
> The line below basically says that a schema import directive is pointing to
> the void.
>
> Error: uncaught exception: [Exception... "Component returned failure code:
> 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIXMLHttpRequest.send]" nsresult:
> "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame ::
> chrome://firedocs/content/validation/RNGSchemaParser.js :: anonymous :: line
> 121" data: no]
>
> If you want to know which file can't be found without having to do all the
> handy work, add something like this to RNGSchemaParser.js (located somewhere
> below your firefox profile):
>
> 113: dump(includeURI.spec)
>
> and restart firefox from console.
>
> Don't forget to disable xul caching and enable console dumps as described
> here for instance
> http://www.yulup.org/developers.html
>
>
>  The only strange thing I can see is calling the last url:
>>
>>  <edit:uri-resolver protocol="lenya-document"
>>>> href="solutions.html?lenya.usecase=atom.uuid2url&url="/>
>>>>
>>>
>  This returns:
>>
>>  /staticfiredocs
>>>
>>
>> Which is the publication name - but we hide this with the proxy. Could
>> that be an issue?
>>
>>
> That's for resolving lenya:document links. Should be ok.
>
>
> Best
> Thomas
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
>
>


-- 
Regards
Sachin Sharma

Re: Firedocs Editor Problem

Posted by Thomas Comiotto <th...@id.uzh.ch>.
>
> I can call each of the urls and get a page returned using the proxy  
> url.
>

You really need to follow *all* the links, including cross-references  
within schema files.
The line below basically says that a schema import directive is  
pointing to the void.

Error: uncaught exception: [Exception... "Component returned failure  
code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIXMLHttpRequest.send]"  
nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS  
frame :: chrome://firedocs/content/validation/RNGSchemaParser.js ::  
anonymous :: line 121" data: no]

If you want to know which file can't be found without having to do all  
the handy work, add something like this to RNGSchemaParser.js (located  
somewhere below your firefox profile):

113: dump(includeURI.spec)

and restart firefox from console.

Don't forget to disable xul caching and enable console dumps as  
described here for instance
http://www.yulup.org/developers.html


> The only strange thing I can see is calling the last url:
>
>>> <edit:uri-resolver protocol="lenya-document" href="solutions.html? 
>>> lenya.usecase=atom.uuid2url&url="/>

> This returns:
>
>> /staticfiredocs
>
> Which is the publication name - but we hide this with the proxy. Could
> that be an issue?
>

That's for resolving lenya:document links. Should be ok.


Best
Thomas


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: Firedocs Editor Problem

Posted by Vik Tara <vi...@propco.co.uk>.
Thomas Comiotto wrote:
> 
>>>
>>>
>>> Did you check all the links in the service document (atom.entry
>>> usecase), including cross-references in schema/xslt files? You can do
>>> that by hand - simply by typing the corresponding urls in the browser
>>> address bar.
>>
>> I'm not clear on which is the service document - can you elaborate?
>>
> 
> lenya.usecase=atom.entry

OK - I get this document:

> -
> <entry>
> <id>70398150-96fe-11de-a586-bc9262832f6d:en</id>
> <title type="text">Products</title>
> -
> <summary>
> Your Site Summary Here
> </summary>
> <author>alice</author>
> <category scheme="http://apache.org/lenya/atom/categories/language">en</category>
> <updated>1254404367148</updated>
> <content type="application/xhtml+xml" src="lenya-document:70398150-96fe-11de-a586-bc9262832f6d,lang=en"/>
> -
> <title>
> Your Site Title Here
> </title>
> <date>2009-09-01 19:20:17</date>
> <creator>alice</creator>
> <link rel="edit" type="application/atom+xml" href="solutions.html?lenya.usecase=atom.entry"/>
> <link rel="lock" type="application/atomcoll+xml" href="solutions.html?lenya.usecase=atom.locks"/>
> <link rel="assets" type="application/atomcoll+xml" href="solutions.html?lenya.usecase=atom.assets"/>
> <link rel="children" type="application/atomcoll+xml" href="solutions.html?lenya.usecase=atom.children"/>
> <link rel="edit-media" type="application/xhtml+xml" href="solutions.html?lenya.usecase=atom.content"/>
> -
> <edit:edit>
> -
> <edit:styles>
> -
> <edit:style transformPageContext="false" href="../../modules/atom/modules/xhtmlfiredocs/xslt/xhtmlfiredocs2xhtml.xsl">
> <edit:parameter name="editor" value="firedocs"/>
> </edit:style>
> </edit:styles>
> <edit:page-context href="solutions.html.pageContext"/>
> <edit:inserts href="solutions.html?lenya.usecase=atom.inserts"/>
> <edit:schema type="relaxNG" href="../modules/xhtml/schemas/xhtml.rng"/>
> <edit:uri-resolver protocol="lenya-document" href="solutions.html?lenya.usecase=atom.uuid2url&url="/>
> </edit:edit>
> </entry>

I can call each of the urls and get a page returned using the proxy url.

The only strange thing I can see is calling the last url:

>> <edit:uri-resolver protocol="lenya-document" href="solutions.html?lenya.usecase=atom.uuid2url&url="/>

This returns:

> /staticfiredocs

Which is the publication name - but we hide this with the proxy. Could
that be an issue?


Regards



Vik




---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: Firedocs Editor Problem

Posted by Thomas Comiotto <th...@id.uzh.ch>.
>>
>>
>> Did you check all the links in the service document (atom.entry
>> usecase), including cross-references in schema/xslt files? You can do
>> that by hand - simply by typing the corresponding urls in the browser
>> address bar.
>
> I'm not clear on which is the service document - can you elaborate?
>

lenya.usecase=atom.entry

It's all documented here:
http://www.firedocs.org/development/docs/remote_editing

Best
Thomas


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: Firedocs Editor Problem

Posted by Vik Tara <vi...@propco.co.uk>.
Thomas Comiotto wrote:
> Hi Vik
> 
> Am 01.10.2009 um 13:52 schrieb Vik Tara:
> 
>>
>> The last thing that seems to happen (according to my httpd log) is a get
>> request:
>> [01/Oct/2009:11:54:16 +0100] "GET
>> /solutions.html?lenya.usecase=atom.entry HTTP/1.1" 200 4301
>>
> 
> Did you check all the links in the service document (atom.entry
> usecase), including cross-references in schema/xslt files? You can do
> that by hand - simply by typing the corresponding urls in the browser
> address bar.

I'm not clear on which is the service document - can you elaborate?

> 
> I that doesn't help post a complete network traffic log by using tcpdump
> or similar.

OK - taking a look at that now.

> 
> Best
> Thomas
> 
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: Firedocs Editor Problem

Posted by Thomas Comiotto <th...@id.uzh.ch>.
Hi Vik

Am 01.10.2009 um 13:52 schrieb Vik Tara:

>
> The last thing that seems to happen (according to my httpd log) is a  
> get
> request:
> [01/Oct/2009:11:54:16 +0100] "GET
> /solutions.html?lenya.usecase=atom.entry HTTP/1.1" 200 4301
>

Did you check all the links in the service document (atom.entry  
usecase), including cross-references in schema/xslt files? You can do  
that by hand - simply by typing the corresponding urls in the browser  
address bar.

I that doesn't help post a complete network traffic log by using  
tcpdump or similar.

Best
Thomas





---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: Firedocs Editor Problem

Posted by Vik Tara <vi...@propco.co.uk>.
I've tried to check the same as proposed by Thomas.

If I access the server via it's host name (avoiding the ajp proxy) then
I can edit the page in firedocs and the firedocs schema files appear in
my /tmp/firedocs folder. All OK here!

If I use the proxy url, it gets stuck on "setting up xml editor" and no
files are copied to my /tmp/firedocs folder.

The last thing that seems to happen (according to my httpd log) is a get
request:
[01/Oct/2009:11:54:16 +0100] "GET
/solutions.html?lenya.usecase=atom.entry HTTP/1.1" 200 4301

This url works fine - if I put it in the browser it does return an xml.

Firedocs then tries to call this url:
chrome://firedocs/content/firedocs.xul?open-uri=http%3A%2F%2Fsite.example.com%2Fsolutions.html

Which fails.

Interestingly, the files which get copied into the /tmp/firedocs folder
are actually accessible from the proxy url, if I put the url into the
browser - so the problem does not seem to be access to the schema files.

Any help on how to debug this further would be a great help.

Is anyone else using firedocs via an ajp proxy? If so maybe you could
post your virtual host config?



Regards



Vik





Gaurav Kalia wrote:
> Hi Thomas
> 
>> Hint: The editor keeps a local copy of schema files and stylesheets so
>> you also can check what gets loaded and whatnot (see /tmp/firedocs/ or
>> $home/.firedocs depending on your Firedocs version). 
> As Suggested by you i have checked the /tmp/firedocs/ directory, there
> are two folder one with the hierarchy of my localhost and other with the
> URL (cms.firedocs.com).
> 
> I found that the files in the localhost folder are more then the one
> with URL hierarchy (AJP Proxy).
> 
> Can you please suggest how can i resolve this using the AJP Proxy.
> 
> Thanks & Regards
> Gaurav
> 
> Thomas Comiotto wrote:
>> Hi Guarav
>>
>>>>
>>>>
>>>> Error: uncaught exception: [Exception... "Component returned failure
>>>> code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIXMLHttpRequest.send]"
>>>> nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame
>>>> :: chrome://firedocs/content/validation/RNGSchemaParser.js ::
>>>> anonymous :: line 121" data: no]
>>>>
>>
>> Could be that some schema files are hiding behind the proxy.
>>
>> Make sure all the files referenced in the service document (including
>> cross references) are in fact accesibble by the editor.
>>
>> Hint: The editor keeps a local copy of schema files and stylesheets so
>> you also can check what gets loaded and whatnot (see /tmp/firedocs/ or
>> $home/.firedocs depending on your Firedocs version).
>>
>> HTH
>> Thomas
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
>> For additional commands, e-mail: user-help@lenya.apache.org
>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: Firedocs Editor Problem

Posted by Gaurav Kalia <ga...@techblue.co.uk>.
Hi Thomas

> Hint: The editor keeps a local copy of schema files and stylesheets so 
> you also can check what gets loaded and whatnot (see /tmp/firedocs/ or 
> $home/.firedocs depending on your Firedocs version). 
As Suggested by you i have checked the /tmp/firedocs/ directory, there 
are two folder one with the hierarchy of my localhost and other with the 
URL (cms.firedocs.com).

I found that the files in the localhost folder are more then the one 
with URL hierarchy (AJP Proxy).

Can you please suggest how can i resolve this using the AJP Proxy.

Thanks & Regards
Gaurav

Thomas Comiotto wrote:
> Hi Guarav
>
>>>
>>>
>>> Error: uncaught exception: [Exception... "Component returned failure 
>>> code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIXMLHttpRequest.send]" 
>>> nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame 
>>> :: chrome://firedocs/content/validation/RNGSchemaParser.js :: 
>>> anonymous :: line 121" data: no]
>>>
>
> Could be that some schema files are hiding behind the proxy.
>
> Make sure all the files referenced in the service document (including 
> cross references) are in fact accesibble by the editor.
>
> Hint: The editor keeps a local copy of schema files and stylesheets so 
> you also can check what gets loaded and whatnot (see /tmp/firedocs/ or 
> $home/.firedocs depending on your Firedocs version).
>
> HTH
> Thomas
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: Firedocs Editor Problem

Posted by Thomas Comiotto <th...@id.uzh.ch>.
Hi Guarav

>>
>>
>> Error: uncaught exception: [Exception... "Component returned  
>> failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND)  
>> [nsIXMLHttpRequest.send]" nsresult: "0x80520012  
>> (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame :: chrome://firedocs/ 
>> content/validation/RNGSchemaParser.js :: anonymous :: line 121"  
>> data: no]
>>

Could be that some schema files are hiding behind the proxy.

Make sure all the files referenced in the service document (including  
cross references) are in fact accesibble by the editor.

Hint: The editor keeps a local copy of schema files and stylesheets so  
you also can check what gets loaded and whatnot (see /tmp/firedocs/ or  
$home/.firedocs depending on your Firedocs version).

HTH
Thomas



---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: Firedocs Editor Problem

Posted by Gaurav Kalia <ga...@techblue.co.uk>.
Can anyone help me on this ?

Gaurav Kalia wrote:
> Hi All
>
> I am getting this error in the Firefox console:
>
> Error: uncaught exception: [Exception... "Component returned failure 
> code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIXMLHttpRequest.send]" 
> nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame 
> :: chrome://firedocs/content/validation/RNGSchemaParser.js :: 
> anonymous :: line 121" data: no]
>
>
> Regards
> Gaurav
>
>
> Gaurav Kalia wrote:
>> Hi All
>>
>> To add further,
>>
>> I accessed the Firedocs Publication on my system with the URL:
>>
>> http://localhost:8080/testpro/defaultfiredocs/authoring/test.html
>>
>> and it simply worked but when I accessed the same publication with 
>> the AJP Proxing URL:
>>
>> http://cms.firedocs.example.com/test.html
>>
>> then it hangs at "Setting XML Editor".
>>
>> I think this is because of the AJP Proxing. I am investigating the 
>> problem further.
>>
>> If someone else has encountered the same problem and knows the 
>> solution then please suggest.
>>
>> Regards
>> Gaurav
>>
>>
>> Michael Wechner wrote:
>>> Vik Tara schrieb:
>>>> Thanks Michael - could you give us any pointers on how to debug our 
>>>> problem?
>>>>   
>>>
>>> I am not really familiar with Firedocs and I am afraid I cannot 
>>> really help, but maybe Thomas can
>>>> Are you aware of any sort of debugger or ide?
>>>>   
>>>
>>> maybe Firebug is helpful: 
>>> https://addons.mozilla.org/de/firefox/addon/1843
>>>
>>> and also "ngrep" to debug/monitor the http traffic
>>>
>>> Also our tips re Yulup should be applicable to Firedocs
>>>
>>> http://www.yulup.org/developers.html
>>>
>>> HTH
>>>
>>> Michael
>>>> Regards
>>>>
>>>>
>>>> Vik
>>>>
>>>> Michael Wechner wrote:
>>>>  
>>>>> Vik Tara schrieb:
>>>>>  
>>>>>> Just to add to this, we are trying to debug this problem - does 
>>>>>> anyone
>>>>>> know where to get the source code for firedocs?
>>>>>>         
>>>>> I would have assumed somewhere at
>>>>>
>>>>> http://www.firedocs.org/
>>>>>
>>>>> Cheers
>>>>>
>>>>> Michael
>>>>>  
>>>>>> Gaurav Kalia wrote:
>>>>>>  
>>>>>>    
>>>>>>> Hi All
>>>>>>>
>>>>>>> I am facing a problem with Firedocs editor on the server.
>>>>>>>
>>>>>>> The problem is when i try to edit a page on the website which is
>>>>>>> deployed on the server with Firedocs editor, it hung up at status
>>>>>>> "Setting up XML Editor..." although its working absolutely fine 
>>>>>>> on my
>>>>>>> local machine with the same publication.
>>>>>>>
>>>>>>> Please let me know if anything is not clear.
>>>>>>>
>>>>>>> Regards
>>>>>>> Gaurav
>>>>>>>
>>>>>>> --------------------------------------------------------------------- 
>>>>>>>
>>>>>>> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
>>>>>>> For additional commands, e-mail: user-help@lenya.apache.org
>>>>>>>
>>>>>>>             
>>>>>> --------------------------------------------------------------------- 
>>>>>>
>>>>>> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
>>>>>> For additional commands, e-mail: user-help@lenya.apache.org
>>>>>>
>>>>>>         
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
>>>>> For additional commands, e-mail: user-help@lenya.apache.org
>>>>>
>>>>>     
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
>>>> For additional commands, e-mail: user-help@lenya.apache.org
>>>>
>>>>   
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
>>> For additional commands, e-mail: user-help@lenya.apache.org
>>>
>>
>>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: Firedocs Editor Problem

Posted by Gaurav Kalia <ga...@techblue.co.uk>.
Hi All

I am getting this error in the Firefox console:

Error: uncaught exception: [Exception... "Component returned failure 
code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIXMLHttpRequest.send]" 
nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame :: 
chrome://firedocs/content/validation/RNGSchemaParser.js :: anonymous :: 
line 121" data: no]


Regards
Gaurav


Gaurav Kalia wrote:
> Hi All
>
> To add further,
>
> I accessed the Firedocs Publication on my system with the URL:
>
> http://localhost:8080/testpro/defaultfiredocs/authoring/test.html
>
> and it simply worked but when I accessed the same publication with the 
> AJP Proxing URL:
>
> http://cms.firedocs.example.com/test.html
>
> then it hangs at "Setting XML Editor".
>
> I think this is because of the AJP Proxing. I am investigating the 
> problem further.
>
> If someone else has encountered the same problem and knows the 
> solution then please suggest.
>
> Regards
> Gaurav
>
>
> Michael Wechner wrote:
>> Vik Tara schrieb:
>>> Thanks Michael - could you give us any pointers on how to debug our 
>>> problem?
>>>   
>>
>> I am not really familiar with Firedocs and I am afraid I cannot 
>> really help, but maybe Thomas can
>>> Are you aware of any sort of debugger or ide?
>>>   
>>
>> maybe Firebug is helpful: 
>> https://addons.mozilla.org/de/firefox/addon/1843
>>
>> and also "ngrep" to debug/monitor the http traffic
>>
>> Also our tips re Yulup should be applicable to Firedocs
>>
>> http://www.yulup.org/developers.html
>>
>> HTH
>>
>> Michael
>>> Regards
>>>
>>>
>>> Vik
>>>
>>> Michael Wechner wrote:
>>>  
>>>> Vik Tara schrieb:
>>>>   
>>>>> Just to add to this, we are trying to debug this problem - does 
>>>>> anyone
>>>>> know where to get the source code for firedocs?
>>>>>         
>>>> I would have assumed somewhere at
>>>>
>>>> http://www.firedocs.org/
>>>>
>>>> Cheers
>>>>
>>>> Michael
>>>>   
>>>>> Gaurav Kalia wrote:
>>>>>  
>>>>>     
>>>>>> Hi All
>>>>>>
>>>>>> I am facing a problem with Firedocs editor on the server.
>>>>>>
>>>>>> The problem is when i try to edit a page on the website which is
>>>>>> deployed on the server with Firedocs editor, it hung up at status
>>>>>> "Setting up XML Editor..." although its working absolutely fine 
>>>>>> on my
>>>>>> local machine with the same publication.
>>>>>>
>>>>>> Please let me know if anything is not clear.
>>>>>>
>>>>>> Regards
>>>>>> Gaurav
>>>>>>
>>>>>> --------------------------------------------------------------------- 
>>>>>>
>>>>>> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
>>>>>> For additional commands, e-mail: user-help@lenya.apache.org
>>>>>>
>>>>>>             
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
>>>>> For additional commands, e-mail: user-help@lenya.apache.org
>>>>>
>>>>>         
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
>>>> For additional commands, e-mail: user-help@lenya.apache.org
>>>>
>>>>     
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
>>> For additional commands, e-mail: user-help@lenya.apache.org
>>>
>>>   
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
>> For additional commands, e-mail: user-help@lenya.apache.org
>>
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: Firedocs Editor Problem

Posted by Gaurav Kalia <ga...@techblue.co.uk>.
Hi All

To add further,

I accessed the Firedocs Publication on my system with the URL:

http://localhost:8080/testpro/defaultfiredocs/authoring/test.html

and it simply worked but when I accessed the same publication with the 
AJP Proxing URL:

http://cms.firedocs.example.com/test.html

then it hangs at "Setting XML Editor".

I think this is because of the AJP Proxing. I am investigating the 
problem further.

If someone else has encountered the same problem and knows the solution 
then please suggest.

Regards
Gaurav


Michael Wechner wrote:
> Vik Tara schrieb:
>> Thanks Michael - could you give us any pointers on how to debug our 
>> problem?
>>   
>
> I am not really familiar with Firedocs and I am afraid I cannot really 
> help, but maybe Thomas can
>> Are you aware of any sort of debugger or ide?
>>   
>
> maybe Firebug is helpful: 
> https://addons.mozilla.org/de/firefox/addon/1843
>
> and also "ngrep" to debug/monitor the http traffic
>
> Also our tips re Yulup should be applicable to Firedocs
>
> http://www.yulup.org/developers.html
>
> HTH
>
> Michael
>> Regards
>>
>>
>> Vik
>>
>> Michael Wechner wrote:
>>  
>>> Vik Tara schrieb:
>>>    
>>>> Just to add to this, we are trying to debug this problem - does anyone
>>>> know where to get the source code for firedocs?
>>>>         
>>> I would have assumed somewhere at
>>>
>>> http://www.firedocs.org/
>>>
>>> Cheers
>>>
>>> Michael
>>>    
>>>> Gaurav Kalia wrote:
>>>>  
>>>>      
>>>>> Hi All
>>>>>
>>>>> I am facing a problem with Firedocs editor on the server.
>>>>>
>>>>> The problem is when i try to edit a page on the website which is
>>>>> deployed on the server with Firedocs editor, it hung up at status
>>>>> "Setting up XML Editor..." although its working absolutely fine on my
>>>>> local machine with the same publication.
>>>>>
>>>>> Please let me know if anything is not clear.
>>>>>
>>>>> Regards
>>>>> Gaurav
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
>>>>> For additional commands, e-mail: user-help@lenya.apache.org
>>>>>
>>>>>             
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
>>>> For additional commands, e-mail: user-help@lenya.apache.org
>>>>
>>>>         
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
>>> For additional commands, e-mail: user-help@lenya.apache.org
>>>
>>>     
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
>> For additional commands, e-mail: user-help@lenya.apache.org
>>
>>   
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: Firedocs Editor Problem

Posted by Michael Wechner <mi...@wyona.com>.
Vik Tara schrieb:
> Thanks Michael - could you give us any pointers on how to debug our problem?
>   

I am not really familiar with Firedocs and I am afraid I cannot really 
help, but maybe Thomas can
> Are you aware of any sort of debugger or ide?
>   

maybe Firebug is helpful: https://addons.mozilla.org/de/firefox/addon/1843

and also "ngrep" to debug/monitor the http traffic

Also our tips re Yulup should be applicable to Firedocs

http://www.yulup.org/developers.html

HTH

Michael
> Regards
>
>
> Vik
>
> Michael Wechner wrote:
>   
>> Vik Tara schrieb:
>>     
>>> Just to add to this, we are trying to debug this problem - does anyone
>>> know where to get the source code for firedocs?
>>>   
>>>       
>> I would have assumed somewhere at
>>
>> http://www.firedocs.org/
>>
>> Cheers
>>
>> Michael
>>     
>>> Gaurav Kalia wrote:
>>>  
>>>       
>>>> Hi All
>>>>
>>>> I am facing a problem with Firedocs editor on the server.
>>>>
>>>> The problem is when i try to edit a page on the website which is
>>>> deployed on the server with Firedocs editor, it hung up at status
>>>> "Setting up XML Editor..." although its working absolutely fine on my
>>>> local machine with the same publication.
>>>>
>>>> Please let me know if anything is not clear.
>>>>
>>>> Regards
>>>> Gaurav
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
>>>> For additional commands, e-mail: user-help@lenya.apache.org
>>>>
>>>>     
>>>>         
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
>>> For additional commands, e-mail: user-help@lenya.apache.org
>>>
>>>   
>>>       
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
>> For additional commands, e-mail: user-help@lenya.apache.org
>>
>>     
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
>
>   


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: Firedocs Editor Problem

Posted by Vik Tara <vi...@propco.co.uk>.
Thanks Michael - could you give us any pointers on how to debug our problem?

Are you aware of any sort of debugger or ide?

Regards


Vik

Michael Wechner wrote:
> Vik Tara schrieb:
>> Just to add to this, we are trying to debug this problem - does anyone
>> know where to get the source code for firedocs?
>>   
>
> I would have assumed somewhere at
>
> http://www.firedocs.org/
>
> Cheers
>
> Michael
>> Gaurav Kalia wrote:
>>  
>>> Hi All
>>>
>>> I am facing a problem with Firedocs editor on the server.
>>>
>>> The problem is when i try to edit a page on the website which is
>>> deployed on the server with Firedocs editor, it hung up at status
>>> "Setting up XML Editor..." although its working absolutely fine on my
>>> local machine with the same publication.
>>>
>>> Please let me know if anything is not clear.
>>>
>>> Regards
>>> Gaurav
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
>>> For additional commands, e-mail: user-help@lenya.apache.org
>>>
>>>     
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
>> For additional commands, e-mail: user-help@lenya.apache.org
>>
>>   
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: Firedocs Editor Problem

Posted by Michael Wechner <mi...@wyona.com>.
Vik Tara schrieb:
> Just to add to this, we are trying to debug this problem - does anyone
> know where to get the source code for firedocs?
>   

I would have assumed somewhere at

http://www.firedocs.org/

Cheers

Michael
> Gaurav Kalia wrote:
>   
>> Hi All
>>
>> I am facing a problem with Firedocs editor on the server.
>>
>> The problem is when i try to edit a page on the website which is
>> deployed on the server with Firedocs editor, it hung up at status
>> "Setting up XML Editor..." although its working absolutely fine on my
>> local machine with the same publication.
>>
>> Please let me know if anything is not clear.
>>
>> Regards
>> Gaurav
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
>> For additional commands, e-mail: user-help@lenya.apache.org
>>
>>     
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
>
>   


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org


Re: Firedocs Editor Problem

Posted by Vik Tara <vi...@propco.co.uk>.
Just to add to this, we are trying to debug this problem - does anyone
know where to get the source code for firedocs?

Gaurav Kalia wrote:
> Hi All
>
> I am facing a problem with Firedocs editor on the server.
>
> The problem is when i try to edit a page on the website which is
> deployed on the server with Firedocs editor, it hung up at status
> "Setting up XML Editor..." although its working absolutely fine on my
> local machine with the same publication.
>
> Please let me know if anything is not clear.
>
> Regards
> Gaurav
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
> For additional commands, e-mail: user-help@lenya.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@lenya.apache.org
For additional commands, e-mail: user-help@lenya.apache.org