Site initializer batch as client extension in 2025 Q4 has issue

Development Client Extensions
1

I’m doing Site initializer batch as client extension in 2025 Q4 , it’s working fine but the url will come like this :
web/group-{groupId}

how I can make the friendly url like old quarters versions from the site name like

If Site Name : Test , so the url will be /web/test

2 Answers

2
2

@Ahmad_Qasem

I think in client-extension.yaml what you specify for siteName will get pickup as group name and your friendly url will look like web/test

test-site-initializer-structure:

    name: Test Site Initializer

oAuthApplicationHeadlessServer: test-site-initializer-oauth-application-headless-server

siteExternalReferenceCode: test

siteName: Test

type: siteInitializer

test-site-initializer-oauth-application-headless-server:

.serviceAddress: localhost:8080

.serviceScheme: http

name: Test Site Initializer CX

scopes:

        -   Liferay.Headless.Site.everything

        -   Liferay.Headless.Admin.User.everything

type: oAuthApplicationHeadlessServer
3

No, friendlyURL is always set to /group-{groupId}. When it is manually changed in the Admin UI and the Site Initializer CX is redeployed or Liferay is restarted it’s set back to this value.

The docs say this about the site-configuration.json file:

You can check the values for these configurations by inspecting data from the Group_ database table in an existing site.

But as seen in the source here, it only handles a few of the attributes and ignores the rest, like “friendlyURL” :face_with_diagonal_mouth:

Please update this to actually make Site Initializer CX useful.