Response Time
24 — 48 hours
Just a suggestion for you guys to make life a little bit easier for some of us building custom stuff. 
The adoption of Twitter Boostrap 3 is really welcomed BUT you should use the original boostrap classes for your templates layout. Without the original boostrap classes it's a nightmare
A quick example i found in the code, we have "btn-es-success" instead of "btn-success" (the default/original bootstrap class)
This is not "bootstrap 3" but more like a "custom stackideas modified bootstrap 3"
If we are already running a fully compatible Bootstrap 3 Joomla template, we already did all the styling needed for all the bootstrap elements and all original bootstrap classes, EasySocial templates should blend into this smoothly and great IF you are using the core bootstrap classes and provide an option to turn off the "easysocial bootstrap customization" in order to make use of the joomla template's bootstrap.
The irony is that i am running a bootstrap 3 custom template, i am runing a bootsrap 3 EasySocial template ..... BUT i still got display errors caused by css conflicts. Isn't that funny ?
You should have used the core bootstrap classes, core grid system, core "everything".
That's what i thought when you guys announced Bootstrap 3 for ES 1.2.
I was like, man, my life will be saved with inclusion of Bootstrap 3 in ES 1.2 - no more conflicts and everything will look blended-in.
Just my 2 cents on this ! Bootstrap 3 should be used more wisely (or any framework for that matter).
The adoption of Twitter Boostrap 3 is really welcomed BUT you should use the original boostrap classes for your templates layout. Without the original boostrap classes it's a nightmare
A quick example i found in the code, we have "btn-es-success" instead of "btn-success" (the default/original bootstrap class)
This is not "bootstrap 3" but more like a "custom stackideas modified bootstrap 3"
If we are already running a fully compatible Bootstrap 3 Joomla template, we already did all the styling needed for all the bootstrap elements and all original bootstrap classes, EasySocial templates should blend into this smoothly and great IF you are using the core bootstrap classes and provide an option to turn off the "easysocial bootstrap customization" in order to make use of the joomla template's bootstrap.
The irony is that i am running a bootstrap 3 custom template, i am runing a bootsrap 3 EasySocial template ..... BUT i still got display errors caused by css conflicts. Isn't that funny ?
You should have used the core bootstrap classes, core grid system, core "everything".
That's what i thought when you guys announced Bootstrap 3 for ES 1.2.
I was like, man, my life will be saved with inclusion of Bootstrap 3 in ES 1.2 - no more conflicts and everything will look blended-in.
Just my 2 cents on this ! Bootstrap 3 should be used more wisely (or any framework for that matter).
8 Replies
The replies under this section are restricted to logged in users or users with an active subscription with us
