# Resource Bundle changes not reflected on webpage

**URL:** <https://community.bloomreach.com/t/resource-bundle-changes-not-reflected-on-webpage/1583>\
**Category:** Experience Manager (PaaS/OnPrem)\
**Created:** [November 19, 2019, 1:31pm UTC](https://community.bloomreach.com/t/resource-bundle-changes-not-reflected-on-webpage/1583 "2019-11-19T13:31:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![gprice](https://avatars.discourse-cdn.com/v4/letter/g/278dde/32.png) [@gprice](https://community.bloomreach.com/u/gprice)\
**Post date:** [November 19, 2019, 1:31pm UTC](https://community.bloomreach.com/t/resource-bundle-changes-not-reflected-on-webpage/1583/1 "2019-11-19T13:31:31Z")

</div>

- I have a page which gets all its content via a resource bundle.
- Published **changes** are not reflected when browsing the associated webpage
- **Unpublishing** the content still shows an **old version** of the content when I would expect to see no content
- Our CDN is not cacheing the page

Any ideas how I can resolve this?

Hippo Version 11

---

<div class="post-metadata">

**Author:** ![jasper.floor](https://yyz1.discourse-cdn.com/flex027/user_avatar/community.bloomreach.com/jasper.floor/32/28_2.png) [@jasper.floor](https://community.bloomreach.com/u/jasper.floor)\
**Post date:** [November 19, 2019, 2:56pm UTC](https://community.bloomreach.com/t/resource-bundle-changes-not-reflected-on-webpage/1583/2 "2019-11-19T14:56:09Z")

</div>

Does this also happen in a private session (ie, is it the browser cache)

You could try adding “?a” to the URL. This can be used to bust some caches. If that works then at least you are sure that caching is the problem.

Are you using any other caches outside your CDN or the Bloomreach native ones?

Increase the log level on “org.hippoecm.hst.resourcebundle.internal.ResourceBundleRegistryImpl”. It probably logs nothing right now. This should log unregistering your resource bundle on publish/unpublish. If this isn’t happening then there is something wrong. Perhaps the event listener didn’t register. Check for any errors on startup.