# Site initializer batch as client extension in 2025 Q4 has issue **URL:** \ **Category:** Client Extensions\ **Created:** [February 11, 2026, 2:15am UTC](https://discuss.liferay.com/t/site-initializer-batch-as-client-extension-in-2025-q4-has-issue/342 "2026-02-11T02:15:50Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![ChrisHof](https://dub1.discourse-cdn.com/flex014/user_avatar/discuss.liferay.com/chrishof/32/226_2.png) [@ChrisHof](https://discuss.liferay.com/u/ChrisHof)\ **Post date:** [June 10, 2026, 7:31am UTC](https://discuss.liferay.com/t/site-initializer-batch-as-client-extension-in-2025-q4-has-issue/342/3 "2026-06-10T07:31:37Z")
What happens in DXP 2026.Q1.8: On first deployment of the Site Initializer CX and setup of the new Site, the friendlyURL is set to _/{siteName}_ After all subsequent deployment, _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](https://learn.liferay.com/w/dxp/development/importing-exporting-data/site-initializers) 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](https://github.com/liferay/liferay-portal/blob/6737a2337308d2f8b144fb7bbe40d5bb497d5038/modules/apps/site-initializer/site-initializer-extender/site-initializer-extender/src/main/java/com/liferay/site/initializer/extender/internal/BundleSiteInitializer.java#L4659), it only handles a few of the attributes and ignores the rest, like “friendlyURL” 🫤 It’s still a bug that the friendlyURL is changed after the first deployment of the CX. --- _[View the full topic](https://discuss.liferay.com/t/site-initializer-batch-as-client-extension-in-2025-q4-has-issue/342)._