Home>Support>SiteOrigin Widget 504 Error When Attempting to Edit

SiteOrigin Widget 504 Error When Attempting to Edit

When I try to edit an SiteOrigin Widget that was previously added to a page, I get a 504 error reading “The page request was canceled because it took too long to complete.”

This appears on all widgets and is not exclusive to any particular browser (Chrome or Firefox).

I can edit widgets that I have just created, even those I save in that same session. This is an error which comes up when I am editing widgets that were added to the page in a previous session.

This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.

  1. 17 days, 6 hours ago Andrew Misplon Hi, I Work Here

    Hi, thanks for reaching out.

    There are a few potential 504 error causes. Before diving into those, it’ll be worth checking for a working baseline. Does the issue persist with all plugins except for the Widgets Bundle and Page Builder deactivated?

  2. 17 days, 6 hours ago lc3460

    Hi Andrew,

    The only plugin that is having a problem, so far as I can tell, is the Accordion within the SiteOrigin widget. I’m reluctant to deactive and then reactivate the plugin if it means we will lose the widget features already on our other webpages. Does that answer your question?

  3. 17 days, 6 hours ago Andrew Misplon Hi, I Work Here

    Hi, thanks for your reply.

    The test is to see if the issue is resolved when all other plugins are deactivated. If the issue persists, then we will have ruled out a plugin conflict. The test can potentially be completed in 30 seconds. You can add a maintenance mode plugin if you’d prefer your site not to be seen in the testing state. In that event, the only plugins activated during the test would be Page Builder, Widgets Bundle, and the maintenance mode plugin.

  4. 16 days, 5 hours ago lc3460

    Hi there,

    Unfortunately, I wasn’t able to resolve the problem with the other plugins deactivated. What would you recommend as a next step?

  5. 16 days, 5 hours ago Andrew Misplon Hi, I Work Here

    Thanks for the update. You can perhaps let your hosting company know the details of the 504 and ask if they can check their logs to see if there are any rules in place that may be causing the issue.

  6. 16 days, 4 hours ago Andrew Misplon Hi, I Work Here

    There are a few troubleshooting steps listed at the below URL that are quite quick to try if you have a few moments:



Please log in to post on our forums. Signing up is free.

Get The Most Out of SiteOrigin with SiteOrigin Premium

Find Out More