Tridion Sites 9 and DXA 2.0
Does anybody knows what happens with Tridion Sites 9 and DXA 2.0? I think I have all the configuration files and settings ok, but I am not able to make it work.
Is there any known issues? Any workaround?
dxa dxa-2.0 sites-9
edited Nov 16 '18 at 8:42
Rick Pannekoek
17.6k11125
asked Nov 15 '18 at 7:29
Raúl EscuderoRaúl Escudero
3,3741026
add a comment |
Does anybody knows what happens with Tridion Sites 9 and DXA 2.0? I think I have all the configuration files and settings ok, but I am not able to make it work.
Is there any known issues? Any workaround?
dxa dxa-2.0 sites-9
edited Nov 16 '18 at 8:42
Rick Pannekoek
17.6k11125
asked Nov 15 '18 at 7:29
Raúl EscuderoRaúl Escudero
3,3741026
What is the error you are getting?
– Velmurugan
Nov 15 '18 at 8:53
Someone got it to work: hem-kant.blogspot.com/2018/11/…
– Nuno Linhares♦
Nov 15 '18 at 8:55
The curious thing is that I don't get any error, but home screen is white
– Raúl Escudero
Nov 15 '18 at 9:18
add a comment |
Does anybody knows what happens with Tridion Sites 9 and DXA 2.0? I think I have all the configuration files and settings ok, but I am not able to make it work.
Is there any known issues? Any workaround?
dxa dxa-2.0 sites-9
edited Nov 16 '18 at 8:42
Rick Pannekoek
17.6k11125
asked Nov 15 '18 at 7:29
Raúl EscuderoRaúl Escudero
3,3741026
Does anybody knows what happens with Tridion Sites 9 and DXA 2.0? I think I have all the configuration files and settings ok, but I am not able to make it work.
Is there any known issues? Any workaround?
dxa dxa-2.0 sites-9
dxa dxa-2.0 sites-9
edited Nov 16 '18 at 8:42
Rick Pannekoek
17.6k11125
asked Nov 15 '18 at 7:29
Raúl EscuderoRaúl Escudero
3,3741026
edited Nov 16 '18 at 8:42
Rick Pannekoek
17.6k11125
asked Nov 15 '18 at 7:29
Raúl EscuderoRaúl Escudero
3,3741026
edited Nov 16 '18 at 8:42
Rick Pannekoek
17.6k11125
edited Nov 16 '18 at 8:42
Rick Pannekoek
17.6k11125
edited Nov 16 '18 at 8:42
Rick Pannekoek
17.6k11125
17.6k11125
asked Nov 15 '18 at 7:29
Raúl EscuderoRaúl Escudero
3,3741026
asked Nov 15 '18 at 7:29
Raúl EscuderoRaúl Escudero
3,3741026
asked Nov 15 '18 at 7:29
Raúl EscuderoRaúl Escudero
3,3741026
3,3741026
What is the error you are getting?
– Velmurugan
Nov 15 '18 at 8:53
Someone got it to work: hem-kant.blogspot.com/2018/11/…
– Nuno Linhares♦
Nov 15 '18 at 8:55
The curious thing is that I don't get any error, but home screen is white
– Raúl Escudero
Nov 15 '18 at 9:18
add a comment |
What is the error you are getting?
– Velmurugan
Nov 15 '18 at 8:53
Someone got it to work: hem-kant.blogspot.com/2018/11/…
– Nuno Linhares♦
Nov 15 '18 at 8:55
The curious thing is that I don't get any error, but home screen is white
– Raúl Escudero
Nov 15 '18 at 9:18
What is the error you are getting?
– Velmurugan
Nov 15 '18 at 8:53
What is the error you are getting?
– Velmurugan
Nov 15 '18 at 8:53
Someone got it to work: hem-kant.blogspot.com/2018/11/…
– Nuno Linhares♦
Nov 15 '18 at 8:55
Someone got it to work: hem-kant.blogspot.com/2018/11/…
– Nuno Linhares♦
Nov 15 '18 at 8:55
The curious thing is that I don't get any error, but home screen is white
– Raúl Escudero
Nov 15 '18 at 9:18
The curious thing is that I don't get any error, but home screen is white
– Raúl Escudero
Nov 15 '18 at 9:18
add a comment |
4 Answers
4
active
oldest
votes
DXA 2.1 .Net will support Tridion Sites 9 and is planned to be released in the coming days.
answered Nov 15 '18 at 8:36
Philippe ConilPhilippe Conil
1,936613
1
DXA.NET 2.1 has been released now. Unfortunately, for Java Web Applications, you will have to await DXA 2.2 to benefit from the new features. However, DXA Java 2.0 will run fine on Tridion Sites 9.0 / DXD 11.0.
– Rick Pannekoek
Dec 5 '18 at 18:47
add a comment |
Quick Fix: SWitch off the Custom Resolver (the one that controls the link depth resolving).
It's not formally supported but will be in DXA 2.1 as far as I know.
There is another issue with the context services (explained in the blog post by Hem noted above).
update - per Rick's comment below:
There is more clarity on the reported issue with DXA Resolver UI Extension: it works fine with Sites 9 as long as you don't install it in the WebUI folder. The default location (configured in cms-import.ps1) works fine
answered Nov 15 '18 at 10:48
Dylan .. Mark SaundersDylan .. Mark Saunders
7,3181232
1
The problem with the 9.0 Context Service is that it is more strict regarding URL encoding (because of a Tomcat upgrade) and hence not compatible wirh CIL 10.1. This is fixed in CIL 11.0 (which DXA 2.1 will use).
– Rick Pannekoek
Nov 16 '18 at 8:36
1
In the meantime, you can try to build DXA 2.0 against CIL 11.0 or configureAdfContextClaimsProviderinstead ofContextServiceClaimsProvider(inUnity.config). This effectively disables Context Engine functionality, but at least you Web App will run.
– Rick Pannekoek
Nov 16 '18 at 11:58
As @RickPannekoek mentioned we need to disable the context service dependency to run DXA 2.0 with Tridion Sites 9, that's all I did in order to make DXA 2.0 works with Tridion 9
– Hem Kant
Nov 21 '18 at 11:33
1
There is more clarity on the reported issue with DXA Resolver UI Extension: it works fine with Sites 9 as long as you don't install it in theWebUIfolder. The default location (configured incms-import.ps1) works fine.
– Rick Pannekoek
Nov 22 '18 at 8:25
add a comment |
DXA 2.1 is out, but it's only compatible with Sites 9 (as far as Tridion is concerned). Compatibility overview here
answered Dec 4 '18 at 22:59
Atila SosAtila Sos
3,3372720
2
The main reason for DXA 2.1 release was to leverage/showcase the new features in Tridion Sites 9.0 / DXD 11.0. However, compatibility with SDL Web 8(.5) will be re-introduced in DXA 2.2 (together with Java Web App support).
– Rick Pannekoek
Dec 5 '18 at 18:51
add a comment |
There is an issue with SDL Tridion Sites 9.0 and MS SQL Server which causes an invalid page template being used for pages with page template inherited from parent. This may result in pages returning an internal server error or just missing header and footer.
This issue can be fixed by applying hotfix CM_9.0.0.13336.
answered Feb 22 at 17:57
Jeroen SuurdJeroen Suurd
1,083516
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "485"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftridion.stackexchange.com%2fquestions%2f19495%2ftridion-sites-9-and-dxa-2-0%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
DXA 2.1 .Net will support Tridion Sites 9 and is planned to be released in the coming days.
answered Nov 15 '18 at 8:36
Philippe ConilPhilippe Conil
1,936613
1
DXA.NET 2.1 has been released now. Unfortunately, for Java Web Applications, you will have to await DXA 2.2 to benefit from the new features. However, DXA Java 2.0 will run fine on Tridion Sites 9.0 / DXD 11.0.
– Rick Pannekoek
Dec 5 '18 at 18:47
add a comment |
DXA 2.1 .Net will support Tridion Sites 9 and is planned to be released in the coming days.
answered Nov 15 '18 at 8:36
Philippe ConilPhilippe Conil
1,936613
1
DXA.NET 2.1 has been released now. Unfortunately, for Java Web Applications, you will have to await DXA 2.2 to benefit from the new features. However, DXA Java 2.0 will run fine on Tridion Sites 9.0 / DXD 11.0.
– Rick Pannekoek
Dec 5 '18 at 18:47
add a comment |
DXA 2.1 .Net will support Tridion Sites 9 and is planned to be released in the coming days.
answered Nov 15 '18 at 8:36
Philippe ConilPhilippe Conil
1,936613
DXA 2.1 .Net will support Tridion Sites 9 and is planned to be released in the coming days.
answered Nov 15 '18 at 8:36
Philippe ConilPhilippe Conil
1,936613
answered Nov 15 '18 at 8:36
Philippe ConilPhilippe Conil
1,936613
answered Nov 15 '18 at 8:36
Philippe ConilPhilippe Conil
1,936613
answered Nov 15 '18 at 8:36
Philippe ConilPhilippe Conil
1,936613
1,936613
1
DXA.NET 2.1 has been released now. Unfortunately, for Java Web Applications, you will have to await DXA 2.2 to benefit from the new features. However, DXA Java 2.0 will run fine on Tridion Sites 9.0 / DXD 11.0.
– Rick Pannekoek
Dec 5 '18 at 18:47
add a comment |
1
DXA.NET 2.1 has been released now. Unfortunately, for Java Web Applications, you will have to await DXA 2.2 to benefit from the new features. However, DXA Java 2.0 will run fine on Tridion Sites 9.0 / DXD 11.0.
– Rick Pannekoek
Dec 5 '18 at 18:47
1
1
DXA.NET 2.1 has been released now. Unfortunately, for Java Web Applications, you will have to await DXA 2.2 to benefit from the new features. However, DXA Java 2.0 will run fine on Tridion Sites 9.0 / DXD 11.0.
– Rick Pannekoek
Dec 5 '18 at 18:47
DXA.NET 2.1 has been released now. Unfortunately, for Java Web Applications, you will have to await DXA 2.2 to benefit from the new features. However, DXA Java 2.0 will run fine on Tridion Sites 9.0 / DXD 11.0.
– Rick Pannekoek
Dec 5 '18 at 18:47
add a comment |
Quick Fix: SWitch off the Custom Resolver (the one that controls the link depth resolving).
It's not formally supported but will be in DXA 2.1 as far as I know.
There is another issue with the context services (explained in the blog post by Hem noted above).
update - per Rick's comment below:
There is more clarity on the reported issue with DXA Resolver UI Extension: it works fine with Sites 9 as long as you don't install it in the WebUI folder. The default location (configured in cms-import.ps1) works fine
answered Nov 15 '18 at 10:48
Dylan .. Mark SaundersDylan .. Mark Saunders
7,3181232
1
The problem with the 9.0 Context Service is that it is more strict regarding URL encoding (because of a Tomcat upgrade) and hence not compatible wirh CIL 10.1. This is fixed in CIL 11.0 (which DXA 2.1 will use).
– Rick Pannekoek
Nov 16 '18 at 8:36
1
In the meantime, you can try to build DXA 2.0 against CIL 11.0 or configureAdfContextClaimsProviderinstead ofContextServiceClaimsProvider(inUnity.config). This effectively disables Context Engine functionality, but at least you Web App will run.
– Rick Pannekoek
Nov 16 '18 at 11:58
As @RickPannekoek mentioned we need to disable the context service dependency to run DXA 2.0 with Tridion Sites 9, that's all I did in order to make DXA 2.0 works with Tridion 9
– Hem Kant
Nov 21 '18 at 11:33
1
There is more clarity on the reported issue with DXA Resolver UI Extension: it works fine with Sites 9 as long as you don't install it in theWebUIfolder. The default location (configured incms-import.ps1) works fine.
– Rick Pannekoek
Nov 22 '18 at 8:25
add a comment |
Quick Fix: SWitch off the Custom Resolver (the one that controls the link depth resolving).
It's not formally supported but will be in DXA 2.1 as far as I know.
There is another issue with the context services (explained in the blog post by Hem noted above).
update - per Rick's comment below:
There is more clarity on the reported issue with DXA Resolver UI Extension: it works fine with Sites 9 as long as you don't install it in the WebUI folder. The default location (configured in cms-import.ps1) works fine
answered Nov 15 '18 at 10:48
Dylan .. Mark SaundersDylan .. Mark Saunders
7,3181232
1
The problem with the 9.0 Context Service is that it is more strict regarding URL encoding (because of a Tomcat upgrade) and hence not compatible wirh CIL 10.1. This is fixed in CIL 11.0 (which DXA 2.1 will use).
– Rick Pannekoek
Nov 16 '18 at 8:36
1
In the meantime, you can try to build DXA 2.0 against CIL 11.0 or configureAdfContextClaimsProviderinstead ofContextServiceClaimsProvider(inUnity.config). This effectively disables Context Engine functionality, but at least you Web App will run.
– Rick Pannekoek
Nov 16 '18 at 11:58
As @RickPannekoek mentioned we need to disable the context service dependency to run DXA 2.0 with Tridion Sites 9, that's all I did in order to make DXA 2.0 works with Tridion 9
– Hem Kant
Nov 21 '18 at 11:33
1
There is more clarity on the reported issue with DXA Resolver UI Extension: it works fine with Sites 9 as long as you don't install it in theWebUIfolder. The default location (configured incms-import.ps1) works fine.
– Rick Pannekoek
Nov 22 '18 at 8:25
add a comment |
Quick Fix: SWitch off the Custom Resolver (the one that controls the link depth resolving).
It's not formally supported but will be in DXA 2.1 as far as I know.
There is another issue with the context services (explained in the blog post by Hem noted above).
update - per Rick's comment below:
There is more clarity on the reported issue with DXA Resolver UI Extension: it works fine with Sites 9 as long as you don't install it in the WebUI folder. The default location (configured in cms-import.ps1) works fine
answered Nov 15 '18 at 10:48
Dylan .. Mark SaundersDylan .. Mark Saunders
7,3181232
Quick Fix: SWitch off the Custom Resolver (the one that controls the link depth resolving).
It's not formally supported but will be in DXA 2.1 as far as I know.
There is another issue with the context services (explained in the blog post by Hem noted above).
update - per Rick's comment below:
There is more clarity on the reported issue with DXA Resolver UI Extension: it works fine with Sites 9 as long as you don't install it in the WebUI folder. The default location (configured in cms-import.ps1) works fine
answered Nov 15 '18 at 10:48
Dylan .. Mark SaundersDylan .. Mark Saunders
7,3181232
edited Nov 23 '18 at 8:47
answered Nov 15 '18 at 10:48
Dylan .. Mark SaundersDylan .. Mark Saunders
7,3181232
answered Nov 15 '18 at 10:48
Dylan .. Mark SaundersDylan .. Mark Saunders
7,3181232
answered Nov 15 '18 at 10:48
Dylan .. Mark SaundersDylan .. Mark Saunders
7,3181232
7,3181232
1
The problem with the 9.0 Context Service is that it is more strict regarding URL encoding (because of a Tomcat upgrade) and hence not compatible wirh CIL 10.1. This is fixed in CIL 11.0 (which DXA 2.1 will use).
– Rick Pannekoek
Nov 16 '18 at 8:36
1
In the meantime, you can try to build DXA 2.0 against CIL 11.0 or configureAdfContextClaimsProviderinstead ofContextServiceClaimsProvider(inUnity.config). This effectively disables Context Engine functionality, but at least you Web App will run.
– Rick Pannekoek
Nov 16 '18 at 11:58
As @RickPannekoek mentioned we need to disable the context service dependency to run DXA 2.0 with Tridion Sites 9, that's all I did in order to make DXA 2.0 works with Tridion 9
– Hem Kant
Nov 21 '18 at 11:33
1
There is more clarity on the reported issue with DXA Resolver UI Extension: it works fine with Sites 9 as long as you don't install it in theWebUIfolder. The default location (configured incms-import.ps1) works fine.
– Rick Pannekoek
Nov 22 '18 at 8:25
add a comment |
1
The problem with the 9.0 Context Service is that it is more strict regarding URL encoding (because of a Tomcat upgrade) and hence not compatible wirh CIL 10.1. This is fixed in CIL 11.0 (which DXA 2.1 will use).
– Rick Pannekoek
Nov 16 '18 at 8:36
1
In the meantime, you can try to build DXA 2.0 against CIL 11.0 or configureAdfContextClaimsProviderinstead ofContextServiceClaimsProvider(inUnity.config). This effectively disables Context Engine functionality, but at least you Web App will run.
– Rick Pannekoek
Nov 16 '18 at 11:58
As @RickPannekoek mentioned we need to disable the context service dependency to run DXA 2.0 with Tridion Sites 9, that's all I did in order to make DXA 2.0 works with Tridion 9
– Hem Kant
Nov 21 '18 at 11:33
1
There is more clarity on the reported issue with DXA Resolver UI Extension: it works fine with Sites 9 as long as you don't install it in theWebUIfolder. The default location (configured incms-import.ps1) works fine.
– Rick Pannekoek
Nov 22 '18 at 8:25
1
1
The problem with the 9.0 Context Service is that it is more strict regarding URL encoding (because of a Tomcat upgrade) and hence not compatible wirh CIL 10.1. This is fixed in CIL 11.0 (which DXA 2.1 will use).
– Rick Pannekoek
Nov 16 '18 at 8:36
The problem with the 9.0 Context Service is that it is more strict regarding URL encoding (because of a Tomcat upgrade) and hence not compatible wirh CIL 10.1. This is fixed in CIL 11.0 (which DXA 2.1 will use).
– Rick Pannekoek
Nov 16 '18 at 8:36
1
1
In the meantime, you can try to build DXA 2.0 against CIL 11.0 or configure
AdfContextClaimsProvider instead of ContextServiceClaimsProvider (in Unity.config). This effectively disables Context Engine functionality, but at least you Web App will run.– Rick Pannekoek
Nov 16 '18 at 11:58
In the meantime, you can try to build DXA 2.0 against CIL 11.0 or configure
AdfContextClaimsProvider instead of ContextServiceClaimsProvider (in Unity.config). This effectively disables Context Engine functionality, but at least you Web App will run.– Rick Pannekoek
Nov 16 '18 at 11:58
As @RickPannekoek mentioned we need to disable the context service dependency to run DXA 2.0 with Tridion Sites 9, that's all I did in order to make DXA 2.0 works with Tridion 9
– Hem Kant
Nov 21 '18 at 11:33
As @RickPannekoek mentioned we need to disable the context service dependency to run DXA 2.0 with Tridion Sites 9, that's all I did in order to make DXA 2.0 works with Tridion 9
– Hem Kant
Nov 21 '18 at 11:33
1
1
There is more clarity on the reported issue with DXA Resolver UI Extension: it works fine with Sites 9 as long as you don't install it in the
WebUI folder. The default location (configured in cms-import.ps1) works fine.– Rick Pannekoek
Nov 22 '18 at 8:25
There is more clarity on the reported issue with DXA Resolver UI Extension: it works fine with Sites 9 as long as you don't install it in the
WebUI folder. The default location (configured in cms-import.ps1) works fine.– Rick Pannekoek
Nov 22 '18 at 8:25
add a comment |
DXA 2.1 is out, but it's only compatible with Sites 9 (as far as Tridion is concerned). Compatibility overview here
answered Dec 4 '18 at 22:59
Atila SosAtila Sos
3,3372720
2
The main reason for DXA 2.1 release was to leverage/showcase the new features in Tridion Sites 9.0 / DXD 11.0. However, compatibility with SDL Web 8(.5) will be re-introduced in DXA 2.2 (together with Java Web App support).
– Rick Pannekoek
Dec 5 '18 at 18:51
add a comment |
DXA 2.1 is out, but it's only compatible with Sites 9 (as far as Tridion is concerned). Compatibility overview here
answered Dec 4 '18 at 22:59
Atila SosAtila Sos
3,3372720
2
The main reason for DXA 2.1 release was to leverage/showcase the new features in Tridion Sites 9.0 / DXD 11.0. However, compatibility with SDL Web 8(.5) will be re-introduced in DXA 2.2 (together with Java Web App support).
– Rick Pannekoek
Dec 5 '18 at 18:51
add a comment |
DXA 2.1 is out, but it's only compatible with Sites 9 (as far as Tridion is concerned). Compatibility overview here
answered Dec 4 '18 at 22:59
Atila SosAtila Sos
3,3372720
DXA 2.1 is out, but it's only compatible with Sites 9 (as far as Tridion is concerned). Compatibility overview here
answered Dec 4 '18 at 22:59
Atila SosAtila Sos
3,3372720
answered Dec 4 '18 at 22:59
Atila SosAtila Sos
3,3372720
answered Dec 4 '18 at 22:59
Atila SosAtila Sos
3,3372720
answered Dec 4 '18 at 22:59
Atila SosAtila Sos
3,3372720
3,3372720
2
The main reason for DXA 2.1 release was to leverage/showcase the new features in Tridion Sites 9.0 / DXD 11.0. However, compatibility with SDL Web 8(.5) will be re-introduced in DXA 2.2 (together with Java Web App support).
– Rick Pannekoek
Dec 5 '18 at 18:51
add a comment |
2
The main reason for DXA 2.1 release was to leverage/showcase the new features in Tridion Sites 9.0 / DXD 11.0. However, compatibility with SDL Web 8(.5) will be re-introduced in DXA 2.2 (together with Java Web App support).
– Rick Pannekoek
Dec 5 '18 at 18:51
2
2
The main reason for DXA 2.1 release was to leverage/showcase the new features in Tridion Sites 9.0 / DXD 11.0. However, compatibility with SDL Web 8(.5) will be re-introduced in DXA 2.2 (together with Java Web App support).
– Rick Pannekoek
Dec 5 '18 at 18:51
The main reason for DXA 2.1 release was to leverage/showcase the new features in Tridion Sites 9.0 / DXD 11.0. However, compatibility with SDL Web 8(.5) will be re-introduced in DXA 2.2 (together with Java Web App support).
– Rick Pannekoek
Dec 5 '18 at 18:51
add a comment |
There is an issue with SDL Tridion Sites 9.0 and MS SQL Server which causes an invalid page template being used for pages with page template inherited from parent. This may result in pages returning an internal server error or just missing header and footer.
This issue can be fixed by applying hotfix CM_9.0.0.13336.
answered Feb 22 at 17:57
Jeroen SuurdJeroen Suurd
1,083516
add a comment |
There is an issue with SDL Tridion Sites 9.0 and MS SQL Server which causes an invalid page template being used for pages with page template inherited from parent. This may result in pages returning an internal server error or just missing header and footer.
This issue can be fixed by applying hotfix CM_9.0.0.13336.
answered Feb 22 at 17:57
Jeroen SuurdJeroen Suurd
1,083516
add a comment |
There is an issue with SDL Tridion Sites 9.0 and MS SQL Server which causes an invalid page template being used for pages with page template inherited from parent. This may result in pages returning an internal server error or just missing header and footer.
This issue can be fixed by applying hotfix CM_9.0.0.13336.
answered Feb 22 at 17:57
Jeroen SuurdJeroen Suurd
1,083516
There is an issue with SDL Tridion Sites 9.0 and MS SQL Server which causes an invalid page template being used for pages with page template inherited from parent. This may result in pages returning an internal server error or just missing header and footer.
This issue can be fixed by applying hotfix CM_9.0.0.13336.
answered Feb 22 at 17:57
Jeroen SuurdJeroen Suurd
1,083516
answered Feb 22 at 17:57
Jeroen SuurdJeroen Suurd
1,083516
answered Feb 22 at 17:57
Jeroen SuurdJeroen Suurd
1,083516
answered Feb 22 at 17:57
Jeroen SuurdJeroen Suurd
1,083516
1,083516
add a comment |
add a comment |
Thanks for contributing an answer to Tridion Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftridion.stackexchange.com%2fquestions%2f19495%2ftridion-sites-9-and-dxa-2-0%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What is the error you are getting?
– Velmurugan
Nov 15 '18 at 8:53
Someone got it to work: hem-kant.blogspot.com/2018/11/…
– Nuno Linhares♦
Nov 15 '18 at 8:55
The curious thing is that I don't get any error, but home screen is white
– Raúl Escudero
Nov 15 '18 at 9:18