►
From YouTube: Backdrop Weekly - Jan 17th
Description
Today’s development agenda: http://bit.ly/2D119SO
A
Hello
back
droppers,
it's
January,
17th
2019.
It
is
the
first
development
meeting
after
the
release
of
1.12.
So
oh
my
gosh,
it's
been
an
action-packed
week
in
the
world
of
backdrop.
Well,
let's
go
through
all
of
the
individual
items
and
we'll
get
through
to
all
the
news.
Once
we
get
down
to
the
product
section
so
updates
from
the
PMC.
There
are
none
nothing
to
report
this
week.
Community
updates
no
real
updates
here
either
as
far
as
new
contribs
the
venture
contribute.
A
It
is
worth
noting
that
we
did
have
lots
of
releases
of
contribs
options,
elements
to
prevent
conflicts
with
the
new
version
of
backdrop,
entity
plus
the
hax
editor
web
components.
New
version
of
drush
that
includes
boilerplate
commands
web
form,
module
paging
module
lots
of
new
releases
just
made
in
the
last
7
days.
So
it
continues
to
be
really
exciting.
Just
to
see
the
the
really
thriving
ecosystem
of
controls
and
I'm,
not
just
being
creative
new
ones
coming
in,
but
the
continuing
maintenance
is
maintenance
is
exciting.
You
know
if
that
means
stability
and
new
functionality.
A
Let's
see,
we've
got
a
couple
of
website
related
tasks
related
to
backdrop,
CMS
org.
A
lot
of
these
things
would
cover
during
the
design
meeting
that
was
just
prior
to
this
one,
including
improving
the
search
system
for
our
modules,
themes
and
layouts.
That's
backdrop:
CMS
org
issue,
442
that
we
covered
in
the
design
meeting
we're
working
towards
improving
the
demo
functionality
from
the
homepage
instead
of
using
a
requiring
a
sign
up
to
Pantheon,
actually
having
a
true
demo.
That
is,
it's
not
so
fast.
A
A
Let's
see
I
don't
think
we
have
any
updates
on
the
forum
site
to
report
today,
nor
on
the
translation
site
that
I
know
of
I'm
just
not
connected
and
with
that-
and
we
don't
have
a
lot
fair
to
report.
So,
let's
see
all
sites
on
backdrops
AMS
org.
It's
been
proposed
that
perhaps
we
set
aside
some
time
to
put
some
focus
on
our
all
our
internal
web
sites
and
have
a
volunteer-driven
virtual
sprint.
Possibly
February
1st,
through
10th
st.
A
Paul
Tim,
suggested
that
it's
a
probably
I
mean
it's
a
really
great
idea
like
if
we
can
get
people
together
and
unblock
them
on.
Maybe
you
know
getting
access
to
the
database
dump
or
telling
him
permitting
and
conveying
information
about
how
to
set
up
the
various
systems
so
that
we
can
have
them
on
local
hosts
and
then
work
through
some
of
the
issues
that
we've
got
with
the
flagship
web
site,
as
well
as
the
forum.
So
then
probably
is
going
to
be
coming
up.
February
1st
to
10th
right
now.
A
A
A
So,
let's
work
kind
of
backwards
here,
so
111
Oh
was
released
at
the
same
time
as
1.12,
and
there
were
a
ton
of
bug
fixes
put
into
1:11,
for
which
was
supposed
to
be
the
last
release
under
the
111
release.
But
as
many
people
are
aware,
yesterday,
security
release
was
put
out
for
Drupal
and
for
our
security
policies.
A
So
that
has
been
addressed
with
backdrop
we
May
1
11.5,
so
security
released
for
the
1.11
branch
as
well
as
one
dot
12.1.
So
right
after
one
that
well
came
out
the
next
day
we
had
a
security
really
created
as
well,
which
which
isn't
really
ideal
to
be
putting
people
through
those
cycles,
but
we
also
can't
really
dictate
the
releases
of
Drupal,
so
it
is
still
important
for
us
to
come
out
as
quickly
as
possible,
even
if
it's
not
perfect
timing
for
our
project.
A
So
let's
talk
about
1.12
dotto,
which
just
came
out
January
15th
so
day
before
yesterday,
lots
of
great
new
features,
including
backdrop
core,
can
now
self
update
that
functionality
actually
1.11,
but
now
it's
in
the
user
interface
in
1.12,
it's
still
off
by
default,
but
you
can
turn
it
on
and
it
only
self
updates
manually.
So
you
have
to
go
there
and
click
update.
So
it's
just
like
updating
a
module
or
a
theme
or
any
other
project.
Where
you
go
to
available
updates,
it
says,
there's
a
new
version
of
core
available.
A
Then
you
apply
the
updates
and
it's
self
updates
the
core
directory.
The
thing
it
does
not
do
is
it
does
not
do
that
automatically
like
on
cron
jobs
are
on
an
interval
or
anything
like
that.
That
is
still
an
objective
for
the
next
version
of
backdrop,
but
again
like
we'll
kind
of
slowly
iterate
on
that
functionality
to
make
sure
that
we
get
it
perfect
before
it
actually
goes
out
publicly
out
of
the
box.
That
is
so.
A
Let's
see
views
grids
when
you
create
a
new
display
that
uses
the
grid
display
mode
that
now
uses
CSS
grids
instead
of
a
table
based
layout.
The
table
base
level
is
still
there
and
old
sites
that
use
the
table.
Layouts
are
will
continue
to
do
so,
but
new
views
that
are
set
up
will
use
CSS
grids
by
default,
but
the
option
to
flip
back
to
the
old
way
as
well,
better
use
of
iconography
throughout
core,
primarily
probably
the
admin
menu
at
the
top
blue
page
now
has
icons
all
across
the
top.
A
A
A
A
Version
of
the
module
that
is
included
has
some
namespace
conflicts
with
the
contribute.
A
new
version
of
the
contribute
is
been
put
out.
That
also
adds
a
warning
saying:
that's
not
compatible
with
112
and
higher,
which
is
great
kind
of
preventive
measure,
but
for
people
that
are
upgrading
right
away,
it
is
critical
that
options
element
be
turned
off
first
before
updating
to
112
something.
It's
not
not
very
idea.
A
We
didn't
realize
that
until
after
we
released
so
we're
saying,
if
there's
a
way
to
prevent
that
problem
in
future
versions,
just
entirely
to
avoid
that
entire
problem,
there's
also
a
new
contact
form
block,
so
you
can
now
place
the
contact
form
as
a
block
anywhere
on
the
site,
and
we
have
new
api's
for
translating
strings
that
are
stored
in
configuration
files.
That's
very
exciting.
A
It
doesn't
actually
have
an
end
user
impact
quite
yet
for
sites
that
are
translated,
but
it
opens
up
the
possibility
of
making
it
so
that
profiles
and
modules
when
they
can
find
configuration
with
code.
All
of
the
strings
can
be
translated
on
the
localization
server
all
take
there,
rather
than
it
just
being
the
streets
that
are
in
the
code.
A
Also,
those
are
the
big
items
which
is
pretty
great
list
of
big
items,
so
there's
also
lots
of
small
functionality
and
just
to
bring
it
up
some
items
from
last
week
that
we
mentioned
CSS
characters
and
views
were
being
stripped
out
in
particular,
hyphens
or
underscores
are
being
converted.
Iphones
that
issued
34-28
was
merged
before
release
making
it
so
that
the
search
bloc
has
options.
A
This
is
useful
for
doing
things
like
hiding
the
label
of
the
search
form
and
instead
using
a
placeholder,
for
example,
it's
a
common
pattern
in
Search
Search
areas
inside
of
headers
and
inside
bars
that
functionality
is
now
possible
without
doing
any
kind
of
custom
coding
just
by
configuring.
Your
search
block
that
issues
2923
and
it
was
also
merged
before
the
1
to
12
release
and,
lastly,
adding
icons
to
the
admin
bar
I.
Guess
I
covered
this
earlier,
a
little
bit
about
the
iconography
throughout
core
that
issue.
A
A
A
I'd
say
there
are
certain
situations
in
which
for
updates
will
fail
due
to
a
conflict
between
dot
info
files
in
tests
and
dot
and
profiles.
Modules
that
issued
1294
is
one
that
we
have
a
set
of
criteria
to
reproduce
the
problem,
but
we
haven't
yet
created
a
poor
request
to
fix
it.
Yet
considering
core
updates
are
one
of
our
key
features
and
one
not
12,
that's
something
that
we
would
like
to
get
fixed
as
soon
as
possible.
A
It
doesn't
happen
to
everybody
in
in
all
situations,
but
but
it
can't
happen
that
core
just
won't
be
able
to
download
or
won't
be
able
to
validate
the
downloaded
file.
It
doesn't
leave
your
site
in
a
usable
State.
It
just
doesn't
succeed,
doing
the
update
so
1294
it's
an
area
in
which
we
could
use
a
little
bit
of
work.
A
Also,
this
just
came
up
this
morning
that
there
apparently
was
a
change
to
github
or
the
underlying
system.
The
kid
abuses
it
over
at
AWS
that
we
use
github
to
host
all
of
our
archives
for
releases
and
some
kind
of
change
occurred
earlier
today.
That
made
it
so
that
we
can
no
longer
have
back
drop,
pull
down
release
archives
from
github,
so
that
affects
the
project
installer
and
the
project
updater.
So
nothing
is
updating
or
installable
right
now
through
the
user
interface.
A
Because
of
this
problem,
even
though
it
was
caused
by
change
on
the
AWS
side.
So
it
seems
there
is
something
that
we
can
do
to
fix
it
within
the
backdrop
codebase
that
will
at
least
fix
it
for
new
releases
of
backdrop,
the
current
ones
that
are
out
there.
Unless
this
change
gets
put
back
on
the
AWS
side,
it's
possible
that
current
are
all
previous
versions
of
backdrop,
won't
be
able
to
use
the
Installer
or
the
updater
until
they
manually
update
to
the
next
version
of
backdrop.
So
that
has
some
repercussions,
of
course.
A
So
3488
is
where
the
discussion
is
happening
there.
There
is
a
pull
request
there
that
needs
review.
That
would
solve
it.
From
the
backdrop
side,
it
is
partly
backdrops
of
all
that
we're
not
doing
everything
perfectly
and
it's
a
stricter,
correct
or
stricter
validation
on
the
AWS
side.
So
3488
definitely
could
use
a
review.
A
Wow
so
much
stuff
going
on
1.13
113
will
be
the
next
release
of
backdrop.
I
know,
a
lot
of
us
are
just
kind
of
taking
a
little
chill
time
after
one
done
12,
which
is
very
good
and
healthy
thing
to
do
so
so,
but
we
are
keeping
our
eyes
forward
on
113,
which
will
be
released,
May
15th
2019,
and
we
have
some
items
that
artist
Lee
were
bumped
from
1.12
that
we
would
like
to
take
a
look
at
making
sure
that
we
can
move
forward
on
them
and
113.
A
So
there's
the
dashboard
dashboard
is
a
new
module
that
uses
layouts
and
a
new
collection
of
blocks
to
provide
a
landing
page
for
administrators.
We
covered
that
in
the
design
meeting
just
before
this
one.
The
issue
is
409
and
495.
So
if
you'd
like
to
take
a
look
at
the
design
meeting,
you
can
see
the
current
state
of
dashboard
feel
double
file
types
making
it
so
that
files
can
have
bundles
and
fields
attached
to
them
is
issue
26
32.
A
We've
got
issue
of
1992,
which
would
add
package
signing
to
to
our
update
and
install
mechanisms
that
ones
still
in
progress,
no
updates
in
the
past
couple
of
months.
Actually,
let's
see
I
think
our
roadmap
for
1.13
was
also
updated.
Let
me
see
if
I
missed
anything
in
here
dashboard
save
draft
in
core.
Let's
say
we
mentioned
that
during
the
design
meeting
as
well
and
more
TBD.
Okay.
A
So
I
think
that
those
are
the
key
items
that
we've
got
focused
on
for
for
1.13,
we're
still
open
to
other
new
options
and
always
like
if
something
comes
along.
That
is
really
compelling
that
we
have
the
potential
to
include
in
the
next
release.
Will,
of
course
take
a
look
at
that,
so
that
does
it
for
the
product
update.
A
A
Interesting,
so
I
don't
think
we
can
so.
The
security
release
that
came
out
was
specifically
fixing
tar.gz
files,
which
right
now
we
only
use
for
config
file
imports
and
exports.
I,
don't
think
we
can
remove
the
libraries
from
core
I
mean
even
though
they're
updated
and
they're
now
secured
I,
don't
think
we
can
remove
them.
A
Even
if
we're
not
using
the
mend
core
from
an
API
change
perspective,
we
can
stop
using
them
for
config
files,
though
we
can
switch
over
to
is
using
zip
files
for
download
and
upload
and
I
think
that
would
probably
be
preferable.
Tar.Gz
files
are
not
the
easiest
things
to
work
with
for
a
lot
of
users
right,
yeah,.
A
Ok,
well,
that's
it
then
there's
been
it
was
a
super
action-packed
week
for
releases
of
backdrop,
lots
of
things
happening,
pull
requests
getting
merged
in
just
beforehand
and
then
some
follow
up
ones
coming
in
and
well
one
twelve
one
as
well
just
lots
of
great
great
improvements
all
across.
So
it's
been
yeah
been
exciting,
so
I'm
ready
to
take
a
little
break,
but
you
know
there's
always
more
to
be
done
in
the
world
of
development.
So
thank
you,
everybody.
A
Yet
but
we
hope
to
see
in
a
future
version,
so
thanks
again,
thank
you.
Thank
you
to
all
of
our
community
members
that
have
come
together
to
make
such
awesome
releases
month
after
month.
So
all
right
that
does
it
for
today's
meeting.
Thank
you
again.
Everybody
out
there
for
watching
and
just
keep
on
back
drop
in
see
you
guys
on
the
Internet.