• Resolved Roman Cieciuch

    (@romancieciuch)


    Hello there!

    I wanted to ask – how can I force Hummingbird to generate new name for compiled CSS or JS files?

    As I am making updates in my theme stylesheet and increase version number (in my case: to 273):

    wp_register_style(“theme-css”, “/wp-content/themes/base/style.css”, false, “273”);
    wp_enqueue_style(“theme-css”);

    Then, I Clear Cache in Hummingbird, and the file name stays the same, like: b383b50e4665139ef83a0b642db7747a.css

    Which is a pain in my neck, because my users don’t see my changes.
    I have set CSS expiration header for 1 year, and as long as the file name doesn’t change – the browser wouldn’t download the new content.

    Please help or show me the way 🙂

Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Support Dimitris – WPMU DEV Support

    (@wpmudev-support6)

    Hello @romancieciuch

    Just to be clear on this, did you clear Page Caching or Asset Optimization Cache?
    Can you please to clear both if not already?
    Let me know if that makes any difference.

    Thank you,
    Dimitris

    Thread Starter Roman Cieciuch

    (@romancieciuch)

    Hi Dimitris!

    Actually I had been clearing both.

    Although, in the Hummingbird Dashboard there’s a button and its tooltip says: “This will clear your Page, Gravatar & Asset Optimization caches”.

    As I have mentioned in the first place – the cached name stays the same.

    The ideal solution for this would be – when I press Clear Cache button in the Hummingbird dashboard – it generates the new name.

    Plugin Support Pawel – WPMU DEV Support

    (@wpmudev-support9)

    Hello @romancieciuch,

    I trust you’re doing well!

    Indeed, when a cache is cleared, the cached file name is not changed. I’m afraid this is how the Hummingbird works out of the box.

    The file hash will change only if the theme/plugin will update their assets. So far I see the $ver argument is updated in your code, I’ve forwarded this to our developers for further feedback.

    Once there will be an update, we will follow back in this thread.

    Have a good day and take care!

    Kind regards,
    Nastia

    Thread Starter Roman Cieciuch

    (@romancieciuch)

    That will be awesome, thank you!

    So far, I have come up a different route – I change this name (XXX), and then Hummingbird generates the new hash filename, eg.

    wp_register_style(“theme-cssXXX”, “/wp-content/themes/base/style.css”, false, “273”);
    wp_enqueue_style(“theme-cssXXX”);

    Thread Starter Roman Cieciuch

    (@romancieciuch)

    When can we expect the update?

    Plugin Support Pawel – WPMU DEV Support

    (@wpmudev-support9)

    Hello @romancieciuch

    I trust all is well!

    The fix is currently being tested by our QA team. Once the next version will pass all the required testing it will be released.

    We really appreciate your patience!

    Kind regards,
    Nastia

    Plugin Author Anton Vanyukov

    (@vanyukov)

    @romancieciuch,

    This will be released with Hummingbird 2.5.0. Version 2.4.0 is already tested and ready for release, so it’s not possible to add it there. I can provide a list of changes so you can adjust by editing a few files.

    Best regards,
    Anton

    Thread Starter Roman Cieciuch

    (@romancieciuch)

    Ok, nice, thank you! Waiting impatiently 🙂

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘New styles – old file name’ is closed to new replies.