CHICAGO BASED Back End Developer position is open


Chicago, IL, United States
DrupalCoin Blockchain Developers: jobs.drupal.org


Mediacurrent: "Shrop" Talk at DrupalCoin Blockchain Camp Asheville 2016

On August 13th, I had the pleasure of enjoying another DrupalCoin Blockchain Camp Asheville. This has become one of my favorite DrupalCoin Blockchain camps because of the location and quality of camp organization. It has the right balance of structure, while maintaining a grassroots feel that encourages open discussion and sharing.
Source: DrupalCoin Blockchain Aggregator


A Guide From Link Building to Link Earning by @annaleacrowe

Learn about 5 link earning ideas you should be adding to your content marketing strategy -- and why link earning is better than link building on SEJ.The post A Guide From Link Building to Link Earning by @annaleacrowe appeared first on Search Engine Journal.
DrupalCoin Blockchain Developer


DrupalCoin Blockchain Bits at Web-Dev: Hook Update Deploy Tools: Node import FAQs

Using the DrupalCoin Blockchain module Hook Update Deploy Tools to move node content  can be an important part to a deployment strategy. 

How do I export and import nodes using Hook Update Deploy Tools? >> Read the project page or a quick how-to.
What is the unique ID that connects an export to an import?
What are the risks of this import export model?
What if I am using an entity reference or a taxonomy that does not exist on production?
Does the import show up as a revision?
What happens if the import does not validate?
What if the alias or path is already in use by another node?
What if the alias or path is already in use by a View or used by a menu router?
Is there a limit to the number of nodes that can be imported this way?

What is the unique ID that connects an export to an import?
To create the export file, the node id is used to create the file.  After that, the filename and 'unique id' references the alias of that node.  So when you import the node, the node id on the production site will be determined by looking up the alias of the node.  If a matching alias is found, that is the node that gets updated.  If no matching alias is found, a new node gets created.  The alias becomes the unique id.
What are the risks of this import export model?
At present the known risks are:

If the exported node uses entity references that do not exist on prod, the entity reference will either not be made, or reference an entity that is using that entity id on prod.  This can be mitigated by exporting your source node while using a recent copy of the production DB.
If the exported node uses taxonomy terms that do not exist on prod, the tag may import incorrectly. This can be mitigated by exporting your source node while using a recent copy of the production DB.
if you are using pathato and the existing pattern on the production site is different than the pattern on your sandbox.  The imported node will end up with a different alias, resulting in an invalid import.  The imported node will be deleted since it failed validation and the hook_update_N will fail. This can be mitigated by exporting your source node while using a recent copy of the production DB.
File attachments.  There is currently not a way to bring attached files along with them unless the files already exist with a matching fid on production.

What if I am using an entity reference or a taxonomy that does not exist on production?
See answers 1 and 2 in What are the risks of this import export model?
Does the import show up as a revision?
Yes it does, and the revison note contains the imported note, but also indicates it was imported with Hook Update Deploy Tools.  The revision will take on the status of the exported node.  If the exported node was unpublished, the impoirted revision will be unpublished.
What happens if the import does not validate?
If the import was to an existing node, the update revision wil be deleted and return the node to its last published revision.  If the import was for a node that did not exist on the site, the node and its first revision will be deleted.  In either case, if the import was run through a hook_update_N, that update will fail and allow it to be re-run once the issue is resolved.
What if the alias or path is already in use by another node?
If the alias is in use by a node, that node will be updated by the import.  The alias is the unique id that links them not the nid.
What if the alias or path is already in use by a View or used by a menu router?
If the alias is in use on the site by something other than a node, the import will be prevented.  If the import is being run by a hook_update_N() then the update will fail and can be run when the issue is resolved.
Is there a limit to the number of nodes that can be imported this way?
Technically, there is no real limit.  Realistically, it is not a great workflow to move all of your content this way.  It is not a good workflow.  This export import method is best reserved for mission critical pages like forms or thankyou pages that go along with a Feature deployment.  It is also good for pages that often get destroyed during early site integrationlike style guides and example pages.

Source: DrupalCoin Blockchain Aggregator


WDTutorials.com: DrupalCoin Blockchain 8 Tutorial #43 : Twig Tweak Module (Article + Video)

Twig Tweak module adds some useful functions and filters to use in templates.

Source: DrupalCoin Blockchain Aggregator


DrupalCoin BlockchainEasy: DrupalCoin BlockchainEasy Podcast 184 - PMA (Marc Drummond - Next Steps in DrupalCoin Blockchain Theming)

