Is there a way to remove the code below?
<style>.G3-body ... </style>
<script>
/*
* # Fomantic UI - 2.8.6
Removing the CSS would make the form not so nice looking, and removing the script would break some core features like dropdowns and checkboxes and fields validations...etc
Why do you need to remove that ?
Why do you need to remove that ?
Hi Max,
I want to use custom html and custom validations.
My form worked on CF5. But I can't move to CF7.
Regards
Masatoshi
I want to use custom html and custom validations.
My form worked on CF5. But I can't move to CF7.
Regards
Masatoshi
Custom HTML and custom validations ? then why do you even need to use ChronoForms ? you can add your code to the page directly!
Hi Max,
I have a dark background on my website ( www.microstudioweb.com/download/dark.png ) and the chronoform style set text to black on black.
Ho can I delete/remove color rule form chornoform and use template color for text?
Thx
I have a dark background on my website ( www.microstudioweb.com/download/dark.png ) and the chronoform style set text to black on black.
Ho can I delete/remove color rule form chornoform and use template color for text?
Thx
Hi Simone,
You can use Custom CSS to override the default ChronoForms settings and change the text Color to white.
Bob
You can use Custom CSS to override the default ChronoForms settings and change the text Color to white.
Bob
That can be quit a lot of work.
I edited the corefile
/plugins/system/chronog3_plg/chronog3/helpers/semantic.php
line 127 change
return $css_content;
to
if (\GApp3::instance()->site == 'admin') {
return $css_content;
}
the css in the admin stays intact that way.
Keep in mind this will probably be overruled while updating chronoforms in future releases.
This should be an on/off button in the backend per form to be honest. It once was. Why it was removed i still don't understand.
I edited the corefile
/plugins/system/chronog3_plg/chronog3/helpers/semantic.php
line 127 change
return $css_content;
to
if (\GApp3::instance()->site == 'admin') {
return $css_content;
}
the css in the admin stays intact that way.
Keep in mind this will probably be overruled while updating chronoforms in future releases.
This should be an on/off button in the backend per form to be honest. It once was. Why it was removed i still don't understand.
You need to login to be able to post a reply.
