Recursion error

[saltenasbenas]

Bug description

Hello, after latest update, when i clean cache i get: Recursion detected while augmenting [Statamic\Entries\Entry] with ID [45694750-f312-495e-97d9-1502458566cd]. This ID is copy of original collection post

I have multisite, with propagate, before update it worked fine. I do not use any special fields. I propagate fields and do not edit them in other languages. Shouldn't it work fine even if i do not edit them in other languages? Because it seems, what this causes error

How to reproduce

Set up a multisite Statamic project with at least two locales.

Create a collection with propagation enabled for all sites.

Create an entry in the primary site

Let the entry auto-propagate to the other site

Do not modify the propagated entry manually in the secondary locale.

Clear the cache using admin panel

Logs

Environment

Environment
Application Name: Statamic
Laravel Version: 12.19.3
PHP Version: 8.2.0
Composer Version: 2.7.7
Environment: local
Debug Mode: ENABLED
URL: test.local/
Maintenance Mode: OFF
Timezone: UTC
Locale: en

Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED

Drivers
Broadcasting: log
Cache: file
Database: sqlite
Logs: stack / single
Mail: smtp
Queue: sync
Session: file

Storage
public/storage: NOT LINKED

Locales
Installed: en, et, lt, lv
LaravelLang\Actions\Plugin: 1.10.1
LaravelLang\Attributes\Plugin: 2.13.4
LaravelLang\HttpStatuses\Plugin: 3.10.3
LaravelLang\Lang\Plugin: 15.22.0
LaravelLang\MoonShine\Plugin: INCORRECT
LaravelLang\StarterKits\Plugin: 1.3.9
Locales Version: 2.10.0
Protected: en
Publisher Version: 16.6.0

Statamic
Addons: 6
Sites: 4 (Lithuanian, Latvian, Estonian, English)
Stache Watcher: Enabled (auto)
Static Caching: Disabled
Version: 5.58.0 PRO

Statamic Addons
alt-design/alt-redirect: 1.6.3
lucapon/statamic-content-backup: 3.0.3
pixelastronauts/statamic-autocomplete-address-field: 1.0.0
ryanmitchell/statamic-translation-manager: 2.2.0
statamic/seo-pro: 6.7.0
thoughtco/statamic-cache-tracker: 0.9.3

Installation

Fresh statamic/statamic site via CLI

Additional details

No response

[clee-fma]

We're also getting this error now after updating. Also a multisite installation.

[jeroenpeters1986]

Hi! Same here. I also have a multisite installation with entries in different languages, and posts with propagation (origin: in the YAML file) gave this error when I was trying to clean and then warm the stache after a deployment.
I also use full static caching, but it didn't get to the point of being able to save files.
Just reverted to 5.57.0 for now.

It seems that the feature of PR#11854 is a bit too protective? I am not really sure what it's for but it seems to throw the Exception when HasOrigin is called twice for an Entry?
The description in the PR is "This PR does not fix the underlying issue here, but makes it easier to detect and debug."
I would like to think that making thing easier for detecting and debugging should include some kind of logging, and not blocking/disruption.. especially when it does not affect the underlying issue. Having said that, the effort of @JohnathonKoster is very well appreciated, but I hope this will get less blocking.

[JohnathonKoster]

@jeroenpeters1986 Thanks for the extra info! I am working to address this, as the protection should only trigger if things starts to recursively call that values() method (usually ending in an infinite loop).

I am having difficulty reproducing this in a new test site, and believe I'm missing something here. Would you be able to share more info about the site and collection's routing?

The suggestion for simply logging something is a good one, and will look into that if I cannot find the root cause of these unintended side effects.

[jeroenpeters1986]

I could give you my content @JohnathonKoster but I would also be okay with giving you temporary access to my private repo which contains the content, that might be giving you even more context?

[miteyema]

Same here, also multisite installation.
It said Recursion detected while augmenting [Statamic\Entries\Entry] with ID [a888909d-d9cb-49ca-8d0b-82248a61c172] but when I searched my repo, there was only one file (content/trees/collections/en/coaching_themes.yaml referring to that ID.

[JohnathonKoster]

I could give you my content @JohnathonKoster but I would also be okay with giving you temporary access to my private repo which contains the content, that might be giving you even more context?

That would be incredibly helpful! I'll work to get something going to resolve this in the short term, but would love to figure out what is causing this to solve in a better way long term.

[jeroenpeters1986]

@JohnathonKoster I will email you so we will not be 'littering' this thread since its closed