Developer forum

Forum » CMS - Standard features » Not able to use Page Templates in 8.9.1.7

Not able to use Page Templates in 8.9.1.7

Simon Eldevig
Reply

Hello everyone!

We just upgraded a solution to 8.9.1.7 for solving a problem with copying Item Relation List in 8.8.x.x which has been resolved, but now a differnt problem occurs.

We would like to use Page Templates for easy content creating, but when creating a contet page as a Page Template we are no longer able to create new pages.

No matter we try to create a page as blank or from template we get a System.NullReferenceException - https://www.screencast.com/t/lO2eJT7iyCQQ

If we delete all Page Templates we are able to create blank pages ones again.


Does anybody have a solution for solving this problem? :-)

Copy of the error:

Server Error in '/' Application.


Object reference not set to an instance of an object.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 

Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.
Source Error: 

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace: 

[NullReferenceException: Object reference not set to an instance of an object.]
   Dynamicweb.Admin.PageTypeSelect.SetPageState(Page p, Boolean isItemBased) +33
   Dynamicweb.Admin.PageTypeSelect.Page_Load(Object sender, EventArgs e) +1767
   System.Web.UI.Control.OnLoad(EventArgs e) +95
   System.Web.UI.Control.LoadRecursive() +59
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +678

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.6.1586.0


Replies

 
Nicolai Pedersen
Reply
This post has been marked as an answer

Hi Simon

I've asked the service desk to contact you for figuring this out and see if this is a bug.

BR Nicolai

Votes for this answer: 1
 
Simon Eldevig
Reply

Hi Nicolai,

I've already been in contact with your support who didn't seem to have a solution ready right away.

The case ID is: CAS-01693-G4H5W5

 
Simon Eldevig
Reply

Hi again Nicolai,

Together with your support team we managed to find a solution.

For future reference I would just like to mention that the problem was due to a higher SQL version (2016) in our test enviroment than on live (2012).

This proberly resulted in some half done housekeeping, and we also found out that the SQL user can't be owner and dlladmin during the update, since this will result in the same problem :-)

 

You must be logged in to post in the forum