Skip to Content

Planet Drupal

Syndicate content
Drupal.org - aggregated feeds in category Planet Drupal
Updated: 16 hours 12 min ago

Drupal Association News: Announcing Our New Drupal Co-Marketing Initiative

14 April 2015 - 8:35am

Marketing is a key factor to growing Drupal adoption and spreading the goodness of Drupal. One way to do that is by exhibiting at key industry events. The CMS Garden team has done a great job getting Drupal included in some key events in Europe and now the Drupal Association will take on a parallel effort.

The initiative will be an experimental “co-marketing” campaign to promote Drupal in the European marketplace. It is called a “co-marketing” campaign because it will be crowdfunded by a group of Drupal businesses (if you would like to find out how your Drupal business can get involved, keep reading). This is a pilot program that will allow us to experiment with the best ways to promote Drupal in the global marketplace and reach the CMS evaluator audience.

Why Europe? Data from our DrupalCon surveys show that relative to DrupalCon North America, DrupalCon Europe has a higher percentage of developer attendees but a lower percentage of CMS “evaluator” attendees. From that standpoint, it makes sense to target Europe evaluators in this pilot program. The evaluators we are targeting in the pilot program are digital marketers who have significant sway over CMS selection.

So what’s the plan?

This year, Drupal Association will secure exhibit space at two European digital marketing industry events (dmexco in Germany and Festival of Marketing in the UK). We will exhibit as Drupal and together with representatives from the anchor sponsors who have already signed on (including Wunderkraut (Germany), Wunder (UK) and Deeson (UK), we will promote Drupal and the sponsoring companies’ expertise and successes with Digital Marketing and Drupal. Leads generated from the exhibit presence will go to the sponsoring companies. We are offering first right of refusal to sponsor the effort to Drupal Premium Supporting Partners, followed by other Supporters.

Why these two events? There are many events in Europe that target the audiences we want to reach. After researching attendee types, costs and other factors, we determined the abovementioned events make the most sense for this pilot project.

If you would like to learn more about how your business can participate in this exciting initiative, please contact Johanna Bergmann. johanna@association.drupal.org.

Categories: Drupal

Blink Reaction: Free as in Training. Blink Launches Free Drupal Training Initiative

14 April 2015 - 7:43am

Blink Reaction has announced it has begun to offer free live public Drupal training online, in NYC and in other major markets.The free classes will focus on Drupal 8 adoption and will include Site Building classes formerly offered at $799.

Announcing the decision to offer free Drupal training, Blink CEO Nancy Stango explained the decision.

Building a robust Drupal ecosystem requires attention to all the things. We can’t just build great software. For many people formal training is the best way to learn and we need to lower obstacles to Drupal adoption everywhere. Providing this training free of charge on a regular schedule is part of our contribution back to the community.

Included in each free class listing is an appeal to support the Drupal Association by becoming a paid member.

Why is this class free?

Providing this class free of charge is one of the many ways we give back to the open source community. 

Blink is highly committed to helping organizations and individuals adopt Drupal successfully. At Blink we believe great training helps create great, results-oriented websites. That's a win-win-win for you, Drupal and Blink.

Please consider supporting the Drupal Association instead. Individual membership is only $15.

And if you’re interested in Developing for Drupal 8 register for our Drupalcon LA class, ‘Introduction to Symfony/Getting Ready for Drupal 8.’ Half of all proceeds goes to support the Drupal Association.

Blink has been delivering paid public training since 2011 through the Blink Institute and has offered free training during Global Drupal Training days since the start of the program. 

Visit our training pages for more information and to register for a free training.

If you’re interested in Developing for Drupal 8 register for our Drupalcon LA class, ‘Introduction to Symfony/Getting Ready for Drupal 8.’ Half of all proceeds goes to support the Drupal Association.

 

DrupalDrupal PlanetDrupal TrainingPost tags: Trainingdrupal 8
Categories: Drupal

Blink Reaction: Introduction to Symfony/Getting Ready for Drupal 8 Training at Drupalcon LA

14 April 2015 - 7:19am

After making it’s first Drupalcon appearance to a sold out crowd in Austin, I’m really excited to be offering an updated version of our class in LA. 

Since Austin we’ve offered the class in Drupalcon Amsterdam and Drupalcon Bogota. Each time it has been filled to capacity and tickets are already going fast for Drupalcon LA.

This year we’ve focused even more on the Symfony components that are most important for developing in Drupal 8.  We’re spending additional time in Drupal 8 too since we are oh so close to a release. 

The class will be led by Blink Drupal 8 Solutions Engineer Jesus Olivas, lead contributor on the Drupal Console project supported by Blink. Jesus will also share some of the latest new features he's built in the Console project. No fewer than eight Blink developers will be supporting Jesus so that we can give each and every participant a hands on experience.

Register for the class now on the Drupalcon LA site.

DrupalDrupal PlanetDrupal TrainingPost tags: drupal 8symfonyTraining
Categories: Drupal

Tag1 Consulting: Drupal Changed My Life - Will You Take My Drupal Commit Challenge

14 April 2015 - 7:00am

I want to share two stories with you.

read more

Categories: Drupal

Drupal Watchdog: VIDEO: DrupalCon Amsterdam Interview: Holly Ross

14 April 2015 - 6:58am

On a beautiful summerlike day at DrupalCon Amsterdam, we stop at the Drupal Association table, where we are introduced to DA Staff Members JOE SAYLOR, LEIGH CARVER, and RUDY GRIGAR. Then it’s on to HOLLY ROSS (Executive Director, Drupal Association). Erudite cameraman BOB WILLIAMS (Financial Manager, Tag1 Consulting) works the GoPro.

HOLLY ROSS: Yep, so we had a BoF for people who like to knit and are at DrupalCon and it was really great because we all worked on our projects, and we all talked about how we learned to knit. And what I love the most about the fact that there are so many knitters in Drupal is that – I love the relationship between knitting and coding – right? -- like pattern discernment and building – and all the things we talk about that we love about Drupal – it’s all there in knitting, too.

This one is really interesting to me because – well first of all, I’ll just share that we have 2,300 people here – 500 more than Prague. That’s a lot bigger.

What I am reading right now actually is a book called The Last Ship. I don’t recommend it – I hate it – it’s taking me months to read. I’m also concurrently reading a couple of Cory Doctorow books, because I was getting ready to come here and see Cory speak, so I’m reading Little Brother, which is a young adult novel he wrote, which is really really good. And I’m also reading right now, the uh – oh, what’s it called when all the people go to heaven except the bad people that are left on Earth?

RR: Left behind?

BOB WILLIAMS: The Rapture.

HR: The Rapture of the Nerds, that’s it, The Rapture of the Nerds, yeah.

Tags:  DrupalCon DrupalCon Amsterdam Video Video: 
Categories: Drupal

ERPAL: 3 things to consider when creating project specifications

14 April 2015 - 3:45am

In the last part of our series, we talked about "Agile work at a fixed price". We realized that detailed requirements in terms of a project specification are the key to agile management of fixed-price projects. Today, we’ll deal with those project specifications.

A “specification” describes the results or certain milestones of a project. Thus, it defines what we have to measure in order to find out whether the project is finished, that is: either the requirements are fulfilled – or they’re not. This point harbors the greatest potential for conflict! Neither restrictive contracts nor other contractual pieces of art can help here. Only when both parties know exactly what has to have been implemented by the end of the project, can you:

  • Show, prove, demonstrate and understand that everything that should have been done has actually been done
  • Check whether a new request is indeed new during the project
  • Find out whether changes have negatively affected the software (change management and risk management)

Using some negative examples of a specification, I’ll try to demonstrate what to avoid during a project.

1) Avoid ambiguous wording in your specifications

