Posted by jhodgdon on October 2, 2017 at 3:18pm
Start:
2017-10-12 10:00 - 12:00 America/Los_Angeles Organizers:
Event type:
User group meeting
We hope you can join us for the next meeting of the Spokane Drupal User Group!
- When
- Thursday, October 12, 2017, 10 AM to noon
We meet on the 2nd or 3rd Thursday of most months at this time/location. Log in and join the Spokane Drupal User Group (see sidebar on https://groups.drupal.org/spokane-wa ) to be notified of future meetings, events, and discussions (typically just a few email messages per month). - Where
- Spokane County Library - Argonne branch, 4322 N. Argonne Road, Millwood. We are currently meeting in the small conference room at the library. From the hallway, go into the library proper, past the checkout/information desk, take a right and you'll see the room on the right.
- To be reminded, sign up!
- To receive an email reminder closer to the date of the meeting, log in and click the "Sign up" button; log in and click "Cancel signup" at a later time if your schedule changes and you can no longer come. There's no obligation to come if you sign up (but we hope you will!). There's also no obligation to sign up in order to come (it's up to you if you want a reminder or not). However, the meeting could be canceled if the organizer isn't sure anyone is coming.
- What
- We spend two hours in a question and answer format, with the participants around a table and a laptop on a projector. Come with questions about a project you're working on, something you've learned that you'd like to share with others, a desire to improve Drupal in some way (documentation, programming, design, marketing etc.), or a desire to help others with their projects and questions. Or just come and listen and observe.
- Who
- Everyone is welcome -- the only prerequisite is having some interest in Drupal. This group is usually 5-10 friendly people, with experience levels ranging from novice to expert, so you'll fit right in. Because of the size of the group, you will have time to share something you've learned, or get your questions answered, or both!
Comments
Yes
I will be there.
Meeting notes
What we talked about today:
https://www.drupal.org/project/resmushit
This module works with existing Image Styles functionality in Drupal Core. You add it as the last step, and it tries to compress your image after all the other style steps. It uses a web service. Doesn't alter the original uploaded image, just the "styled" image (same as other styling).
- When you clear the Drupal cache, they do NOT get cleared!
- If you save an image style or an effect within the style, the cached images get flushed out (and will be rebuilt as they are requested on web pages)
- You can use
drush image-flush
to flush images of all styles- You can delete all the images under sites/default/files/styles
- You can use this contrib module to add a "flush" operation to your Image Styles admin page in the Drupal UI https://www.drupal.org/project/imagestyleflush
- PNW Drupal Summit - http://pnwdrupalsummit.org/2018 - Feb 3-4 in Portland, Oregon
- DrupalCon Nashville - https://events.drupal.org/nashville2018 -- April 9-13
- Look for other regional events too -- there's Twin Cities (Minneapolis), SANDCamp (San Diego), etc.
- Drupal 7 and 8 have suites of automated tests. When someone makes a code patch to fix an issue, the patch is run through all the automated tests. Drupal 8 has something like 22,000 tests.
- Some but not all contributed modules also have automated tests.
- The tests verify that some (hopefully most) of the module or Drupal Core's functionality doesn't break when the code is changed, and ensure that fixing one issue doesn't cause lots of other issues.
- There's a server farm called "Replace" that runs the tests automatically
2014 presentation by Katherine Senzee on this topic:
http://2014.pnwdrupalsummit.org/2014/sessions/deploying-confidence-autom...
https://www.drupal.org/project/project_module/?solrsort=ds_created%20desc
It doesn't seem to have an RSS feed.
- When you log in, browsers these days will warn you that your site is not secure, if you are using HTTP vs. HTTPS.
- HTTPS sites -- all traffic to/from the site is encrypted (secure and private)
- HTTP sites -- traffic (including passwords) is not encrypted, so it can be "sniffed" on the network
- If you switch to HTTPS, you will want to set up a redirect from the old HTTP to the new HTTPS address in your .htaccess site.
Drupal programmer - http://poplarware.com
Drupal author - http://shop.oreilly.com/product/0636920034612.do
Drupal contributor - https://www.drupal.org/u/jhodgdon