nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

6.7.2 SP1:Page are no editable

shivgaytri

Hi,

We have recently migrated to 6.7.2 SP1 from 6.7.2.

I tried to migrate one branch(site) from 6.7.2 SP1 to 6.7.2 for roll-back testing using open deploy.Sitemap is preserved but i am unable to edit .pages.

Getting this error:

"An error occurred while getting the page. Contact your system administrator for details."

As per my understanding components version are different in both environment,that's why I tried to update .page using "Get Latest component" under Livesite tab..but again I am getting this error:

Status: Completed with errors

Can anybody help me to resolve this issue or suggest any alternate.

Thanks
Shiv

Find more posts tagged with

Comments

vpatel

Look at your servletd log and see if there are any errors in there.

shivgaytri

Look at your servletd log and see if there are any errors in there.

Thanks for the reply
I checked the log file....JAVA errors are there.
But I want to know about the root cause of the issue..any idea abt that?

vpatel

What sort of Java errors are you getting? Without looking at logs who knows what is the root cause.....

ccprofessional

Were the pages originally in TS 6.7.2 or an earlier version?

Like I said in other posts, the .page, .component and .template format have changed in 672 sp1

shivgaytri

What sort of Java errors are you getting? Without looking at logs who knows what is the root cause.....

The system has encountered an internal error.
com.interwoven.livesite.runtime.rendering.RenderingException: Unhandled Exception at com.interwoven.livesite.runtime.rendering.RenderingManager.handleException(RenderingManager.java:656) at com.interwoven.livesite.runtime.rendering.RenderingManager.render(RenderingManager.java:164) at com.interwoven.livesite.runtime.impl.BaseRequestContext.render(BaseRequestContext.java:190) at com.interwoven.livesite.iw.servlet.preview.PreviewFilter.doFilter(PreviewFilter.java:126) at org.springframework.web.filter.DelegatingFilterProxy.invokeDelegate(DelegatingFilterProxy.java:183) at org.springframework.web.filter.DelegatingFilterProxy.doFilter(DelegatingFilterProxy.java:138) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:869) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:664) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:80) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:684) at java.lang.Thread.run(Thread.java:595) Caused by: java.lang.RuntimeException: Unable to access page (CS): //Servername/default/main/xyz/www-abc-com/WORKAREA/Content/sites/www-abc-com/a/b/index.page at com.interwoven.livesite.iw.servlet.preview.PageBuilder.getPage(PageBuilder.java:135) at com.interwoven.livesite.iw.servlet.preview.PageBuilder.getPreviewPage(PageBuilder.java:90) at com.interwoven.livesite.iw.servlet.preview.PreviewDataMapping.setPage(PreviewDataMapping.java:172) at com.interwoven.livesite.iw.servlet.preview.rendering.PreviewRenderingManager.doSetupPage(PreviewRenderingManager.java:120) at com.interwoven.livesite.runtime.rendering.RenderingManager.doSetupRenderingObjects(RenderingManager.java:316) at com.interwoven.livesite.runtime.rendering.RenderingManager.renderPageGoal(RenderingManager.java:207) at com.interwoven.livesite.runtime.rendering.RenderingManager.render(RenderingManager.java:148) ... 18 more Caused by: java.lang.NullPointerException at com.interwoven.livesite.runtime.model.page.RuntimeComponent.parse(RuntimeComponent.java:355) at com.interwoven.livesite.runtime.model.page.RuntimeComponent.(RuntimeComponent.java:114) at com.interwoven.livesite.model.page.RuntimePageConverter.convertXMLToPage(RuntimePageConverter.java:108) at com.interwoven.livesite.model.page.PageConverter.convertXMLToPreviewPage(PageConverter.java:85) at com.interwoven.livesite.iw.servlet.preview.PageBuilder.getPage(PageBuilder.java:131)

shivgaytri

Were the pages originally in TS 6.7.2 or an earlier version?