"We integrate social media functions." What does that really mean? The developer may understand this to include a Facebook Like button, a Google +1 button and a Tweet this button. In fact, what the customer would like is to have a portal for his Facebook app. It’s purely a matter of interpretation what social media functions really are and how they should be integrated. Always check that your requirements are clear and without ambiguous wordings.

2) Avoid comparisons

"We implement web pages with the same functions as those of awesome-competitor.com." No one knows exactly which functions the competitor’s websites possess in detail. Here again, two different expectations would collide at the end of the project. As provider, you don’t know for sure what features are implemented in the backend. However, if you agree to the statement above, then you must provide these functions. Arguing after the fact with statements like "But I didn’t know that..." doesn’t suffice. The extra costs can be enormous! So, avoid comparisons with other systems in your specification. This might save time in the beginning, but at the end of the project one of the parties could have over twice the expected expenses, which would no longer be controllable.

3) Write clear definitions

"We import the current data of the previous software." The data format for new software is usually not the same as for the previous version. Here, it’s important to clarify how the import should take place. Which old fields should be mapped to which new fields? Which validations should be processed, and, most importantly, what does the data format of the previous version look like, exactly, and how can you get this data and map it to the new structure? Clarify these points up front in order to avoid explosive increases in the effort required. In this case, it’s hard to argue using experience from past projects, because it implies that imports in previous projects are similar to the case at hand, which may be true – but usually isn’t. "We implement ... according to the usual ..." What’s usual here and who defines what’s normal? Make absolutely clear that both parties are talking about the same thing. Otherwise, two worlds will again clash over their differing expectations, which can be difficult to reconcile. Instead, refer to or quote the text that clearly defines "... the usual ..." and the requirements. Then everyone involved knows what the wording means.

