You can't get rid of the Step 1 page(it populates the customer table); however you can change the image on Step 1 to say something besides Ship, You Can also edit the "Shipping Information" on the invoice to say something else, like Customer Information:

You can change "ship" to something like "customer info"

If you look under App_LocalResources in the Smith.BuyNow folder, you will see Step1.ascx.resx, Invoice.ascx.resx, ConfirmStatus.ascx.resx, and Confirm.ascx.resx all of which you can change "Shipping Information" to something else, like Customer Information.

Regarding the skin issue, this is actually a bug/limitation in dnn when you redirect to another user control (ascx) dnn applies the admin skin instead of the portal skin.

http://www.dotnetnuke.com/Community/F...

This is a technique we have been working on but it’s kind of a big change and will require a lot of testing before its release and we are hoping that dnn will fix the bug so we dont have to implement this workaround.

http://www.r2integrated.com/dnn/Forum...

Long story short you will need to set your portal and admin skin to the same skin temporarily if you want the same skin on the cart and checkout. We are hoping that dnn will fix the bug soon.

Christian

Hi again Christian --

The more I think about this, the more I think it may be a big problem. I have no clue why DNN decides to expose the admin skin to non-admin users, and FORCE that skin on a page. It really is kind of crazy. However, in our case we were going to have multiple points of checkout with your product. One of them will be embedded on the standard page, so having us just make the admin skin the same as our web skin is something we can live with.

However, we were going to have an alternative storefront that was access in a mini-skin, kind of like just having a popup window when someone pressed a button to purchase something, then quickly let them purchase an electronic download which they would then view in this popup window. The page skin for this "popup window" have to be completely different (almost empty). But basically because of this design its going to revert to the main site's skin.

I'm assuming you are considering doing something along the lines of getting rid of using DNN's ctl= functionality to show each step as a seperate module and move to a more standard panel display? Is there an ETA on this? we are a month or so away from launch, so I can wait if this is something on the table.

Thanks,

jasen