-
Bug
-
Resolution: Fixed
-
Medium
-
8.0.0, 8.2.0, 8.5.0, 8.0.3, 8.1.1, 8.4.1, 8.5.1, 8.5.4
-
6
-
Severity 2 - Major
-
87
-
Issue Summary
Using the page link in the 'Change History' macro leads to a 'Page Not Found' error.
The URL displayed in the Change History macro:
| Confluence Version | URL from Change History macro | Working? |
|---|---|---|
| Confluence 8.0.0 | /display/<spacekey>/viewpage.action?pageId=<pageID> |  |
| Confluence 7.19.6 | /display/<spacekey>/viewpage.action?pageId=<pageID> |  |
The URL displayed in the Page History list (
> Page History:
| Confluence Version | URL from Change History macro | Working? |
|---|---|---|
| Confluence 8.0.0 | /pages/viewpage.action?pageId=<pageID> | |
| Confluence 7.19.6 | /pages/viewpage.action?pageId=<pageID> | |
This is reproducible on Data Center: yes
Steps to Reproduce
- Create a page
- Make changes to the page and save multiple times.
- Add change history macro to the page.
- When we access the page we could see multiple versions of the page in the 'Change History' macro's list.
- When trying to navigate to a previous version of the page by clicking one of the links in the list, we get a 'Page Not Found' error.
Expected Results
When any page version is chosen, it should take us to the relevant version.
Actual Results
We get to see the 'Page Not Found' error and the below error is logged in the atlassian-confluence.log:
2023-03-23 16:14:58,946 WARN [http-nio-6813-exec-5] [apache.struts2.dispatcher.Dispatcher] logConfigurationException Could not find action or result: /c813/display/SX/viewpage.action?pageId=98380 -- url: /c813/display/SX/viewpage.action | userName: admin | referer: http://localhost:6813/c813/display/SX/Change+History+macro+test | traceId: 412bf3d3e8e9a26e There is no Action mapped for namespace [/display/SX] and action name [viewpage] associated with context path [/c813]. - [unknown location] at com.opensymphony.xwork2.DefaultActionProxy.prepare(DefaultActionProxy.java:195) at org.apache.struts2.factory.StrutsActionProxy.prepare(StrutsActionProxy.java:57) at org.apache.struts2.factory.StrutsActionProxyFactory.createActionProxy(StrutsActionProxyFactory.java:32) at com.opensymphony.xwork2.DefaultActionProxyFactory.createActionProxy(DefaultActionProxyFactory.java:60) at com.atlassian.confluence.impl.struts.ConfluenceStrutsDispatcher.serviceAction(ConfluenceStrutsDispatcher.java:97) at org.apache.struts2.dispatcher.ExecuteOperations.executeAction(ExecuteOperations.java:79) at org.apache.struts2.dispatcher.filter.StrutsExecuteFilter.doFilter(StrutsExecuteFilter.java:77) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:189) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:162) at com.atlassian.plugin.servlet.filter.IteratingFilterChain.doFilter(IteratingFilterChain.java:39) at com.atlassian.plugin.servlet.filter.DelegatingPluginFilter.lambda$doFilter$0(DelegatingPluginFilter.java:57) at com.atlassian.confluence.plugins.baseurl.IncludeResourcesFilter.doFilter(IncludeResourcesFilter.java:52) [...]
Workaround
- Go to the page and choose
> Page History - Choose a version number to view the content of that version.
- was cloned as
-
-
- Closed
-
- mentioned in
-
Page Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[CONFSERVER-82535] Unable to view previous version of the page using 'change history' macro due to removed URL action mapping
We are affected with same bug. Looking forward, that the bug is handled according Atlassian Bug Policy https://confluence.atlassian.com/support/atlassian-bug-fixing-policy-201294573.html
why is the status still in gathering impact?
The support has onfirmed the problem and now also several customers.
This should be "Ready for development". It is not so complicated to reproduce 
Hello,
I can confirm this on our prod & test system on 8.1.1.
In my opinion the summary should be changed to "Unable to restore view a page to its previous version using 'change history' macro".
That you can not restore a page is a secondary effect, because the button is on "appearing".
Fix would be really nice. This is a awful bug regarding user experience.
Kind regards,
for us the priority is not low.
you have broken a much-used function (like many others in the past).
When does the quality control pull and when are such bugs fixed?
I look forward to the day when we have found a reasonable alternative.
Then you can break as much as you want
One week over and still in triage?
It is a bug that is confirmed by support.
This must be solved better for the customer.
With new functions ok, but if old are broken?
Please correct this quickly, colleagues need the macro
this is a really stupid mistake and my colleagues are mad at me that it doesn't work anymore.
The problem is that for the macro "<Base_URL>/pages" is no longer used, but the page URL (including section) and the history is simply appended there.
Example:
The link in the macro is: https://svr-wiki/display/TST/viewpage.action?pageId=514380329
And from pagehistory: https://svr-wiki/pages/viewpage.action?pageId=514380329
Base-URL: https://svr-wiki/
Inside the macro the url is: viewpage.action?pageId=514380329
So the only problem is when you create the complete URL!
A fix for this issue is available in Confluence Server and Data Center 8.5.6.
Upgrade now or check out the Release Notes to see what other issues are resolved.