Broken reference errors piling up logs

[Zyles]

Logs becoming bloated and Sentry going crazy with broken reference errors.

$ cat var/log/system.log | grep "Broken reference"
[2020-01-23 03:32:33] .WARNING: Broken reference: The element with the "category.view.container" ID wasn't found. Verify the ID and try again. [] []
[2020-01-23 03:32:39] .WARNING: Broken reference: The element with the "category.view.container" ID wasn't found. Verify the ID and try again. [] []
[2020-01-23 03:33:44] .WARNING: Broken reference: The element with the "category.view.container" ID wasn't found. Verify the ID and try again. [] []
[2020-01-23 03:33:45] .WARNING: Broken reference: The element with the "category.view.container" ID wasn't found. Verify the ID and try again. [] []
[2020-01-23 03:35:56] .WARNING: Broken reference: The element with the "category.view.container" ID wasn't found. Verify the ID and try again. [] []
[2020-01-23 03:37:41] .WARNING: Broken reference: The element with the "category.view.container" ID wasn't found. Verify the ID and try again. [] []
[2020-01-23 03:38:48] .WARNING: Broken reference: The element with the "category.view.container" ID wasn't found. Verify the ID and try again. [] []
[2020-01-23 03:41:30] .WARNING: Broken reference: The element with the "category.view.container" ID wasn't found. Verify the ID and try again. [] []
[2020-01-23 03:41:32] .WARNING: Broken reference: The element with the "category.view.container" ID wasn't found. Verify the ID and try again. [] []
[2020-01-23 03:42:48] .WARNING: Broken reference: The element with the "category.view.container" ID wasn't found. Verify the ID and try again. [] []
[2020-01-23 03:42:50] .WARNING: Broken reference: The element with the "category.view.container" ID wasn't found. Verify the ID and try again. [] []
[2020-01-23 03:42:51] .WARNING: Broken reference: The element with the "category.view.container" ID wasn't found. Verify the ID and try again. [] []
[2020-01-23 03:42:52] .WARNING: Broken reference: The element with the "category.view.container" ID wasn't found. Verify the ID and try again. [] []
[2020-01-23 03:43:05] .WARNING: Broken reference: The element with the "category.view.container" ID wasn't found. Verify the ID and try again. [] []
[2020-01-23 03:43:07] .WARNING: Broken reference: The element with the "category.view.container" ID wasn't found. Verify the ID and try again. [] []
[2020-01-23 03:43:15] .WARNING: Broken reference: The element with the "category.view.container" ID wasn't found. Verify the ID and try again. [] []
[2020-01-23 03:43:17] .WARNING: Broken reference: The element with the "category.view.container" ID wasn't found. Verify the ID and try again. [] []
[2020-01-23 03:43:29] .WARNING: Broken reference: The element with the "category.view.container" ID wasn't found. Verify the ID and try again. [] []
[2020-01-23 03:43:45] .WARNING: Broken reference: The element with the "category.view.container" ID wasn't found. Verify the ID and try again. [] []
[2020-01-23 03:44:26] .WARNING: Broken reference: The element with the "category.view.container" ID wasn't found. Verify the ID and try again. [] []
[2020-01-23 03:44:28] .WARNING: Broken reference: The element with the "category.view.container" ID wasn't found. Verify the ID and try again. [] []
[2020-01-23 03:44:46] .WARNING: Broken reference: The element with the "category.view.container" ID wasn't found. Verify the ID and try again. [] []
[2020-01-23 03:45:01] .WARNING: Broken reference: The element with the "category.view.container" ID wasn't found. Verify the ID and try again. [] []
[2020-01-23 03:45:03] .WARNING: Broken reference: The element with the "category.view.container" ID wasn't found. Verify the ID and try again. [] []
[2020-01-23 03:46:15] .WARNING: Broken reference: The element with the "category.view.container" ID wasn't found. Verify the ID and try again. [] []
[2020-01-23 03:46:25] .WARNING: Broken reference: The element with the "category.view.container" ID wasn't found. Verify the ID and try again. [] []
[2020-01-23 03:47:41] .WARNING: Broken reference: The element with the "category.view.container" ID wasn't found. Verify the ID and try again. [] []
[2020-01-23 03:47:56] .WARNING: Broken reference: The element with the "category.view.container" ID wasn't found. Verify the ID and try again. [] []
[2020-01-23 03:49:35] .WARNING: Broken reference: The element with the "category.view.container" ID wasn't found. Verify the ID and try again. [] []
[2020-01-23 03:49:37] .WARNING: Broken reference: The element with the "category.view.container" ID wasn't found. Verify the ID and try again. [] []

The only occurance of changing "category.view.container." is in our theme:

app/design/frontend/Theme/theme/Magento_Theme/layout/default.xml:
<move element="content.top" destination="category.view.container" />

Preconditions (*)

1. Magento 2.3.3 & 2.4-develop
2. Custom theme extended from Luma

Steps to reproduce (*)

1. Extend luma theme
2. Move the container:

app/design/frontend/Theme/theme/Magento_Theme/layout/default.xml:
<move element="content.top" destination="category.view.container" />

3. Browse website etc. and check logs after a while

Expected result (*)

Stop bloating the logs.

Actual result (*)

Bloating of logs with useless errors.

[m2-assistant]

Hi @Zyles. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

@Zyles do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[mrtuvn]

This issue is not related with magento. This is 3rd-party theme issue
The reason is your destination id in custom theme is not exist

[Zyles]

Luma is not part of Magento 2?

[m2-assistant]

Hi @engcom-Hotel. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[magento-engcom-team]

✅ Confirmed by @engcom-Hotel
Thank you for verifying the issue. Based on the provided information internal tickets MC-30875 were created

Issue Available: @engcom-Hotel, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[mrtuvn]

Luma is not part of Magento 2?

I don't say that you should check my reply. I said this problem come from your custom theme

[mrtuvn]

category.view.container only visible in category page add move directive in default.xml is not best practices