Tagged: x
-
AuthorPosts
-
April 6, 2016 at 3:20 pm #870022
I typically build sites locally using MAMP. I keep one of my licenses available specifically for this feature. I’m at localhost:8888 so, I when I’m building a site, I can throw that key in, build it, when the site goes live, I buy a new license and transfer it over.
However, when i tried to validate today, it says URL is not valid? It’s worked like this for a month with no changes, now it won’t work. Help me understand what’s going on please and how to fix it.
April 6, 2016 at 11:06 pm #870509Hello There,
Thanks for writing in!
Please walk-through following thread and let us know how it goes:
https://community.theme.co/forums/topic/using-a-single-domain-license-within-mamp/#post-174773
Thanks.
April 7, 2016 at 11:15 am #871445Other than the link in the post (http://blainsmith.com/articles/quick-and-dirty-local-domain-names-for-mamp/)being broken and useless, it went swimmingly. Do you have another article you can point me to?
April 7, 2016 at 12:23 pm #871523Ok, so i scrolled through the blog that you directed me to. I made the changes according to the blog. I still cannot validate. Which means as you know, I can’t work with any of the extensions.
I followed the directions from the blog and put a .dev on the end of the url rather than a .com
I’ve revoked the license and reinstated it multiple times trying different names.
Please let me know what I need to do? I’m also curious as to why you guys thought that this was something that needed to be changed in the first place? Was it too easy?
Please don’t start complicating things for the sake of complicating things.
April 7, 2016 at 1:02 pm #871578This is what I see when I try to validate. The site url
premieraudio.dev DOES match what I’ve placed in the X license Activation space.This site URL is not a match for your API key.
April 7, 2016 at 11:34 pm #872323Hi There,
You must provide a domain name to be able to assign the license to. Since you are validating the localhost, you need to create a virtual hostname and use this fake hostname to assign the license. If you haven’t created a virtual hostname like myvirtualhost.com, please follow these links:
http://stackoverflow.com/questions/19425086/alias-hostname-for-localhost
http://foundationphp.com/tutorials/vhosts_mamp.phpFor example, my own virtual host name is http://myvirtualhost.com/. See attached screenshots.
Inside my virtual host folder, I have beta folder which is my WordPress site. So my site URL ishttp://myvirtualhost.com/beta
same with URL I have set on WordPress > Admin > Settings > General >WordPress Address (URL) and Site Address (URL). Then when you assign licence to site, you can also use this virtual host name.Hope this helps.
April 8, 2016 at 8:48 am #872833I followed the instructions previously given for using MAMP. Here are my screenshots.
https://www.dropbox.com/s/s6ijx543iy8v6pp/Screenshot%202016-04-08%2009.42.46.png?dl=0
https://www.dropbox.com/s/ozmsth4oqp6k0y2/Screenshot%202016-04-08%2009.45.22.png?dl=0
https://www.dropbox.com/s/kmbve1puz54xmb7/Screenshot%202016-04-08%2009.46.07.png?dl=0
https://www.dropbox.com/s/9xok4bfql5fia8m/Screenshot%202016-04-08%2009.47.57.png?dl=0
https://www.dropbox.com/s/91k5hyxlcv5sh68/Screenshot%202016-04-08%2009.47.13.png?dl=0
April 8, 2016 at 11:23 pm #873707Hi there,
Is there a way we can access your installation publicly? I really like to see some logs to see what causes this.
For the meantime, please install Debug Bar plugin, and Debug Bar Remote requests plugin. Please activate them, then please validate your license again. Once done, please toggle/open the debug menu at your admin bar and head to remote requests section.
That should give you the log of what’s happening during the remote requests (validation). And please provide any information you’ll get. Screenshot is okay too.
Thanks!
April 9, 2016 at 7:46 am #874075This reply has been marked as private.April 9, 2016 at 9:20 pm #874695Hello There,
Sorry for the inconvenience. When you are working locally, most of the time, it is necessary to validate it unless you want to receive automatic updates. Please understand that in order to receive these updates you need to have your product validated. And as a requirement in the validation process, you need to assign the license to a domain. If you do no have a correct domain, there will be no validation process that can be done. This is why we always suggest that when working locally, you must have a virtual hostname for easier access and to help you with the validation process locally. To avoid from getting your project delayed, I would recommend that you just do not validate your product. You can always update it manually. The latest version of X is always available for you to download anytime when you need it right in your dashboard (https://community.theme.co/dashboard/).
Hope this helps.
April 10, 2016 at 6:58 am #875096I feel like you didn’t even read my previous posts.
#1. If you checked my previous posts, you would know that I’m using a virtual host, I’ve assigned a domain name, and I’ve attempted to validate using this domain name. IT’S NOT WORKING.
#2. Then you recommend to continue to work without validating. The problem with NOT validating, is that I can’t use the download the extensions because you can’t download extensions until X is valiidated.
April 10, 2016 at 8:28 am #875183This reply has been marked as private.April 10, 2016 at 8:29 am #875185This reply has been marked as private.April 10, 2016 at 8:27 pm #875752Hi there,
In that case, I’ll forward this issue 🙂
Thanks and stay tuned!
April 18, 2016 at 7:16 pm #889099I haven’t heard anything. It’s been 8 days. Checking in to see what the resolution will be.
-
AuthorPosts