Importation issues

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Importation issues

Marine Julian
Hi !

I discovered two bugs (?) of importation function (from the top menu "Create page from office document") :

The first problem is that importation by splitting the document doesn't work in 2.3 version... I tried to split by heading of level 1. It said to me that the importation succeeds and showed me the link to the new page (said Rapports.parent) but when I accessed it I had the "The page doesn't exist"... Later, I realized that my document was imported in the Main.WebHome page !! Weird ! In fact, the importation succeeded but not where I wanted and asked for ! In fact, I had the equivalent of "Rapports.parent" in the Main.WebHome i.e. the content and the links to Rapports.child pages. Unfortunately, the links had the [?] of "page not existing". Indeed, they links to "Rapports.children" pages which don't exist : the child pages were also imported behind the parent page (itself behind the content of Main.WebHome)...

The second issue (I don't know if it's a real one) : I created a word (.doc) document in which I imported an image (with Word 2007 interface). Then, when I imported the doc in the wiki, the image wasn't imported... Then, I tried by copying the image in the word document (and not importing it) and the wiki importation worked ! Can you reproduce this behavior ? It seems to be a little strange.

Thank you in advance for your answers.
(And please, if you know about exportation, can you look and my last posts : warn/error messages and bad behaviour of table exportation ? Thanks !)
Reply | Threaded
Open this post in threaded view
|

Re: Importation issues

Marine Julian
Marine Julian wrote
The first problem is that importation by splitting the document doesn't work in 2.3 version... I tried to split by heading of level 1. It said to me that the importation succeeds and showed me the link to the new page (said Rapports.parent) but when I accessed it I had the "The page doesn't exist"... Later, I realized that my document was imported in the Main.WebHome page !! Weird ! In fact, the importation succeeded but not where I wanted and asked for ! In fact, I had the equivalent of "Rapports.parent" in the Main.WebHome i.e. the content and the links to Rapports.child pages. Unfortunately, the links had the [?] of "page not existing". Indeed, they links to "Rapports.children" pages which don't exist : the child pages were also imported behind the parent page (itself behind the content of Main.WebHome)...
Does it need to be reported on jira ? I don't know in which case we must do it and if we are allowed to do it (perhaps only devs can report a bug...).

Please note that, in wiki farm, from a subwiki, the document is not imported in its Main.WebHome page but in the Main.WebHome page of the admin wiki (Main wiki)...
Reply | Threaded
Open this post in threaded view
|

Re: Importation issues

Thomas Mortagne
Administrator
On Mon, May 31, 2010 at 10:01, Marine Julian <[hidden email]> wrote:

>
>
> Marine Julian wrote:
>>
>> The first problem is that importation by splitting the document doesn't
>> work in 2.3 version... I tried to split by heading of level 1. It said to
>> me that the importation succeeds and showed me the link to the new page
>> (said Rapports.parent) but when I accessed it I had the "The page doesn't
>> exist"... Later, I realized that my document was imported in the
>> Main.WebHome page !! Weird ! In fact, the importation succeeded but not
>> where I wanted and asked for ! In fact, I had the equivalent of
>> "Rapports.parent" in the Main.WebHome i.e. the content and the links to
>> Rapports.child pages. Unfortunately, the links had the [?] of "page not
>> existing". Indeed, they links to "Rapports.children" pages which don't
>> exist : the child pages were also imported behind the parent page (itself
>> behind the content of Main.WebHome)...
>>
> Does it need to be reported on jira ? I don't know in which case we must do
> it and if we are allowed to do it (perhaps only devs can report a bug...).

Sure you have the right to do it ;)

When anyone find what is a bug for sure (I did not followed the issue
closely here so i don't know) he should always report it on jira (if
it's not already there obviously).

>
> Please note that, in wiki farm, from a subwiki, the document is not imported
> in its Main.WebHome page but in the Main.WebHome page of the admin wiki
> (Main wiki)...
> --
> View this message in context: http://xwiki.475771.n2.nabble.com/Importation-issues-tp5107820p5120875.html
> Sent from the XWiki- Users mailing list archive at Nabble.com.
> _______________________________________________
> users mailing list
> [hidden email]
> http://lists.xwiki.org/mailman/listinfo/users
>



--
Thomas Mortagne
_______________________________________________
users mailing list
[hidden email]
http://lists.xwiki.org/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: Importation issues

Marine Julian
tmortagne wrote
> Does it need to be reported on jira ? I don't know in which case we must do
> it and if we are allowed to do it (perhaps only devs can report a bug...).

Sure you have the right to do it ;)

When anyone find what is a bug for sure (I did not followed the issue
closely here so i don't know) he should always report it on jira (if
it's not already there obviously).
I didn't find jira report which deals with this issue so I created a new one : http://jira.xwiki.org/jira/browse/XAOFFICE-48. I hope that I created it well...

For the second issue I noticed, I think it's better if someone can try to reproduce this behavior. I'm not sure that is really a bug and I don't know where the problem comes.
Marine wrote
The second issue (I don't know if it's a real one) : I created a word (.doc) document in which I imported an image (with Word 2007 interface). Then, when I imported the doc in the wiki, the image wasn't imported... Then, I tried by copying the image in the word document (and not importing it) and the wiki importation worked ! Can you reproduce this behavior ? It seems to be a little strange.