There are countless other formulations that you should avoid. However, the above are the most common. A detailed engineering of requirements is always a good investment for both project parties to provide a solid basis for project success. Additionally, relevant user stories with related acceptance criteria can help to clarify the project deliverables.

Incorrect specification happens!

Specifications are wrong if they don’t serve the overall project goal. A short example: the sales manager of a company orders an app to support the sales team. The software is developed according to his requirements. However, it can’t be imported because no one involved the sales team and asked them for their requirements. Take the conditions of each case into account: nothing is more dissatisfying for both sides than fully-developed software that can’t be used because it doesn't deliver value to the users or the company as a whole. You should pay attention to these conditions right at the start of the project, both as a supplier and as a customer. During the analysis of requirements, involve all the stakeholders. Finally, the specification also serves to keep the documentation effort low, because it has already described what the final product looks like. It also provides for good planning and systematic change management to ensure that the software is stable. Imagine you’re building a house and want to combine the kitchen and the living room. For this, you only need to remove one wall. However, if this is a load-bearing wall, the floor above will collapse onto your head as the whole house caves in. This should be prevented at all costs, so be attentive and take all the challenges listed into account!

In the next part in our series, we examine responsibilities and communication in projects.

Other blog posts of this series:

These 3 questions help you to ensure satisfactory project results

Setting objectives in projects with these 3 rules

Agile projects for a fixed price? Yes you can!

Categories: Drupal

Steindom LLC: Sorting a view by a list field's allowed values

14 April 2015 - 2:52am

There's a neat feature in MySQL which lets you sort a result set by arbitrary field values. It's the ORDER BY FIELD() function. Here's how to leverage this in your Drupal views.

Let's say you have a field in your Article content type called Status, and it has the following allowed values:

Draft
Pending Approval
Published
Postponed
Canceled

It can be very helpful to sort the articles by status. You could key your allowed values with alphabetical prefixes, numbers, etc. But let's say you didn't. Or don't want to.

With bare MySQL, the query would look something like this (not an actual Drupal query, but used to illustrate how FIELD() works):

SELECT *
FROM articles
ORDER BY FIELD(status, 'Draft', 'Pending Approval', 'Published', 'Postponed', 'Canceled')

This is now possible in Drupal & Views with the Views List Sort module, which creates a sort handler that populates the FIELD() sort with the allowed values of a given "List (text)" field.

To use it is easy, just add the "List (text)" field to your sort criteria, and set "Sort by allowed values" to "yes".

Submitted by Joel Stein on April 14, 2015.Tags: Drupal, Drupal 7, Drupal Planet
Categories: Drupal

J-P Stacey: Safe, performant generation of a unique Drupal username

14 April 2015 - 1:53am

There are examples out there for generating a unique Drupal username. The usual technique is to continue incrementing a numeric suffix until an unused name is found. There's also a project to automatically generate usernames for new users. All of this makes sense and works, but compared to the existing solutions, I wanted one that focussed on encapsulation and stability; by which I mean it should:

Read more of "Safe, performant generation of a unique Drupal username"

Categories: Drupal

Drupal @ Penn State: Install ELMSLN on Digital Ocean in one line

13 April 2015 - 4:06pm

This screencast shows how you can use a cloud provider like Digital Ocean to install a working copy of ELMSLN by copying and pasting the following line into the terminal:

yes | yum -y install git && git clone https://github.com/btopro/elmsln.git /var/www/elmsln && bash /var/www/elmsln/scripts/install/handsfree/centos/centos-install.sh elmsln ln elmsln.dev http email@elmsln.dev yes

Categories: Drupal

Gizra.com: Shoov - CI tests on the live site

13 April 2015 - 2:00pm