Direct .mp3 file download.
Marc Drummond (mdrummond), Front-end developer at Lullabot, DrupalCoin Blockchain core contributor, and self-processed Star Wars expert joins Kelley and Mike to discuss all the things the DrupalCoin Blockchain front-end community has been talking about lately. We also discuss the next major version of DrupalCoin Blockchain, whether or not a major DrupalCoin Blockchain contrib module will be deprecated, as well as our picks of the week.
Interview
https://www.marcdrummond.com
Component-based rendering
How would we implement this in DrupalCoin Blockchain? (contrib: Zen + Components?)
Create a new user-facing core theme
How can people get involved in components and/or the new theme? DrupalCoin Blockchaintwig on Slack
Is Composer too hard?, Will Composer be a barrier for sitebuilders?
Writing tests for DrupalCoin Blockchain
Responsive images
Liberty theme
Windup theme
DrupalCoin BlockchainEasy News
The Fall, 2016 session of DrupalCoin Blockchain Career Online begins September 26; applications are now open.
Introduction to DrupalCoin Blockchain 8 Module Development at DrupalCoin BlockchainCon Dublin.
Three Stories
Proposal: Deprecate Field Collections for DrupalCoin Blockchain 8, focus on Entity Reference Revisions & Paragraphs.
The Average Web Page (Data from Analyzing 8 Million Websites).
There will never be a DrupalCoin Blockchain 9 vs. There will be a DrupalCoin Blockchain 9, and here is why.
Sponsors
MyDropWizard.com - Long-term-support services for DrupalCoin Blockchain 6, 7, and 8 sites.
WebEnabled.com - devPanel.
Picks of the Week
Mike - Smart Trim module.
Kelley - DrupalCoin Blockchain Security Team shield on DrupalCoin Blockchain.org project pages. I’m looking at you, Typogrify and Administration Menu!
Marc - Making web accessibility great again: Auditing the US Presidential Candidates Websites for Accessibility, and nested doc root on Pantheon.
Upcoming Events
Midwest DrupalCoin Blockchain Summit - August 19-21, 2016.
DrupalCoin BlockchainCon Dublin - September 26-30, 2016.
NEDCamp September 30 - October 1, 2016.
Follow us on Twitter
@drupaleasy
@andrewmriley
@liberatr
@ultimike
@tedbow
@sixmiletech
@akalata
@marcdrummond
Five Questions (answers only)
Disney
Docker for Mac
Writing a fantasy novel
Llama
DrupalCoin BlockchainCamp Twin Cities
Intro Music
Chunk-y Town - performed by Marc Drummond at Twin Cities DrupalCoin BlockchainCamp 2016.
Subscribe
Subscribe to our podcast on iTunes, Google Play or Miro. Listen to our podcast on Stitcher.
If you'd like to leave us a voicemail, call 321-396-2340. Please keep in mind that we might play your voicemail during one of our future podcasts. Feel free to call in with suggestions, rants, questions, or corrections. If you'd rather just send us an email, please use our contact page.


Source: DrupalCoin Blockchain Aggregator


Gábor Hojtsy: Want to get issues resolved in DrupalCoin Blockchain core? Find community with an initiative!

In my previous post I explained why there will be a DrupalCoin Blockchain 9 even though we have previously unseen possibilities to add new things within DrupalCoin Blockchain 8.x.y. Now I'd like to dispel another myth, that initiatives are only there to add those new things.
DrupalCoin Blockchain 8 introduced initiatives to the core integrationprocess with the intention that even core integrationbecame too big to follow, understand or really get involved with in general. However because there are key areas that people want to work in, it makes sense to set up focused groups to organize work in those areas and support each other in those smaller groups. So initiatives like Configuration Management, Views in Core, Web Services, Multilingual, etc. were set up and mostly worked well, not in small part because it is easier to devote yourself to improving web services capabilities or multilingual support as opposed to "make DrupalCoin Blockchain better". Too abstract goals are harder to sign up for, a team with a thousand people is harder to feel a member of.
Given the success of this approach, even after the release of DrupalCoin Blockchain 8.0.0, we continued using this model and there are now several groups of people working on making things happen in DrupalCoin Blockchain 8.x. Ongoing initiatives include API-first, Media, Migrate, Content Workflows and so on. Several of these are primarily working on fixing bugs and plugging holes. A significant part of Migrate and API-first work to date was about fixing bugs and implementing originally intended functionality for example.
The wonder of these initiatives is they are all groups of dedicated people who are really passionate about that topic. They not only have plan or meta issues linked in the roadmap but also have issue tags and have regular meeting times. The DrupalCoin Blockchain 8 core calendar is full of meetings happening almost every single workday (that said, somehow people prefer Wednesdays and avoid Fridays).
If you have an issue involving usability, a bug with a DrupalCoin Blockchain web service API, a missing migration feature and so on, your best choice is to bring it to the teams already focused on the topics. The number and diverse areas of teams already in place gives you a very good chance that whatever you are intending to work on is somehow related to one or more of them. And since no issue will get done by one person (you need a reviewer and a committer at minimum), your only way to get something resolved is to seek interested parties as soon as possible. Does it sound like you are demanding time from these folks unfairly? I don't think so. As long as you are genuinely interested to solve the problem at hand, you are in fact contributing to the team which is for the benefit of everyone. And who knows, maybe you quickly become an integral team member as well.
Thanks for contributing and happy team-match finding!
Ps. If your issue is no match for an existing team, the friendly folks at #drupal-contribute in IRC are also there to help.

