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
Related
I am running zencart and use an add on module for sagepay form. I have just upgraded this to the latest version which should comply to v3 but when I log into mysagepay it still says I need to upgrade to V3. Is there somewhere else I should be going to make the changes? I have a copy of the technical guide for migrating from v2.23 to v3 which tells me the changes I need to make but I don't know where I need to go to make these changes. I am sure this is really simple but I am struggling. Any help would be much appreciated.
I'd recommend that you have a transaction ID (that you believe to be at 3.00) to hand and give Sage Pay a call - they can check the protocol value for you, so you can be sure you have upgraded successfully (MSP isn't always 100% reliable in the messages once you have upgraded!)
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.
my Joomla-backend ist destroyed. i can do a log in in a normal way, but then i see only text, no graphics. and also the wohle site is not visible and i can't scoll it. i made a screenshot, please look at it to see what i mean. i have to upgrade my Joomla Version but i cant do it with this broken backend. The current Joomla Version is 1.5.26
So, how can i fix this? I need full acces to my backend. Please help.
This is why we should not use older version of joomla.
you must install newer version of joomla
It is more reliable and secure.
Here is the step by step migration process
I've been given a request to upgrade an application running under filemaker pro 6.5.
It's connected to some serial devices and uses plugin-component (troi) to solve the communication (rs232).
It's running in a closed network attached to a remote FM65-database.
Will FMP12 be able to run the application w/o a lot of recoding or has things changed too much?
Regards,
/t
Simple answer, yes.
First of, there was no FileMaker 6.5. It went from version 5 to 5.5. to 6 and then 7. When version 7 was released there was a major update in fileformat for the databases, introducing multiple tables in a singel file and a new relationship schema.
Between version 11 and 12 there was another big update in fileformat. The bigest change being that the layouts are now rendered as HTML/CSS using WebKit.
Even though a lot has happend since version 6 FileMaker Inc always try to be backward compatible. As far as I know, no functionality has been removed, at least nothing vital.
Troi Serial Plugin works with FileMaker 12 but you will need to upgrade the plugin. you can read more about the changes for the plugin, pricing and download a demo at
http://www.troi.com/software/serialplugin.html
You can also download a 30 day trail of FileMaker from http://www.filemaker.com
Thus you can easily try the entire setup for free before doing it for production.
The only thing you probably will have to adjust is the function call for the plugin Troi Serial, but that should be easy!
Hope this helps
I'd recommend you use Metadata Magic to analyze the FP5 solution.
There are some script steps that can be problematic when upgrading. This will give you a comprehensive report of what issues to look for and where to find them. It's not uncommon to find script steps that need to be reordered or changed.