If I print_r($item), variable "core_images" it was empty.

I can confirm this. The problem is, that article images are stored in the column "images" (or "core_images" in ucm_content), whereas the category image is stored as a param in the "params" column ("core_params" in ucm_content).

However, I still don't figure out everything that com_tags is doing when saving an article. On first glance, one possibility to fix this would be making com_content and com_categories more consistent and make both store their images the same way. The other could be a dirty fix inside com_tags to check for images inside params, too.

@goshalviv
Do you want to test this PR #6792 ?
It's related to your issue because without it it's not possible to pick images from core_params at all e.g. of categories, some other items than articles and so on.
Detailed test instructions: #6792 (comment)

Testing it successfully would be a step forward.

I don't have problem with the category images, so it seems like this issue is solved now.

If this issue is fixed indeed, please close this issue :)

@n9iels The issue still exists for me with current staging branch. Just to clarify, I'll add some testing instructions here.

Testing instructions

1. Create a tag, e.g. "Red".
2. Create or edit an article:
   • Add the previously created tag.
   • Add an intro image.
   • Save.
3. Create or edit a category:
   • Add the previously created tag.
   • Add an image (under "options").
   • Save.
4. Create a menu item:
   • Type: Tagged Items
   • Tag: "Red" (your tag)
   • Content type: "Article"
   • Item Options - Item Image: Show (or set this option in the global options).
5. Create a menu item:
   • Type: Tagged Items
   • Tag: "Red" (your tag)
   • Content type: "Category"
   • Item Options - Item Image: Show (or set this option in the global options).
6. Compare both menu item views in frontend. The article one displays the item/intro image, while the category one doesn't display any image.

Thanks for provide this very clear test instructions! I confirmed the issue, and will try to find a solution.

@n9iels Could you find a solution for this issue?

this Issue exists.

@franz-wohlkoenig can you please test?

#14747

@goshalviv @Kubik-Rubik @n9iels there is a pull request in waiting to be tested! See my above comment.

i am closing this as #14747 was merged to address this issue