Can I use license-key Backpack v3 on Backpack v4 version?
What to do if I use the temporary a.com domain later the project will be transferred to the b.com domain. When buying a license, which domain should I specify?
Thank you in advance!
No, a v3 license will work inside Backpack v4. You have to purchase a separate license for v4. Unfortunately, you just missed huge Black Friday discounts.
No problem if you move from a.com to b.com, just email the Backpack team.
When upgrading from 3.x to 4.x make sure you follow each upgrade guide individually. For example:
upgrade Backpack 3.5 to 3.6
upgrade Backpack 3.6 to 4.0
upgrade Backpack 4.0 to 4.1
They are all major versions. The first number signifies need for additional payment. The second number signifies breaking changes.
Related
I was wondering if you could help – we have previously used a version of Postsharp 2.1.5.1 basic features for the last number of years on a historical application.
All of a sudden, it has started asking for a license key and we cannot find one – it was originally set up by a developer who has long since moved on.
We are trying to use the basic features and don’t require a full license – is this possible?
The version runs on VS 2010 and every time I select an option via the pop up I receive a “Postsharp is configured” message, but when I build the solution, I receive build errors related to Postsharp. Also, the same windows pops up again, and I am taken back to the start of the process i.e. Trial, register or purchase a licence.
Am I missing something in the setup? How do you configure the Express version or download a licence, every time I choose the Express download from the web site I get the full version.
Hope this makes sense. Any help would be greatly appreciated.
Best regards
D
You should upgrade to the latest build of PostSharp 2.1. It will give you the ability to register PostSharp Express without getting a license on our website.
Guys I am planning to use moodle 2.7 as the lms in my organization..could you please let me know if there are any know vulnerabilities which could grant a user a higher order privilege?? if yes then how do I make sure I fix it...I have to use moodle 2.7 only..cannot upgrade that
Moodle 2.7 is out of support in about 6 weeks. It's patched (security wise) as of this point in time, but if someone discovers something 3 months from now, it won't be fixed and you'll have to upgrade anyway. It's a really, really bad idea to use it for a new site when you might as well use 3.1 (LTS) or 3.2
I can not find any link related with 2.1.5 from SourceForge. I wonder whether I can still use this version as a third party component in my product.
Any comment would be appreciated very much!
Sure you can. Search the web and you will find that version easily (e.g. here or here) It is a different question however whether you should still use that version. It is quite old and lots of bugs have been fixed and new functionality has been added. So do the following:
check the license restrictions (LGPL vs. AGPL)
if you don't have a problem with a GPL based license then use the latest 5.X version
if you can't use APGL buy a commercial license or use at least version 2.1.7
if you go the 2.1.7 route do some testing - in many cases it will do its job still fine. If not you'll probably have to fix it by yourself
Update: I would now use openPDF which is a maintained fork based on 2.1.7.
I want to create a php application that can be used by many users, As laravel 4 requries 5.3.7 i am confused weather to use it or not because many of the users may not have the php version supported as they will be using shared hosting.
How to overcome this ? Is it by using older version of laravel or some other solution please help me. I am really intersted in using laravel cause of its robust nature.
To be honest, depending on what your application is, it's probably enough to think that most users are either already going to be on PHP 5.3.7+ or they will be willing to upgrade to the latest version or a more recent version of PHP.
When PHP 5.3.20 was released, there was an extremely public announcement that PHP 5.3 was going to be EOL'd after March 2013.
It's now obviously past March 2013.
People should have moved to PHP 5.4 by now. If your application is a one of a kind, or the best in it's class, then you should not need to worry about what version of PHP is being operated on, as people should either
be running PHP version > 5.3.20
be able to upgrade to a PHP version > 5.3.20
The Laravel dependancy on PHP 5.3 is a nice one, and to be honest, with all of the new features and general code style of Laravel being introduced, I would not be surprised if the version requirement is increased to PHP 5.4 "soon" (in say the next 6-12 months).
If you want to create an application used by many users, simply advise them that there is a minimum requirement for PHP 5.3.7. This is not too unusual for web applications.
For example, a very popular PHP forum phpBB has required PHP 5.3.3 since March 2012.
I looking forward to upgrade vBulletin 3.8 to vBulletin 4.0. What i need to know is how much effort it will be to migrate. I have about 15 products installed.
Any idea is there any change in hooks or functions or way to call things that i will need to change in products and templates? Also is there any thing that deprecated in 4.0 that i will have to look into?
I found Styles are not at all compatible and Products are not compatible 99% of times. SO i will have to redo styles and also fix custom products and upgrade downloaded products.