Schema option creates 503 timeouts

  • Resolved erichaalo

    (@erichaalo)


    4 years, 7 months ago

    Hi,

    I’ve found a bug in which the Schema option, when enabled, creates 503 timeouts on several pages. This is a serious issue, since user might be unlikely to discover it until their income drops. It also drains RAM.

    I went through each setting in the plugin and isolated it to the Schema option. When enabled several pages on the site never load and return 503.

    When disabled, they load perfectly.

    I have no idea if it is a conflict with another plugin, but this was replicable across several sites, hosts and installs.

    I’m not going to link it, as I don’t want to enable. I can provide you with information, if you email me or send me a message.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Support Steve M

    (@wpsmort)

    @erichaalo Does your site have a lot of user accounts under Users? I ask because the only thing that may impact performance is that when you go to All in One SEO > General Settings, the plugin builds a drop down with a list of all your user accounts. This is a known issue and we have a Github issue open for it.

    Thread Starter erichaalo

    (@erichaalo)

    No, not at all. There’s but a few users on each.

    It simply times out and never loads.

    I’m guessing it is a plugin conflict maybe, since it doesn’t seem to be widely reported here. However, this is a really nefarious bug, because people might not discover that they’re losing trafic, unless they check their log. I found mine in the server logs, showing a huge amount of 503s.

    Plugin Support Steve M

    (@wpsmort)

    Please contact us here https://semperplugins.com/contact/ so we can help you. Please choose Plugin support and paste the URL of this forum post in the License Key field.

    I’ve had this happen too. Very simple site, no user accounts, using something very close to the default configuration.

    PHP Fatal error: Maximum execution time of 120 seconds exceeded in /home/XXXXX/public_html/wp-content/plugins/all-in-one-seo-pack/inc/schema/aioseop-context.php on line 860

    I am going to need to remove schema on a LOT of installs now. It only timed out on a specific post, at least that I’m aware of. It could be affecting more. The post had nothing special going on, maybe a long-ish title and slug.

    Plugin Support Steve M

    (@wpsmort)

    @stormymondays Please contact us here https://semperplugins.com/contact/ so we can help you. Please choose Plugin support and paste the URL of this forum post in the License Key field.

    Plugin Support Steve M

    (@wpsmort)

    @erichaalo and @stormymondays We did have someone respond to us and so we were able to troubleshoot this. We found that the problem was caused by a plugin that had added post_parent to a non-hierarchical post type such as Posts. As post_parent is not a valid WP Object, this causes problems when querying the post object.

    This is not something we can reproduce here because we don’t know what plugin caused this in the first place. There’s no reason to add post_parent to a non-hierarchical post type. The very concept of parent child makes something hierarchical.

    We’ve got a patch for this very rare situation which will be released next week. However, you should be aware of the cause, because this can affect other plugins so you may run into it again in the future.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Schema option creates 503 timeouts’ is closed to new replies.