Changes in Hippo release not fully showing on PROD

Experience Manager (PaaS/OnPrem)
1

A couple of days ago we installed a new version of hippo on our production environment.

In this hippo release we added some custom changes (changes in html, new Document types).
We installed this release first on QA. I can see all the changes there.

After that we installed the release also on PROD.
When I look in PROD, I can’t find my changes on the site/cms.
When I look in the server I can see the class files for the new DocumentTypes.
We have also a meta tag “<meta name=“version” content=3…” which shows the version number of hippo. This tag shows the correct version

We restarted Hippo again to see if that would help. Which didn’t.
We copied production database to QA, to see if QA will have the same problem like PROD. But QA still showed the correct changed.

At this moment we are trying to install the same release again on PROD

Does anybody have other ideas how to solve this problem?

Thanks in advance.

Greetings,
Hikmet

2

Hi,

might it be that on production you start up with bootstrapping set to false, see [1]?

Regards Ard

[1] https://documentation.bloomreach.com/library/concepts/configuration-management/bootstrapping.html

3

Hi,

Maybe you have cache / CDN configured in your PROD environment that is showing you old page?

Regards,

Junaid K

4

Thanks for the answer Ard,
Bootstrapping is set to false on PROD and on QA :slightly_frowning_face:

5

Thanks for the answer Junaid, but there is no cache that I know of.

6

Hikmet_Pasa

    May 9

Thanks for the answer Ard,
Bootstrapping is set to false on PROD and on QA :slightly_frowning_face:

Ok, it has to be set to true if you want to have your changes being applied.

Regards Ard

7

Thanks again Ard.
But we used the same commands also on QA. And QA works fine.

And when we copy production DB to QA, should QA not have the same problem like production?

8

Hikmet_Pasa

    May 9

ard.schrijvers:

Hikmet_Pasa

    May 9

Thanks for the answer Ard,
Bootstrapping is set to false on PROD and on QA :slightly_frowning_face:

Ok, it has to be set to true if you want to have your changes being applied.

Regards Ard

Hikmet_Pasa

    May 9

Thanks for the answer Ard,
Bootstrapping is set to false on PROD and on QA :slightly_frowning_face:

Thanks again Ard.
But we used the same commands also on QA. And QA works fine.

And when we copy production DB to QA, should QA not have the same problem like production?

The bootstrap is not a DB option so that is unrelated. The only explanation I have is that you did have the system property repository.bootstrap not set to false for QA, but have it set to false for prod.

At least it does explain why you don’t see the changes on production

Regards Ard

9

Thanks again Ard,
I am asking it again to the ones who installed it on the server. I will have an answer tomorrow.

If this doesn’t help. Do you have any other idea?