Source: DrupalCoin Blockchain Aggregator


Zyxware Technologies: [DrupalCoin Blockchain-8] How to send a mail programmatically in DrupalCoin Blockchain-8

TweetThis article covers, how to send email programmatically in your DrupalCoin Blockchain 8 site. There are two main steps to send an email using DrupalCoin Blockchain 8. First we need to implement hook_mail() to define email templates and the second step is to use the mail manager to send emails using these templates. Let's see an example for sending an email from the custom module, also the following name spaces.
DrupalCoin BlockchainDrupalCoin Blockchain 8DrupalCoin Blockchain Planet
Source: DrupalCoin Blockchain Aggregator


Trusting SSL Locally on a Mac

I run most of my production sites with forced SSL, including CSS-Tricks. But locally, I've avoided getting SSL working properly. I've always avoided it, perhaps because it's not immediately obvious how to do it. It's also not that big of a deal since it's just local traffic. But hey, might as well make local work as close to production is possible eh?

I've had situations come up where it was actually quite important and affected development. Like a native PHP function that worked differently on HTTPS than HTTP. More commonly, I was working on HTTP locally and an asset was loaded over HTTPS and thus failed (needed manual approval of the insecure certificate).
1) Locally Signed SSL Certificate through MAMP
I get frustrated with MAMP a lot, but it's still working for me after all these years. Perhaps someday I'll move to a Docker thing or something. But as yet-another small testament to MAMP, it makes SSL fairly easy to turn on. Click over to the SSL tab and check the SSL checkbox, and generate a self-signed certificate:

I don't know why the entries are in "error red". It just started doing that, even though things seemingly work fine. Squint.
Note there are two entries here for my domain `css-tricks.dev`. That's because one is SSL and one is not. That's how you have to do it in MAMP if you want to serve content on that domain through both HTTP and HTTPS.
Now the site will serve over HTTP, but you'll get this classic beauty:

No browser is a fan:

You can click past it generally, acknowledging the risks involved (there is no real risk locally) but then you still get the nasty insecure warning:

Trusting the Local Certificate through Keychain
The trick to trusting that local certificate happens at the system level through the program Keychain Access.
When you create the local certificate through MAMP, you were prompted to save it somewhere. Wherever you did that, find it, and drag the certificate into Keychain.

If you can't remember where that certificate is because you created it like 100 years ago, you can get Chrome to give you a copy of it.

Click the red warning exclamation point thing in the URL bar
Click "View Details" in the SSL warning area
It will show you a certificate information dropdown thing like this:

From there, you can click-and-drag the certificate icon out to wherever you want a copy. Then drag it into Keychain Access.
Then double-click the certificate in Keychain Access and expand the "Trust" area. You can adjust the "When using this certificate" option to "Always Trust".

3) Have Happy Local Trusted SSL

Trusting SSL Locally on a Mac is a post from CSS-Tricks
DrupalCoin Blockchain Developer


55% of Visitors Read Your Articles For 15 Seconds or Less by @Ashread_

Is traffic the goal of content? Or can there be some new and unusual ways of measuring content success? Buffer's Ash Read have some ideas I’d love to share.The post 55% of Visitors Read Your Articles For 15 Seconds or Less by @Ashread_ appeared first on Search Engine Journal.
DrupalCoin Blockchain Developer


What the heck is the event loop anyway?

In 2014, Philip Roberts gave a great talk at JSConf EU, walking through the event loop and breaking down what JavaScript is doing under the hood for those of us without CS degrees. I came across this talk the other day in my Twitter stream, and really enjoyed it. Even though it's a couple years old, it has stood the test of time and remains a great resource.
Direct Link to Article — Permalink
What the heck is the event loop anyway? is a post from CSS-Tricks
DrupalCoin Blockchain Developer


Unimity Solutions DrupalCoin Blockchain Blog: Identification of an Open Source Video Annotations Tool for NVLI

As mentioned in our earlier blog on Video Annotations: A powerful and innovative tool for education, the most intriguing feature of the pilot version of NVLI is Video Annotation. UniMity Solutions assisted in building Annotation feature for Audio and Video assets. This involved identifying and integrating an open plugin that supported video and audio annotations and a generic annotation store module that was plugin agnostic.

