Pull Request resolves #48753 .

Related to #48690.

• I read the Generative AI policy and my contribution is either not created with the help of AI or is compatible with the policy and GNU/GPL 2 or later.

Summary of Changes

When an article is updated with PATCH /api/index.php/v1/content/articles/{id} and the body contains articletext, the change is ignored. For PATCHthe controller fills all fields missing from the request with the stored values, including introtext and fulltext. Content::bind() splits articletext into introtext/fulltext, but parent::bind() then overwrites them with the stored values.

This PR removes the stored introtext and fulltext from the data on PATCH when articletext is sent and those fields are not in the request. articletext already works on POST.

Testing Instructions

1. Create an API token for a Super User and enable the Web Services - Content plugin.
2. Create an article (or use an existing one, ID X).
3. Send:

curl -X PATCH -H "X-Joomla-Token: <token>" -H "Content-Type: application/json" \
  -d '{"articletext":"<p>New intro</p><hr id=\"system-readmore\"><p>New full text</p>"}' \
  http://<site>/api/index.php/v1/content/articles/X

4. Check the article in the backend and its Versions.
5. Also check that PATCH with only title or only introtext still worksas before.

Actual result BEFORE applying this Pull Request

Response is 200, but the article text is unchanged and no new version is stored.

Expected result AFTER applying this Pull Request

The intro text is "New intro", the full text is "New full text", and a newversion is stored. PATCH with other fields is unchanged. If introtext and articletext are both sent, introtext wins, same as on POST.

Link to documentations

Please select:

• Documentation link for guide.joomla.org:

• No documentation changes for guide.joomla.org needed

• Pull Request link for manual.joomla.org:

• No documentation changes for manual.joomla.org needed