Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Debug Option #8

Open
bupp925 opened this issue Jun 8, 2018 · 1 comment
Open

Add Debug Option #8

bupp925 opened this issue Jun 8, 2018 · 1 comment
Labels

Comments

@bupp925
Copy link
Collaborator

bupp925 commented Jun 8, 2018

https://github.com/SearchSpring/magento2-searchspring-feed/blob/master/Helper/Generator.php#L218

When debugging certain data issues, it'd be very helpful to be able to pass a single Entity ID as an option in the regen script, rather than having this to comment on/off - the way it is, this runs the risk of forgetting to uncomment the line, which I know has happened before.

In a perfect world, this &debug=12345 option would dump a JSON object of the data record directly to the regen screen in browser, bypassing any need to update a test feed file.

@shrekked
Copy link

shrekked commented Aug 7, 2020

@julesbravo @bupp925 In addition to passing an entity ID, it would also be nice to output debug statements based on the current page parameter.

Reason being, Magento's product database frequently seems to have corruptions which cause a 500 error when we try and request product attributes for specific products, this prevents us from even knowing which entity ID is causing the issue.

If we had the ability to add a debug statement that output the entity ID(s) contained within the current product collection before fetching product attributes, this would allow us to quickly and easily determine which products are corrupt and causing the regen to fail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants