Announcement

Collapse
No announcement yet.

What is my best upgrade path? (From 3.5.1 to what?)

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Dominic
    replied
    Your addons and style (if used) won't work with vB5.
    You can have a look at our language forums where user provide language packs too.

    Leave a comment:


  • mamamiforum
    replied
    but what any other problems can come from this upgrade? the language is also a problem, does anyone know if there is a language package for hungarian? there is no offiical one.

    Leave a comment:


  • Dominic
    replied
    Hello,

    you could purchase vBulletin 5 Connect. vB 5 is designed for responsive view, so when using a mobile device like smartphones or tablets, the forum will be displayed in an optimized view.

    Leave a comment:


  • mamamiforum
    replied
    I am completly new here, need some help.
    i just took over a forum run on vbulletin, mamami.hu/forum and thinking about to upgrade to 5 mobile.
    first of all because of the users complaint that it is not moblie friendly. Right now it is working with 3.8.0

    do i need the 5 connect?
    i am afraid of it, it is a big change and i am not very familiar with the forum installation etc, and here in Hungary i just did not find anyone who is familiar with this vbulletin (there was a blog but since 2012 nothing)

    what do I need to consider before an upgrade?
    thanks, if someone can help me

    Leave a comment:


  • Joe D.
    replied
    Don't worry about overwriting files right now. Just setup the licenses in the Member's Area hour you want them. Use the Edit License Details link to change the URLs.

    Make sure when you are done the software installed on any given URL is equal to or less than the version you are allowed to run for that site. What is confusing is you might be allowed to run 4.0.8 but not 3.8.9 because 4.0.8 came out 3 years before 3.8.9. So if in the 3.x branch make sure you are using a 3.x version below or equal to the max 3.x version you can use.

    Do not copy over any files at this time. The next time you upgrade simply use the files downloaded from the correct license at that point.

    Leave a comment:


  • MikeSD
    replied
    Originally posted by Mark.B View Post
    You can move licenses to different sites yes, as long as it's one site per license. Just update the URL in the license itself via the members area.

    A license will always give you the latest version you are able to download for that specific license, so if you have any licenses that give you 3.8.9 and 4.2.3, then those are "new style" licenses and you need to nothing with those. You can move them to other sites if you wish, as long as they are only used on one site at a time.

    If a license only gives you 3.6.2 as the latest version that's an old style license and that would need upgrading as mentioned earlier, then you'd get access to 3.8.9 and 4.2.3. Or, as you point out, you can attach that site to a different license instead, one that is "current".
    Ok, that's almost like I understood it. I'm not following why I can't upgrade 3.5.1 to 3.6.2, since that was allowed when the license was active, and can still be downloaded. If that requires an upgrade fee, it seems odd it would be limited to 3.6.2. If I got to pay for any upgrade, they should all say 3.8.9. That's odd. I don't understand why waiting changes anything. 3.6.2 is still authorized for that license, which is why I can download it. But no matter, what I want to do, can best be accomplished by my unused active license.

    I just want to use it on my first site. So, what I will do is to NOT use it where it's currently registered (and not used), and move it to the other site. Then, change the link, so that the one and only copy is being used on my site 1.

    But my question now is, how to best accomplish that? 3.5.1 (license-X) is currently installed. I want to overwrite that, and preserve the database, by using 3.8.9 (License-Y). When done, License-Y software will be used only on site 1. The link will be corrected. License-Y will be referenced. But when I begin the install, I wonder if it will think I'm trying to update 3.5.1 vs just installing 3.8.9. Maybe I should backup then delete all those files first, so there will be no confusion.

    Leave a comment:


  • Mark.B
    replied
    You can move licenses to different sites yes, as long as it's one site per license. Just update the URL in the license itself via the members area.

    A license will always give you the latest version you are able to download for that specific license, so if you have any licenses that give you 3.8.9 and 4.2.3, then those are "new style" licenses and you need to nothing with those. You can move them to other sites if you wish, as long as they are only used on one site at a time.

    If a license only gives you 3.6.2 as the latest version that's an old style license and that would need upgrading as mentioned earlier, then you'd get access to 3.8.9 and 4.2.3. Or, as you point out, you can attach that site to a different license instead, one that is "current".

    Leave a comment:


  • MikeSD
    replied
    Originally posted by Mark.B View Post
    That's the way the old licensing system works. It isn't going to change now. Owned licenses worked using annual renewals....you had the right to run the software but to access latest versions you had an annual renewal..
    Which is why, I assume, for each of my licenses, there is the option to download a different version, when all are the same level. When each of those expired, I was locked to a particular version (still visible and should be usable), for each site, with the existing license. All of my sites are version 3.x, except 1 which is 3.8.9 or 4.2. But each of my 3.x sites are locked to different levels. One is locked to 3.6.2 (it appears), one to 3.6.5, one to 3.6.8 and the unused one to 3.8.9.

    But something I just noticed. I still have ONE license that is not expired. It's Active and doesn't expire. It's for a site that no longer exists. So I should be able to use it on any site I like, by changing the web site link to which it's attached. (i.e. stop using 3.5.1, on site 1, replace it with my active license, and then change the link to point to the new site.)

    I've sent an email to the sales folk. I'm 100% sure there should be a way to use my existing licenses, on a different site, if I change the links. No license would be used more than once. I have valid licenses for versions from 3.5.1 up to 4.2. I just want to put them on different sites (i.e. reorganize which sites they are on).

    For instance, since I have a valid license for 3.8.9, on an unused site, I should be able to use it on any site, even if it was one that previously had 3.5.1. The licenses aren't locked to a site that is why we have the form to change the link. And, I've done this before, through vBulletin. They told me to change the link, after I moved the forum. I was more concerned about trying to save the data from the old site, than anything.

    I must not be explaining something right. Let me try this again.

    * I have a valid license on site 1 (License-X, has 3.5.1 but should be good to 3.6.2 because they allow me to download that).
    * I have a valid license on site 2 (License-Y, has 3.8.9 but is UNINSTALLED at present. Was hacked and I removed the installation, so it's unused.

    * I want to abandon License-X, on site 1. Or at least stop using it on site 1
    * I want to MOVE site 2 forum, using License-Y, to my site 1

    All of this seems appropriate and legit. I would then just change the link for License-Y, to point to site 1, instead of site 2. I am NOT trying to upgrade license-X. I'm trying to MOVE my license-Y to another site and put the forums on a different domain. That's all.

    Initially I was thinking about upgrading. But beginning with post #10, I began to consider just moving my forums to different locations. Not upgrading anything. This would be taking existing licenses and moving the location of the forums. In the end, I could have exactly the same legit licenses, only residing on different forums. Links would be changed to reflect these changes. All forums would have properly licensed software, just different locations from where they were originally installed. It's a forum relocation only operation.
    Last edited by MikeSD; Sun 5th Jul '15, 6:51am.

    Leave a comment:


  • Mark.B
    replied
    Originally posted by MikeSD View Post
    That doesn't even makes sense to me. If I "own" my license (Owned License), how can it expire? I should be able to run those licenses I bought, forever. Further, my member site, allows me NOW (still) to download specific versions, for my "owned" license. Why would the vBulletin system allow me to download an update, if they don't work?

    And since I have an "owned" license for 3.8.9 or 4.2.3, I should be able to put it on any of my sites.
    That's the way the old licensing system works. It isn't going to change now. Owned licenses worked using annual renewals....you had the right to run the software but to access latest versions you had an annual renewal.

    Your only option is to purchase the renewal, which is the 149 package mentioned, which will also effectively move you from the old licensing system to the current one, which is lifetime download access for that version (in this case vB4). You would only need to pay again after that if you wanted vB5.

    Leave a comment:


  • MikeSD
    replied
    That doesn't even makes sense to me. If I "own" my license (Owned License), how can it expire? I should be able to run those licenses I bought, forever. Further, my member site, allows me NOW (still) to download specific versions, for my "owned" license. Why would the vBulletin system allow me to download an update, if they don't work?

    And since I have an "owned" license for 3.8.9 or 4.2.3, I should be able to put it on any of my sites.

    Leave a comment:


  • Mark.B
    replied
    If you have old-style "owned" licenses, these will have expired. That older licensing system enabled you to run the software for life, but only versions that were current at the time the license was still current.
    Some of these licenses therefore had access to early versions of vB4, however do not upgrade to those versions as they are now very old.
    Most though only had access to vB3, and then only to the version that was current at the time.

    For all such licenses, you can now buy an "upgrade pack" for $149, this will convert the license into a newer-style license with lifetime upgrade access, but only as far as the vB4 line (no vB5 access). This is what you need to do for those "expired" licenses, whether you want 3.8.9 or 4.2.3.
    Don;'t upgrade to any older versions than those, as you will encounter security issues, php compatibility problems and other undesirable results.

    If you'd like to clarify the situation on specific licenses, drop an email to sales@vbulletin.com with the license numbers and sales will advise specifically. Make sure you tell them you are looking for vB3 and vB4, NOT vB5.

    Leave a comment:


  • MikeSD
    replied
    Followup questions:

    Understanding vBulletin licensing

    I have four "owned copies" that are currently registered with four different domains, all of different versions. Two of my domains, that DID have vBulletin on them, have been lost or shut down, so those licenses are unused.

    License 1: vBulletin 3.5.1, clicking download shows 3.6.2
    License 2: vBulletin NOT installed now, clicking download shows 3.6.5
    License 3: running vBulletin 3.6.8, clicking download shows 3.6.8 Patch Level 2
    License 4: licensed vBulletin v4.x but NOT installed right now, clicking download shows 3.8.9
    License 4: also shows I can download v 4.2.3

    vB 3.6.2 is for msdsite
    vB 3.6.5 is for ArrowCache
    vB 3.6.8 Level 2 Patch is for RetroPCDesign
    vB 3.8.9 is for ipscone
    vB 4.2.3 is for ipscone

    Questions:
    1) Each of these show that 3.8.9 is available. But does this download option mean that is the ONLY version I can download without a fee?
    Ex: License 1 to 3.6.2 (only), License 2 to 3.6.5 only, License 4 to 3.8.9 or 4.2.3 only? Or can all be upgraded to 3.8.9 without a fee.

    2) Can my version 3.5.1 be upgraded to 3.8.9 without a fee? Or am I stuck at only going to 3.6.2?

    3) I know that the domain associated with these can be changed. Since I'm not using two of my licenses, currently, I assume that means, that if I prefer, I can just change the domain to the higher license. Right?

    4) Since there was a license associated with each of my downloads, and there is a license associated with my current installs, if I use my 3.8.9 license, on my License 1 site, or rather upgrade my 3.5.1 (license 1 site) with 3.8.9 (license 4), will there be an install problem. I would correct the license # and make the appropriate changes on my registration data, to conform with terms. Just wondering if I will have some install issue?

    Summary of what I'd like to do:

    I have a currently "not being used" vBulletin 3.8.9 update on one of my sites and I'd like to swap it with my version that is on a site that I am using. Then, make the changes on the vBulletin registration area. What is the best way to proceed with upgrading a site with one license, with an update that is a different license?

    PS: Where is the license # stored on my site. Couldn't I just change that to match the new update license?
    Last edited by MikeSD; Sat 4th Jul '15, 9:25am.

    Leave a comment:


  • Zachery
    replied
    PHP 5.6 compatibility support is a huge reason.

    Leave a comment:


  • MikeSD
    replied
    Originally posted by Paul M View Post
    If you want to stay on vB3, go for 3.8.9, If you want to upgrade, go for 4.2.3.
    Ok thanks. I'm probably going to upgrade from 3.5.1 to 3.8.9, this weekend. No real reason to do it. My 3.5.1 is working well enough, but might as well get it upgraded to at least 3.8.9.

    However, is it worth the effort to upgrade from 3.5.1 to 3.8.9? Is there much difference to make it worthwhile?

    Thanks,

    Leave a comment:


  • Paul M
    replied
    If you want to stay on vB3, go for 3.8.9, If you want to upgrade, go for 4.2.3.

    Leave a comment:

widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
Working...
X