It is not true that in order to live one has to believe in one's own existence. There is no necessity to that.
We in NFPservies have some client using secure.Worldpay as their payment processor and it was always an issue in making it work and now worldpay has introduced online.worldpay gateway with API reference which are easy and quicker than before
Earlier in secure.worldpay gateway we use to redirect from CiviCRM to secure.worldpay website and process all the card details and then it will be passed over to CiviCRM website and we process the details. But, In Online.Worldpay we are using API for creating Tokens and Card Authorize. so no more redirection also the processes is straight forward and quicker
This Extension is based on Online.Worldpay.com - https://online.worldpay.com/
Please make sure you have an account with https://online.worldpay.com/
To install the uk.co.nfpservice.module.worldpay, move the uk.co.nfpservice.module.worldpay directory to your civicrm Custom extension folder directory and Install the extension.
HOW TO USE
Please obtain the service key and client key from your online.worldpay.com account setting
This extension uses https://api.worldpay.com/v1/ api for accessing the website. This link might change from time to time so please make sure you are using the correct URL given by your Online Worldpay Account.
For more documentation regarding the API please refer to https://online.worldpay.com/docs
- Recurring Payment.
- Webhook Integration.
This module was developed based on CiviCRM 4.6 and Drupal 7.x. - hasn't been tested in any other version.
Please give a test and if you want to use it in lower or higher version. Please feel free to contact me if you have any issues. You can find the contact details at the footer of this document.
Currently tested in CiviCRM 4.6 / Drupal 7.x with Webform CiviCRM Integration 7.x - 7.14
you can download the Extension from CiviCRM Extension folder or from GitHub https://github.com/rameshrr99/uk.co.nfpservice.onlineworldpayAttachmentSize uk.co_.nfpservice.onlineworldpay.jpg195.45 KB CiviCRMDrupalExtensionsv4.6
Last Saturday Oskar and Dirk from the ERPAL Platform Team went to UX Day Graz 2015. A small community conference on user experience, interaction design and usability.
The event had 3 Keynotes as well as some showcases from the community.
The Keynote by Eric Eggert from the W3C Web Accessibility Initiative showed how small changes in markup can already improve accessibility by a lot. He demonstrated this by showing button markup and providing the readings from a screenreader. But also delivering fallback solutions for other disabilities is not that hard.
Regulations, like for example BITV in Germany to make governmental websites accessible or the BGStG in Austria to make every website accessible from 1.1.2016 on, show that accessibility is not only a nice thing to have, but also required by law.
Other than that, there are millions of people with disabilities using the internet. To be exact about 15% of the worlds internet users have some kind of disability. So you exclude a lot of people by not making your site accessible. More information on making websites accessible including the WCAG guidelines and easy to follow tutorials for beginners can be found on at the Web Accessibility initiative.
In his keynote Philipp Sackl, Lead Designer for Firefox, talked about building empathy with your audience. It was interesting seeing an example where he thinks firefox has improved the user experience and where it still needs lot’s of work. His opinion on designing for user experience showed us that user experience is something than can be improved by precise planning. But one major take home lesson is that you should never rely on your knowledge, you always need to test and get feedback from your target audience. You as a designer or developer are the pro user of your system, so you are biased before you even use the software. Get out there and collect data about how non experienced users use your software, that the only way to improve usability and user experience. Interesting as well was his opinion on how much influence you can have with making decisions, even with the bad ones. He showed us how a user had to search 2 minutes to solve a simple task. Assuming that every of the million users was wasting 2 minutes with this task he feels like firefox was wasting a lot of the worlds time.
In his talk on "Visual Search and Analysis“ Tobias Schreck, Professor at Graz University of Technology, explained some approaches for visual search. His argument was to make visual interfaces interactive to get the most from it. He showed some interesting projects and how they helped retrieving valuable information form big sources of information. The talk showed again how much potential is in data visualization and how easy it can be to extract information if you choose the correct format.
In the Panel Discussion follwing the Keynotes Eric Eggert, Tobias Schreck, Keith Andrews and Heinz Wittenbrink were discussing the future of UX. The main points: content is always the most important thing do deliver, so you don't need to talk about user experience when you don't deliver interesting content. In future a lot of will focus on user testing with prototypes, made with special prototyping tools or html dummys. And one of the hottest topics at the moment is data visualization as it makes it easy to review large numbers of for example measurements. Providing easy to undarstand and oversee data improves the users experience by a lot.
On the picture (f.l.t.r) Oskar Bechtold, Chair Keith Andrews (Graz University of Technology), Vice-Chair Konrad Baumann (FH Joanneum) and Dirk Peter.
I’ve recently been reading some books on how to improve my story writing, and one of the tips they invariably give is to not start your stories with a massive exposition dump. This is bad news for me because my writing is usually nothing but exposition dump, so I probably will never write the next bestseller to take the world by storm. That’s OK though, because it brought into focus one of the traditions of tabletop gaming that I’ve never really cared for. That is, of course, starting a campaign with every player going round and taking a massive character exposition dump right on your table.
I find this exercise more than a little boring and I always felt it was also a good deal odd, both because the expectations laid out rarely jive with gameplay, because you tend to end up with a group of really special snowflakes, and because it ends up with characters knowing a good deal more about each other than they probably should (think about your vague knowledge of your coworkers and compare to how much you would have known about your friend’s character if you hadn’t fallen asleep during his half hour monolog).
Of course some of my distaste for this probably harkens back to the era in which I joined the hobby. In the “start with 1 rolled hit die” era you could conceivably take more time telling everyone at the table your character’s backstory than your character might actually survive in the game, so backstory was usually “My character is a fighter. His name is Joe D. Fighter.” If Joe survived more than a session or two not only did he have some interesting backstory created by play, but then and only then might we start thinking about why Joe D. Fighter started adventuring instead of joining up with the army or the town militia. Most likely Joe has serious anger management issues and problems with authority.
But on the other hand I get that “Meh. Screw that noise.” just isn’t fair to those in the hobby who enjoy finely crafting characters and their backstories and then exploring their development. So instead, I propose what the writing books assure me is a better alternative to the exposition dump. They recommend that if you want to show a character’s traits, instead of simply telling the reader about them you slip some examples into the story in which you get to put them on display via the character’s actions. The same goes for backstory elements. Find a way to bring them to the forefront of the action and put them on display.
This seems like it would be a tricky thing in an RPG. It requires you as GM to know what characteristics the players would like their characters to have opportunities to display, and then for those that are unlikely to come up naturally it requires you craft and insert a few from time to time. Then it depends on your players recognizing and taking advantage of these opportunities to show off aspects of their character. This of course requires a little cooperation from both sides of the screen. The two biggest potential pitfalls are not knowing what your players want to highlight, and players not taking advantage of opportunities you present.
Not knowing what opportunities to highlight is easily solved by asking each player for a short list. Players missing cues could be miscommunication if you see something as a clear opportunity to show off a trait but it goes right over their head. In this case if a cue or two is missed, you can talk to the player about it. But of course there’s always the fairly common setup of a player describing their character one way then acting a completely different way in play. On the one hand that would seem to be a weakness of this system because a player that lacks follow through has problems showing the traits they wanted to make clear, but on the other hand it’s actually a strength since it forces players to put their money where their mouth is. You can’t just claim your character has a trait and then act completely opposite, which is where some of my distaste for the exposition dump comes from in the first place. If you don’t show it in play it doesn’t exist.
For the GM, this system isn’t that much extra work. You already have to plan elements to highlight other aspects of the game, this is just one more and it should overlap well with already existing work.
Resurrecting and delivering our indie game after 5 years - Part I: Birth of the studio - by Mauricio Perin
Drupal 8 is set to be released this week and it promises to be the best version of Drupal yet.
In these two videos, Rod will show you how to install Drupal 8 at your host or on your computer.
Drupal 8, a collective work of 3.3k contributors from 90+ countries, after more than a couple of years of development with more than 200 new features and improvements finally reaching a milestone and limelight. Tentatively 1232 companies have supported its development.
For Drupal specialized companies like KnackForge this is a momentous occasion. We are feeling excited about the release of Drupal 8. KnackForge is proud to join hands with Drupal Chennai Group and other Drupal shops in Chennai along with other Drupal groups around the world in hosting a release party on Thursday, November 19th, 2015!
We celebrate the party in honor to appreciate the great efforts of thousands of contributors all over the world! Let’s do it together!
Please sign up at Event posted on Groups.Drupal.org. Grab your Drupal 8 T-shirt for free. Limited offer only, please RSVP sooner.
This module is in alpha. Test thoroughly and use at your own risk.
This integrates a Google Search Appliance (GSA) with Facet API.
The GSA Faceted Search module adds the ability to create faceted search using anything that integrates with the Facet API, including Views.
The GSA Metatags module adds the ability to put data from Drupal fields into the the metatags of the node page, for use with the Google Search Appliance.
Administrators can configure which content types and which fields have faceting data exposed to the GSA, using metatags in a format the GSA can evaluate.
This module is usually used with the GSA Faceted Search module, which allows administrators to build faceted searches using the Facet API and Views.
This week's new video class is "Managing Multiple WordPress Sites With ManageWP".
Managing multiple WordPress sites can be a challenge. There are always updates, comments and more to deal with. ManageWP is a great solution.
In this class, Topher takes you through the basics that you get for free and shows the benefits of easy site maintenance that ManageWP brings to your workflow.
Drupal 8 the newest version of the Drupal content management system is around the corner and will be released Nov 19. PHP7 - the newest generation of the PHP language powering Drupal - will be released later in 2015.
PHP7 features lots of new things, but the most significant part is a 20-50% speed increase, which comes from the completely rebuilt Zend engine VM that powers PHP under-the-hood.
The new code is not only easier to understand, but also cleaner, faster and doing much less memory copying.
However as with all bleeding-edge software there are bugs and sometimes those bugs can be so tricky that during normal development they do not occur. In fact the bugs Drupal 8 found pushed the release date of PHP 7 back - http://news.php.net/php.internals/89102 - but more to that later in this post. So when should you switch?
Drupal 8 already early on had a plan to support PHP7 out of the box with Drupal 8. (https://www.drupal.org/node/2454439).
During that effort by several Drupal 8 contributors, bugs and segfaults have been reported to the PHP team (bugs.php.net) and also incompatibilities have been resolved in the Drupal 8 and Symfony 2 code bases.
For example Null, False, True, which had been classes in Symfony 2, are now reserved keywords. Or Drupal 8 used the String namespace, which also now is reserved. Also Drupal 8 had been relying on uasort behavior being deterministic (which it is not) - though some cases still remain: https://www.drupal.org/node/2466097.
In the end Drupal 8's test suite did almost pass on PHP7, but there were some remaining test failures. Drupal’s tests run on DrupalCI, which is hosted and fully integrated into Drupal.org itself, supporting PHP 5.3-7, MySQL, sqlite and PostgreSQL for both Drupal 7 and Drupal 8 core and contrib modules. As the core maintainers wanted Drupal 8 to ship with full PHP7 support and no known bugs and, because PHP7 stable release was one week before Drupal 8's release now was the last chance to fix that. So the issue became critical again.
With the help of a 10 hour Drupal 8 Accelerate grant (thank you very much Drupal Association), neclimdul, me (Fabianx) and alexpott embarked on a journey to track down and fix the remaining really really tricky test failures. (https://www.drupal.org/node/2603152, https://bugs.php.net/bug.php?id=70805 and https://bugs.php.net/bug.php?id=70808)
They succeed after close collaboration with the PHP internals team with me (Fabianx) providing the core developers with an EC2 instance, where the bug was easily reproducible and such the PHP internals team finally tracked down the bug in the garbage collector. I reported another bug with a script to reproduce ("array_merge_recursive corrupts memory of unset items") and it was fixed within 3-5 hours after posting the bug report(!).
And such PHP7 became green on Drupal CI on Oct 30, 2015 (https://www.drupal.org/pift-ci-job/73342).
Now with it being green an incentive was started to make PHP7 the default test environment (https://www.drupal.org/node/2607222).
This incentive lead to also testing Postgres and SQLite (and those environments are now available for testing) and while SQLlite passed (yeah), postgres failed with several strange bugs.
I followed up again with the PHP team, created two bug reports (https://bugs.php.net/bug.php?id=70861, https://bugs.php.net/bug.php?id=70862) and a pull request (https://github.com/php/php-src/pull/1619), which solved many of the issues and led to overall more stable PHP7 code base as it was a weird edge case (again!).
One issue is as of this time still remaining with postgres (https://bugs.php.net/bug.php?id=70866), but I am pretty sure that the awesome PHP team will track this one down, too. (Even though Drupal CI passes now, it still fails on my test machine.)
However as we still branch test Postgres with PHP 5.5 daily and that is stable, this will only affect a minority of the users and does not affect our ability to switch to PHP7 for general patch testing (with MySQL 5.5). As of now Drupal 8 has 100% test passes with PHP 7 and MySQL, PostgreSQL and SQlite (https://www.drupal.org/node/3060/qa).
Switching to PHP7 for patch testing will allow to reduce patch test time by around 30% (from 30 min to 21 min) and it will allow us to find potential regressions early. This should reduce the costs of the testing infrastructure to the Drupal Association significantly.Lessons learned
Drupal 8 and PHP7 is an open-source community collaboration success story with close collaboration of PHP with Drupal 8 and Drupal 8 with Symfony.
Drupal 8 was able to find many many strange bugs with its very extensive test suite and being a complex application itself. That made PHP7 more stable for everyone, as well as finding Symfony/PHP7 incompatibilities earlier than they might otherwise have been discovered
Being able to run Drupal 8 on PHP7 directly and know that it will work is a huge benefit to Drupal 8 itself. In fact I also switched over my own Drupal 8 development environment now to PHP7, which means I can test my code faster.
Running and switching your test suite to PHP7 not only will give you confidence that your application is well supported on the newest PHP version, but it will also give you beneficial speed improvements.
All of this means that Drupal 8 and PHP 7 will be viable for production more or less as soon as they reach stable releases, so that real sites can take advantage of the ~30% performance improvement relative to PHP 5.6.
Midwestern Mac, LLC: Celebrate Drupal 8 in St. Louis, MO on Nov 19 - Food, Drinks, and a Raspberry Pi!
On November 19, the St. Louis Drupal Users Group is having a party to celebrate the release of Drupal 8, which has been 4 years in the making! The party will be hosted at Spry Digital in downtown St. Louis, and will have beer provided by Manifest, food and drinks provided by Spry, and a Raspberry Pi 2 model B giveaway sponsored by Midwestern Mac!
Drupal 8.0.0 has been built by over 3,000 contributors in all corners of the globe, and will help kick off the next generation of personalized, content-driven websites. During the meetup, we'll build a brand new Drupal 8 site on the Raspberry Pi using Jeff Geerling's Drupal Pi project, and we'll highlight some of the awesome new features of Drupal 8.
After we build one of the first Drupal 8 sites, we'll give away the Raspberry Pi to a lucky winner to take home and tinker with! Special thanks to the Austin Drupal Users Group, who came up with the Pi giveaway idea!
We'll also eat, drink and be merry, celebrating the start of a new era of site building with the best version of Drupal yet!
If you'd like to join us, please RSVP on the STLDUG Meetup page: STLDUG Drupal 8.0.0 Release Party.
We just launched our first Drupal 8 website for the Northwest Atlantic Marine Alliance (NAMA). During our project retrospective, a few of us brought up how nice it was that so many contrib modules that were part of the D6 site weren’t necessary in Drupal 8 – this was a major factor in making it possible to launch... Read more »
Adds Transitions to Entity Registration, because States are fun, but not very user-friendly without Transitions.