All RPGs and Storygames by Tod Foley are now available at DrivethruRPG and RPGnow. Bring these games to your table!
Do you know how much enterprise companies spend on their website annually? What makes their website great? I mean there is obviously the high traffic, better bounce rates and over the top numbers, but is that all?
This module helps in searching the data from multisites using search_api_solr.
The backend uses, like the popular Apache Solr Search Integration module, Apache Solr servers for indexing and searching content.
The Search API module
Search API Solr
The module creates a block that has a form with autocomplete field searching the data from selected solr server.
The different sites should be configured with the same core to fetch the results.
We are organizing the biggest Drupal event in Europe in 2018 with a group of community volunteers in collaboration with the Drupal eV (German Drupal Association) and the Drupal Europe Foundation. We’d like to update you on our progress and turn to you for input.
Mark your calendars for September 10–14, 2018 when Drupal Europe will be held in the beautiful Darmstadtium in Darmstadt, Germany. This is a great venue for the conference and only a 20 minutes’ drive from Frankfurt Airport. We just had our second walkthrough last week discussing details with the venue and were impressed.Photo by Baddy Breidert @baddysonjaBuy your Early Supporter ticket now!
We are now selling Early supporter tickets for 380 EUR (including VAT). Only 300 of these tickets are available, and only for a limited time. Buy now at https://www.drupaleurope.org/#ticketsA new logo
Thanks to all designers we worked with who came up with such great ideas for our branding! We are delighted to release our final logo proudly crafted by sixeleven. Drupal Europe stickers (pictured here) will be available at various Drupal events where our team shows up in the coming months.Latest on the conference schedule
We are continually looking at how to structure the biggest Drupal event in Europe, and based on exploratory discussions with community members, we believe we are on the right track.
First of all we strongly believe contribution is at the heart of the Drupal project. Figures show that over 44% of Drupal contributors are in Europe. Therefore, in our programme we want to give you more time to contribute by making both Monday and Friday contribution days (formerly called sprints). Mentors will be available on both days to help those new to Drupal contribution.
We are structuring the rest of the event between Tuesday and Thursday on the successful summit model that has worked well at the start of DrupalCons and other regional events. Topics will include government, education, publishing, technology, and community. We are looking for sponsors for each to make possible to put them on.
And the great news is that your single Drupal Europe ticket will give you access to all these workshops, panels and discussions.We want to hear from you
Although we have plenty of ideas, we realize that this is your conference.DrupalCON Amsterdam Group photo
Please help us understand you, our audience, better by completing our survey. It should only take 8 minutes or so and still give us lots of valuable insight. While not all questions are mandatory, we added a few open questions to get to know you better.
Thank you, and please share our survey with all your Drupal friends and colleagues to help us make Drupal Europe a success.
See you in September!
The Exit Pop UP Module help you to convert the leaving visitor for your traffic and help yo to grow your business and engaging visitors. Whenever user tries to leave your site a pop up will appear displaying offer, or anything that you would like to display.
The module comes with full customisation feature all you need to write your own custom html template and css code.
This module will rewrite the output of the picture module so it can be better integrated with patternlab. The picture module constructs its html inside a theming function, this module will expose all needed variables to the template.
It extends the picture field formatter to provide a modifier which gets exposed as theme-suggestion and the possibility to select a different image for a specifc breakpoint.
This module allows admin to ban the website from specified country code.
Unofficial integration module with SDK of the LINE Messaging API for PHP.
The Messaging API allows for data to be passed between the server of your bot application and the LINE Platform. When a user sends your bot a message, a webhook is triggered and the LINE Platform sends a request to your webhook URL. Your server then sends a request to the LINE Platform to respond to the user. Requests are sent over HTTPS in JSON format.
Paizo Announces Partnership with Roll20: Virtual Tabletop Coming for Pathfinder and Starfinder Roleplaying Games
The GDC 2018 Producer Bootcamp on Tuesday, March 20th is going to be a fantastic day-long learning opportunity with a ton of expert sessions on the ins and outs of being a great producer in game dev. ...
This, the first 'universe book' for Amazing Engine should be used in conjunction with the System Guide, the combination making a complete game.
It opens by describing the alternate history of the setting, a Victorian England where the fey do not only exist, they have seats in Parliament and are invited to all the best parties. This all dates back to Roman times if not before, but at that time the dark powers of the Unseelie Court were defeated in a great battle, and from then faerie blood has mixed with that of human beings throughout the history of Britain. Needless to say, the Unseelies haven't gone away, they've just gone underground, and still cause problems upon occasion although due to their appearance they have to recruit and operate through human allies and agents.
History has taken a largely similar track to the real world, although a descendant of Napoleon rules in France, a foil to Bismarck in Germany, and the big surprise, America is still a colony of Britain having been defeated in 1812 after their brief flirtation with independence. Fey live openly in Ireland, having an enclave named Tir Nan Og that operates as a separate country - or is that countries, as each sidh or barrow has its own British Embassy! Many challenges face the British Empire at this time. This opening portion, The State of England, is presented as a report suggesting the provision of 'special agents' to troubleshoot any problems... and this is where the player characters come in.
The role of both player characters and the GM are briefly touched upon and then the matter of creating player characters based on the existing player core (as detailed in the System Guide) is dealt with in detail. The first thing you have to determine is whether or not your character has fey blood - there's quite a high chance of having at least some, although full-blooded fey are quite rare. There are usually some visible hints of fey blood such as a greenish tint to the skin, pointy ears - or maybe hooves instead of feet. The more fey blood the character has, the more noticeable it is. Apart from full-blooded faeries, you next need to choose nationality. This determines where you come from and the language(s) you speak - apparently everyone from Wales speaks Welsh, which certainly wasn't the case in real Victorian England (in fact, the Welsh language was discouraged!). Next up in social class and occupation. These choices lead to background and to the skills available to that character. Naturally there is plenty of information to aid an informed decision. Much is (mostly) historically accurate, but magic exists and so sorcerer is an established profession.
Setting-specific notes on awards and experience follow material on wealth and resources. Many genuine Britsh awards and medals are listed here. Next up is magic. In this setting, magic works rather like a recipe, with a magic formular being constructed like a sentence including the action, the target, special conditions and so on. Each part has a range of options, this results in every spell cast having the potential, indeed likelihood, of being unique. The best spells are researched in advance, but they can be created on the fly although the chances of success are lower. A skill check is necessary every time a spell is cast, and it takes a physical toll on the caster. There are guidelines and examples aplenty, but spell-casting is something that the player will have to work at, there's no handy spell list to pick a spell from and just cast it as needed.
The next section, By All That is Holy, deals with religion. Faeries are pagan, it's somehow so deeply embedded in their being that they cannot embrace any other religion. There are various Christian denominations - based on real ones although with different names - and it is in their clergy that divine power is concentrated, although they do not cast spells as such but have certain powers that they can wield. No other faiths are mentioned, not is there any detail on what being a pagan entails.
This is followed by a section on Combat. Here we read about violence and the law, along with a note that combat is by and large deadly and ought to be avoided whenever possible. Much fighting is little more than brawling - mostly fistfights, perhaps a knife. Gun crime is rare, although a prudent fellow may take a pistol when entering a situation about which he is nervous. There's plenty of detail on both firearms and melee weapons.
We then turn to details about the fey, presented as Peak-Martin's Index of Faerie, a series of lectures to the Royal Academy of Sciences in 1877. It makes for fascinating reading, categorising the different varieties of fey folk and classifying them... and providing game statistics so that they can be used as opposition! For those who want to know more about the geography of the setting, there is also Crompton's Illustrated Tourbook of Great Britain, a quite comprehensive gazetteer. Back to everyday life, The Glorious British Life provides ample detail on what it's like to live in this setting: time, money, incomes, city and country life... and even how much you ought to be paying your servants! Modern conveniences, or the lack thereof, are discussed, along with price lists for the things characters may require and details of transportation - rail between towns, carriages or horseback within them, or out in the country once you have alighted from your train. The current state of knowledge and the policical scene are also covered, along with foreign relations and law enforcement. Much of this is historically-accurate, but with a distinctive spin on things to reflect the differences between this setting and historical Victorian England.
There's a rather entertaining guide on How to Speak Proper, which seems to be mainly aimed at Americans. This covers not just "the Queen's English" but Scottish and Irish dialects and a somewhat bizarre attempt at Welsh (which, it must be said, is my native tongue), claiming that Welsh words are unpronouncable... Best to move on to the underworld slang section. There's also a note about the role of women in Victorian times: strange to modern attitudes but historically accurate. Likewise, provision for the poor and disabled - mostly woefully inadequate by modern standards - charities and leisure pursuits are also covered. Various leading Victorians are introduced, perhaps the party will bump into them, or they will at least know about them.
The setting, then, is well presented with as much historical accuracy as the introduction of the faerie folk permits. Character creation is a bit clunky, but once you have built the characters and formed the party there's an impressive amount of background to set the scene in which they will operate. The GM, however, is left to come up with adventures. Some of the background might suggest ideas, but nothing is provided in the way of suggestion or plot idea, although the setting is good.
After my article about Drupal Development Environments, we had some discussions about the differences junior developers see when using Drupal and PHP applications locally, compared to React and other front-end tools. Someone mentioned how easy it was for them to get started by running yarn serve in a React project, and I was curious how close to that we could get for Drupal.
To make this a fair comparison, I’m not including managing MySQL databases and the like. Most React apps don’t use a database directly, and if you do need to run backend services locally, the complexity goes way up. In between writing and publishing this article, Stranger in a familiar land: Comparing the novice's first impression of Drupal to other PHP frameworks was published, which constrained itself to using the Drupal GUI installer. I think this guide shows that we can run Drupal locally in very few steps as long as we don't force ourselves to use a GUI.
I also wanted to see what the “new laptop” experience was like. I’ve been migrating my macOS setup between computers for nearly 15 years (if only Windows worked as well!), and it’s easy to forget what exactly is built in and what I’ve added over time. So, I installed a fresh copy of High Sierra in VirtualBox to ensure none of my terminal or Homebrew customizations were giving me a leg up.Installing Composer
We need Composer to install Drush. Change to the drupal directory in the terminal (cd drupal), and run the Composer installation instructions to download composer.
When composer is done, you will have a composer.phar file in your Drupal directory.undefined Installing Drush and Drupal
Drush is what will let us easily run Drupal using the built-in PHP webserver. It’s also required to do the initial site installation. Pull Drush into your Drupal site by running:
$ composer require drush/drush
This will not only pull in Drush, but it will also install all of the other libraries Drush needs at the same time.
Once Drush is installed, we have to use it to install Drupal. Drupal does have a graphical installer, but Drush won’t run the PHP webserver unless Drupal is already installed. The most important parameter is the database URL, which tells Drupal what database server to use and how to connect to it. We’re going to use SQLite, which is a simple single-file database. We don’t want the database file itself to be accessible from the web server (in case it’s ever exposed to respond to external requests), so we tell Drupal to put the database in a directory above our Drupal document root.
$ vendor/bin/drush site-install --db-url=sqlite://../drupal.sqliteundefined
When the installation is done, Drush will tell you the administrator password. If you ever forget it, you can reset it by generating a login link with drush user-login.Running the Drupal Web Server
To start the web server, use the run-server command:
$ vendor/bin/drush run-server
By default, the server will listen on http://127.0.0.1:8888. Run vendor/bin/drush help run-server to see how to change these and other defaults.
Finally, open that URL in a browser. You should see the Drupal 8 home page and be able to log in with the administrator account shown earlier. Press CTRL-C in the terminal to shut down the web server.undefined
The default macOS PHP configuration is pretty good, though it sets a very low limit of 2MB for uploaded files. If you need to raise it, copy /etc/php.ini.default to /etc/php.ini with:
sudo cp /etc/php.ini.default /etc/php.ini
Then, edit it with sudo nano /etc/php.ini to change settings as you see fit. You will need to restart the Drush web server after changing this file.Bonus: Installing Git and Cloning Drupal
I like to use git even for basic testing because I can run git status at any time to see what files I’ve changed or added. I opened the Terminal and ran the git clone command copied from the Drupal project page.
$ git clone --branch 8.5.x https://git.drupal.org/project/drupal.git
The first run of this command prompts to install the developer tools:undefined
After they install, you need to rerun the git command again (which is accessible by pressing the up arrow on your keyboard).
When this initial clone is done, you will have a Drupal 8.5.x checkout in a folder called “drupal,” and you can go back to the earlier steps to install and run Drupal.Next Steps
Now that you have a running Drupal 8 site, it’s easy to try out contributed modules or new experimental modules without worrying about breaking a real site. It’s easy to run a “clean” instance of Drupal 8 later, by reinstalling the current site with drush site-install, or by creating a new Drupal git clone separate from the first one. And, if you are evaluating Drupal and decide to use it for a real website, you can set up a better development environment without having to learn Composer and Drush at the same time.