I have a critical page skin error on my search results page which forced me to delete it. This search results page being the one set-up by default when creating a portal. After deleting it and creating a new page i have found that the DNN search control no longer points to my new page. When I submit a search it jest refreshes the page I am currently on....

But.. if I use the Search Imput Module, then there is no problem....

Was there something particular about that default page DNN portals have?

Anyone else had this problem??

Thanks in advance

Mark Hollas

Hello Mark,

I had the same problem, and I've posted it in the forum. Here you can find how I've solved the problem:

http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/108/threadid/179541/scope/posts/Default.aspx

I don't know if it was the correct way, but it worked for me!

I have created an hidden page, "Search results", which is my new search results page. I have put in it a "Search results" module.

In Enterprise manager I ran this query:

SELECT dbo.vw_Modules.* 
FROM dbo.vw_Modules INNER JOIN dbo.ModuleDefinitions as MD ON dbo.vw_Modules.ModuleDefID = MD.ModuleDefID 
WHERE PortalId = 0 AND MD.FriendlyName = 'Search Results' AND IsDeleted = 0

where PortalId is your PortalId.

The query returned two rows:

• the first row had a ModuleId, but TabId NULL, TabModuleId NULL, PaneName NULL... It was about a module which didn't exist on the portal. And the search didn't worked because it pointed to this non-existent module.
• the second row was about the search results module I've put in my search results page.

In "Modules" table I've deleted the row in which ModuleId was the same that the ModuleId of the first record returned by my query, and now search works .

I'm not sure this is the proper method, before I tried I done a backup.