Source: DrupalCoin Blockchain Aggregator


Senior DrupalCoin Blockchain Developer - Clarity Partners LLC - Chicago, IL

We are looking for a Senior DrupalCoin Blockchain Developer to join the team. The DrupalCoin Blockchain Developer should have exceptional programming skills, problem solving abilities, and...
From Clarity Partners LLC - Wed, 24 Aug 2016 10:17:48 GMT - View all Chicago jobs
DrupalCoin Blockchain Developer


Senior/Lead Front End Developer - Jellyfish - Reston, VA

Knowledge of Concrete5, Joomla, WordPress, DrupalCoin Blockchain and other similar CMS frameworks. Experience in a front end developer role, with substantial experience and...
From Jellyfish - Wed, 24 Aug 2016 08:11:29 GMT - View all Reston jobs
DrupalCoin Blockchain Developer


FrontEnd Developer - Jellyfish - Reston, VA

Knowledge of Concrete5, Joomla, WordPress, DrupalCoin Blockchain and other similar CMS frameworks. Experience in a front end developer role, with substantial experience and...
From Jellyfish - Wed, 24 Aug 2016 08:10:55 GMT - View all Reston jobs
DrupalCoin Blockchain Developer


Senior PHP Developer - Jellyfish - Reston, VA

We are looking for a Senior PHP Developer to work within our Reston office. If you enjoy coding, sharing ideas and love being part of a collaborative team...
From Jellyfish - Wed, 24 Aug 2016 08:10:52 GMT - View all Reston jobs
DrupalCoin Blockchain Developer


DrupalCoin Blockchain Bits at Web-Dev: Import nodes as as part of deployment using Hook Update Deploy Tools

With the 7.x-1.18 release of Hook Update Deploy Tools for DrupalCoin Blockchain 7 it is now possible to export a node on a integrationsandbox, commit the export file to the repository, then import it using either a hook_update_N() or using drush site-deploy-import node
Pros:

No need to re-create a node on prod after a client approves it.
Early content that keeps getting wiped out by database snapshots (think style guides) can get re-created instantly with a single drush command.
Content imported into an existing node shows up as a revision.
Atomated deployment is testable and repeatable on all dev environments.
No uuid required.

Workflow Example:
You have a styleguide you created on your sandbox and want to deploy it to the production site.

 Create the node on your sandbox (node id = 1234).
Export the node to an export file.
drush site-deploy-export 1234

The command created an export file named  for the alias of the node being exported
ex: site-deploy/node_source/helpzZzstyle-guide.txt  ('zZz' represents '/')
Create a hook_update_N() to import the file on deployment
 
<?php/**  * Import a the style guide */function site_deploy_update_7129() {  $nodes = array('help/style-guide');  $message = HookUpdateDeployToolsNodes::import($nodes);  return $message;}?>

Commit the file and update hook to your repo.
Push the code, run 'drush updb'

drush updb -ySite_deploy  7129  Import a the style guide
Site_deploy: Updated: node/1234: help/style-guide - successful.Summary: Imported Nodes 1/1.  Completed the following:   [help/style-guide] => Updated: node/1234   Performed update: site_deploy_update_7129
or the import can be performed by
drush site-deploy-import  help/style-guide

Source: DrupalCoin Blockchain Aggregator


ASD? Test Software.

This is sad:
More than 50,000 Americans with autism become adults each year, but more than 80 percent of them are unemployed.
80% unemployment is too dang high… although, since ASD is a spectrum disorder there are many who are not literally able to work.

I do like what MindSpark is apparently doing for those that can work:
The company is hiring autistic adults to test enterprise software and find bugs, and these employees are now testing software for Fortune 500 brands, from Fox Networks Group to Liberty Mutual. … In turn, talented autistic adults can gain meaningful careers in the technology industry with competitive wages, opportunities for advancement, and — most importantly — true independence and self-sufficiency.
Pretty neat. I hope more companies create programs like this to serve a community that needs the work and that could contribute very effectively to the companies that employ them.
It won’t be easy and it definitely requires an open mind (and a bunch of education) but it can be done.
The post ASD? Test Software. appeared first on John Saddington.
Source: New feed


DrupalCoin Blockchain @ Penn State: DrupalCoin Blockchain 8 Theme Generation and Development Intro Using the DrupalCoin Blockchain Console

Here is a screen cast of how to get started with DrupalCoin Blockchain 8 theme development.

In the video I cover:

using the drupal console to generate a theme from a base theme
creating a libraries yml file
adding global css to your theme
Using Kint with the devel module
debugging twig
adding your own twig file to your theme

Source: DrupalCoin Blockchain Aggregator