►
From YouTube: Backdrop Weekly - Nov 14th 2019
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
B
All
right
today
is
Thursday
November
14th,
and
this
is
checking
meeting
on
active
development
asks
for
backup,
CMS
and
before
we
get
into
core
issues.
I
want
to
say
that
there
are
two
new
contributed
projects
out
this
week.
We
have
both
a
stable
release
for
max
length
and
bamboo,
which
I
believe
is
a
theme.
I
haven't
looked
at
it.
B
We
also
have
a
couple
of
things:
we're
working
on
on
backdrops
websites.
First
and
foremost,
I
am
trying
to
work
on
some
changes
to
our
newsletter.
Signup
form
to
make
sure
that
everybody
who
signs
up
for
our
newsletter
is
adequately
opted
into
gdpr
requirements
and
that's
gonna
go
across
all
websites
and
then
for
backdrop,
CMS
org.
B
It
looks
like
we
might
need
to
update
our
DNS
to
deal
with
Demark
stuff,
because
emails
coming
from
the
website
are
not
getting
through
to
people's
inboxes
I
know
we
did
a
server
change
recently
and
I,
don't
know
if
we
were
using
an
IP
address
that
might
have
been
tied
to
the
old
server
and
that
needs
to
be
updated
to
go
to
the
new
one.
So
that
seemed
like
kind
of
an
urgent
issue,
so
I
figured
I'd
throw
that
into
that
Genda.
B
Today,
yeah
I
think
right
now,
you're
the
only
one
with
access
to
DNS
or
the
domain.
So
maybe
we
can
throw
that
into
the
new
backup
one
password
thing
and
there
might
be
another
way
to
solve
that
problem.
Yeah.
B
C
Might
want
to
be
careful
with
that,
though,
because
if
we
might
end
up
with
the
you
know,
backdrop
separate
financial
information
in
the
backdrop
account
and
so
any
domains
you
transfer
into
their
backdrop,
would
be
responsible
for
paying
for
in
the
future
and
maybe,
if
they're,
just
speculative,
it
might
be
best
to
keep
them
okay
until
we
use
them
right.
That's.
B
C
Okay,
so
a
project
report.
For
this
week,
the
current
bug-fix
release
that
were
working
on
is
114.
There
have
been
a
couple
of
more
additional
fixes
that
have
been
going
in
into
114,
but
I.
Don't
think
any
of
them
are
things
that
are
really
worth
mentioning
that
have
happened
in
the
last
week,
so
you're
looking
at
the
114
milestone,
we
currently
have
54
open
issues
in
the
114
milestone,
many
of
which
need
review,
looks
like
milestone.
C
One
14
23
of
those,
so
almost
half
of
the
open
issues
in
114
to
have
pull
requests
are
open
that
are
in
the
needs,
review
state.
So
I,
don't
think
that
there's
anything
on
our
T
V
CEQ
at
this
point.
So
if
you're
looking
to
contribute
some
effort
into
fixing
bugs
and
getting
them
out
in
the
very
near
future,
the
114
miles
donors
great
place
to
start
and
look
at.
There
were
issues
that
currently
a
review.
D
Just
to
mention
a
single
ticket
that
there
was
recently
brought
to
my
attention
and
I
did
the
testing,
but
not
the
code
review,
because
I
participated
in
the
pull
request
so
for
193
the
one
about
the
file
temporary
pass,
all
right,
uh-huh,
yeah,
so
Alan
knows
filed
the
second
pull
request.
I
helped
with
that.
D
C
Yeah,
this
looks
really
simple.
Thank
you
for
helping
Alan
with
that.
I
saw
that
he's
been
really
adamant
that
it's
a
big
thing
that
needs
to
be
taken
care
of,
but
really
it's
like.
No.
This
doesn't
seem
to
affect
too
much
really.
It
doesn't
have
any
end
user
facing
issues
or
anything.
However,
the
fix
is
simple
and
it
looks
like
you
guys
got
it
sorted
out,
and
it
looks
right
to
me
so
yeah
I
think
it
would
be
great
to
get
that
through.
C
C
I'm
trying
to
add
to
the
issue
agenda
just
as
something
that
was
discussed,
so
the
other
two
items
that
we've
got
marked
on
the
agenda
are
big
meta
issues,
one
for
views,
cross
ports,
they've
used
cross
ports,
issue,
numbers,
36,
85
and
then
also
flexible
templates,
a
new
feature
that
we
added
in
114
as
a
big
meadow
at
40
46.
So
both
of
those
have
lots
of
sub
issues
they
all
could
potentially
be
work
done
and
integrated
into
the
bug
fix
release
as
soon
as
they're
ready.
C
C
No
okay,
okay!
Well,
let's
talk
about
115,
then
115
is
the
next
minor
version
of
backdrop
that
includes
new
features.
We
have
about
8
features
that
are
currently
in
progress
for
115
that
are
noted
as
having
advocates.
These
aren't
necessarily
the
only
issues
that
we'll
get
into
115
but
they're,
the
ones
that
we
mentioned
during
these
weekly
meetings,
because
they
have
individuals
who
are
advocating
for
their
inclusion
and
sometimes
those
people
will
be
present
to
give
their
updates
other
times.
They
might
leave
an
update
and
issue
for
us
to
report
on
them.
C
C
Okay,
I'll
go
over
it,
so
Graham
72
has
been
doing
development
work
on
this.
It
looks
like
it
actually
functions.
Lauren
posted
a
great
video
of
how
the
whole
thing
works
in
the
issue,
which
is
3297
and
they're
still
consideration
and
their
concern
that
right
now
it's
an
inline
view
that
lets
you
select
images
and
dr.
Elmont
posted
long
or
a
good
comment
summarizing
why
it
might
be
better
for
it
to
be
in
a
modal
instead,
I
haven't
put
my
personal
opinion
in
here,
but
I
also
kind
of
agree:
I,
don't
I,
don't
want
to.
C
You
know,
force
that
decision,
but
but
I
agree
with
that
moment
that
I
think
overall,
this
would
be
better
and
in
a
modal
probably
to
allow
for
other
elements
like
search
and
the
pager
and
other
things
like
that
and
a
dedicated
location
separate
from
the
rest
of
the
note
form
anyway.
C
C
Next
up
Auto
menu
settings
in
core
issue
1610.
This
simple
feature
just
makes
it
so
that
when
you
create
a
new
node,
possibly
of
a
page
content
type,
we
could
have
it
so
that
a
menu
item
is
created
by
default.
When
that
piece
of
content
is
saved,
I,
don't
think
that
there's
been
any
changes
in
the
past
two
weeks,
however,
the
current
status
of
is
that
there's
a
pull
request
that
just
needs
review,
so
I
think
that's
where
that
is
Jenn.
C
C
Recent
newest
block
on
the
dashboard
issued
thirty
five
sixty
six
will
make
it
so,
potentially
the
backdrop
of
CMS,
org
flagship
site
could
aggregate
news
and
send
it
to
individual
backdrop,
websites
in
the
main
dashboard
that
you
see
when
you
log
into
a
new
backdrop
website
Tim
you're.
The
advocate
for
this.
Are
there
any
updates
this
week,
I'm.
A
C
D
There's
no
update
since
last
time,
but
it
has
a
clear
path
forward
and
you're,
pretty
close,
like
we
got
pretty
close
on
getting
it
114,
it's
just.
It
was
breaking
certain
things,
but
the
image
has
provided
a
an
idea
of
how
to
move
forward
with
being
with
it
being
safer
that
seamless
things
so
it
just
just
needs
to
the
PR
needs
to
be
updated
to
remove
the
bits
of
code
that
we're
breaking
things
elsewhere.
Just
yeah.
C
Last
we
saw
this
issue
code.
Sign
has
been
put
into
the
contribute.
Positive
project.
Module
has
been
updated
for
code
science,
support
I've
got
my
local
copy
of
backdrops
EMS
org,
with
code
sign
and
the
updated
project
module
on
it
and
generating
signatures
on
projects,
all
of
which
is
very
cool.
Angry.
C
However,
if
we
were
to
like
it
like
I
haven't
I
haven't
gotten.
It
fully
worked
out,
even
though
it's
creating
signatures
and
it's
updating
the
feed
with
signatures
in
it.
The
way
that
John
has
structured
this
module
is
that
bankruptcy.
My
stork
needs
to
become
a
certificate
authority
and
right
now,
I've
just
created
a
self-signed
private
key
to
generate
the
signatures.
D
Not
just
nothing
that
I
what
trace
not
from
the
past
Drupal
con
and
they
announced
that
automatic
updates
are
also
coming
at
the
end
of
the
year
becoming
stable
for
d8.
So
if
we
manage
to
get
this
in,
it
would
be
about
the
same
time
that
we
sort
of
like
release
this
feature.
Yeah
I'm
gonna
have
to
check
what
what.
C
A
purge
that
they've
been
using
and
what
yeah
how
it's
gonna
work,
because
there
are
some
questions
that
we
have
yet
to
figure
out
as
well
like
I.
Imagine,
maybe
they're
really
talking
about
self
updates,
initially
kind
of
like
we
already
have,
because
the
question
of
how
to
do
in
truly
automatic
update
we
haven't
figured
out
yet
because,
like
the
step
of
running
update
dot
PHP,
we
don't
know
how
to
do
that.
Yet.
C
D
At
some
point
there
was
a
an
independent
sort
of
like
github
project
that
sorry
I
can't
remember
the
name
of
the
person.
That's
terrible.
It
was
race
at
VI,
CMS,
agnostic,
sort
of
like
resets,
and
it
was
meant
to
be
for
he
came
from
the
Drupal
community,
but
he
worked
with
us
as
well,
but
it
was
supposed
to
be
like
for
every
so
like
CMS
or
PHP
framework
right
and
I'm,
not
sure
I'm,
not
sure
if
they
were
based
off
of
that,
because
he
made
that
announcement.
D
A
D
D
He's
his
work
was
published
in
github,
repo
and
I.
Remember
strongly
that
his
intention
was
for
it
to
be
CMS
agnostic,
despite
the
fact
that
it
was
based
of
like
sort
of
like
maybe
was
using
Drupal
impact
opposite
of,
like
an
experimental
so
like
nice
to
start
with,
but
yeah
I'm,
not
sure
if
the
Drupal
implementation
was
based
off.
Of
that,
though,
or
not.
C
Xhosa
is
the
advocate
for
this
fund,
but
he's
basically
put
forward
the
code.
It
said
here
it
is,
it
seems
to
all
be
working.
It
currently
needs
to
review.
So
that's
where
that
stands
today.
Issue
74
entity
cash
in
court
just
needs
some
eyeballs
a
new
one
for
this
week.
I'm
not
sure
dark
moment
is
actually
accepted.
Being
an
advocate
for
this
issue,
but
I
think
that
Jenny
were
hoping
that
he
would
officially
become
one,
but
the
issue
is
1475.
B
C
Advocating
for
this
issue
great-
and
he
did
post
an
update,
excellent,
so
his
status
is
that
so
the
overall
approach
of
this
issue
was
looking
at
it
before
the
meeting
seems
that
it's
really
about
making
it
so
that
backdrop
core,
can
better
support
forward
revisions
or
an
alternative
name
for
that
is
pending
revisions
of
revision
in
which
they,
you
created
a
draft
but
don't
publish
it,
and
a
previous
revision
stays
published
exactly
how
big
we
want
to
get
into
and
like
how?
How
large
the
scope
of
this
issue
is.
C
We
haven't
quite
decided
yet
it
seems
like
dark
moments.
Work
he's
saying
that
it's
primarily
to
make
it
so
that
more
advanced
workflows
could
become
possible,
but
at
the
same
time,
there's
also
some
user
interface
changes
that
imply
that
some
additional
functionality
would
be
supported,
out-of-the-box
in
core.
So
this
issue,
I,
think
everyone
that's
looked
at
it
so
far,
hasn't
looked
at
through
the
from
the
code
perspective
to
see
exactly
what
is
being
changed,
but
the
user
interface
ads
checkbox
right
now
that
says
make
default
whether
or
not
that
revision
becomes
the
default
revision.
C
A
A
Well,
first
of
all
that
woman
may
be
listening
right
now
he
was
just
trying
to
get
plugged
in.
So
thanks
for
doing
this,
I
think
the
ambitions
might
be
a
little
bit
bigger.
But
sir,
the
first
step
that
he's
got
is
basically
that
if
you've
got
revisions
on
a
node,
you
can
pick
any
one
of
them
and
make
it
the
act
of
revision.
A
So
you
could
have
three
revisions,
but
you
could
say
you
know
you
could
have
a
draft
version,
that's
ahead
of
the
one
you're
on
and
then
the
current
one
would
be
active
and
I
suspect
that
this
would
open
up
the
possibility
for
other
sort
of
workflow
features
that
you
could
add
down
the
road.
But
at
the
beginning
that
you
know
the
very
first
usage
of
this
is
just
that
I
I
revised
a
node,
but
don't
you
know
but
keep
it
in
the
draft
state
and
for
other
people
to
look
at
and
well.
A
C
Yep,
it
does,
and
and
I
think
that
yeah
that
it's
to
be
determined
exactly
how
you
know
how
much
functionality
we
want
to
get
into
with
this
I'm
a
little
bit
hesitant
about
adding
thanks
to
the
known
forum,
but
I
definitely
can
see.
Adding
thanks
to
the
revision
list
is
being
like
a
pretty
easy
way
of
getting
that
put
together
right.
A
And
I:
don't
I,
don't
remember
out
the
template
of
how
he
did
it,
but
I
do
remember
like
viewing
the
revision
list
where,
like
it
showed
you,
which
was
the
active
revision
and
I,
think
you
could
like
switch
that
on
the
revision
list:
anyways
I
apologized,
a
quill
man.
If
I'm
saying
this
wrong
because
it's
memory
from
about
two
weeks
ago,
yeah.
C
I
think
the
screenshot
that
you
posted
Tim
it
currently
just
highlights
the
active
revision.
It's
kind
of
interesting
I
kinda
would
have
expected
there
to
be
an
option
to
set
the
default,
set.
The
active
revision
like
a
radio
button-
you
know
you
like
say
make
this
one
active,
but
I
can
see
that
being
conflicting
with
like
diff
module,
which
also
sets
radio
buttons
and.
C
Radio
buttons
per
row
that
would
be
like
really
overwhelming
to
try
to
figure
out
what
the
tank
was
going
on,
but
maybe
that's
problem
with
diff
module.
Although
we
have
speaking
of
diff
module,
we
have
the
diff
engine
in
Cornell
to
diff
module
II
used
to
include
its
own
definition,
but
when
we
added
the
dipping
of
config
files,
we
moved.
E
C
Definition
into
court,
so
that
also
kind
of
presents
some
interesting
possibilities
of
having
dip
in
core
as
well,
because
really
we're
just
missing
something
that
exposes
that.
You
know
like.
Let's
look
at
the
two
things:
I
don't
know
it
might
get
hairy,
though
so
maybe
maybe
not
I
should
just
put
that
aside.
E
It's
better
if
we
can
a
share
thing
separate
things,
so
we
can
check
the
codes.
What
is
new
and
what
is
old,
so
we
can
decide
what
will
be
best
for
revision,
so
revision
can
once
we
compare
mushrooms,
so
I
cannot
I
can
check
or
you
can
take
what
we
change
and
what
is
not
also
its
need
to
hydrate
highlight
it.
C
E
E
C
The
whole
thing
starts
unraveling,
pretty
quickly
like
trying
to
accurately
demonstrate
like
a
relationship,
change
and
then
showing
what
changed
inside
of
the
related
items,
which
can
be
challenging
even
on
things
like
files
and
in
addition
to
things
like
note
references,
so
I
I
was
I'm
stepping
back
from
the
idea
of
putting
different
a
court
just
because
the
number
of
teacher
of
module
situations
that
need
to
be
accommodated
for
can
be
really
complicated.
You
might.
B
Be
able
to
do
something
like
with
body
feels,
which
is
like
the
majority
use
case
for
wanting
to
see
the
diff,
where
we
could
say
like
okay,
we're
going
to
show
you
the
different
22
body
feels,
but
that's
it
and
then,
if
you
want
more,
you
can
add.
If
you
know,
if
I'm
we've
already
got
like
the
color
coding
from
diff
and
I,
think
we
even
have
some
of
the
defense
in
it
will
be
curious
to
see
what
we
can
do
just
using
what
we
have
on
like
text,
fields
or
body
fields
alone.
Yeah.
C
I
suppose,
if
you
made
it
so
that
the
diff
like
the
dip
functionality
and
core
supported
like
the
field
types
that
were
in
court,
but
then
other
fields,
types
that
were
provided
by
contributor,
write
their
own
diff,
which
I
think
that's
the
way
differential
works
right
now,
actually
that
each
field
type
has
to
provide
its
own
mechanism
for
showing
it.
If
the.
B
C
C
C
Think
how
do
we
make
it
so
that
we
know
what
the
problems
are
with
these
Drupal
7
modules,
so
that
we
can
fix
and
continue
to
maintain
that
within
backdrop
and
the
approach
that
we're
pursuing
right
now?
Is
that
we're
trying
to
figure
out
what
the
security
problems
are,
so
that
we
can
fix
them
on
the
on
the
backdrop
side,
on
the
backdrop,
port
of
those
modules,
but
we
haven't
been
able
to
find
records
of
where
the,
where
the
security
problems,
what
what
security
problems
exist
in
these
modules.
C
So
what
we're
trying
to
do
is
reach
out
to
the
security
team,
either
through
email,
security
at
your
blood
work
or
through
individual
security
team,
maintainer
x',
and
see
if
we
can
get
access
to
those
security
issues
that
affect
these
modules.
I
wish
Jeff
was
still
on
there's
three
modules
that
are
affected
the
most
prominent,
which
is
node
q.
Do
you
guys
remember
the
other
two
that
we
have
ports
of
in
fact
rub
kinship
just.
C
7
version
would
be
a
really
great
thing
for
us
to
contribute
to
the
Drupal
community
as
far
as
I
have
providing
some
continuity,
especially
since
people
on
those
Drupal
7
modules,
like
our
primary,
are
one
of
our
primary
goals
with
back
job
is
to
make
it
so
that
people
can
maintain
their
sites
longer
and
with
less
maintenance
overhead
and
so
make
it.
So
the
Drupal
7
modules
can
continue
to
be
used,
means
that
they'll
be
able
to
upgrade
to
the
backdrop
versions
without
needing
to
replace
that
mantra
with
something
else.
E
You
can
instill
through
automatically
better
abduct
or
but
it
can
be
instilled
through
website
it's
good,
but
why
cannot
delete
from
the
website
from
our
self
ostrich
site
he
can
in
Estelle
also
he
can
earn
a
mystery
and
do
it
through
the
website
is
need
to
FTP
or
SFTP
to
delete
this
software
manually.
So
we
have.
B
I
think
Gregory
recorded
this
in
the
queue
where,
if
you
install
something
using
the
installer
module,
you
can
uninstall
it,
but
you
can't
delete
the
files,
and
so
especially
for
things
like
this
I
have
security
issues.
It's
important
to
let
people
delete
those
files,
I
mean
if
they're
not
running,
that's
good,
but
I
do
think
we
need
to
visit
that
issue.
So
there
there
is
an
issue
in
the
queue
already
for
this
that
we've
been
working
on,
but
I
think
it
would
be
good
to
bring
it
back
up
to
the
top
of
the
list.
B
B
C
B
E
A
I'm
kind
of
time
for
us
to,
but
I
just
want
to
mention
we
had
that
whole
discussion
about
the
bases
sub-theme,
and
maybe
we
just
revisit
that
in
a
future
topic.
I
briefly
updated
the
ticket
in
the
github
issue.
Q2
mentioned
me
idea
about
creating
a
a
module
that
would
help
create
a
something
and
I'd
still
love
to
know
more
about
what
that
means.
But
we
talked
about
that
in
the
future.
Yeah.