-
AuthorPosts
-
January 10, 2016 at 9:21 pm #740192
Hi,
I’ve scoured the forums, but can’t quit get it to work.
WAMP Server, WordPress & the X Theme are installed and ‘mostly’ working on my computer.
I need an API key, so I can apparently update ConvertPlug, then enable “yep” in the dialog box, so I can download the Demo themes.
I’ve tried various URLs, received some API keys, entered them and nothing has happened.
When I installed WordPress I renamed the WordPress folder to “pjtest” beforehand. It’s in the WampServer “www” folder.
pjtest.com, http://www.pjtest.com, localhost/pjtest all work fineWAMP Server
Uses default port 80. (according to WampServer/Apache/”Test Port 80″ it is the only service that uses port 80)
In the hosts file pjtest.com and http://www.pjtest.com are enabled.The URLs I’ve tried are:
pjtest.com
http://www.pjtest.com
http://localhost:80/pjtest/ (says the URL is “80” when I use this URL)Thanks for your help,
PhilJanuary 10, 2016 at 9:22 pm #740196BTW – pjtest.com isn’t my website; just the name I used.
My actual website is philjaeger.com
Thanks.
January 10, 2016 at 9:37 pm #740204Hello There,
Thanks for writing in! To validate your localhost, you need to generate an api key using pjtest.com as your domain name. The generated key will work as long as you access your local server using http://www.pjtest.com. /localhost/ will not work and will return invalid URL.
For more details about product validation and api key generation, please check out our knowledge base here: https://community.theme.co/kb/product-validation/
Hope this helps.
January 10, 2016 at 9:59 pm #740224Hi,
I entered http://www.pjtest.com , which brought me to the local website.
When I click to go into the back end the URL changes to localhost/pjtest
I go into the back end.
Under Addons/Product Validation I enter the API key & click Submit API Key. Nothing happens. No error. Nothing.
How can I tell if the API key worked?
January 10, 2016 at 10:04 pm #740232Hi there,
It changes back to localhost/pjtest because it’s the URL that is set at Admin > Settings > General
Hence, if you really wish to use http://www.pjtest.com, then change your WordPress and Site URL to http://www.pjtest.com at Admin > Settings > General.
Validation should display a message that it’s successful and your API Key input would be in color green.
Thanks.
January 10, 2016 at 10:39 pm #740269Thanks,
It says that Automatic updates are up and running. FYI – I had to restart the browser to get it to work.
The Demo content still doesn’t give me a “yep” button, only “nope”. I thought I read somewhere that ConvertPlug needed to be updated for the Demos to work. ConvertPlug is still at version 1.0.0.
January 10, 2016 at 10:43 pm #740279Hi there,
Yes, there is a known issue with ConvertPlug plugin styles conflicting with X. Please disable it momentarily for the Yes button to show up.
We’re sorry for the inconvenience.
January 10, 2016 at 10:48 pm #740286Thanks for your help. I appreciate it.
It looks like everything is working…:0)
January 10, 2016 at 10:51 pm #740289You are welcome!
Glad that it helped. However the latest version of ConvertPlug fixed that issue. You can remove the ConvertPlug and install again from X Addons > Extensions to get the latest version.
Cheers!
January 10, 2016 at 11:00 pm #740297Thanks!
Deleting ConvertPlug, then reinstalling it worked.
Will Theme X extensions/plugins normally update on their own or do I need to delete, then reinstall them from the Addons>Extensions panel?
January 10, 2016 at 11:03 pm #740305Hi there,
Thanks for updating. It will be available on auto update from now on.
Cheers!
January 11, 2016 at 1:01 am #740382Hey,
I just changed my local site from pjtest.com to philjaeger.com
When I enter the API key for philjaeger.com I get the message “No API Key Provided”.
Is there a solution to this message?
January 11, 2016 at 1:04 am #740383Hi there,
Please revoke current API key (which was generated with pjtest.com) and regenerate it with philjaeger.com.
Hope it helps.
January 11, 2016 at 1:17 am #740389Thanks.
I had done what you suggested.
It turned out that I had to log out of WordPress, then log back in, then enter the new api key.
Logging out and back in worked.
January 11, 2016 at 1:21 am #740395Glad it worked for you.
-
AuthorPosts