mareike
Returning Observer

Projectsettings not available in CaaS

Jump to solution

We are currently setting up the FirstSpirit CaaS Version 3 and use the CaaS Connect Module that automatically generates the pages into the CaaS.

It works fine with regular Pages but the project settings are not appearing in the CaaS.

The doku says that the project settings have the identifier projectsettings https://docs.e-spirit.com/module/caas-connect/CaaS_Connect_FSM_Documentation_EN.html#urlschema

We tried to call it like any other page but with "projectsettings" instead of the page identifier:

http://localhost:8080/defaultTenant/e54cb80e-1f9c-4e8d-84b8-022f473202eb.preview.content/projectsett...

but it results in a 404. All other pages are there.

Is there anything special you need to do to get the projectsettings into the CaaS with CaaSConnect Module.

Labels (1)
1 Solution

Accepted Solutions
Peter_Jodeleit
Crownpeak employee
Crownpeak employee

Re: Projectsettings not available in CaaS

Jump to solution

Aktueller Status:
Es geht hier entgegen meiner ursprünglichen Vermutung um eine "on-premises" Benutzung des Moduls.
Die dort eingesetzte FirstSpirit-Version war 2020-09. Laut Release-Notes wird für das Feature eine FirstSpirit-Version von mindestens 2021-01 benötigt.

Peter

View solution in original post

0 Kudos
7 Replies
Peter_Jodeleit
Crownpeak employee
Crownpeak employee

Re: Projectsettings not available in CaaS

Jump to solution

Did you make any change on the project settings page after upgrading the caas-connect module?

In CaaS v3 everything is deployed to CaaS event-based, so issuing a change and / or release would trigger the deploy.
The other option would be to trigger a full deployment.

Peter
0 Kudos
mareike
Returning Observer

Re: Projectsettings not available in CaaS

Jump to solution

Hey pjodeleit,

yes I assumed that I have to do a change so the projectsettings would appear, but it had no effect. I also released the settings (Freigabe) and looked it up in the .release.files but there also is a 404:

{  

    "http status code": 404, 

    "http status description": "Not Found",

    "message": "document 'projectsettings.de_DE' does not exist"

}

Is there a possibility of ensuring that the generate process of a file is triggered when making a change or seeing errors?

0 Kudos
mareike
Returning Observer

Re: Projectsettings not available in CaaS

Jump to solution

I tried excecuting the CaaS Connect Release Generation and it gave me the following error:

ERROR (com.espirit.caasconnect.pipeline.CaasPipeline): Not deployed 4 items. 3 element(s) of type PageRef not rendered successfully and therefore they are not processed 1 element(s) of type ProjectProperties not rendered successfully and therefore they are not processed

Could ProjectProperties be the projectsettings? And what does "not rendered successfully" mean. There is no visible Error in the SiteArchitect...

0 Kudos
Peter_Jodeleit
Crownpeak employee
Crownpeak employee

Re: Projectsettings not available in CaaS

Jump to solution

That may indeed be the root cause. "ProjectProperties" is the technical / API name for Project-Settings. The error should be available in the FirstSpirit server log. Could you please open a ticket for this so that we can have a closer look. We need the informations about the environment (dev, qa, prod) and the project where this is occuring.
Thank you and sorry for the inconveniences.

Peter
0 Kudos
mareike
Returning Observer

Re: Projectsettings not available in CaaS

Jump to solution

Hallo Peter, danke für die Info. Die Fehlermeldung habe ich bereits aus den Logs im Server Monitoring. Weitere Details stehen dort nicht. Ich habe ein Ticket eröffnet: https://help.e-spirit.com/servicedesk/customer/portal/6/HELP-50160

0 Kudos
Peter_Jodeleit
Crownpeak employee
Crownpeak employee

Re: Projectsettings not available in CaaS

Jump to solution

Danke dir, wir melden uns morgen.

Peter
0 Kudos
Peter_Jodeleit
Crownpeak employee
Crownpeak employee

Re: Projectsettings not available in CaaS

Jump to solution

Aktueller Status:
Es geht hier entgegen meiner ursprünglichen Vermutung um eine "on-premises" Benutzung des Moduls.
Die dort eingesetzte FirstSpirit-Version war 2020-09. Laut Release-Notes wird für das Feature eine FirstSpirit-Version von mindestens 2021-01 benötigt.

Peter
0 Kudos