Hi,

1. You should try and upgrade DNN to 4.9.2 - I don't recall any changes in the framework that could affect any 3rd party modules. - DONT FORGET TO BACKUP, though.

2. Relative paths will be allowed in teh next version. I would give it about a month or so - we are just about ready to start a release process.

3. Host account has more privileges than Admin, so you really don't need to re-sign as Admin - you can continue doing things as Host

4. There is nothing wrong with doing it the way you did. In fact, it's a very cool workaround! Whether you are linking to your aspx page via url or as a file, the result is exactly the same - a url.

As far as security is concerned, IFrame displays linked files or pages without any checks regardless of how you are displaying things. 

 While I can't take a responsibility here, I will suggest the following path that I would take in a situation like yours:

1. Backup files and DB

2. Backup files and DB

3. Back.. OK - everyone got my point :)

4. Upgrade the platform to DNN 4.9+

5. Test the site

6. Copy all customized skin objects back to the newly upgraded site from the backup copy

7. Test the site

None of your database tables or any other objects should be affected by the upgrade - unless you've MODIFIED any of the core tables - which you should NEVER do if you want to be able to upgrade.

SkinObjects should work ok when you copy them back. Suggestion, though - it is a MUCH better idea to make your own copy of the SkinObject you wish to modifiy, give it a distinct name and use it then - ths way it will not get in the way of an upgrade process.