Forum Replies Created
-
Posts
-
This seems to be a very persistent problem!
I’ve just updated a site with a new, licensed and authenticated version of Enfold (4.8.1)
I’ve cleared all the caches, reset the permalinks, and cleared all the transients in the database.The result for pagination is still “https://[site-name]/blog/?avia-element-paging=2” (The real URL is in the private content area)
Like others I’ve applied the various patches recommended — changing lines in wp-content > themes > enfold > framework > php > function-set-avia-frontend.php or even outright replacing the contents of the file with code from pastebin.To be honest I really don’t care and I’m not positive Google does either. But it’s driving my client’s SEO people crazy.
To be clear, the URL for pagination should be “https://[site-name]/blog/2” not “https://[site-name]/blog/?avia-element-paging=2”
I was able to persuade the client to just let me revert them to Helvetica. That took care of the FOUT.
I’ll reopen the issue if they ask me to re-instate the TypeKit fonts that were loading late.
Update:
Here’s the code I use in the child theme’s functions.php to load the TypeScript fonts// Add TypeKit fonts to top of HTML head function realbasics_add_typekit(){ ?> <script src="https://use.typekit.net/kul0okt.js"></script> <script>try{Typekit.load({ async: true });}catch(e){}</script> <?php } add_filter( 'wp_enqueue_scripts', 'realbasics_add_typekit', 0 );Sure. I’ve added the links in the private section.
But basically on the News page each archive item is listed in Title / Excerpt / Meta, and on single pages it’s Title / Full Text / Meta.
In both instances the client wants it to be title, then meta, then content.
Update: I fixed problem #1. A condition in the spec called for a border between 2/3 and 1/3 columns on most pages, with padding and other buffering. Enfold has lots of great CSS classes, but no obvious way to add our own classes to anything.
The hack I chose was too general, with the result that when I had only three columns in the footer the classes hooked them too. Adding #footer in front of .el_before_av_one_third.flex_column, and .el_after_av_one_third.flex_column seems to have done the trick.
Still no explanation for problem #2 in my original request, and I’m not sure how CSS would cause unattached widgets to display. But at least they’re no longer displaying on screen.
Thanks, Ismael.
So is it safe to modify the theme files directly or will they be overwritten with the next update? I’m assuming not, which is why I was asking about making the changes in the child theme.
What are the the best steps for importing just that script to the child theme then? Do I need to enqueue the new one, dequeue the old one? Will just copying it to the same folder tree do the trick the way copying php templates will?
Thanks!
