Experience site retrieval

[Adam Stepanek]

Hi Scott,

I’ve found out that IC2 is not retrieving default pages from experience site and because of that deployments fails with

‌

java.lang.NullPointerException

Site structure retrieved by IC2:

.
└── config
    ├── languages.json
    ├── loginAppPage.json
    ├── mainAppPage.json
    ├── nativeConfig.json
    └── partnerPortal.json

Site structure retrieved by workbench.developerforce.com:

.
├── brandingSets
│   └── buildYourOwn.json
├── config
│   ├── languages.json
│   ├── loginAppPage.json
│   ├── mainAppPage.json
│   ├── nativeConfig.json
│   └── partnerPortal.json
├── routes
│   ├── checkPassword.json
│   ├── createRecord.json
│   ├── error.json
│   ├── forgotPassword.json
│   ├── home.json
│   ├── login.json
│   ├── loginError.json
│   ├── recordDetail.json
│   ├── recordList.json
│   ├── register.json
│   ├── relatedRecordList.json
│   ├── search.json
│   └── serviceNotAvailable.json
├── themes
│   └── buildYourOwn.json
└── views
    ├── checkPassword.json
    ├── createRecord.json
    ├── error.json
    ├── forgotPassword.json
    ├── home.json
    ├── login.json
    ├── loginError.json
    ├── recordDetail.json
    ├── recordList.json
    ├── register.json
    ├── relatedRecordList.json
    ├── search.json
    └── serviceNotAvailable.json

It is just plain site, Build-your-own (Aura), without any customization.

‌

[Scott Wells]

Hi, Adam. The most likely reason for this is that IC2 doesn't know about the ExperienceBundle metadata type. Please confirm that you have the following:

1. Digital experiences enabled in the org.
2. ExperienceBundle metadata API enabled in the org.
3. An updated cache of org metadata in IC2 based on those things being enabled. You can refresh this cache in Illuminated Cloud > Configure Module.
4. Restart the IDE just to make sure that all caches are fresh (shouldn't be necessary but I'd prefer not to waste your time).

I see a similar NPE without those (which I'll address for a better experience), but once those are configured properly everything works as-expected.

If you're still seeing the issue after doing the above, please reproduce the problem and attach your idea.log which should contain the full stack trace. You can find it using Help > Show Log in Explorer/Finder/Files.

[Adam Stepanek]

1. Yes, without that you are not able to create an experience site.
2. Yes, as I retrieved a site from that sandbox a few months before.
3. Yes
4. Yes

So now it retrieves as expected. Not sure what exactly made this bug, but we just managed to fix one major issue in our development cycle, which could be responsible for this. I will just briefly mention it here, otherwise this can be closed.

So few months back we developed a Experience Site named eLearning. This was our first site and we did not have proper knowledge of Experience cloud so we started with some site where we did POC. This site then were moved to a different sandbox where the site were developed and released.

And now when we started to work on second site, for some reason unknown to me, the project started building the site on top of the old eLearning one in the first sandbox. That means that the foundation for the two sites were same. Especially the page Ids were same. That probably resolved in some issues in the IC2 such that some pages were assigned under the eLearning site, and some were assigned under the second site, despite that in sandbox all of theme were under one site.

In the end we resolved that by manually adjusting the id references on all .json files from third site from which we just took the ids.

‌

[Scott Wells]

I'm glad it's resolved for you now. It certainly wouldn't surprise me if the intertwined sites you describe caused the issue.