Hello Jaakkosaarenketo,
Thanks for the report.
Can you be more specific? What style is rewrited? Also, are you using the latest 0.8.2 Update? I use both and don’t have any problem.
Regards!
For example the rules with !important broke some form stylings:
.select2-container .select2-selection–single .select2-selection__rendered{
line-height: 31px !important;
}
.select2-container .select2-selection–single .select2-selection__arrow, .select2-container .select2-selection–single {
height: 32px !important;
}
In acf-extended.css?ver=0.8.2
If the front-end features were opt-in. There would be less problems since then usually some visual tests are done.
But with this update, ACF Extended brought new stylesheets in the front end when there was no reason to do so.
Thanks for answering.
Hello,
I see. The select2 custom CSS has been added in the 0.5.8 version. I understand that you don’t necessarily want it in the front-end. I’ll move it in the admin custom CSS, and not load it in the front-end (using ACF Form, ACFE Form or Advanced Forms).
Regards.
Hello jaakkosaarenketo,
Just to let you know that the latest ACF Extended 0.8.3 Update this issue. Select2 CSS enhancements are now only enqueued in the admin and will not interfere with the front-end anymore.
Thanks again for the report. Have a nice day!
Regards.