Thanks!!! p.s. how can I remove the standard TF bar from the top? I’ve reviewed the theme now and asked the reviewer to remove the standard bar. He said ok, but the standard bar is still there.
<script>if ( top !== self ) top.location.replace( self.location.href );</script>
I assume you are talking about the latest WordPres page builder plugin?
If so, that plugin was removed from the wp.org repository upon publishing on CodeCanyon, so everything is as it should be, no rules are broken.
Why don’t you just pull an array of available fonts and store it locally, and then you can update the list with each theme update.
That way you don’t have to worry about external requests or api keys.
Neither am I but it still happened to me
Happened here once, make sure you have actually selected the files you uploaded in appropriate places (theme only zip, zip for end users etc.).
lol yeah your son obviously
How long does the battery last on the glasses, and how do you recharge them, usb cable?
Awesome, how satisfied are you with them?
freeace00 said1.) You don’t have to minify them all in one file, though it would be nice if you would offer an option for your users to load a single minifed file (+ style.css, so 2 css files) or all files separate.
we have css files like this.
common.css header.css single-pages.css post-pages.css footer.css
We mostly work like this for organize. it is easy to see and modify.
Question, do we have to combine them to 1 file (style.css)? is it better or any rules for it in themeforest?
We want to import these files. it will be good for clients to see. like this.. on style.css
@import url(‘assets/css/header.css’); @import url(‘assets/css/my-page.css’); @import url(‘assets/css/custom-bootstrap.css’); @import url(‘assets/css/grid-list.css’);
Is this a proper way to do? Is this going to be a problem?Please give me an advice. Thank you,
2.) You should not (and you are not allowed) to use @import, always use wp_enqueue_style.