URGENT: All Products and Categories Disappeared in Magento 2.4.6-p4 Admin Panel

[webfull100]

Preconditions and environment

• Magento version

• Anything else that would help a developer reproduce the bug

• Magento version: 2.4.6-p4 (Open Source)

• Storefront and admin are online, but the catalog is empty

• No known manual deletion or deployments before the issue

• Cache cleared, indexes rebuilt, still no products/categories visible

• Admin user has full privileges

• Hosted on NeXcess

This is a critical issue. We are about to launch our most important sales campaign of the year (HOT SALE) and our site is non-functional. Any urgent support or guidance would be greatly appreciated.

Thanks,
Ezequiel Guidon
WebFull – Argentina

Steps to reproduce

1. Login to Magento Admin
2. Go to Catalog > Products – no records found
3. Go to Catalog > Categories – only Default Category (ID: 2) is shown, with 0 items
4. Database tables catalog_product_entity and catalog_category_entity are empty
5. Cache and index commands run with no result
6. No new modules or updates applied recently

Expected result

• All previously loaded categories and products should be visible and functional
• No data loss in catalog structure

Actual result

• Admin and storefront display zero products
• No subcategories under Default Category
• No products visible even after reindexing and cache flush

Additional information

This is a critical issue. We are about to launch our most important sales campaign of the year (HOT SALE) and our site is non-functional. Any urgent support or guidance would be greatly appreciated.

Thanks,
Ezequiel Guidon
WebFull – Argentina

Release note

Store is empty after categories and products disappeared. Critical for upcoming commercial event (HOT SALE).

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 @webfull100. 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.

• 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-November. 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

  - 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.

[engcom-November]

Hello @webfull100 ,

Thank you for your report and collaboration.

We have reviewed the description provided; however, we are currently unable to reproduce the issue without a clear and specific scenario.

Could you please check the var/log/ and var/report/ directories for any related error messages?

Additionally, are there any custom modules, automated scripts, or recent processes (such as cron jobs or data synchronizations) that might be influencing this behavior?

To proceed with a resolution, we will need the exact steps or conditions that lead to the issue. Please keep us informed of any new findings or relevant details.

In the meantime, we are marking this ticket as "Issue: Needs Update."

Thank you!

[ananth-iyer]

@webfull100 You could contact Nexcess to retrieve the most recent database (DB) backup.