Charles,

Thanks very much for that - it looks to have solved both problems. I was able to perform the backup that failed yesterday and the "Info" tab is working on the pages that were giving trouble before.

I'd say it is safe to close this issue now.

Thanks again for your help.

Regards,

pj.

Try putting the attached OutgoingLink.class file in WEB-INF/classes/com/atlassian/confluence/links and restarting the server.

Hi Charles/Jens,

I was doing some more investigation on this problem and have uncovered another piece of information that may be useful. I thought that an export of all of my data to XML and a re-import would be useful to determine whether the db was giving me any trouble. When I tried to backup I got the following error:

"2005-03-07 09:31:11,066 ERROR [confluence.importexport.impl.BackupExporter] Couldn't backup database data.
org.springframework.orm.hibernate.HibernateSystemException: Exception occurred inside setter of com.atlassian.confluence.links.OutgoingLink.de
stinationPageTitle; nested exception is net.sf.hibernate.PropertyAccessException: Exception occurred inside setter of com.atlassian.confluence
.links.OutgoingLink.destinationPageTitle
"

Notice the mention of destinationPageTitle - on my previous problem I was also getting messages relating to the destinationPageTitle:

"Throwable:
net.sf.hibernate.PropertyAccessException: Exception occurred inside setter of com.atlassian.confluence.links.OutgoingLink.destinationPageTitle
"

Do you think these errors are related - is there some kind of integrity checker I could run on the data to validate the page titles or destination page titles?

Regards,

pj.

Hi Charles / Jens,

I upgraded to 1.4DR4a this morning and tried to view the page again - same problem it looks like. Attached is a textfile with the error message/stack trace.

If you need any more info just let me know.

Regards,

pj.

PJ,

We weren't able to reproduce your error locally. However, the code that was causing this error was significantly rewritten in DR4 - there's a good chance we've already fixed the problem without knowing. Any chance you could try the latest Confluence DR?

Hi Jens,

I have attached the error as a .txt file so it should be readable. The page that is giving trouble is titled:

"Using JIRA for Project Issue Tracking"

Regards,

pj.

PJ,

The Confluence-error.pdf you attached to this issue is invalid. Can you please add the stack trace in text format to this issue or just post it.

I imported your space and I had no problem choosing the More... tab for any the pages which were imported. What page is causing the exception on you side?

No worries about the children macro. It works as it is supposed to. The link "Changes to JIRA to facilitate bug-tracking" is displayed as a page id because it contains special characters which might cause problems in the url.

Hope the stack trace can give us a better idea of what is going on.

cheers,
Jens

Jens,

Exported page attached as JIRA-143-20050202-14_45_37.zip

Regards,

pj.

Hi Jens,

I spoke too soon - we are getting the problem again today with a new page we have added. I cannot see the pageId you refer to in your post above. Actually it is a bit weird - here is the situation:

We have a Home page which contains the

tag, we have three child pages but one of them shows up as a hyperlink with a pageId and the other shows up as a hyperlink with the page title.

I have exported the page to XML so you can take a look for yourself.

The really weird bit is that I have added some pages to the same workspace today and can view them no problem - and the "More" option also. It might be something around the way the page gets created - either the "Add Page" option or the "Add Child Page" option. When adding using "Add Child Page" it does not make it a child of the workspace.

We will keep digging here to see if we can get a more reproducible scenario for you.

Regards,

pj.

Hi Jens,

I have been trying to re-produce this for you since we got the problem and now it does not happen at all. We did a restart of the application on the day we had the trouble (after we logged the issue) and it has been fine since.

It feels like a problem that you can close off for the moment - if I get it again I will export the page as you suggest and add a comment to this issue.

Regards,

pj.