New Parent Portal

Hi

i have just added a new parent portal to my dnn 4.8.2 install and am having a few problems

under the admin menu on new portal there is no pageblaster link, the link is working on three old parent portals, is there a sql script that i have to run to display on new portal

when i try to add new page i get error WebForm_PostBackOptions is undefined, i checked on dotnetnuke forums and a few posts there think relates to compression. (i still get this when i exclude pageblaster from the web.config)

have you seen this error before??

Hi Martin,

You can fix that by running the install SQL again.

I have attached it to this post.

I thought it would add the item to new portals, but I guess I need to look closer at that.

The webForm_post back problem is pretty common and can have many different reasons.

If it isn't PageBlaster (which isn't very common now that it has matured) then I would suspect the core compression module, or maybe IIS settings that isn't mapping .axd files to ASP.Net

yeah that seams to have added the pageblaster link to the menu of the new portal

i have checked the web.config and the dotnetnuke < !--compression -- > sections have been excluded, does this not mean that it should be using pageblaster compression and not the dotnetnuke compression

is there any test i can do to see if there is a mapping problem with IIS settings for .axd files to ASP.Net (hosting websecurestores, i will create a support request if not)

one thing that did suprise me was i enabled pageblaster within web.config file cleared the cache browsed a few pages then cleared the cache (both times from the pageblaster module)

Configuration saved successfully. 4 Files removed totalling 317 MB.

can i ask what files would be in the cache that would be that large??

To test .axd you can look in the page source and try putting the Url to the WebResource.axd file directly in the browser.  If it comes back with a page can't be found then it probably isn't mapped.

You can also use YSlow which is a FirFiox plugin to do analysis on the components of your page and see if that component is returning a 404.

The 317 MB is actually 317 KB.  It was displaying 0 MB so I changed it to calc KB, but forgot to add the decimal point in front. .317 MB is what it should read.

That will be fixed in the next release.

Thanks

all sorted now, i checked the WebResource.axd for the source and the file was empty (not 404) double checked with yslow.

i rolled back to a backup of my dnn install, updated a few modules, and all looks good