Apache OpenOffice (AOO) Bugzilla – Issue 101885
Adding server fails when Mediawiki installed in Root Folder
Last modified: 2013-03-05 02:38:36 UTC
This issue is similar to Issues 88649 and 88624, but neither of these Issues are current...So this bug is for Wiki Publisher 1.0 and Openoffice 3.1. Very much like the Issues mentioned above, the adding of a new server in Wiki Publisher fails due to the URL not being recognized. My mediawiki install is internal for people in my team to share info. I have it installed on a dedicated server and have installed it into the root of the web server (i.e. not in a /wiki or /w sub folder) and using a subdomain. So my URL simply looks like this: http://wiki.example.com/Main_Page - Is this extension hard coded to see only the /wiki or /w subfolders? - Why does it fail adding a server when the URL is pointing to the root folder directly instead of the alias/redirect of a default install. - Is this extension still being developed? - Does it matter that I am using openoffice-bin and not compiling from source? - How do I get debug information from Writer so I can see the actual error message? Bottom line, how do I get this to work in Oo3.1? Thanks,
mav->odr4ver: Please try the development version of the extension attached to issue 96279 ( wiki-publisher.oxt ). This is no official version, but it will allow to check whether your problem is already fixed in the development version. The new version of the extension ( including the changes from the mentioned development version ) will be released soon.
No the new version does not work. It is still looking only for installations in the /wiki with redirect to /w. This simply does not make this extension usable to those who have custom setups. Is there a particular version of jre I should be using? Are there any source compiling instructions that I could have a try at fixing it myself?
The extension does not have path /w or /wiki hardcoded. The path is retrieved from the links that are used in the server, till now it has been working with all other wikis that have been tested. If you would like to investigate it yourself please find the sources in swext project of the office. I would suggest to do the investigations on the version not later than DEV300_m47. As for the jre, the requirements are just the same as for the office. Also please take a look to the following article http://www.mediawiki.org/wiki/Manual:Wiki_in_site_root_directory As it is mentioned there: "Any scheme which does this [installation in the root of web server] is not supported by the MediaWiki developers." Now I have a question, if MediaWiki developers do not support it, what are the reasons for us to do it?
I'll answer your question with one or two of my own ... Question 1: If having mediawiki installed in the root is unsupported, then why make it an option? If I run mediawiki on a dedicated server, it just seems silly to put it in a sub-folder when nothing is using the root. Question 2: Why won't you support it? Let's not start throwing attitudes around ... all I want is to be able to use this extension and I just don't see why adding a server fails when the url I point it too is perfectly valid. Also I found this discussion in the same mediawiki manual you found the "unsupported" message in: http://www.mediawiki.org/wiki/Manual:Wiki_in_site_root_directory#Questions The above discussion obviously proves I am not the only one that feels having mediawiki on a dedicated server or subdomain (as is mine) and installing it into a /wiki sub folder is stupid and redundant. So again ... Can this extension be written so that it accepts an installation no matter how the admin chooses to structure the folders on the server?
Sorry, but you did not really answered my question. As for your questions, the first one has nothing to do with OpenOffice, please ask it on mediawiki forums. As for the second one, supporting of any feature needs resources. If developers of the MediaWiki say that they do not support installation in the root of web server, I see no reason to invest time in supporting this scenario. If somebody would decide to implement a patch for this, and this patch would not break extension functionality, I also see no reason to deny the integration.
I guess you could have simply say "I don't want too" or "I don't know how"!! But ... In the spirit of research and development...I moved my wiki into a /wiki sub-folder and configured it as per the default instructions. I have to leave the URL as a sub-domain, because in the office I do not have dns admin control. Guess what? It still does not work. If you can find me a quote from Mediawiki stating that they do not support sub-domains, then this issue will be over. Else I ask that you please look into this a bit more and see if there is something you can do. I know this extension is free, but come on! Re-cap: My mediawiki v1.14 is installed in a sub-folder /wiki and assigned a dedicated IP with sub-domain: ex. http://wiki.example.com/wiki/Main_Page
mav->oldr4ver: Your last comment sounds either like misunderstanding of my words, or explicit try to be impolite. This my comment is only based on the idea that it is the first case, the second one needs no comments I assume. Supporting of any feature needs resources. Supporting a feature in alien product makes no sense, if the product itself has deprecated the feature with decision not to support it any more. This is the case here with the root folder installation. From other side, if another developer decides to invest his time in it, I see no reason to prevent integration of his work if it does not break the supported scenarios. As I have already mentioned, all the known wiki-installations look to work well with the last version of the extension. If the extension does not work even with a wiki installed in supported way in your case, it should mean that there is a specialty in the installation itself or in the environment that let it behave differently. Based on mentioned above we need more information regarding your installation to investigate the problem. The best way would be if you would allow to access it per Internet.
Unfortunately. You would not be able to access this site from the internet. This is an internal wiki used by my support engineers. The only difference in the way the installation looks now is that the domain has a sub-domain. The sub-folder and alias settings are back to default...So my Main_Page url looks similar to this now: http://supportwiki.example.com/wiki/index.php?title=Main_Page This is the Long URI configuration. What else can I post here to help identify why this is not working correctly?
mav->oldr4ver: Could you please attach the html sources of the MainPage as they are got from the browser ( View/Page Source ).
Attached file Main_Page.txt ... All private URL information removed but the rest of the syntax is as it is on the web.
Created attachment 62616 [details] Main_Page source code from my wiki