Like I said in other posts, the .page, .component and .template format have changed in 672 sp1

Actually pages were in TS 6.7.1 and migrated to TS 6.7.2 SP1.and now I am trying to test roll-back activity and migrating to TS 6.7.1 from TS 6.7.2 SP1.

Here goes my question: As .page, .component and .template format have been changed in 672 sp1 , is Interwoven providing any work-around to make it backward compatible?

ccprofessional

If you are migrating from 671, here's a workaround.

Apply 6.7.2 base on 6.7.1 sp1. (or if it is a fresh install of 672, copy the backing store to the 672 base instance).

Then open/edit save/close all your components & templates. This will change their format to the new one. Then ofcourse, update all your .page files. It may give you invalid/non existent site error - but lemme know if you face this.

This has to be done before you upgrade to 672sp1.

Apply sp1 on 672 then follow the same process above.

That should fix it.

If you have already applied SP1, then I hope you have a backup of your backing store. Roll back (actually reinstall) to TS 6.7.2 then copy over the 671 sp1 backing store.

Let us know how it goes.

As far as I know Interwoven is unaware of this issue.

Adam Stoller

Actually pages were in TS 6.7.1 and migrated to TS 6.7.2 SP1.and now I am trying to test roll-back activity and migrating to TS 6.7.1 from TS 6.7.2 SP1.

Here goes my question: As .page, .component and .template format have been changed in 672 sp1 , is Interwoven providing any work-around to make it backward compatible?

I do not know the answer for sure - this is the kind of question you should run through Support - but I would guess the answer is no that Interwoven does not provide for backwards compatibility of .page / component files.

ccprofessional

While I did not/ do not have time to work with Support on this issue, I believe Interwoven should provide a clean solution(instead of my hack) for upgrading .pages from TS 6.7.1 sp1 to TS 6.7.2 sp1.

The way I envision the fix to work is in the page update process - where it checks for the version (which is coded in the .page /.component xml) and does the proper munging.

I think Interwoven QA missed this one big time.

Considering everyone in IW upper management making a big deal about TS 6.7.2 SP1, they better provide a fix.

I just dont have time to deal with Support

vpatel

... I believe Interwoven should provide a clean solution(instead of my hack) for upgrading .pages from TS 6.7.1 sp1 to TS 6.7.2 sp1. ...

I believe there is a "migration" script that exists that'll allow you to convert pages from SP 3.0 (TS 6.7.1) to SP 3.1 (TS 6.7.2) version. I am not sure if it is documented anywhere or not. Definitely contact support and check about this.

Adam Stoller

While I did not/ do not have time to work with Support on this issue, I believe Interwoven should provide a clean solution(instead of my hack) for upgrading .pages from TS 6.7.1 sp1 to TS 6.7.2 sp1.

The way I envision the fix to work is in the page update process - where it checks for the version (which is coded in the .page /.component xml) and does the proper munging.

I think Interwoven QA missed this one big time.

Considering everyone in IW upper management making a big deal about TS 6.7.2 SP1, they better provide a fix.

I just dont have time to deal with Support

The question was not about migration forward to a newer release (though admitedly that's a good question) - the question was about rolling back to an older product version - which I am pretty sure that IWOV does not support and is not something they are likely to spend any time on providing a solution for (unless a very big customer gets involved - and even then...)

sajiddc

I have come across a similar issue in the past. Can you open a support case?

While I did not/ do not have time to work with Support on this issue, I believe Interwoven should provide a clean solution(instead of my hack) for upgrading .pages from TS 6.7.1 sp1 to TS 6.7.2 sp1.

The way I envision the fix to work is in the page update process - where it checks for the version (which is coded in the .page /.component xml) and does the proper munging.

I think Interwoven QA missed this one big time.

Considering everyone in IW upper management making a big deal about TS 6.7.2 SP1, they better provide a fix.

I just dont have time to deal with Support