Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GET request for a specific article returns "text" filed where intro text and full text are concatenated together #41176

Open
MayaSima opened this issue Jul 17, 2023 · 2 comments

Comments

@MayaSima
Copy link

I need to automatically process fulltext from multiple articles. I pull the article, process fulltext, and then send it back via PATCH.
I noticed that "text" field in the GET request response contains both introtext and fulltext concatenated with "\r\n \r\n" like so:

`

Intro Text.

First Paragraph of full text.

`

As a result, I do the processing, publish the result back as a "fulltext", which results in intro text being copied to the full text and being duplicated on the updated page.

Steps to reproduce the issue

GET request to {{base_url}}/{{base_path}}/content/articles/{{article_id}}
parse the returned payload and retrieve "text" attribute
process
PATCH request wit hthe updated fulltext

Expected result

"fulltext" and "introtext" should be kept as separate fields in the response from GET request to {{base_url}}/{{base_path}}/content/articles/{{article_id}} endpoint

Not sure if "text" field is needed at all

Actual result

I receive "text" field with concatenated "introtext" + "fulltext" with no <hr id="system-readmore"> separator in between in the response from the GET request to {{base_url}}/{{base_path}}/content/articles/{{article_id}} endpoint

System information (as much as possible)

Joomla version 4.3.3

Additional comments

@alikon
Copy link
Contributor

alikon commented Dec 2, 2024

please test #44566

@alikon alikon closed this as completed Dec 2, 2024
@alikon alikon reopened this Mar 24, 2025
@alikon
Copy link
Contributor

alikon commented Mar 24, 2025

as pr #44566 has been closed i'm repoening this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants