Issue 76454 - [stage] Project Content Editor does'nt show for svn backed project
Summary: [stage] Project Content Editor does'nt show for svn backed project
Status: CLOSED FIXED
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Website general issues (show other issues)
Version: current
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: Unknown
QA Contact: issues@www
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2007-04-17 17:04 UTC by Unknown
Modified: 2012-03-01 21:54 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description Unknown 2007-04-17 17:04:24 UTC
The project content editor is not showing up for svn backed project . Initial
findings point to the fact that might be the rewrite rule present in the
openoffice site is overriding the Project Content Editor link.

[project].openoffice.org/ => [project].openoffice.org/index.html
(i.e. use www/index.html instead of www/DomainHome.html.html as the project home
page).
Comment 1 Unknown 2007-04-17 17:05:39 UTC
Updating whiteboard.
Comment 2 stx123 2007-04-17 19:54:26 UTC
Hm, that explanation does not help to understand why the editor doesn't work for
http://svn.stage.openoffice.org/test.html
Comment 3 Unknown 2007-04-18 14:17:22 UTC
Stefan , 

The engineers has confirmed it's due to rewrite rule . The conculsion is that
the links to the DomainHome servlet page are not shown due to the rewrite rule.

Also has there been any recent discussions about getting rid of that rewrite 
rule for oo.o ??? If done it would slightly change the look of all the project
though..

Your comments.
Comment 4 stx123 2007-04-18 20:23:52 UTC
The change of the look of the project home page is what led to the introduction
of the rewrite rule. We would like to stick with the homepage without the
elements CEE generates.
Is there a public site which shows what a project (home) page with editor
capabilites enabled would look like?
Comment 5 Unknown 2007-04-19 07:00:25 UTC
https://openofficetesting.sclatest.inst.collab.net/

I have added you as Project Owner. This is a public project hence should be
accessible for everyone let me know if you would like to add some users into the
project.
Comment 6 stx123 2007-04-20 13:40:56 UTC
I investigated this a bit more. One can create new pages / subpages / ... in 
http://svn-projecteditor.stage.openoffice.org/ (no redicet rule)
or
http://svnprojecteditornodash.stage.openoffice.org/servlets/ProjectProcess?tab=1
(redirect rule)
That all works fine (neglecting the rendering of the home page for projects with
redirect) for new created projects and for the project svn.
http://svn.stage.openoffice.org/servlets/PageEditor?editTabs=true
(I thought I saw some error messages, but can't reproduce the problem).

The question that is still open for me is more related to a SVN migration.
Is there a way to integrate existing (home) pages in the system, so that the
content editor can be used to modify them?

Comment 7 Unknown 2007-04-20 14:15:33 UTC
Stefan , 
   After the SVN migration is completed for the project's . The content editor
would be appear on the home page of all svn backed projects. I think the content
editor is tied specifically to a project and not in a global manner which might
conflict with the single SVN repository structure as proposed by Openoffice.



Comment 8 Unknown 2007-04-23 06:28:15 UTC
We have received feedback from the engineers stating that Open office proposed
layout still has the individual projects and www areas for each module . Stefan
you should be able to customized project web page with PCE. However we have
concerns with possibilities of Open office losing the redirect rule that
effectively bypasses PCE.
Comment 9 Unknown 2007-04-23 11:06:14 UTC
Closing this issue as Stefan was successful in testing with the Project Content
Editor for svn backed project in the stage box .

Stefan , please reopen this issue if you think otherwise.
Comment 10 ace_dent 2008-05-17 21:41:29 UTC
The Issue you raised has been marked as 'Resolved' and not updated within the
last 1 year+. I am therefore setting this issue to 'Verified' as the first step
towards Closing it. If you feel this is incorrect, please re-open the issue and
add any comments.

Many thanks,
Andrew
 
Cleaning-up and Closing old Issues
~ The Grand Bug Squash, pre v3 ~
http://marketing.openoffice.org/3.0/announcementbeta.html
Comment 11 ace_dent 2008-05-17 23:45:57 UTC
As per previous posting: Verified -> Closed.
A Closed Issue is a Happy Issue (TM).

Regards,
Andrew