Bug report: Pro Unlimited license not working on Localhost

Support
#1

After purchasing the Pro Unlimited license I attempted to use this on a new installation using Local (https://localwp.com).

After entering the license the validation screen shows “Congratulations, your site is now validated!” but then refreshes to show the “You’re almost finished!” screen asking for the license again. Moving the site to production and then entering the Unlimited license works, but once the site is pulled back to local the license validation breaks again.

Hoping you can fix this as it would be great to have the unlimited license loaded in a blueprint for Local to speed up spinning up a new site.

Thanks!

#2

Hi @bangak,

Would you mind giving this another try? The system is meant to accept any kind of site URL. We encountered a similar issue yesterday with a Pro Unlimited site not validating (same issue where it would accept at first, but not stick) and pushed an adjustment to correct it. Let us know if this is working for you now, otherwise we can take a closer look. Thanks!

#3

Thanks for the reply. Unfortunately this is still happening. I’ll include a private note of a screen recording of the bug.

#4

Ok, thanks for double checking! I’m sorry it’s still not working for your use case here. We’ve tested with several different forms of local development sites without issue, but perhaps there’s some conflict related to Local.

I can take a closer look at how that platform works. Just a hunch, but they might be dynamically adjusting the site URL which could interfere with the X validation code. Regretfully I’ve got some other things I need to get resolved first so I won’t be able to take a closer look until tomorrow. It would be good to test specifically on that platform.

Certainly no pressure or obligation, but off the top of my head I know what I’d check first when the environment is setup. If you have a moment, and a child theme (or other way to run arbitrary PHP) the first thing I’d check is what gets output with this code. I would pretty much just see what happens when this is in functions.php of a child theme.

add_action('init', function() {
  var_dump( esc_attr( trailingslashit( network_home_url() ) ) );
});

Mostly talking aloud here and certainly have no expectations of you having to look into it, but knowing that output would be the first thing I’d check. It would likely reveal any discrepancies about how the URL could be different in Local. I’ll have more time to take a closer look tomorrow.

Talk to you soon!

#5

Hi @bangak,

We’ve tested using Local and it’s working on here. That said, we have uncovered there may be a discrepancy with URLs that contain port numbers. From your video I can tell because it’s Safari, but could you advise if there is a port number in your localhost URL? If that’s the case, this could be why it’s not validating. We’ll followup when a fix for that issue is deployed.

#6

Hi @bangak,

We pushed some changes this morning that should resolve issues validating sites with port numbers in the URL. Could you try validating again and letting us know if it sticks for you? Thanks!

#7

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.