Post update conflict

  • Resolved cstangor

    (@cstangor)


    2 years, 2 months ago

    Hello, I am using both Photonic and SearchWP plugins. They are creating a problem together when I update a post. The problem is that the post takes about 15 seconds to update. This doesn’t happen when either Photonic or SearchWP are activated individually. I received this message from SearchWP:

    The debug logs basically show that your CPU limit is being breached whenever a post is updated in the backend. This does not necessarily mean that SearchWP is taking a lot of CPU usage but there could be other reasons, like a custom code or conflict with another plugin that is causing it. For example if another plugin is also using HTTP ajax or curl requests when updating posts then it may cause the background process to lock and consume CPU resources.

    Can you shed any light on this?

    Thank you.

Viewing 1 replies (of 1 total)
  • Plugin Author Sayontan Sinha

    (@sayontan)

    2 years, 2 months ago

    This wouldn’t happen due to Photonic – it doesn’t make a cURL or AJAX call when you save. Photonic simply keeps the shortcode, and the cURL call happens while the page is rendered on the front end (not upon save) – this is how Photonic is always able to show you the current content.

    Check if you have a caching plugin. Caching plugins will try to evaluate shortcodes upon saving, and that might be causing the issue when it is trying to render Photonic’s shortcodes. It is also possible that SearchWP is trying to expand all shortcodes, causing the issue. You can try the Photonic JS load mode – that forces caching plugins to skip the Photonic shortcode. Maybe that will also prevent SearchWP from evaluating the shortcode.

Viewing 1 replies (of 1 total)

The topic ‘Post update conflict’ is closed to new replies.