Shoov keeps evolving, and now has an example repo that demonstrates how we're trying to make UI regression simpler, we took some time to implement the second feature we were missing - automatic testing on the live site.

We saw a very strange situation everywhere we looked: Dev teams were writing amazing test coverage. They were going the extra mile to setup a Travis box with environment as close as possible to the live site. They tested every single feature, and added a regression test for every bug. Heck, every commit triggered a test suite that run for an hour before being carefully reviewed and merged.

And then the site goes live - and at best they might add Pingdom monitoring to check it's working. Pingdom at its simplest form sends an http request every minute to your site. If the answer is 200 - it means that all is good in the world. Which is of course wrong.

Our mission is to change this, and bring functional testing to the live site. One that is easy to setup and that integrates with your existing testing and GitHub flow.

The Drupal backend holds the CI build data, including the full log, and status

While Pingdom is wonderful and is alerting us on time whenever a site goes down, its "page is fine, move along" approach doesn't cut it for us. Here are some examples why testing on the production server is a good idea:

Continue reading…

Categories: Drupal

Drupal @ Penn State: We stole this site, you should too

13 April 2015 - 12:56pm

Welcome to the new Drupal @ PSU!

We hope you enjoy the site so much that we want you to have it. No really, go ahead, take it. Steal this site. We did, and we’re proud of that fact. This site is actually a fork of the Office of Digital Learning’s new site that just launched recently.

Categories: Drupal

Mediacurrent: Drupalcon LA - Mediacurrent’s Gameplan

13 April 2015 - 12:02pm

We’re gearing up for Drupalcon 2015 in sunny Los Angeles and we are looking forward to the exciting plans we have in store. We are Platinum sponsors once again and there are a ton of ways to connect with our team. In fact, here are the highlights:

Categories: Drupal

LevelTen Interactive: DrupalCamp PHX Session: Drupal as an Inbound Marketing Platform

13 April 2015 - 11:32am

A few weeks ago, Brent Bice attended DrupalCamp PHX to host a session on Drupal as an Inbound Marketing Platform. The video of the PowerPoint presentation of the session, along with audio were made available for everyone to visit and listen to this session.... Read more

Categories: Drupal

Liran Tal's Enginx: The Drupal Rap song – Everyday I’m Drupalin’

13 April 2015 - 10:26am

This YouTube video doesn’t need any further explanation beside it’s title: The Drupal Rap song – Everyday I’m Drupalin’

 

 

 

Lyrics:

Chorus
Everyday I’m drupalin

Verse
Where them forms you gettin fapi with I’m the fapi boss/ hookin into edit form and webforms is my specialty sauce/ I’ll hook form alter by form id’s or entities/ put a list on Ajax/ just to keep it callin back/

I got them distrobutions, I’m like acqia/
Check my public repos, I didn’t copy nuttin/ I know dries n webchick, I kno Ryan szrama/ all the commerce guys we hipchat when they got some drama/
Might not be pretty code but it gets me paid/ I’m using rules like php loopin through arrays/ I put it all in features, so the code is stable/ it might take longer, but next time I just click enable/ These dudes clearin caches, on every hook init/ queries by thousands, page loads by the minutes

Verse
No matter the language we compress it hard/ drugs cc all, we just drugs cc all/
Where’s all of the changes, you never saw/ so drush cc all, we just drugs cc all/ I lean heavy on smacss, compass compilin my sass/ you just installed flexslider now you teachin a class/
I seen your content types, I don’t need to kno you/ to know that we ain’t even in the same nodequeue/
I’m on drupal answers, check my reputation/ I’m on my tablet earnin karma while I’m on vacation/ ya girl like a module, she stay hookin n/ you couldn’t code an info file, without lookin in/
Mo scrums, equals better sprints, break the huddle, n the work begins

Thanks to New Valley Media for helping with the video http://www.newvalleymedia.com/
Thanks to Broadstreet Consullting http://www.broadstreetconsulting.net

(adsbygoogle = window.adsbygoogle || []).push({});

The post The Drupal Rap song – Everyday I’m Drupalin’ appeared first on Liran Tal's Enginx.

Categories: Drupal

Drupal Association News: Drupal Newsletter: Jobs, Events, News, and Conversation

13 April 2015 - 9:58am

A long, long time ago—7 years, if you remember—the Drupal Newsletter faded away. On March 26th, the Drupal Association rebooted it. The community does so much that we want to share.

