OK...just does a test through your site again.....it's 3-4 years since I looked at this, but I think when the readme.txt says.
Apply a blank skin, This must just have a "Content Pane" and the "DNN control panel".
It really does means "BLANK"....with nothing showing apart from a "return to store button"... I think the checkout needs to be there in order to pickup a OK from Authorize.Net. I think that non-css page your seeing is because authorize.Net are blocking all included files....meaning your css file! That second checkout page you've created is just to pickup the return and to display a message so the person buying can click it and return to the store....nothing really need to be displayed there. Have you read through the authorize.Net documentation, it should explain this???
It's basically a workaround so Authorize.Net can work within the DNN framework........it's really not like anyother gateway....they've really made it awkward to use.
Dave.
Apply a blank skin, This must just have a "Content Pane" and the "DNN control panel".
It really does means "BLANK"....with nothing showing apart from a "return to store button"... I think the checkout needs to be there in order to pickup a OK from Authorize.Net. I think that non-css page your seeing is because authorize.Net are blocking all included files....meaning your css file! That second checkout page you've created is just to pickup the return and to display a message so the person buying can click it and return to the store....nothing really need to be displayed there. Have you read through the authorize.Net documentation, it should explain this???
It's basically a workaround so Authorize.Net can work within the DNN framework........it's really not like anyother gateway....they've really made it awkward to use.
Dave.