►
From YouTube: Backdrop Weekly - July 14th 2022
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).
A
A
A
Thanks
Robert
Joseph
and
then
Jen.
A
Now
yeah
go
ahead,
we've
got
some
announcements
and
you
can
do
the
community
update
as
well.
That
would
be
great
okay.
D
Well,
that's
sort
of
community
related
so
starting
tomorrow
at
eight
o'clock,
Pacific
time,
11
o'clock,
Eastern
I,
don't
know
what
time
UTC
we
are
starting.
The
sixth
backdrop
live.
It
will
go
for
three
hours
on
three
hours
off
all
through
Friday
and
through
halfway
through
Saturday,
maybe
more
than
halfway
through
Saturday.
D
We
have
a
whole
bunch
of
discussions
scheduled.
So
that's
where
a
bunch
of
people
are
going
to
come,
hang
out
in
the
same
room
and
talk
about
stuff,
it's
rather
informal.
You
don't
need
to
do
any
preparation
ahead
of
time.
You
can
drop
into
any
sessions
as
you'd
like
anyone
who
wants
to
attend
should
go
to
events.back.cms.org.
You
can
register
there
and
you
can
take
a
look
at
the
stuff,
that's
already
on
the
schedule,
so
anyone
who's
interested
in
backdrop
might
be
watching
this.
D
Video
between
now
and
tomorrow
morning
or
Saturday
afternoon,
is
welcome
to
come
and
join
that
event.
D
D
Nate
mentioned
before
this
meeting
that
it
might
be
possible
to
put
it
into
the
reference
to
entity
reference
field,
migration
module.
So
I'm
going
to
take
a
look
at
that.
It's
also
very
similar
architecturally
between
reference
and
entity
reference.
It
might
just
need
an
update,
so
I'll
take
a
look
at
that
and
see
if
that
might
be
a
easier
path
forward.
D
Herb
dual
worked
on
that.
So
thank
you
heart
bill
for
doing
all
of
your
work.
On
entity
reference-
and
this
can
trip
module
in
addition
to
everything
else,
you're
doing,
we
also
have
one
other
contributed
module
that
came
out
in
the
last
two
weeks.
It's
called
user
email
display
I'm,
not
sure
whether
we
talked
about
it
last
week
or
the
week
before,
but
I
didn't
want
it
to
get
missed
so
put
that
back
on
the
list
here.
Thank
you
for
the
user,
email
display
contrib
module.
D
This
is
one
that
was
written
by
Alejandra.
So
thank
you.
A
All
right,
let's
see
topics
for
today
we
have
a
forum
post,
Under,
The,
Forum
forum.backtropcmus.org,
for
each
one
of
these
weekly
meetings.
There
weren't
any
posts
this
week
for
things
to
be
discussed
during
this
meeting,
but
Joseph,
who
is
here
in
this
meeting,
has
some
update
he's
been
working
on
cash
tags.
A
It's
been
a
performance
issue,
I
think
we
were
targeting
it
for
the
last
release
or
maybe
the
release
before,
but
it's
complicated
gnarly
issue,
and
so
it's
been
taken
off
of
the
like
having
a
particular
Milestone
Target
and
it's
just
kind
of
an
ongoing
effort
that
he's
been
working
on
so
yeah
Joseph
yeah
tell
us
how
how
cash
tax
is
coming
along
and
and
where
things
are.
C
All
right,
so
the
current
state
of
the
pull
request
it
has
I
believe
everything
is
working
as
intended
on
PHP
versions,
7
and
up.
However,
on
page
versions
prior
to
seven,
don't
allow
an
interface
extending
another
interface
to
change
the
parameters
on
a
method,
but
because
we
have
to
add
new
method
parameters
in
order
to,
in
order
to
require
people
to
actually
pass
an
array
of
cash
tags
into
the
cache
functions.
C
It
breaks
on
older
versions
of
PHP,
so
that's
kind
of
the
it's
kind
of
the
big
issue.
It's
just
it
doesn't
work
on
PHP,
5.6
and
I
am
not
sure
of
a
way
around
that,
because
I
mean
like
I,
don't
know,
I
just
don't
know
how
I
would
get
around
that
without
allowing
people
to
add
the
hashtags.
A
Interesting
that
that's
that's
the
whole,
that
Biz
is
it?
What
you're
saying
that
one
interface
extending
another
interface,
is
that
yes,.
C
What
you
see
we
have,
we
have
a
cache
interface,
and
then
we
have
a
cache
taggable
interface,
that
extends
it
and
the
default
cache
interface
doesn't
have
any
hashtag
handling
and
the
one
that
extends
it
adds
a
tags
array
as
a
parameter
to
the
functions
that
look
up.
Data
from
the
cache.
A
With
their
be
a
reason,
why,
or
would
it
have
some
downside
if
all
cash
bins
were
always
taggable,
so.
A
A
A
Yeah
I
think
I
might
be.
Oh
yeah
I
could
see
that
possibly
being
a
problem
if
their
interfaces
or
their
classes
extended
the
current
interfaces,
but
didn't
have
those
parameters
that
could
be
a
problem
right,
yeah,
yeah,
I'm,
not
quite
sure
what
php's
behavior
is,
when
you
add
a
parameter,
even
if
it's
like
an
optional
one,
I
think
that
sometimes
it
throws
errors.
If
not
all
parameters
are
specified
in
extended
classes.
D
D
A
A
D
C
The
the
problem,
the
problem
is
only
on
PHP
below
seven.
Oh,
a
pretty.
C
A
Well,
Joseph,
it
sounds
like
you're
saying
that
it's
you're
saying
it's
working.
Does
that
mean.
B
A
You're
you're
wanting
a
code
review
on
the
overall
approach
and
implementation.
At
this
point.
C
Sure,
actually
people
want
to
do
code
reviews
I
could
I,
don't
think
I've
marked
it
that
way.
I
could
do
that.
Yeah.
A
I
think
that
would
be
helpful
because
there's
even
if
even
this
one
particular
problem
aside,
there
might
be
lots
of
other
suggested
changes
and
concerns
that
yeah
might
might
not
be
related
to
this.
This
particular
version
problem.
A
Yeah
I'm
curious
just
to
hear
your
based
on
your
experience
so
far.
Building
that
out
what
kind
of
impact
this
would
have
on
existing
code
bases
like
how
much
work
is
it
going
to
be
to
go
through
and
start
adding
tags
to
everything
that
doesn't
have
it
so
far
as.
C
Far
as
core,
so
the
the
pull
request
adds
hashtags
to
all
core
and
it
isn't
anything
that
depends
on
cash
checks
and
core
entities.
C
Work
as
far
as
adding
the
cash
tags
when
you're
loading
a
custom
entity
I
not
that
much,
the
probably
it'll,
be
more
work.
If
you
are
building
something
that
renders
other
entities
nested
inside
of
itself,.
A
Yeah
yeah,
it's
interesting,
yeah
I'd
be
curious
to
see
how
well
this
works
in
the
the
year
is
now
that
it's
been
since
Drupal
has
had
cash
tags.
It's
still
pretty
frequently
a
problem
that,
on
the
projects
I've
worked
on
that
developers
just
have
a
lot
of
issues
getting
the
cache
tags
correct,
and
so
you
end
up
with
a
lot
of
stuff
that
ends
up
like
not
not
clearing.
A
So
yeah
I'm,
not
quite
sure
what
to
really
do
about
that,
though
other
I
mean.
If,
if
we
add
this
caching,
you
know
caching
will
probably
get
more
aggressive.
A
You
know
it
won't
just
automatically
clear
itself
out
most
of
the
time,
but
but
we'll
see
I
don't
backdrop
also
doesn't
really
have
like
partial
page
caching
like
Drupal
does
so.
Potentially
we
won't
have
quite
the
same
level
of
problem
that
the
Drupal
does
right.
Yeah,
let's
we'll
see,
yeah
the
the
trouble
with
the
drip
was
that
it
has
so
many
caches.
The
render
caches
just
like
on
absolutely
everything
and
a
lot
of
that
stemmed
from
the
problem
that
was
created
because
the
templating
system
is
so
slow,
so
yeah.
A
We
we
have
got
in
some
ways
like
some
advantages
that
we
don't
need
to
cash
as
much.
If
we
don't
cash,
this
much
that's
less
potential
for
error,
with
the
cash
tag
configuration.
A
Yeah
well,
I
think
there
should
be
a
very
real
benefit
in
the
event
that
you're
using
a
reverse
proxy
of
some
kind
like
if
you're,
using
varnish
or,
if
you're,
using
a
CDN
fastly
like
that's,
that's
really.
A
The
best
use
of
cash
tags
in
my
mind,
is
that
that
benefit
that
you
can
get
On
Demand
cash.
Clearing
like
in
your
reverse,
proxies
right,
so
yeah,
it's
definitely
kind
of
a
this
is
a
larger
site,
would
would
see
the
greatest
benefit.
A
Okay,
okay,
great
well,
thank
you
Joseph
and
thank
you
for
the
continued
work
on
that.
That's
that's
really
amazing.
Just
hear
that
you're
still
chuggling
Along
on
that
I
know
it's
a
it's
a
gnarly
issue.
A
Okay,
let's
see
Jen
we've
also
got
a
this
design.
Meeting
in
the
general
discussion.
Is
that
anything
that
needs
to
be.
D
Yeah,
that
was
just
in
the
Forum
today
there
was
a
post
to
talk
about
the
layout
issue,
with
placeholders
versus
wild
cards
being
confusing,
there's
an
update
on
that
in
today's
design
meeting.
So
if
you
want
to
hear
summary
of
the
problem,
you
can
watch
that
current
status
is.
There
are
three
pull
requests
with
very
different
approaches,
and
if
anyone
wants
to
weigh
in
on
those,
we
need
help
deciding
which,
if
any
or
all
approaches,
we
should
fursuit
yeah.
D
A
True
1602
yeah,
yeah,
okay,
great
yeah
I,
have
seen
that
there's
been
a
lot
of
discussion
on
that
in
in
this
past
week.
So
great,
let's
see
just
generally
speaking.
If
we
go
into
an
update
on
just
issues
and
development,
that's
been
happening
in
court.
There's
been
a
lot
of
activity
as
of
late
communities
being
very
active,
developing
new
functionality
and
fixing
bugs
it's
been
great.
The
122.1
Milestone
has
21
merged
issues
now,
I
think
we're
still
waiting
on
that.
A
The
layout
context
relationships
sometimes
get
the
wrong
context.
I
don't
have
that
issue
number
here,
but
that
issue
I
think
that
it's
it's
ready
to
go.
It's
marked
needs
review,
but
I
think
the
Alejandra
is
actually
looked
at
it
as
a
stockwellmont.
So,
but
once
that
issue
is
completed,
I
think
that
we'll
be
looking
at
the
122.1
release
coming
out
pretty
quickly
after
that,
just
because
we're
really
accruing
an
awful
lot
of
fixes
in
the
the
122
Branch.
A
So
so
we've
got
that
around
the
corner,
probably
coming
up
pretty
soon
here,
there's
only
four
remaining
rtbc
issues
and
two
of
them
are
blocked,
I
think
so.
Yeah.
We're
really
closing
in
on
on
getting
to
a
good
place
for
a
bug,
fix
release
all
right.
Well,
the
real
real
big
news
this
week
and
I
feel
kind
of
silly
having
waited
this
long
into
the
meeting
to
to
announce
it.
But
in
the
123
release
we
have
merged
issue
1301,
which
is
adding
entity
reference
into
core.
A
So
it's
a
huge
huge
deal
moving
entity
reference
into
core
wholesale
from
the
contrib
version,
really
solidifies.
Our
solution
for
handling
references
permanently
and
into
the
future
and
herbdul
really
did
an
excellent
job.
Getting
that
pull
request,
put
together,
as
well
as
maintaining
the
contribution
and
getting
it
ready
for
core
inclusion.
A
He
also
followed
up
really
quickly
with
there
were
three
additional
commits
that
had
been
made
to
the
contrib
version
that
he
made
pull
requests
for
after
it
was
merged
and
those
changes
are
also
merged
into
123
as
well,
so
yeah
yeah
he's
doing
a
really
really
excellent
job
and
I
think
that
this
week's
official
release
of
the
entity
reference
field
migration
also
is
timed
really
well
that
he's
trying
to
help
people
that
have
chosen
other
reference
module
solutions
for
backdrop
and
get
them
merged
or
get
get
them
moved
over
to
the
new
entity
reference
that
is
part
of
core.
A
So
that's
really
great
to
be
able
to
say
that
when
123
comes
out,
there's
already
potential
Solutions
out
there
to
get
people
onto
the
entity,
reference
module
provided
by
core,
so
yeah
very,
very
exciting
huge.
Thank
you.
We
had
over
20
contributors
to
that
issue,
but
yeah
herbdul
was
the
one
that
would
basically
carried
the
the
final
solution
there
so
very
exciting.
We
do
have
another
issue
and
several
other
issues.
That's
are
coming
out
of
this
one.
A
We
actually
have
a
a
talk,
let's
see
during
backdrop,
live.
That
is
like
what
do
we
do
next
I
think
it's
actually
tomorrow
night
for
for
me
at
least
it's
8
p.m
and
8,
PM,
Pacific
and
so
we'll
be
discussing
or
we'll.
We
have
a
session
to
kind
of
discuss
like
you
know
what
needs
to
be
done,
what
things
are
still
left?
What
we'll
do
about
other
places
to
use
references
like
taxonomy
module
and
we'll
just
discuss
that
during
that
session.
A
Okay,
let's
see
other
issues
that
are
moving
along
John
I'm
curious.
If,
if
you
want
to
do
an
update
on
issue,
647
field,
Group
functionality,
anything
to
mention
there.
D
So
I,
don't
think,
there's
been
an
update
since
last
week,
but
where
it's
standing
right
now
is
that
I
am
threatening
to
remove
the
vertical
tab
that
allows
you
to
clone
a
field
Group,
for
example,
from
a
form
display
to
front
end
display.
What's
that
called
just
a
display,
manage
I
mean
it's
just
light
display
because
it's
really
hard
to
figure
out
how
to
add
it
to
the
manage
Fields
page
in
a
way
that
is
not
confusing.
D
We
do
have
some
other
follow-up
issues
about
cleaning
up
the
manage
Fields
page
in
a
way
that
would
allow
us
to
add
the
managed
group,
our
ad
group
option,
in
a
way
that
we
could
allow
it
to
be
cloned
from
other
displays
later.
D
So
there's
an
option
down
the
road
to
add
it
back,
but
this
would
mean
that
when
it
went
from
a
trip
to
core
we
would
be
losing
that
feature.
So
try
and
yeah
I
don't
know.
If
that's
going
to
be
acceptable.
D
If
not,
we
could
pursue
the
option
of
switching
from
a
vertical
tab
on
that
page
to
a
Action
Link,
which
was
what
the
recommended
solution
would
be.
That
would
just
say,
add
field
Group,
and
then
you
could
choose
to
clone
one
from
another
display
on
the
second
page.
So
it
wouldn't
be
on
the
managed
Fields
page
itself,
but
we.
C
D
A
D
So
just
that
I
mean
that,
rather
than
removing
the
vertical
tab,
I
should
work
on
adding
the
Action
Link.
Instead.
A
Well,
I
mean
there's
that
that
would
be
one
approach,
but
if,
if
what
you're
removing
is
a
convenience,
is
that
right,
yeah.
B
A
Tedious
than
you
know,
then,
that's
not
it's
not
like
a
compatibility
problem.
It's
a.
D
D
D
You
do
exactly
the
same
repeat
exactly
the
same
process
twice,
so
it's
definitely
possible
to
achieve
the
same
goal.
It
just
takes
a
lot
more
time,
but
if
the
goal
is
to
move
the
Action
Link
in
the
in
the
long
term,
we
would
immediately
open
up
a
follow-up
issue.
That's
like
move
ad
group
to
Action
Link,
and
then
we
could
work
on
I'm
sure,
there's
a
clone
option
in
there.
In
addition
to
Great.
A
View
yeah,
my
initial
upon
hearing
this
is
that
it
this
could
happen
like
separately,
that
the
restoration
of
that
feature
can
happen.
Okay
follow
up.
Okay,
let's
see,
Jen
looks
like
you
also
volunteered
to
give
the
update
on
45
69
that
allow
an
admin
to
hide
the
title
on
comments.
Yep.
D
So
Tim
gave
us
an
update
on
this
at
the
beginning
of
the
meeting.
He
said
that
he
got
all
the
tests
passing,
but
he
wanted
his
second
review
on
them
because
he's
not
sure
that
what
he
did
to
get
them
passing
is
the
right
thing
to
do
so.
Last
time
we
talked
about
this
at
a
weekly
meeting.
He
asked
for
help
writing
tests
and
I
helped
him
write
tests
and
everything
was
not
passing
when
I
left
left
him.
D
A
Great
yeah,
thanks
for
for
helping
Tim
with
that,
that's
fantastic
yeah.
That's
all
we've
got
for
123.
I've
got
a
a
general
question.
I
I
haven't
found
the
issue
for
this.
Maybe
if
I
looked
around
a
little
bit
further,
but
I
was
working
on
a
project
and
I
needed
to
limit
the
list
of
allowed
formats
like
per
field.
A
You
know
so
that
let's
say
you
have
five
text
formats
on
your
site,
but
you
only
want
one
of
them
to
ever
be
used
on
a
particular
field
or
you
have
another
field
that
uses
two
of
them,
but
not
the
other.
A
Three
type
situation
also
sometimes
like
we
have
a
site
that
uses
paragraphs
and
one
of
the
paragraph
types
is
actually
called
markdown
and
it's
the
only
place
that
markdown
is
ever
allowed
versus
other
paragraph
types,
and
so
you
end
up
with
a
text
format
that
is
only
ever
used
on
one
particular
field
and
I
found
that
we
don't
have
a
port
of
the
allowed
formats
module,
but
we
do
have
BW
pandas,
preferred
text,
format,
module
which
is
pretty
close
and
functionality,
but
I,
don't
think
that
we
have
a
core
request.
A
Yet
it
seems
like
this
should
just
be
something
that's
in
core,
because
this
sort
of
thing
happens,
all
the
time
I
feel
like,
and
it's
not
like.
A
big
expansion
like
BW
pandas
module
is
like
100
lines
of
code
is.
D
It
on
the
per
field:
it's
like
a
field
setting
yeah.
B
D
Format,
I'm
not
sure
that's
been
merged
either,
but
it's
the
same
thing
where
it
seems
like
kind
of
a
no-brainer
was
never
in
core
but
yeah.
If
you
want
to
create
an
issue
to
put
either
of
those
in
court,
I
think
that's
a
great
idea.
I
think
it's
a
relatively
small
change
and.
B
D
Be
a
good
Improvement
yeah.
D
For
example,
the
same
same
scenario
you're,
describing
where,
like
you,
want
people
to
always
have
access
to
the
advanced
format,
but
there's
one
in
particular,
where
you
know
they're
always
going
to
be
putting
in
a
table
or
something
so
rather
than
making
them
change
it
every
time
they
create
that
node
or
whatever
you
could
just
say
on
this
node.
It's
going
to
be
this
other
one.
D
A
If
you
start
moving
settings
to
a
per
field
basis,
then
more
of
this
setting
should
be
per
field
and
the
global
settings
shouldn't
even
really
exist
like
the
weights
on
the
text
formats.
Don't
really
matter.
If
you're
going
to
start
having
to
have
per
field,
they.
D
I
just
wanted
to
set
the
default.
That's
all
I
was
doing,
I
mean
you
might
have
a
scenario
where
you
want
to
change
the
order
or
we're
talking
about
like
removing
some
from
the
list.
Yeah.
A
D
Yeah
I
still
think
that
might
be
confusing
because
things
in
a
select
list-
I,
don't
know
the
way
selectus
is
supposed
to
work
is
that
the
user
is
supposed
to
know
everything
that
exists
in
that
list
right.
Otherwise
it
would
be
radio
buttons,
and
so,
if
you
have
a
familiarity
with
your
website,
you're
like
okay
I,
know,
there's
four
text
formats
and
I
know
that
the
the
basic
format
is
always
the
first
one
and
then,
if
you
start
moving
them
around,
does
that
like
make
it
less
intuitive
I,
don't
know?
Maybe
it
doesn't
yeah.
A
D
A
Well,
well,
anyway,
I
think
maybe
I'm
just
getting
getting
in
the
details
there,
because
the
solution
I
mean
there's
already
contrib
solutions
for
this
problem
and
they're
quite
simple
and
I.
Think
that's
all
that
I'm
asking
for
is
that
we
get
the
The
Simple
Solution
like
allow
a
reduction
in
the
list
of
text
formats
on
a
per
field
basis
and
I.
Think
that
would
be
a
huge
help,
but
yeah
I,
don't
think
there's
an
issue
for
that.
Yet
so
I
might
make
one
okay,
okay,
that's
it
I!
A
Well,
we'll
close
for
today
once
again
backdrop
live
starts
tomorrow,
so
I
hope
to
see
some
of
those
out
there
watching
this
tomorrow.
That
would
be
excellent
and
yeah
thanks
for
thanks
for
being
here,
everyone
and
thanks
for
watching.