non-production auto-updates

Home Forums Product Support Forums Ajax Search Pro for WordPress Support non-production auto-updates

This topic contains 1 reply, has 2 voices, and was last updated by Ernest Marcinko Ernest Marcinko 1 year, 6 months ago.

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
  • #39392

    Hi there!

    We’re using WPEngine’s Smart Plugin Manager for automatic updates to WordPress plugins.

    Based on the documentation ( we’ve added the license key to our production WordPress instance for Ajax Search Pro.

    According to the above referenced rules, it seems this single license should also work for auto-updates on staging and development instances, but we’re finding that isn’t the case. It only seems to work on a single instance at a time.

    The production instance is and the non-production instances are and

    Do you have any advice or is there something we’re missing here in the configuration?



    Ernest Marcinko
    Ernest Marcinko


    The auto updater server tries to check the origin server URL agains the license code, and if common subdomains are used, then it will allow the license to remain active (as if it was active on the main domain).
    It is a fairly problematic process alltogether, in most cases it works, in others it dont – depending on if the origin can be determined. Determining the origin is a whole other topic, it is a nightmare on it’s own.

    I have made a few corrections on the server, but I can’t promise it will recognize the correct origins.

    If you are using a staging environment, which is worked on and then pushed to the live, then having it active there is sufficient. License activation is not neccessary for the plugin to function correctly, it is only used for automatic updates.

    Ernest Marcinko

    If you like my products, don't forget to rate them on codecanyon :)

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic.