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!)
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
This is about sonarqube 5.1 version
I have issue assign plugin and also subscribed to the emails in my profile page. I've done some erroneous SVN commits deliberately to check the email notification settings but it doesn't seem to work correctly. I receive emails sometimes but other times it doesn't work like that.
I know this is not a constructive enough question but I'm really stucked here after trying all the scenarios and going through the documentation.
Any insight would be highly appreciated.
You should uninstall this plugin. It is compatible, but it does not work correctly. The problem is that SonarQube 5.1 introduced core auto assignment (see automatic issue assignment and SONAR-5906). The core functionality & plugin execution order is as follows:
Plugin during the execution assigns issues & collects information to whom he should send e-mails. Next core functionality reassign issues.
Core functionality reassigns issues
Plugin sends emails with incorrect data
See topic on SonarQube mailing list
I am also using SQ 5.1 and Issue Assign plugin works perfectly fine without any issues. You should check your email notification settings.
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've been asked to make some changes to a site that was built with Expression Engine 1.6.8. Even though I'm not familiar with this CMS, I can find my way around to make the updates, except I'm not sure about adding a contact form. I'm guessing that ultimately I'll have to upgrade this version to the newest (2.7, I believe?) in order to get the tags found on this page to work: http://ellislab.com/expressionengine/user-guide/modules/email/contact_form.html?
My only hesitation in making the upgrade is my unfamiliarity with EE, and the fact that someone else is probably creating a brand new website for the one I'm working on, and very likely without EE (so I'm learning something that I may not need again).
Any suggestions for a quick fix, or should I just bite the bullet, upgrade, and use what I've found?
Take a look at the EE 1.x docs.
At a glance it appears that syntax has changed little bit. Maybe that's why your EE2 tags were not working in EE1.
I would definitely try to use the tags as shown in the EE1 docs if this site is that old. Making a jump from 1.6.8 to 2.7 can become treacherous due to variables such as how the templates were coded, which add-ons were used, if those add-ons are even available any longer, what functionality was deprecated or absorbed, etc...
I only say ditch the efforts because you mentioned having another site in progress. If you would like to work through the updates/upgrades, follow the docs here and here and learn it. It is definitely worth the learn. Once you tap into EE, it's hard to roll back.
I ended up writing my own html code within the template and processed it with a php script to send the form input to an email address, just as I normally would on a website. Not being familiar with ExpressionEngine, I don't think I understood why I was continually being referenced to use a module in order to do this, but I suppose for anyone who is not a coder but is experienced with EE, that would be the way to go. From what I understand, the email module is not free and does not come with the core version, which is what I had to work with, but comes with the licensed version, which made this all the more confusing.