►
From YouTube: Backdrop Weekly Meeting - Jan 24
Description
Weekly Backdrop CMS development call! Agenda for this week: http://bit.ly/2S7XF9s
A
Hello
back
dropper
is
its
January
24th
2018,
and
this
is
the
weekly
developer,
meaning
or
backdrop
CMS,
where
we
get
together
every
single
week
and
talk
about
what
we're
working
on
and
backdrops
the
MS
functionality
that
we're
working
on
ways
that
we
can
improve
our
website
and
peripheral
things.
The
world
looking
trip.
We
cover
it
all
here.
In
the
backdrop
contrition
reading
I
mean
we
cover
it
all,
except
for
outreach
and
design
which
happens
an
hour
before
this
meeting
every
other
week,
so
check
out
those
meetings
as
well.
A
You
know
the
dev
meetings
are
the
most
popular
or
mostly
devs,
but
let's
get
rolling
here
so
updates
from
Project
Management
Committee
no
updates
this
week,
then
I
am
aware
of
no
community
updates
either
I.
Don't
think
Jen
usually
put
together
numbers,
but
as
she
is
off
jumping
horses
around
in
Southern
California
who
is
unavailable
to
aggregate
those
number.
As
far
as
this
week,
I
didn't
find
some
updates
here
in
the
world
of
contribute
have
joined
the
backdrop
contribute
since
last
week
the
photos
swipe
of
module,
which
is
a
lightbox
like
alternative.
A
A
If
this
contribute-
and
it's
also
where
people
can
go
and
say,
hey
I
need
this
module
like
it
would
be
great.
If
anybody
has
time
on
it,
they
can
work
on
it
and
this
photo
swipe
module
was
an
example
of
that
that
current,
are
you
open
up
an
issue
saying:
hey
I
would
really
love
this
module
being
ported
from
Drupal
and
cram
72
popped
in
and
said
there
you
go
it's
ported
and
not
only
in
any
party.
He
made
it
really,
which
is
even
better.
A
So
thanks,
gram,
72
for
doing
that
port
and
awesome
to
see
our
community
members
talking
back
and
forth,
like
that,
other
controls
that
were
added
in
the
headless
module.
Oh,
oh
and
Gregory,
the
headless
module
which
looks
like
it
was
made
by
our
own
sarin
deputy
here.
If
you
want
to
give
a
little
shout
out
about
what.
A
C
It
exposes
an
admin,
config
form
and
it
looks
up
the
machine
names
of
views
and
gives
you
a
checkbox
to
say.
I
want
to
provide
a
json
endpoint
for
that
and
then,
if
you
hit
like
API
slash
views,
slash
machine
name,
it
will
give
you
JSON
output
of
the
fields.
So
you
can
render
that
on
your
on
your
front-end,
app
or
whatever
you're
using
importer
is.
C
A
So
the
headless
mantra
join
the
bank
trope
contribute
as
well
as
user
import,
which
is
a
tool
for
importing
user
accounts
into
backdrop,
looks
like
mostly
from
CSV
files,
which
looks
like
that
could
be
handy
for
bulk
import
of
easier
data.
Also,
new
releases
ubercart
had
a
new
release
version
1.0,
0.3,
beta
and
filled
group.
One
point
0.3
as
well.
Actually
so,
as
always
like
it's
great
to
see
country,
oil,
thriving
and
new
releases
and
much
was
being
maintained.
A
Let's
see
we'll
move
on
to
website
related
development
tasks,
things
that
were
working
on
backdrops
EMS
org.
There
were
some
more
updates
to
the
demo
button
functionality.
We
covered
that
in
the
outreach
meeting
just
before
this,
but
if
you'd
like
to
take
a
look
at
issue
422
in
the
backdrop,
CMS
dot,
org
issue
queue
and.
A
There's
some
feedback
going
on
there
there's
currently
a
demo
of
site,
a
demo
functionality.
You
can
go
and
try
it
out.
It's
at
backdrop,
CMS
org,
slash,
demo,
slash,
create
and
you
can
click
a
button
there
and
make
a
sandbox
in
a
couple
of
seconds.
It's
kind
of
fun,
so
we're
soliciting
more
feedback
for
that
functionality
in
issue
422
and
yeah.
There's
there's
definitely
lots
of
improvements
to
be
made,
but
you
know
it's
it's
doing
something
so
thoughts
of
feedback.
Welcome
on
that
functionality.
A
A
A
In
the
case
of
all
sites,
it's
been
suggested
by
Tim
that
we
do
a
virtual
Sprint's
for
a
10-day
period
at
the
beginning
of
February
February
1st,
through
10th,
maybe
like
it
seems
like
a
pretty
good
idea
to
just
get
together,
put
a
little
bit
of
focus
on
a
couple
of
problems
that
we
have
on
our
collection
of
websites.
There
hasn't
been
a
lot
of
conversation
around
this.
Yet
its
backdrop
CMS
board
issue
494.
If
you're
interested
in
participating
post
a
comment
there
saying
hey,
that
sounds
like
fun:
I
could
work
on
this.
A
Let's
see
you
guys
have
anything
else,
you
guys
would
like
to
bring
up
regarding
the
websites
all
right.
Well,
we're
all
on
to
just
the
project
progress
report-
let's
see
so
we
mentioned
this
last
week
that
last
week
there
was
a
lot
of
activity.
Not
only
did
we
put
out
backdrop
1.12
right
after
the
day
of
our
release,
there
was
a
security
release
of
Drupal
that
made
it
so
that
we
released
one
dot
12.1.
A
So
1.12
already
has
its
first
update,
which
included
a
button,
including
two
security
fixes
and
some
other
minor
updates
that
were
found
in
the
one
day
between
112
and
112,
one
OK
for
112.
Two,
though
we
have
a
number
of
issues
that
have
cropped
up
here,
remove
that
one
so
some
may
have
cropped
up
this
week
we
found
that
the
new
views
grid
functionality
was
intended
to
be
backwards,
compatible
where
existing
sites
would
be
completely
unaffected
by
the
new
option
to
use
CSS
grids
for
views
instead
of
table
based
layouts.
A
A
The
issues
currently
needs
review
adds
an
update,
hook
to
explicitly
set
all
legacy
views
to
use
the
table
based
version
instead
of
the
CSS
grid,
based
version
of
use,
so
that
issue
could
use
some
review
because
it's
an
update
hook,
it's
the
sort
of
thing
that
we
usually
have
to
test
out
manually
because
it
doesn't
really
present
anything
in
the
demo
sandboxes,
because
they'll
already
start
with
the
update
supplied.
This
is
really
about
an
upgrade
issue
from
111
and
prior
versions
to
112.
A
A
B
A
A
Now
it's
also
turned
off
by
default,
but
you
can
turn
it
on
and
then
it
doesn't
work
right
now
because
it
turns
out
actually
pretty
much.
All
downloading
from
github
seems
to
be
intermittently
functional
right
now.
There's
an
issue
for
this
at
3488
that
it
seems
as
though
a
change
on
the
github
side
or
AWS
side
we're
not
quite
sure
which
one
made
it
so
that
backdrop
can
no
longer
download
files
from
github
consistently.
A
It's
it's
actually
been
a
little
bit
strange,
like
I
hadn't
had
any
problems
until
recently,
but
then
after
I
posted
the
pull
request,
some
other
people
said
that's
working
for
them,
fine
right
now
without
it.
So,
but
it
does
look
like
we
have
a
fixed
that
will
solve
the
problem
regardless
it's
in
3488,
it's
currently
our
TBC,
and
so
that
will
be
in
112
for
certain
also
related
to
core
updates.
A
A
A
Let's
see
also
again
calling
out
a
couple
of
RTL
issues
that
Shabba
bomb
filed
he's
been
making
great
issues
that
say
how
to
fix
RTL
issues,
but
he
hasn't
found
any
patches
on
them.
I
know
that
we've
had
a
lot
of
community
members
coming
in
and
Creek
creates
pull
requests
based
off
of
his
suggestions,
which
has
been
extraordinarily
helpful.
We
got
four
of
those
issues
merged
into
one
12
one
and
there's
still
several
more
to
be.
You
can
find
those
just
by
searching
for
RTL.
In
the
backdrop
issued,
you.
B
We
got
into
that.
There
was
a
suggestion
by
sorry:
I,
don't
remember
the
handle
of
the
person,
one
member
of
the
community,
that
we
should
have
a
single
pull
request
for
all
the
RTL
issues,
but
I
suggested
that
we
should
leave
them
as
they
are
like
for
its
issue
separately.
We
are
because
then,
if
something
goes
wrong,
we
can
remove
it
easily,
but
I
don't
know
what
the
policy
is.
There.
A
B
I
I
would
appreciate
if
you
chimed
in
Donna,
because
there
was
it
was
a
discussion
back
and
forth.
So
if
we
have
an
official
reply
or
else
I'll
post
the
link
to
the
issue
where
the
discussion
was
going
on
on
git
er
and
then
maybe
you
can
spend
like
a
minutes
to
just
comment,
I
mean
yeah
yeah
cool
thanks.
A
A
Which
will
be
coming
up,
May,
15th
2019
right
now,
the
items
that
we've
got
in
the
113
milestone
are
largely
things
that
have
been
pushed
from
112.
They
include
the
dashboard
field,
about
files,
adding
more
translation
functionality
to
config
files
and
package
signing.
So
all
four
of
those
who
are
things?
That's
you
know
we
made
a
pretty
good
start
on
in
112,
but
they
didn't
make
it
in
let's
go
through
them
one
at
a
time
here.
A
A
You
know
it's
basically
just
a
whole
lot
of
listings
that
kind
of
firehose
information
at
you,
which
is
probably
great
from
you,
know
an
experienced
site
manager
perspective,
but
from
a
new
user
perspective
I
when
I
pull
it
up,
it's
just
a
it's
really,
it's
a
lot
so
feedback
and
concepts
for
improving
the
dashboard
are
495.
Technically,
it's
really
solid.
We've
got
a
really
great
implementation
of
how
it's
built
and
the
way
blocks
are
provided
and
what
blocks
are
provided,
but
we
really
could
use
some
more
thought.
Arounds.
A
Is
there
some
design
that
we
could
apply
to
this,
and
what
kind
of
information
can
we
show
that
is
actually
useful
to
to
administrators
so
issue
495
could
use
some
additional
review.
There's
a
great.
You
know,
demo
sandbox
that
you
can
pull
up
and
play
with
to
get
an
idea
of
what
functionality
it
has.
A
A
Fields
are
added
to
files
of
the
image
type,
but
then
these
fields
aren't
actually
used
anywhere,
for
example,
so
there's
things
that
are
kind
of
cruft
that
was
made
to
be
a
assistive
in
the
Drupal
7
version
of
the
file
and
any
module
kind
of
stubbing
things
out
for
you
to
then
build
upon.
But
as
far
as
core
is
concerned,
like
these
things
should
do
something
if
they're
in
core
they
shouldn't
just
be
there
to.
You
know
well,
there's
this
field
in
case
you
want
to
use
it
like,
but
it
doesn't
do
anything.
A
A
The
when
you
upload
a
file
right
now
it
in
the
image
field,
it
asks
you
for
the
title
and
alt.
Those
are
used.
The
per
instance
of
using
that
image.
The
the
title
and
alt
fields
are
used
from
the
field
that
you
in
which
you
uploaded
the
image
into,
but
then
the
image
itself
you
can
go
and
edit
it
after
this
pull
request
and
then
there's
fields
on
the
file
itself
for
title
and
alt,
and
they
don't
do
anything.
For
example,.
A
B
A
B
A
I'm,
actually
not
sure
what
that
this
needs
to
be
in
the
1:13
release
like
this
is
the
sort
of
thing
that
there's
no
functional
difference
before
and
after
them
or
just
modifying
config
files,
or
it
could
be
something
that
we
could
push
into
112
we'll
see
like
as
the
implementation
comes
together,
like
the
scope
of
it.
If
it
looks
like
it
would
have
any
kind
of
any
kind
of
effects
on
on
any
existing
sites,
I
mean
the
work
that
basically
needs
to
be
done.
Here
is
adding
a
new
key
to
the
config
files.
A
That
say,
you
know
these
are
the
the
key
inside
of
the
config
file
would
be
a
list
of
other
keys
inside
of
the
config
file
that
are
translatable
so
they're,
actually
ii,
don't
be
too
terribly
difficult,
but
I'll
probably
be
a
little
bit
of
legwork,
going
through
all
the
config
files
and
updating
all
those
properties.
So
once
we
establish
a
pattern
for
how
we
want
to
do
that,
and
it's
going
to
be,
you
know,
pattern
applying
throughout
all
of
Kordich
find
all
of
those
strings.
A
Let's
see
and
lastly,
package
signing
this
is
functionality
that
we'd
like
to
add
to
make
it
so
that
the
transit
of
packages
from
where
they're
hosted
on
github
to
where
they
get
downloaded
onto
your
site
can
be
validated
and
guaranteed
that
that
package
was
officially
run
through
backdrop,
CMS
orgs
packager.
So
that's
you
can
be
assured
at
least
that
that
package
is
valid
from
what
we
expect
it
to
be
across
transit.
So
this
is
a
1992
and
we
actually
seen
some
pretty
good
progress
here.
A
Recently
john
franklin
has
posted
a
new
version
of
his
approach
to
things
which
uses
this
new
module
called
code.
Sine
and
cosine
has
looks
like
he's
working
to
make
it
work
with
GPG,
canoe,
PG
or
open
ssl
kind
of
as
swappable
systems
or
for
signing
the
packages.
So
I
haven't
had
a
chance
to
look
at
it
yet,
but
it's
kind
of
exciting,
looking
like
as
an
alternative
to
one
of
the
other
signing
approaches
that
we
had
been
looking
at
previously.
So
that's
pretty
pretty
great,
actually
I.
A
And
that's
it
for
the
product
update
I,
don't
think
we
have
any
things
in
113
that
haven't
been
talked
about
previously.
You
know
it's
a
long
way
until
May.
So
it's
like
you
know,
the
doors
are
open
for
other
functionality
as
well.
If
there's
anything
that
you
guys
would
like
to
talk
about
for
113,
then
we
can
bring
them
up
now.