I have a web site kluge.biz set up with CMS made simple. When we initially set up the web site we made a "literature download protection" form, the user was prompted to fill out this form when they clicked to view product literature. We have since stopped using this. However, I would now like to begin using the form again to restrict access to our videos, so when the user clicks to see the video library they are prompted with the form.
The form uses a user defined tag with the coding and then a regular page with the form fields.
Heres the problem: It seems to work correctly as far as prompting the user to fill in the form when they try to access the video-library page. The problem is though, that when you fill in the form, it reverts back to the form again to fill it out and doesnt transfer the user to the video library page.
After looking into this and comparing it with the original code, it seems as though there is some code missing on the form page:
When i add this code back in in the html editor and press update, it doesnt save the change and removes it automatically. I have tried several times and in firefox, ie and chrome without any luck.
Why wont it accept this change?? what could a work around be. I'm sure that this will fix the problem if i can get it to accept the change
Any help would be appreciated, Thanks
problem with html editor
Re: problem with html editor
Tiny will eat that kind of code, 2 ways to do it...
1) Put it in a GCB with tiny turned off so it don't eat it and then you can go to the page add the GCB call to it and when editing the page it won't break the code...
2) In tiny admin set it to not start on page edit then you can add the code and submit and it will not get broken, but you can't edit the page in wysiwyg mode or it will break the code...
1) Put it in a GCB with tiny turned off so it don't eat it and then you can go to the page add the GCB call to it and when editing the page it won't break the code...
2) In tiny admin set it to not start on page edit then you can add the code and submit and it will not get broken, but you can't edit the page in wysiwyg mode or it will break the code...
Re: problem with html editor
Thanks the second option seems to be the one that would work best for me. However, i pretty illiterate when it comes to backend work. I did take a quick look and tried a couple of things for removing the start with page edit function, but it did not seem to change anything. would you mind giving me step by step instructions to do this?
thanks
thanks
Re: problem with html editor
So you went to Extensions » TinyMCE WYSIWYG and didn't find Startup enabled: in any of the tabs?...
Even doing this is only going to work if nobody goes to that page to edit, or does and leaves tiny off, as soon as it gets turned back on it will eat code, try to clean it up...
Even doing this is only going to work if nobody goes to that page to edit, or does and leaves tiny off, as soon as it gets turned back on it will eat code, try to clean it up...
Re: problem with html editor
mmm... could it be "Force clean on paste: This should be enabled to remove strange formatting codes when pasting from Word etc."
Ok so if i configure the setting to be html only while i edit that page. can i switch the wysiwyg setting back on to edit other pages? Its only that page that needs to be left alone while Tiny MCE wysiwyg is turned on correct?
Ok so if i configure the setting to be html only while i edit that page. can i switch the wysiwyg setting back on to edit other pages? Its only that page that needs to be left alone while Tiny MCE wysiwyg is turned on correct?
Re: problem with html editor
Did you see the little tick box under tiny, look around play with everything, is best way to learn, not many here are going to want to hold your hand the whole time...
Re: problem with html editor
I understand. The cms has been customized by my programmer so maybe that was excluded? "Did you see the little tick box under tiny" what screen should it be on?
Re: problem with html editor
anything that has tiny in it, if you hack/change any core files you may not be supported...