main.INFO: Broken reference in debug.log

[cptX]

Preconditions and environment

• Magento version
  2.4.5
• Anything else that would help a developer reproduce the bug
  I think it's happening in a pure magento installation

Steps to reproduce

Enable developer mode. Just visit some pages including the main page. Then check the debug.log and you will see these errors!!

Expected result

No errors should be produced.

Actual result

[2023-02-04T16:47:27.794836+00:00] main.INFO: Broken reference: the 'catalog.compare.sidebar' element cannot be added as child to 'sidebar.additional', because the latter doesn't exist [] [] [2023-02-04T16:47:27.795021+00:00] main.INFO: Broken reference: the 'sale.reorder.sidebar' element cannot be added as child to 'sidebar.additional', because the latter doesn't exist [] [] [2023-02-04T16:47:27.795145+00:00] main.INFO: Broken reference: the 'wishlist_sidebar' element cannot be added as child to 'sidebar.additional', because the latter doesn't exist [] [] [2023-02-04T16:47:27.795211+00:00] main.INFO: Broken reference: the 'paypal.partner.right.logo' element cannot be added as child to 'sidebar.additional', because the latter doesn't exist [] [] [2023-02-04T16:47:27.795275+00:00] main.INFO: Broken reference: the 'bml.right.logo' element cannot be added as child to 'sidebar.additional', because the latter doesn't exist [] [] [2023-02-04T16:47:27.795325+00:00] main.INFO: Broken reference: the 'sidebar.container.paylater' element cannot be added as child to 'sidebar.additional', because the latter doesn't exist [] []

Additional information

I'm really surprised this bug exists in magento since 2016!!!!! There are dozens of references of this issue over the years. Although I didn't find any recent reference about this in magento 2.4.x.
The only difference is that then was declared as main.CRITICAL and now is main.INFO.

Why isn't this solved 7 years now???
This should be solved because is clogging the logs and in my opinion takes resources from the system as it tries to find things without success, even in production mode (not tested) where maybe is not showing in the logs...

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @cptX. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

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

For more details, review the Magento Contributor Assistant documentation.

Add a comment to assign the issue: @magento I am working on this

To learn more about issue processing workflow, refer to the Code Contributions.

---

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

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-Alfa. 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).

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.

• 3. Add Area: XXXXX label to the ticket, indicating the functional areas 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.

[mrtuvn]

Not sure but possible somewhere in legacy code used wrong reference in incorrectly place

[engcom-Alfa]

@cptX

Thanks for writing the ticket.

After retesting we found, that the issue is also reproducible on the "2.4.x Developer" local, which is ahead of the branch in all the instances.

Steps to reproduce

1. Install/upgrade your Magento local using the terminal.

2. Enable Developer mode using the terminal using the command ( ./bin/magento deploy:mode:set developer).

3. Now log in to backend Admin and enable debug mode to 'yes' using the following path (Stores >> Settings >> Configurations >> advance >> Developer >> Click on Debug Setting Dropdown >> Enable all settings to Yes.

4. Now go to the front end and try surfing the storefront by accessing to multiple pages and if possible try placing one order

5. Now go to the terminal and select the 'Log' - folder using the following path (cd magento/ Var/Log) of Magento local setup.

6. Now ls command in and open debug folder with the installed editor of your system to verify if broken logs are captured or not

7. now try searching word 'Broken' in debug log file

8. confirm if broken logs are captured or not.

Expected result
Debug log should be captured without any errors.

Actual result
broken logs are captured as displayed in snapshot

Attachment Proof

[github-jira-sync-bot]

Unfortunately, not enough information was provided to create a Jira ticket. Please make sure you added the following label(s): Reproduced on 2.4.x, ^Area:.*

Once all required labels are present, please add Issue: Confirmed label again.

[github-jira-sync-bot]

Unfortunately, not enough information was provided to create a Jira ticket. Please make sure you added the following label(s): Reproduced on 2.4.x, ^Area:.*

Once all required labels are present, please add Issue: Confirmed label again.