We partnered with TheWeeklyDrop to bring blog posts, articles, podcasts, and more to your inbox. Now, once a week, we’re taking all the effort out of keeping up with the best in Drupal news and events.

The fourth issue hit more than 32,000 inboxes on April 9. Inside it, subscribers from all around the world found Drupal 7.36 and Webform 7.x-3.24 releases, an introduction to D8Upgrade.org (a service offering advice for when you should upgrade to Drupal 8), and more.

To get the newsletter, subscribe via your Drupal.org profile.

The (Renewed) Drupal Newsletter

The Drupal Newsletter will be an opt-in-only thing. Once you’ve subscribed, you’ll get the newsletter in your inbox once a week, every Thursday, at about 06:30 PT / 13:30 GMT.

What kind of content will you get?

  • Drupal 8 progress updates
  • Jobs, so you can find work (or people who get work done)
  • Tutorials, guides, and podcasts
  • Events throughout the community
  • Projects and releases
  • News and conversation

It’s all brought to you by TheWeeklyDrop and us, the Drupal Association. It’s content hand-picked by humans, not bots or aggregators. You’ll get an uncluttered, distraction-free snapshot of the latest from the Drupal community. (Though we could be swayed by community vote to add gratuitous pictures of cats.)

It’s Like the Amazon Dash Button

Ok, no, it’s not. That’s not true. Unless you want it to be, in which case it sort of is.

Subscribe and never run out of the latest news, announcements, and innovations from the Drupal community. We made an animated gif to show you how.

  1. Log in to your Drupal.org profile <www.drupal.org/user>.
  2. Choose Edit.
  3. Scroll to the bottom, to the Subscribe to section.
  4. Check the box next to Drupal Weekly Newsletter.
  5. Hit the Save button.
Keep Up with the Drupal Community

The Drupal Newsletter is the easiest way to keep up with the Drupal community. Don’t already have a Drupal.org account? Create your profile today.

Oh, and two more things:

  1. Please add newsletter@drupal.org to your address book as an approved sender, so the newsletter doesn’t get lost in a pesky spam folder.
  2. Tell us what you think. Comment on this post, or send feedback to newsletter@drupal.org. We’d love to hear from you.
Personal blog tags: Drupal Newsletter
Categories: Drupal

Drupal @ Penn State: The year, is 2020.

13 April 2015 - 9:46am

The year is 2020.

Categories: Drupal

Drupal core announcements: Drupal core security release window on Wednesday, April 15

13 April 2015 - 7:51am
Start:  2015-04-15 (All day) America/New_York Online meeting (eg. IRC meeting) Organizers:  David_Rothstein

The monthly security release window for Drupal 6 and Drupal 7 core will take place on Wednesday, April 15.

This does not mean that a Drupal core security release will necessarily take place on that date for either the Drupal 6 or Drupal 7 branches, only that you should prepare to look out for one (and be ready to update your Drupal sites in the event that the Drupal security team decides to make a release).

There will be no bug fix/feature release on this date; the next window for a Drupal core bug fix/feature release is Wednesday, May 6.

For more information on Drupal core release windows, see the documentation on release timing and security releases, and the discussion that led to this policy being implemented.

Categories: Drupal

Code Karate: Installing a Drupal Site and Database - 2 of 3

12 April 2015 - 7:07pm
Episode Number: 201

In part 2 of the 3 part series, we are looking at how get a Drupal website and database setup and running. If you followed part one, you will remember we are doing this all on our local environment using MAMP. As the video will show, we begin by going to Drupal.org/project/drupal and downloading the newest version of Drupal. At the time of this DDoD, Drupal is at version 7.36.

Tags: DrupalInstallation ProfilesDrupal 7Drupal PlanetDeploymentServers
Categories: Drupal

Pixelite: How and why you should update PHP to PHP 5.5 with Drupal

12 April 2015 - 5:00pm

This post is a follow up to my previous blog post on how to upgrade PHP to 5.4 to support Drupal 8.

Why you should upgrade PHP

If you are looking for reasons to ditch PHP 5.3, here are some:

Security

PHP 5.3 reached end of life in August 2014, this means that if you are running this version, you are running an insecure version of PHP that potentially has security holes in it. This is bad for obvious reasons.

Bundled opcode cache

PHP 5.5 is the first version that bundles an opcode cache with PHP, this means there is also no need to also run APC (unless you need userland caching in APCu).

Performance

PHP profiled the 5.4 release compared to 5.3 for Drupal, and that found that:

  • 7% more requests/second
  • 50% PHP memory reduction

