Fixes to not break on upgrade related to subpages

[hightowe]

To fix issues #336

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[hightowe]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

What does SAP have to do with WonderCSM?

[hightowe]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

What does SAP have to do with WonderCSM?

From a LLM:

This appears to be a configuration error on the part of the WonderCMS project. They are using CLA-Assistant.io, a free service created and hosted by SAP that integrates with GitHub to automate CLA signing for pull requests. Projects can set up CLA-Assistant by linking their repo and selecting (or providing) a CLA template—often a custom one stored as a GitHub Gist, or one of the service's predefined options. In this case, WonderCMS seems to have selected or defaulted to SAP's own ICLA template, which is meant for SAP-owned open-source projects (like their UI5 framework). This template isn't appropriate for an unrelated project like WonderCMS, as it would give SAP perpetual rights to use, distribute, and sublicense your code contribution, while providing no benefit or protection to WonderCMS itself.

Many other open-source projects use CLA-Assistant without this issue by uploading their own neutral CLA text (e.g., based on Apache or Harmony templates that grant rights to the project owner). The SAP branding and references on the signing page (headers, footers, emails like opensource@sap.com) are there because SAP owns and runs the service, but the actual agreement content should be project-specific.