Wrong (emty) items in testimonial slider

Hi Tim,

Please post us your login credentials (in the “private data” field), so we can take a look at your backend.

1. Install and activate ” Temporary Login Without Password “.
2. Go to ” Users > Temporary Logins ” on the left-side menu.
3. Click ” Create New “.
4. Add the email address for the account ( you can use (Email address hidden if logged out) ), as well as the ” Role ” making that the highest possible and the expiry about four days
   ( to be sure that we have enough time to debug ).
5. Click ” Submit “.
6. You’ll now have a temporary account. Please provide us here in the private section the URL, so we can login and help you out.

When your issue is fixed, you can always remove the plugin!
If you prefer to not use the plugin, you can manually create an admin user and post the login credentials in the “private data” field.

Best regards,
Nikko

Hi Tim,

I have checked it again and it seems the cache has already expired and now fetching the correct css and js files. (screenshot in private content)
Also, I would disagree that the theme doesn’t work properly with Chrome since it’s obviously a caching issue and not the theme.
As for using two browsers, it’s just a temporary workaround because of the weird interaction caused by caching.

Best regards,
Nikko

Hi Tim,

If I did not try investigate the issue then just tell you it’s caching from the beginning of our discussion then I would have really blamed caching without pointing to any evidence (I gave you screenshots of the content of style.css when logged in and not, I posted it again in private content).
If this is not a caching issue, then why is the style.css from the child theme which was not fetching when you’re logged in the other day, now working properly?
If it’s something we can control by changing the code of the theme then that would have already added that to the theme however this is not the case for caching.
If something goes wrong we try to help our users to figure out the cause of the issue so the problem can be addressed, if we find out it’s a bug in the theme we report it to our devs and try to give a workaround to our users if we can, if the cause is the plugin we tell it to our users and try to atleast give some evidence why we believe it’s the plugin, in this case it’s caching and I did try the possible solutions that can be done in the backend which unfortunately is not working but then after a single day the styles are being fetched. Since some hosting provider have built-in caching in their servers then that might be something that you can check on with your hosting provider.
Caching is great for performance but it gives a lot of headache when enabled during development and some of it still caches even if the plugin is deactivated.

Best regards,
Nikko

Hi Tim,

I have added this code in your functions.php file:

function enfold_child_enqueue_parent_style() {
    $version = '1.0.3';

	wp_dequeue_style( 'avia-style' );
	wp_deregister_script( 'avia-style' );
    wp_enqueue_style( 'child-style', get_stylesheet_directory_uri() . '/style.css', array(), $version );
}
add_action( 'wp_enqueue_scripts', 'enfold_child_enqueue_parent_style', 20 );

If you make changes to your child theme’s style.css just increment version number with 1.
Let us know if this helps.

Best regards,
Nikko

Hi Tim,

I did test it out on your site by changing this code in style.css of the child theme to 18px (turned it back after checking) then just change the version number from 1.0.1 to 1.0.2 to 1.0.3 (increment by one after each change) and it worked properly:

#tel {
    font-size: 17px !important;
}

You can also use Quick CSS for it since the change does show unlike style.css
As for layout.css I believe that’s in the parent theme, since it caches styles and js files, to force it to fetch new ones, you need to increment the version number before checking for example it’s now 4.8.2, you can change it to 4.8.2.1 then you’ll see these changes show up properly.

Best regards,
Nikko

Hi Tim,

No, not the file name, only the version number in style.css.
If you notice WordPress adds the version number after the file (link in private content).
You can inspect your site to verify this.
If you make changes to any css or js files, in some sites/servers this is automatically cached for a certain period.
But if you change the version number, let’s say to 4.8.2.1 then a new style URL is fetched (basically the same just different version but you’ll notice the difference in the content) the 4.8.2 version number will hold the old css values while 4.8.2.1 will be forced to generate a new cached css file.

Best regards,
Nikko

Hi Tim,

I could see the it taking effect properly on my end (please see screenshot).
Also I have updated the code I added in functions.php with this one:

function enfold_child_enqueue_parent_style() {
	$child_theme = wp_get_theme( 'enfold-child' );

	wp_dequeue_style( 'avia-style' );
	wp_deregister_script( 'avia-style' );
	wp_enqueue_style( 'child-style', get_stylesheet_directory_uri() . '/style.css', array(), $child_theme->get( 'Version' ) );
}
add_action( 'wp_enqueue_scripts', 'enfold_child_enqueue_parent_style', 20 );

Best regards,
Nikko

Hi Tim,

We’re glad to hear that :)
Thanks for using Enfold and have a great day!

Best regards,
Nikko