PHP 5.5 offers more performance again, and there is a section at the bottom of this article that goes through a real life scenario.

Cool new features

Read through the list of new features, here are some neat things you are missing out on:

$array = [ "foo" => "bar", "bar" => "foo", ];
  • Function array dereferencing
$secondElement = getArray()[1];

And many others.

How to upgrade to PHP 5.5

There are a number of ways to update your server to PHP 5.5.

Upgrade to Ubuntu Trusty Tahr 14.04

Ubuntu Trusty Tahr 14.04 (which is an LTS version), which comes bundled with PHP 5.5.9. This is probably the best solution if you are managing your own Ubuntu box.

Install a PPA on Ubuntu Precise 12.04

If you are running the older Ubuntu Precise 12.04, you can add a PPA

sudo add-apt-repository ppa:ondrej/php5 sudo apt-get update sudo apt-get install php5 php5 -v

It would be worth considering a dist upgrade though, but this at least can buy you some time.

Acquia Cloud UI

If you use Acquia Cloud for hosting there is a convenient PHP version selector in the UI.

More information can be found in the documentation. Be aware, once you upgrade beyond PHP 5.3, you cannot downgrade, so ensure you test your code on a development server first ;)

Common coding issues

Although Drupal 7 core, and most popular contributed modules will already support PHP 5.5, it would pay to do a code audit on any custom code written to ensure you are not using things you should not be. Here are some links you should read:

Below are some of the most common issues I have found in sites:

Call time pass-by-reference

If you have this in your code, you will have a bad time, as this is now a PHP fatal.

foo(&$a); // Bad times. Only variables can be passed by reference

This will cause PHP to throw notices.

$ php -a Interactive shell php > ini_set('error_reporting', E_ALL); php > var_dump(reset(explode('|', 'Jim|Bob|Cat'))); PHP Strict Standards: Only variables should be passed by reference in php shell code on line 1 Strict Standards: Only variables should be passed by reference in php shell code on line 1 string(3) "Jim"

Where you will likely find this in Drupal in my experience is when manually rendering nodes:

This code works in PHP 5.3, but will throw notices in PHP 5.5:

$rendered = drupal_render(node_view(node_load(1), 'teaser'));

The fix is to simply use a temporary variable:

$view = node_view(node_load(1), 'teaser'); $rendered = drupal_render($view);

The reason being that drupal_render() expects a variable to be passed in (as it is passed by reference).

How do you find coding issues

Enable the syslog module, and tail that in your development environment, hunt down and fix as many notices and warnings as possible. The more noisy your logs are, the harder it is to find actual issues in them. While you are at it, turn off the dblog module, this is only helpful if you do not have access to your syslog (as it is a performance issue to be continually writing to the database).

Real world performance comparison

This was taken from a recent site that underwent a PHP 5.3 to 5.5 upgrade. Here are 2 New Relic overviews, taken with identical performance tests run against the same codebase. The first image is taken with PHP 5.3 running:

You can see PHP time is around 260ms of the request.

With an upgrade to PHP 5.5, the time spent in PHP drops to around 130ms. So this is around a a 50% reduction in PHP time. This not only makes your application faster, but also it means you can serve more traffic from the same hardware.

Comments

If you have gone through a recent PHP upgrade, I would be interested to hear how you found it, and what performance gains you managed to achieve.

Categories: Drupal

Drupal for Government: Tree cross pollination maps using Drupal! aka debugging drupalgap geofield with genymotion and gapdebug

12 April 2015 - 4:27pm

DrupalGap continues to rock.  Today I wanted to test the geofield module and get some maps in my apps... duh... it came about as a result of meeting with Tom Cormons from Appalachian Voices. He mentioned a problem - you often need two trees to pollinate eachother, and only have space for one... an app might help neighborhoods coordinate healthy tree communities.  

Anyhow - my dev skills were amok.  I followed the instructions on Tyler Frankenstein's site however I wasn't getting the maps to show up on my phone.  They showed up fine on the web-app side of things (eg https://www.cvillecouncil.us/mobile-application/index.html#node_23 ) however after building and piping to my android phone I couldn't get the maps to show up on my kyocera hydro (c5170...) ... I needed a debug environment... enter gapdebug!  oh yeah... gapdebug only works with android 4.4... my ghetto phone is running android ice cream 4.04... enter genymotion!

Categories: Drupal


Google+
about seo