Splash Editor

How can I stop the html editor from stripping out my code? I need to put some nav tags in there so my new splash page will work but the bloody thing keeps stripping out my code, is there anyway to stop this its starting to drive me mad

You really should clarify your question because you say you are using the HTML editor. TinyMCE IS the HTML editor.  Is that what you are attempting using as a CODE editor?  It's not clear what you are doing.

I need to put this code into my splash page

      <nav class="slides-navigation">     

      <a class="prev" href="#"><div class="back" style="float:left; margin-left:0px;"></div></a>

      <a class="next" href="#"><div class="forward" style="float:right; margin-right:0px;"></div></a>

      </nav>

but by the time the html editor has finshed only this bit of the code is left

<div class="back" style="float: left; margin-left: 0px;"></div>

which is just mad.

houstonlively its the html editor on on the splash page. you know the thing in basic settings that lets you put your splash code into it

i made this

http://shoomblitz.com/shoom/splash/welcome.html#1

and i managed to transfere it onto the splash page so when logged out people arrive at that page. Everything works, the touch drag screen, the only thing I can't get to work is my little navigation buttons back / next which the splash editor thingie seems to think I don't want :|

I NEED the buttons to navigate to the next page because not everyone has a touch screen right?

You should know this by now but the HTML Editor will strip out code.  You turn off the HTML editor to enter code and you need to save a copy in a text file because if you open it back up and the HTML editor loads, it will clean up the code and remove stuff.

well how do i turn it off?

I got rid of mine altogether by editing /administration/basic_setting.php like this:

        'params' => array(),
        'inputs' => array(
/*            'editor' => array(
                'type' => 'checkbox',
                'name' => 'editor',
                'caption' => _t('_adm_txt_settings_splash_editor'),
                'info' => _t('_adm_dsc_settings_splash_editor'),
                'value' =>  'on',
                'checked' => $bEditor,
                'attrs' => array(
                    'onchange' => 'javascript:splashEnableEditor(this)'
                )
            ),
*/
            'code' => array(
                'type' => 'textarea',
                'name' => 'code',
                'caption' => '',
                'value' => getParam('splash_code'),
//                'html' => $bEditor ? 2 : 0,
                'colspan' => 2,
                'tr_attrs' => array(
                    'id' => 'adm-bs-splash-editor-wrp'
                ),

Boonex put TinyMCE where it had no business being, because a bunch of whiney little weenies couldn't be bothered to learn rudimentary html... thus we all have to suffer. 

ok i got it. it kinda works. well its not stripping the code out anymore. I am situating my code inbetween the popup tag from boonex.

<div id="dolPopupFog" style="position: fixed; top: 0px; left: 0px; width: 100%; height: 100%; z-index: 999;"> 

STUCK MY CODE HERE

</div>

and it covers my screen nicely without showing the site underneath, except when i flip the pages then it flashes the site underneath, I think because its trying to be a pop up. So instead of trying to use that popup tag, how to I make my slide pages cover the entire screen? This is proberly basic html but I just can't do it. when I take out the fogpopup i end up with the splash stuck in a small square.

Have you considered using a Fancybox modal? I believe it might behave a little better for what you want to accomplish.

actally i stuck a background into the fog attribute, the same one i am using for my pages and it worked, it covers up the poping effect. now my pages swish just nicely. Just need to sort out the size of the wrappers cause they all out of sink when I put the code in. its weird how it looks one way when your making it then totally different when you plonk it into dolphin

Because it has to play with the Dolphin stuff; lots of javascript/jquery codes will conflict with each other.