Why does a Listdom shortcode cause an HTTP 500 error in a SiteOrigin HTML Widget?
Ce contenu n’est pas encore disponible dans votre langue.
Problem
Section titled “Problem”In affected SiteOrigin Page Builder setups, a page with a Listdom shortcode can load normally while it has no listings, then return an HTTP 500 Internal Server Error or a blank page after listings are published.
The server may report a PHP error similar to:
PHP Fatal error: Allowed memory size exhaustedRemoving or unpublishing the listings can make the page appear to work again. This can make the listing data look like the cause, even though the shortcode container is the relevant difference.
This behavior can occur when a Listdom shortcode is placed in a SiteOrigin HTML Widget. That widget processes content differently from a standard WordPress shortcode or text widget. In affected setups, rendering Listdom output there can use excessive server memory when listings are available.
The shortcode itself does not need to change, and the listings are not necessarily the underlying problem.
Solution
Section titled “Solution”Replace the SiteOrigin HTML Widget with a shortcode-compatible content area. Keep the same Listdom shortcode, for example:
[listdom id="396"]Use one of the following instead:
- WordPress Shortcode block
- WordPress Classic Editor text area
- SiteOrigin Text Widget
- Another widget that explicitly supports WordPress shortcodes
Example
Section titled “Example”Avoid this placement:
Row└── HTML Widget └── [listdom id="396"]Use this placement instead:
Row└── Text Widget └── [listdom id="396"]Troubleshooting steps
Section titled “Troubleshooting steps”- Confirm whether the failure begins only after listings are published.
- Check the widget or block that contains the Listdom shortcode.
- If the shortcode is in a SiteOrigin HTML Widget, remove it from that widget and place it in a Text Widget instead.
- Clear the page cache, plugin cache, and CDN cache if they are active.
- Test the directory page again with the same shortcode.