Invision Community 4: SEO, prepare for v5 and dormant account notifications Matt November 11, 2024Nov 11
Posted July 13, 20222 yr I followed the followed the recommendations for moving the forum from www. to forum. I the cleared system caches. updated the conf_global.php board_url from "https://www. ..." to "https://forum. .." restarted php and cleared system caches again. Now the now license key error won't go away (attached). I've tried clearing caches again, restarting php (due to opcache)... I still had a couple of weeks before renewal and i've paid the bill and the under settings -> license key, it's still showing the error, however it's now showing the new renewal date. I've clicked check again. refreshed license key. and even tried to install the existing key again, and i get "This license key has already been activated. Your license key entitles you to one installation only" i've only moved subdomain from www. to forum. support: could you reset the key from URL's to https://forum.carp.com
July 13, 20222 yr You need to reset your license key in the Client area? Removing www means you have a new board address. An IPS staff may have to help with this as the tool will still detect an instance in the old location still.
July 13, 20222 yr Author 51 minutes ago, Randy Calvert said: You need to reset your license key in the Client area? Removing www means you have a new board address. An IPS staff may have to help with this as the tool will still detect an instance in the old location still. Can't, says already installed.
July 13, 20222 yr Author 6 minutes ago, Marc Stridgen said: I have corrected this for you. Thanks, that solved it.
January 22, 20232 yr We are having the same problem with our www and dev site licenses. Would you be able to take a look at our licenses and see whats going on? We will be building a new Dev server and making some major changes to our site in the coming weeks, I'd like to know how to handle this in the future. Thanks, --Scott
January 23, 20232 yr You appear to have a few sites there, I would need to know which you are seeing this on
January 25, 20232 yr Things seem to be back to normal on gm-trucks.com But we have a new dev.gm-trucks.com and that is giving the error. can you take a look at both dev.gm-trucks.com and gm-trucks.com and make sure they are happy? Thank you,
January 25, 20232 yr 1 hour ago, Mervz said: Things seem to be back to normal on gm-trucks.com But we have a new dev.gm-trucks.com and that is giving the error. gm-trucks.com and dev.gm-trucks.com are two separate licenses which are licensed for different applications. You will not be able to run the same applications on these two communities. Could you please clarify the intent here? If you're running 2 public websites under these, you would need 2 separate licenses. If dev.gm-trucks.com is just test URL for gm-trucks.com, you would simply need to use the -TESTINSTALL license key, you don't need a separate license. (Please keep in mind Test URLs are not to be public facing).
January 26, 20232 yr I guess that's what I'm looking for. This is a staging server for testing updates etc. prior to running them on the production GM-Trucks site. I think because this was a clone, it's mad about the licenses. If I reinstall IPB using the -TESTINSTALL switch, will that set it back to a test license?
January 26, 20232 yr I have some additional questions. I do see that we have a normal license for both GM-Trucks.com and Dev.gm-trucks.com For our Dev/Staging server, would it be better to use the full dev.gm-trucks license, or just use the -TESTINSTALL. We want to keep these two servers as identical as possible and don't want to have a test or trial license expire. Can you advise? Thanks.
January 26, 20232 yr 1 minute ago, Mervz said: For our Dev/Staging server, would it be better to use the full dev.gm-trucks license, or just use the -TESTINSTALL. We want to keep these two servers as identical as possible and don't want to have a test or trial license expire. Can you advise? Thanks. I would advise simply using the test install, as this will allow you to keep them identical, in terms of the license and software installed. The only exception of the test install, like I said earlier, is this can't be publicly accessible. Only your immediate staff should have access to test/develop your community as needed.
January 29, 20232 yr Ok Great, the Dev server will be just accessible to staff and contractors. Thanks for the help.
January 29, 20232 yr I have a few additional questions. 1. Where can I find the instructions on how to use the -TESTINSTALL flag? I'm having a hard time finding info on your site. 2. I'm going to assume I can simply perform the installation using -TESTINSTALL over the existing installation. 3. We are 1-2 revs behind, should I do a -TESTINSTALL of the exact same version we are currently running, or is it safe to run the update using -TESTINSTALL? Thank you in advance! --Scott
January 29, 20232 yr There is mention of how to use the test install license key in this guide. If you are installing on a test install, enter your license key with -TESTINSTALL on the end.
January 30, 20232 yr 15 hours ago, Mervz said: 2. I'm going to assume I can simply perform the installation using -TESTINSTALL over the existing installation. With this one, if you already have it installed, you can just change the key in System>Settings>License Key 15 hours ago, Mervz said: 3. We are 1-2 revs behind, should I do a -TESTINSTALL of the exact same version we are currently running, or is it safe to run the update using -TESTINSTALL? Depends on what exactly you are testing. This can only really be answered by yourself.
February 2, 20232 yr To clarify, I was thinking that -TESTINSTALL was a command line installation flag... After some additional reading, I understood how it works as a suffix to your license key. I'm still learning 😄
February 2, 20232 yr Don’t worry… we were all in your shoes at one point. It’s hard to understand some things until you actually need them! 🙂
February 2, 20232 yr 4 hours ago, Randy Calvert said: Don’t worry… we were all in your shoes at one point. Some say, we never leave 😄
February 20, 20232 yr Was there a hiccup in the licensing server around 9:10 ish PM MST last night (the 19th)? The license finally took during the upgrade after a few tries, but for a few minutes I was getting an error that said: The license key could not be found