• Resolved baddon250

    (@baddon250)


    Here are the steps I do to reproduce the conflict.

    I’ve already gone through all the plugin conflict and narrowed it down to w3totalcache.
    I’ve deactivated features until I found that the browser cache is causing the problem.

    When a user is logged in,
    they visit their profile,
    click on profile settings,
    and change their profile photo.

    The profile photo does not change on the front end.

    But if I deactivate the browser cache, It changes to the one that was just uploaded.

    I’ve already selected don’t cache when logged in but it continues to cache.

    I feel like I’ve exhausted all options and I’m turning to caching gurus for some help.

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • Plugin Contributor Marko Vasiljevic

    (@vmarko)

    Hello @baddon250

    I am sorry about the issue you are experiencing and I am happy to assist you with this.
    Can you please go to Performance>Browser Cache and disable the settings one by one in the General sub-box so we can determine which setting is causing the issue.
    Once you determine what option is causing this, for example, “expires header”, re-enable it and disable it in the sub-boxes for HTM&XML, JS&CSS, and media other files.
    Let us know which option is causing this and leave it unchecked to avoid this in the future.
    Thanks!

Viewing 1 replies (of 1 total)
  • The topic ‘Ultimate Member caching conflict.’ is closed to new replies.