►
From YouTube: Backdrop Weekly - September 1st, 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
Hello,
it's
september
1st
2022,
and
this
is
the
weekly
backdrop
developer
meeting.
This
is
the
feature
freeze
edition
for
123,
which
feature
freeze
is
today
so
we'll
be
talking
about
what
got
in
so
far
and
any
last
items
that
we're
trying
to
squeeze
into
the
release.
Yet
so
we'll
do
some
introductions.
First,
my
name
is
nate
lampton,
I'm
quick
sketch
on
the
internet,
calling
from
oakland
california
we'll
go
to
robert
and
then
joseph.
C
Hi
I'm
greg,
I'm
joining
from
greece
haven't
been
around
in
like
a
few
months
now
trying
to
catch
up
with
everything
I
was
hoping
to
contribute
more
to
this
release,
but
but
yeah
I
got
my
rabbit
holes
in
life,
so
yeah,
I'm
still
trying
to
catch
up,
hoping
to
he'll,
be
helpful
soon
again,.
A
No
problem
greg
and
we're
thrilled
to
have
you
back.
It's
been
yeah,
it's
your
absence
has
been
felt.
Although
you
know
we
managed
thanks
greg,
let's
go
to
tim
and
then
jen,
I'm
tim
erickson,
saint
paul
tim.
B
I'm
in
deerwood
minnesota,
but
in
a
different
location
than
usual.
I
have
two
dogs
that
I'm
dog
sitting
and
they
could
interrupt
our
meeting
at
any
time
so
I'll
try
to
keep
muted.
That's
it.
B
A
All
right,
fantastic
yeah,
a
lot
of
I've
been
saying
the
last
couple
of
meetings.
Summer
vacations
have
all
been
happening
and
now
that's
all
all
wrapped
up
kind
of
back
to
school
season.
Now.
A
All
right
before
we
go
into
the
rest
of
the
meeting,
we
usually
do
a
contrib
and
community
updates.
Jen.
Are
you
available
to
do
that
portion.
B
So
we
have
a
handful
of
new
modules.
This
week
it
looks
like
somebody's
been
busy
with
ubercart
modules
that
are
out
this
week
are
entity
cash
administration,
ubercart,
new
expiration,
uber,
cart
clearance
and
taxonomy
child
blinks.
A
Super
that
looks
like
it
may
be
robert
working
on
those
things
yeah
excellent.
Let's
see
I've
also
been
working
on
stripe
module
recently.
Sorry
just
going
off
on
a
total
tangent,
which
has
been
really
great
to
see
that
laryn
also
has
been
a
great
partner
to
work
with
over
there.
So
it's
great
to
also
have
that
sec
part
of
the
commerce
equation.
Moving
forward.
A
Let's
see
now
I've
lost
my
agenda:
okay,
okay,
123!
Oh
wait!
Hang
on
one
one
more
thing:
general
general
discussion
before
we
get
into
the
123.
tim
just
wanted
to
raise
issue
5631
that
there
is
an
issue
with
backdrop
throwing
500
errors
on
the
promoted
card
view
in
some
situations.
A
That
issue
is
progressing
pretty
quickly
5631,
but
if
we
get
some
additional
eyes
on
reviewing
that,
that
could
be
appreciated
to
fix
that
problem,
because
it
sounds
how
how
often
does
this
occur
or
likely
is
it
to
occur
time.
B
It
I
think
it
varies
from
person
to
person.
For
me,
I
don't
see
it,
I
do
six
or
eight
installs,
I
don't
see
it
at
all
and
then
I
might
see
it
two
or
three
in
a
row.
So
it's
just
really
ad
hoc,
which
makes
it
hard
to
test.
I
think
rj
piano
has
come
up
with
some
some
reproducible
steps
and
he
thinks
he
has
a
possible
fix
on
it.
So
if
anybody
could
help
out,
but
especially
because
it's
so
erratic
having
a
little
more
testers
might
help.
C
B
A
Okay,
let's
see
that's
all
on
that
issue.
Someone
put
hunter.dev
on
here,
I'm
guessing
that
might
have
been
you
jen,
since
yeah.
A
B
I
didn't
know
if
that
was
worth
bringing
up.
Hunter.Dev
is
a
platform
that
distributes
funding
for
security
issues
across
any
number
of
possible
platforms,
and
we
got
access
to
be.
I
don't
know
moderators
for
the
backdrop
project
on
that
platform
just
recently,
and
so
there's
a
handful
of
new
issues
in
the
security
queue.
I'm
not
sure
any
of
them
are
security
issues
them
or
like
hardening
requests
so
far,
but
anyway
I
just
wanted
to
mention
it,
because
it's
kind
of
an
interesting
idea
of
finding
ways
to
pay
people
for
security
things.
B
B
B
I
think
we
could
have
figured
this
stuff
out
on
our
own,
but
it
is
nice
that
people
are
looking
at
backdrop
as
an
open
source
platform.
They
can
contribute
to
in
various
different
places,
yeah
cool.
A
Yeah
and
that's
hunter.hunter
with
no
e
in
it
kind
of
like
flicker,
maybe
the
the
dropped
e
is
coming
back
in
vogue.
A
Yeah.
Very,
very
interesting
idea,
though:
it's
kind
of
like
public
funding
for
bug,
bounty
programs
where
somebody
else
pays
for
the
bug
bounty
amount
and
then
I
guess
we
get
to
distribute
it.
I
haven't
quite
figured
out
how
that
works.
Yet
yeah.
B
It
looks
like
every
issue
the
project
maintainer
gets
to
like
weigh
in
on
like
the
severity
of
it
and
there's
a
calculation
that'll
determine
what
the
payout
is,
and
I
think
there's
like
some
small
payout
for
reporting
the
issue
and
then,
if
someone
else
were
to
fix
it,
they
would
get
a
larger
payoff.
A
B
They
do
have
some
pretty
strong,
like
gamification
around
trying
to
prevent
abuse.
So,
for
example,
the
two
there
were
two
issues
that
I
marked
as
like,
not
applicable
because
they
were
user,
one
related
and
there's
an
option
there
for
when
you
market
n
a
it
says,
the
submitter
will
have
their
karma
decremented
five
points
for
submitting
an
issue.
B
That's
not
a
legitimate
security
concern,
so
they
think
they're
trying
pretty
hard
to
prevent
just
a
bunch
of
noise
from
happening
there,
and
then
there
was
one
that,
like
wasn't
a
security
problem
for
us,
but
was
still
like
you
know.
We
already
had
an
issue
in
the
queue
we've
been
talking
about
potential
hardening,
and
so
I
thanked
the
person
it
was
like
their
karma
has
been
increased
by
one.
So
I
was
like
okay,
I
don't
know
so
yeah
it's.
A
Sounds
great:
okay,
let's
see
all
right,
we'll
go
into
the
status
report
here.
So,
as
I
mentioned
at
the
beginning
of
the
call
today
is
feature
freeze
for
123.0
and
we're
looking
really
good.
There's
one
issue
remaining
in
the
123
milestone
right
now.
A
A
I
didn't
actually
put
it
in
the
agenda.
That's
why
I'm
a
little
bit
frazzled
here
anyway.
There's
an
issue
for
consolidating
fields
on
the
user
profile
form
into
vertical
tabs,
and
that
is
the
last
open
issue
that
is
in
the
123
milestone
here
it
is,
it's
number
3872.
A
Bw
panda
is
the
person
who
owns
the
pull
request,
but
he
hasn't
updated
or
made
a
comment
in
past
couple
of
days.
So
I'm
thinking
that
we
may
need
someone
else
to
make
an
updated
poll
request
there.
I
think
that
the
feedback
is
pretty
clear
as
to
what
needs
to
be
done
and
also,
I
think,
kind
of
we're
arriving
at.
A
You
know
a
consensus
that
this
is
a
safe,
safe
enough
thing
to
do
and
within
our
our
backwards
compatibility
policies
just
generally
like
trying
it
out
it
just
is
a
like
it's
an
improvement
for
sure,
like
the
user
profile
page
is
just
a
big
fat
mess,
and
this
really
helps
clean
it
up
quite
a
lot.
It
also
includes
some
vertical
tabs
include
like
little
summaries
beneath
all
of
the
items,
and
the
pull
request
includes
the
associated
javascript
to
populate
all
of
those
like
little
summaries
that
are
inside
of
the
vertical
tabs
as
well.
A
However,
that
is
where
some
of
the
suggestions
are
in
the
pull
request
for
improving
the
implementation
a
little
bit,
but
that
issue
is
looking
really
good.
We
still
like
our
policy
on
feature
freeze
day,
is
kind
of
like
end
of
day
on
on
that
day,
which
really
means
kind
of
like
literally
as
long
as
it's
still
september,
first
somewhere
in
the
world,
then,
and
there's
a
core
committer,
that's
awake
and
working.
Then
then,
then,
we're
still
kind
of
open
for
for
last-minute
things.
C
Noting
that
this
is
flag
does
a
task,
and
I
agree
with
that
and
not
a
feature
so
in
theory
it
can
get
with
the
bug
fix
release.
So
it's
not
a
blocker
for
123
percent.
A
Yeah,
it's
also
in
theory
a
ux
thing,
which
also
is
exempt.
You
know
so
there's
kind
of
lots
of
ways
that
you
could
say
that
this
is
exempt.
However,
considering
it
it's,
it
is
changing
form
api
structure.
I
do
think
it
would
be
nicest
if
we
got
into
a
1
23
or
into
a
minor
version,
but
I
guess
I
also
see
what
you're
saying
that
that
leaves
the
door.
C
Exactly
not
putting
it
in
20
122,
but
you
know
123.1
or
yeah,
follow
up
whatever
yeah.
A
Yeah
yeah
worth
saying,
of
course,
that
today
is
feature
freeze
and
then
the
official
release
of
123
will
be
coming
out
in
two
weeks
on
september
15th.
A
C
I
have
a
question
with
regards
to
that.
As
I
said,
I
didn't
have
enough
time
to
just
hop
back
in
the
pr
wagon
or
whatever
you
call
it,
and
I
I
remember
that
one
of
the
issues
that
I
was
I
chimed
in
and
I
reviewed
recently.
I
had
some
suggestions
about
naming
the
config
entries
now.
If,
if
we
merge
that
already
without
those
changes,
it
means
that
if
we
decide
to
do
go
ahead
with
those
changes
in
a
future
version,
it
will
mean
that
it
will
need
an
update
hook.
C
So
the
related
question
is:
if,
if
we
are,
if
we
plan
to
change
those
things
between
when
the
the
pre-release
is
out
and
the
actual
release
is
out,
do
we
do
an
update
hook
because
the
pre-release
is,
in
other
words,
what
I'm
asking
is?
Does
the
pre-release
count
as
an
actual
release
or
are
these?
Are
things
still
in
a
flux
there
and
contains
at
any
time
that's
what
I'm
asking.
A
Yeah,
this
is
actually
kind
of
an
interesting
thing
regarding
the
way
that
we
operate,
update
hooks
generally,
and
that's
that
if
there
were
to
be
something
wrong
with
one
of
our
update
hooks
or
something
like
that,
we
would
need
to
add
another
update
hook
to
fix
the
previous
one.
Rather
than
just
going
back.
And
I
mean
if
we
can
fix
the
previous
one
too.
A
But
then
we
also
need
a
follow-up
one
so
that,
like
anybody,
that's
like
following
the
latest
release
should
just
be
able
to
run
update.php
again
to
fix
any
previous
data,
corruption,
problems
or
config
problems
that
we
may
have
caused,
and
we
try
to
actually
maintain
that
continuous
stream
of
like
you,
should
always
just
be
able
to
run
update.php
to
fix
things
almost
constantly
like.
We
really
don't
want
that
to
ever
happen,
even
in
between
minor
releases.
A
Really-
and
I
guess
that's-
maybe
a
bit
a
bit
aggressive,
but
I
would
definitely
think
that
the
preview
release,
if
there's
something
wrong
with
an
update
hook.
We
would
absolutely
add
another
update
hook
for
people
running
preview
to
make
it
so
they
can
move
to
123
final
directly
off
of
their
preview
version
of
their
site
yeah.
A
I
I
also
would
say
that
we
don't
really
encourage
people
to
run
preview
in
production,
you
know
or
to
make
backups
before
they
run
preview,
but
at
the
same
time
like
we
just
want
to
try
to
make
people's
update
as
smooth
as
possible
if
they
are
doing
that.
So
it's
like
kind
of
discouraged,
but
we
also
really
try
our
best
to
accommodate
that
situation.
C
Yeah
yeah,
I
guess
what
what
I
was
asking
is,
that
is
the
pre-release
an
actual
release,
or
is
it
a
release
just
for
the
fact
that
it's
a
release,
because
I
remember
the
the
the
reason
for
it
to
be
born-
was
to
basically
give
an
easier
way
for
people
to
test
the
current
brands
have
a
release.
That's
why
I
was
asking
but
yeah.
If
it
is
to
be
treated
as
a
release,
then
yeah.
It
answers
my
question.
A
Yeah,
it
doesn't
show
up
in
update,
update
module
or
anything
like
that,
because
it's
not
marked
as
a
final
release,
and
so
it's
kind
of
like
a
beta
or
alpha.
It
doesn't
take
precedence
over
the
current
release,
so
it
doesn't
really
get
a
very
wide
distribution
because
of
that,
but
it
does
at
least
you
know
earmark
a
particular
point
in
time
as
being
like.
This
is
the
preview
release
yeah.
A
Okay,
let's
see,
let's
talk
about
123
then
mostly
today
is
going
to
be
a
bunch
of
celebrating,
because
we
had
an
amazing
week
wrapping
things
up
as
always:
deadlines
really
push
us
to
shorten
our
release
cycles
and
hopefully
be
some
of
the
best
developers
we
can
be,
although
I
think
also
people's
patience
ran
a
little
bit
short
at
times,
but
we
worked
it
out
together.
A
Let's
see,
the
first
issue
is
related
to
the
the
one
issue:
that's
still
open,
the
combining
of
field
sets
into
vertical
tabs
and
then
50
5747
was
a
new
idea
that
just
came
up
this
week
from
herb
dual
that,
while
reviewing
that
user
profile
form,
we
have
had
this
situation
where
a
logged,
a
lower
level
permission
user,
might
go
to
their
user
profile
page
and
have
vertical
tab.
A
A
So
it's
a
nice
little
ux
improvement
that
helps
that
situation,
but
also
just
generally
helps
other
places
where
there's
only
one
vertical
tab.
I
think
the
one
that
pops
up
for
me
all
the
time
is
url
aliases
on
taxonomy
terms.
I
think
that
there's
only
one
item
on
taxonomy
terms,
often-
and
this
also
helps
that
that
situation
so
yeah.
B
Thank
you.
Can
I
just
throw
this
out
here
and
that
this
does
affect
the
user
experience
in
that
the
vertical
tabs
are
supposed
to
tell
people
you
can
ignore
everything
in
here,
and
so,
if
there's
something
like
the
url,
alias
that
you're
supposed
to
ignore
you
take
it
out
of
there
and
you
put
it
on
the
page.
B
C
Haven't
tested
the
pr
I
just
saw
the
the
initial
sort
of
like
manifestations
of
the
initial
version
of
the
pr,
but
to
accommodate
for
what
you
just
said,
because
this
is
the
guideline
right
for
when
to
use
vertical
tabs,
we
could
have
it
be
a
field
set
by
b
but
be
collapsed
right
and
then
it's
still
not
as
important
and
as
far
as
I
remember
field
sets
in
a
distant
desktop
mode.
C
They
do
have
a
summary,
like
a
grayed
out
summary
similar
to
how
vertical
tabs
have
the
javascript
generator
summary
so
yeah
that
might
mitigate
that
fact.
Okay,.
A
B
C
C
A
Know
it
all
just
depends
on
what
the
original
field
set,
because
the
original
field's
like
it's
converted
to
vertical
tabs
yeah.
B
A
And
that's
the
case
for
url
aliases
they're
collapsed
on
taxonomy
terms.
I
guess
so
so
it
actually
ends
up
taking
a
lot
less
room
because
a
vertical
tab,
yeah.
A
B
A
Yeah
anyway,
I
think
that's
a
great
change.
Yeah
it'd
be
interesting
jenna.
I
don't
think
you're
going
to
be
the
only
one
to
identify
some
consequences
from
that
change.
I
think
it's
like
a
good
pattern,
but
it
may
also
you
know.
People
might
not
style
both
situations,
for
example
like
so
it
could
potentially
cause
some.
You
know
additional
leg
work
there
on
the
behalf
of
people
that
are
trying
to
make
a
consistent
experience.
B
A
Totally-
okay-
let's
see
here
I
I
guess
the
next
item
I
have
here
is:
I
just
have
entity
reference
yet
again,
issue
1301,
just
again
celebrating
we
got
that
in
months
ago,
and
it
looks
like
the
only
follow-up
issue
that
we
had
on
that.
A
One
is
that
we
also,
you
know,
changed
the
return
value
of
the
uri
method
on
files,
and
so
that's
an
api
change
that
we
had
to
make
to
accommodate
files
and
entity
references,
that's
also
been
in
and
that's
we
have
it
and
now
I'm
saying
it,
but
I'm
not
totally
sure
it's
true
a
change
record.
If
we
don't
have
one,
we
absolutely
need
one
but
yeah
entity.
Reference
and
core
is
going
to
be
our
headline
feature
for
for
this
release
and
it's
very
exciting
that
that
has
been
completed.
A
We
just
lost
tim
I'll,
come
back
to
his
issue
because
that's
kind
of
an
exciting
one
for
him.
I
think
the
one
he
was
advocating
for,
let's
see,
let's
go
to
allow
forms
to
have
custom
validation,
messages
on
required
fields,
issue
53
53-48.
A
We
got
final
reviews
from
robert
into
gozella
and
greg.
So,
thanks
to
the
two
of
you
that
are
that
are
in
this
meeting
I
was
really
happy.
I
was
really
happy
to
see
that
one
come
to
completion
greg.
You
were
the
one
that
originally
advocated
for
this.
Do
you
have
any
thoughts
or
feedback
on
the
way
things
shook
out.
C
Okay
now
I
said
I
started
so
it's
still
half
written
the
comment
there
and
it
was
like
it's.
It
is
a
lengthy
like
it's
an
old
issue,
so
it
was
quite
lengthy
it
and
it's.
We
had
some
good
ideas.
C
Some
good
gotchas
there
that
people
caught
that,
I
don't
wanna,
you
know-
be
missed
for
the
future,
so
I've
started
filing
follow-ups
and
and
this
it
wasn't
a
hard
blocker
for
certain
things,
but
it
sort
of
certainly
makes
things
easier
now,
yeah
one
one
thing
that
I
had
for
a
follow-up,
I'm
not
sure
if
I
filed
I
made
a
note
of
which,
but
it
didn't
file
an
issue.
It
was
that
we
still
have
some
weirdness
happening
with
the
search
form.
B
C
We've
made
it
as
possible
as
as
smooth
as
possible
as
backwards
compatible
or
consistent
as
possible,
but
at
least
we
have
like
we
should
return
to
it
and
fix
things
but
yeah.
It's
I'm
super
excited.
A
Yeah,
the
search
in
general.
The
interfaces
really
need
some
some
work.
My
my
favorite
thing
about
search
in
core
is
I
like
to
use
it
for
views.
However,
I
also
found
some
issues
with
that
with
that
recently,
but
yeah
yeah
search
search
has
just
got
some
complexities
when
you
have
when
you.
A
Yeah,
you
know
something
else
I
wouldn't
mind
talking
about.
If
we've
got
time,
you
followed,
you
filed
the
follow-up
57.50,
which
is
the
idea
that
I
had
about
conditional
fields,
and
I
filled
out
that
issue
with
I
updated
the
summary,
with
a
more
elaborate
description
and
I
posted
some
code,
samples
of
what
that
might
look
like.
A
I
would
love
feedback
from
other
developers
on
the
idea
there
and
also
the
syntax
that
I've
put
forward
there.
I
think
that
this
might
be
a
little
bit
of
a
rabbit
hole
talking
about
a
new
form.
A
Api
property
that
has
a
complex
syntax
kind
of
like
pound
states
has
a
complex
syntax,
but
I
think
that
we
might
be
able
to
do
a
little
bit
better
than
pound
states,
but
the
issue
5750
is
about
replacing
or
providing
an
alternative
to
states
that
as
a
client
side
and
a
server
side
component
to
it,
pound
states
is
entirely
client-side
front-end,
which
means
that
it
can
hide
and
show
fields,
but
it
can't
conditionally
process
the
submit
values
of
those
fields.
A
The
element
validate
handler
would
be
skipped,
as
would
the
requiredness
check,
and
so
it
would
make
it
so
that
we
could
hide
and
show
entire
sections
of
the
form
while
skipping
the
processing,
the
saving,
the
validation.
Everything
about
that
section
of
the
form
that
was
hidden
that
that's
the
the
concept
there
and
I
think
that
c
tools
actually
had
something
like
this.
We
had
to
do
some
minor
converting
of
things
from
c
tools,
conditionals
to
pound
states
when
we
put
views
in
core.
A
Not
widely
used
not
not
terribly
powerful,
I
don't
think
but.
C
C
No
all
I
know
is
that,
because
I
work
a
lot
with
ux
issues,
I
I
I
work
a
lot
with
forms
and
I
use
states.
A
lot
is
that
over
the
last
years
I
I've
been
exposed
to
many
of
its
intricacies
and
shortcomings,
and
I
would
be
glad
I
don't
understand
the
technicalities
the
technical
sort
of
like
I
can't
contribute
to
making
a
decision
with
the
technicalities
of
the
the
new
alternative,
but
I'm
happy
to
test
it
if
it's
to
be
a
a
smoother
alternative
than
states.
That's
all
I'm
saying
yeah.
A
Yeah
yeah,
the
the
kind
of
innovation
that
I
had
in
this
issue
is
a
is
a
form
api,
proper
or
form
api
problem
that
we
have
with
some
other
obscure
properties
like
pound,
limit
validation,
errors,
pound
limitation,
pound
limit
validation,
errors
works
off
of
the
form
api
keys.
You
specify
the
part
of
the
array
that
needs
to
be
validated
when
you
click
this
particular
button.
A
Your
form
is
a
smaller
part
of
a
bigger
one,
and
the
idea
that
I
had
in
57
50
was
that
we
introduce
a
syntax
that
matches
the
directory
traversal
patterns
from
linux,
where
you
do
dot
to
say
my
current
position
or
you
do
dot
dot
to
say
up
one
directory
in
this
case
up
one
form
api
element,
so
you
could
say
you
know
conditionally
depend
on
another
element
that
is
up
one
parent
and
then
down
one
more
sibling
so
that
you
could
traverse
relative
to
your
current
position,
instead
of
needing
to
specify
the
entire
list
of
keys
from
the
very
beginning
of
the
the
form
route.
A
So
I
think
that
that
would
be
a
huge
help
for
this
kind
of
conditional
system,
because
it's
very
often
that
you,
you
want
to
you,
know
you're,
specifying
two
things
that
are
dependent
upon
each
other
in
your
little
partial
of
the
form,
and-
and
this
could
make
it
so
you
don't
need
to
care
about
the
rest
of
the
form
at
all,
so
anyway
very
excited
about
that
kind
of
potential.
It
also
could
make
it
so
we
could
improve
limit
validation
errors,
so
they
could
also
use
this
new
traversal
syntax.
A
Yeah
yeah
and
I
I
think
that
you
know
we
can
do
better
than
states
I
I've.
You
know
I
just
have
the
hardest
time
writing
pound
states,
and
I
can
always
tell
that
I've
been
doing
too
much
work
when
I
can
write
a
pound
states
from
memory.
You
know
I'm
just
like
I
shouldn't
be
able
to
do
this
like
this
is
way
too.
A
This
is
way
too
obscure
to
be
able
to
remember
or
should
be.
A
Anyway,
yeah
I'm
excited
about
that
that
concept.
So
thank
you
for
filing
that
issue,
craig
and
yeah.
That
would
be
great
to
get
some
feedback
on.
A
this
lasts,
I
say
last
minute,
but
it
really
was
just
kind
of
the
the
issue
that
we
weren't
expecting
to
get
done,
but
did
issue
50
42
55,
add
a
new
date
widget
to
utilize
html5
date,
input
type
that
was
spearheaded
by
indigozella,
who
filed
the
issue
a
couple
of
years
ago,
actually
but
really
started
working
on
in
earnest
about
a
month
ago.
So
indigozala
herb,
dual
and
yorkshire.
Pudding
really
went
through
a
rapid
review
cycle
for
the
last
couple
of
weeks
to
bring
that
to
completion.
A
So
that's
a
great
new
feature,
a
nice
new,
modern
widget
for
inputting
dates.
We
actually
already
were
using
the
html5
date
input
for
the
created
an
updated
time
on
nodes,
but
because
those
weren't
fields
field,
module
fields.
We
were
using
the
like
form:
api
head
support
for
html5
dates,
but
date
module
didn't
actually
expose
them
as
an
option
for
inputting
dates
through
the
field
system.
So
this
now
exposes
those
a
really
great
enhancement.
A
A
We
were
talking
about
whether
or
not
this
was
a
a
good
candidate
for
including
in
core,
because
it's
a
little
bit
obscure,
but
it's
also
not
it
does
it
doesn't
pop
up
in
your
face.
It's
not
like
a
you
know
like
a
distracting
feature,
it's
a
complexity
similar
to
that
of
views.
That's
if
you're,
in
the
depths
of
views
needing
a
particular
functionality.
A
We
want
that
functionality
to
be
there
for
a
core
core
systems,
and
this
is
the
same
thing
for
layouts,
that
it
adds
a
visibility
condition
that
is
very
similar
to
views
functionality,
for
you
know,
selecting
the
level
of
depth
if
you
have
a
hierarchical
on
taxonomy,
so
issue
29.55
that
got
completed
this
past
week
as
well.
A
Oh
okay,
yep
sure,
is
okay.
Oh,
I
also
wanted
to
say
one
more
thing
about
that
setting
the
required
validation
error
message
that
robert
I
saw
that
you're
already
working
on
updating
the
form
api
documentation.
A
Okay,
yeah.
Thank
you
for
for
doing
the
work
there
yeah
our
form
api
reference
is
a
a
pretty
incredible
system.
Now
it's
every
property
is
a
node
on
the
dock
site
and
you
can
say
what
or
every
element
is
a
node
on
the
doc
site.
You
can
say
which
form
api
elements
which
support
which
form
api
properties
and
because
this
this
property
is
supported
on
all
of
them.
A
Okay,
let's
see,
and
we
also
had
one
more
api
enhancement
issue:
3902,
adding
config
get
data
to
match.
Config
set
data,
so
a
small
improvement
to
our
for
our
config
system
that
we
had
a
getdata
method
that
got
you
literally
everything
in
the
config
system
and
we
have
config
set,
which
also
could
be
used
to
set
the
entire
config
files
contents.
But
it
wasn't
clear
that
you
could
use
it
in
that
way.
A
The
only
item
that
I'm
aware
of
from
this
past
week
that
got
bumped
into
124
was
field
group
functionality,
issue
647.,
which
would
still
seem
like
it
was
pretty
far
from
from
being
ready
but
yeah
what
a
week
just
I
think
we
got
five
five
issues
completed
for
1
23
and
then
that
one
with
the
user
profile
page
is
right
right
there
on
the
cusp
too,
so
it's
been
a
heck
of
a
week,
really
happy
once
again
for
all
of
the
time
that
our
contributors
have
provided
to
make
all
of
this
great
functionality
happen.
A
123
is
going
to
be
a
great
release.
It's
very
exciting
lots
of
not
just
the
the
major
feature
of
entity
reference,
but
now
you
know,
we've
got
a
couple
of
other.
You
know
definitely
noteworthy
new
features
here
in
this
release.
A
Thank
you
yeah
issue
4569,
which
is
allowing
the
admin
to
completely
hide
the
title
on
comments.
This
issue
was
over
200
comments,
long
on
github,
so
definitely
one
of
our
longer
more
difficult
to
work
out
issues
just
for
the
intricacies
of
backwards
compatibility,
updating,
templates.
A
Whether
or
not
to
add
a
little
link
icon,
like
you,
know,
all
of
the
little
things
that
sometimes
make
make
issues
difficult,
5469
kind
of
had
all
of
them.
I
posted
this.
As
my
comment
when
I
was
marking
the
issue
as
fixed
that
I
recall
my
previous
boss
at
lullabot,
co-founder
jeff
robbins
complained
to
me
very
loudly.
It
was
like
one
of
his
pet
peeves
was
comments
had
titles
in
drupal,
and
it's
just
like
why.
Why
is
this
like
comments?
A
Don't
have
titles
like,
and
that
was
like
that
was
like
15
years
ago
that
that
was
like
his
pet
peeve
and
it's
just
like
now,
it's
finally
finally
fixed
for
a
backdrop,
at
least
that
this
makes
it
so
that
comments
previously,
you
could
have
com
or
comment
titles
be
automatically
generated,
so
a
user
wouldn't
necessarily
need
to
enter
one,
but
then
they
would
get
displayed
an
automatically
generated.
A
One
would
be
displayed
on
the
front
end,
and
this
makes
it
so
that
comments
truly
can
have
no
title
displayed
on
the
front
end
at
all.
A
user
doesn't
need
to
enter
one
and
there's
not
one
displayed.
There
is
no
one
automatically
generated
for
administrative
purposes,
but
but
at
least
it
doesn't
show
up
anymore,
so
yeah,
big
kudos,
I'm
sad
tim
isn't
here
to
receive
the
praise
but
yeah
great
job,
walking
that
one
through
to
to
completion
that
does
it
for
for
123.,
pretty
excited
about
this
release.
C
I
wanted
because
I've
been
away
for
so
long
just
to
ask
if
there
were
any
any
progress
or
plans
to
work
on
ck
editor
live
integration.
C
B
C
How
are
we
going
to
handle
that
then?
I
know
that
they
delayed
or
they
postponed
end
of
life
in
four,
for
the
sake
of
allowing
drupal
to
silver,
complete
the
the
work
that
is
required
to
move
from
four
to
five,
but
once
that
happens,
it's
like
it
sounds
that
this
is
the
only
dependency
core
dependency
that
we
have,
which
is
similar
to
how
drupal
depends
on
symphony
and
because
they're
end
of
life
and
other
things
we
need
to
move
to.
So
that
might
mark
something
that
will
need
to
select
initiate
the
backdrop.
A
It's
a
good
question
because
we're
not
sure
if
seek
editor
4
will
have
a
long
enough
life
for
us
to
continuously
use
it.
You
know,
even
in
new,
like
in
new
versions
of
backdrop,
while
seek
editor.
4
might
be
completely
unsupported.
A
That
could
put
us
in
a
you
know
pretty
tenuous
position
if
there
were
security
issues
discovered
in
sick
editor,
so
it
is
kind
of
a
you
know
it
if
it's
a
backwards
compatibility
problem,
maybe
what
we
end
up
doing.
Is
it
maybe
not
backdrop
two?
But
you
know
we
ship
a
seek
editor,
five
module
with
backdrop,
but
it
still
might
not
be
either
enabled
by
default
or
it
might
not
be.
We
definitely
wouldn't
like
force
people
to
disable
the
old,
sequential
module
to
turn
on
the
new
one.
B
Because
I
think
that
the
problem
is,
it
won't
render
any
of
the
content
in
the
database
properly
because
it
saved
it
the
way
50
editor
4,
wanted
it
and
then,
when
it
goes
to
render
and
5
it's
like,
I
don't
recognize
any
of
that
stuff,
but
on
our
side
like
when
it
renders,
when
it
prints
out,
it
doesn't
matter
right
because
it's
just
markup,
so
it
would
just
be
the
user
interface
that's
affected.
So
it's
kind
of
like
questionable
as
to
whether
that's
an
api
break
for
us
or
not.
B
C
That's
actually
that's
actually
why
I
was
asking,
because
I
remember
about
a
month,
a
month
and
a
half
ago,
reading
what
what
the
drupal
peeps
are
doing
and
they
do
have
an
upgrade
path
or
migration
path
that
they're
working
on.
So
I
was
wondering
if
we
could
leverage
that
as
well
anyway
and
and
I'm
bringing
this
up
because
we
have
nate
here,
and
you
know
if
there's
one
person,
that's
expert
around
there,
it's
linked.
A
Yeah,
the
the
seek
editor
five,
you
know
I
I
think
that
module
wise
like
seek
editor,
the
module
that
we
have
right
now
is
going
to
be
pretty
close
to
what
we
need.
As
far
as
like
the
backdrop
side
of
things
you
know
like
it,
handles
the
the
configuration
form
you
know
dragging
and
dropping
buttons.
A
The
tricky
part-
and
hopefully
it's
not
too
terrible
but
jerky
part-
is
that
we
have
a
couple
of
custom
plugins
for
link,
handling
and
image
handling
that
need
to
be
updated
to,
I
say,
update
it,
but
need
to
be
rewritten
for
seek
editor
five
5.
A
and
I'm
hoping
that
isn't
too
bad,
especially
like.
Maybe
we
can
leverage
the
javascript
from
the
drupal
project,
but
the
drupal
project
is
also
kind
of
moved
away
from.
Actually,
I
think
even
the
the
custom
link
dialogue
they
removed
because
seek
editor.
Five
has
like
inline
link
handling,
but
honestly,
I
I
feel
that
the
dialogue
is
still
necessary
because
the
out
of
box
link
handling
doesn't
deal
with
like
attributes
targets
classes.
A
It
doesn't
have
auto
complete
on
the
the
paths.
There's
all
kinds
of
things
that
the
dialogue
provides
us,
that
the
inline
link
handling
doesn't
and
what
I
would
love
to
see,
and
this
might
be
some
communication
we
need
to
have
with
the
seek
editor
team
that
would
benefit
both
of
our
projects
would
be
if
we
can
make
the
link.
The
inline
link
handling
also
have
like
a
you
know,
edit
details
or
something
like
that.
A
That
then
opens
up
the
the
backdrop
or
drupal
provided
dialog,
so
you
could
retain
the
old
functionality
while
getting
the
ease
of
the
inline
handling
functionality
that
that
cq
editor
provides
yeah
and
yeah.
There's
lots
of
things
about
seek
editor
five
that
javascript-wise
we're
just
going
to
have
to
figure
out
some
of
the
challenges:
the
the
drupal
sequencer
5.
Last
I
looked
at
it,
which
was
only
that
was
like
I
don't
know
like
six
months
ago,
so
it
has
been
a
while.
A
But
even
though
it's
in
core
in
drupal
9,
it's
marked
experimental.
If
you
try
to
use
it
at
this
point
like
it's,
it's
not
really,
it's
not
it's
not
there.
Yet
at
least
it
wasn't.
When
I
looked
at
it
so
there's
I
I
think
what
I'm
getting
at
with.
A
That
is
that
I
think
that
there's
still
more
time,
because
if
drupal
isn't
yet
ready
to
even
move
to
seek
editor
5,
yet
as
a
as
a
stable
module
and
certainly
not
as
the
default
module,
then
I
think
that
that
will
it
continue
to
encourage
the
seek
editor
project
to
maintain
seek
editor
for
for
a
longer
period
of
time,
ck
source,
the
company
that
built
seek
editor,
is
very
tightly
integrated
into
the
drupal
community,
great
relationship
they
use
drupal
for
their
own
website
and
so
they're
they're
very
tied
into
the
drupal
community.
A
I
think,
will
help
make
that
transition
smooth
as
they
can
so
for
now.
I
think
that
means
supporting
seek
editor
for
for
a
longer
period
of
time.
C
Yeah,
well,
I
did
a
really
quick
and
let's
move
away
from
that,
just
as
a
last
nation,
I
did
a
quick
research
and
it
mentions
that
end
of
life
or
what
they
they
consider.
A
long-term
support
program
for
secretary
of
voice
guaranteed
until
2023.
That's
what
I'm
reading
so
yeah
anyways.
A
Which
is
kind
of
interesting,
that's
that
is
interesting.
That's
in
line
with
drupal
7
so
far
that
dribble
7's
end
of
life
is
at
least
2023,
but
you
know
tbd.
You
know
really
yeah.
C
A
C
A
Yeah
yeah,
let's
yeah,
let's
move
on,
but
that
is
a
really
fertile
topic
for
discussion,
because
there's
a
lot
to
happen
there
I
did.
I
will
say
that
I
did
make
a
module
like.
I
started
one,
but
it's
like
not
it's
not
anywhere
close
to
doing
anything
yet
so
I
I
would
like
to
yeah
make
some
progress
on
that
at
some
point.
A
Let's
see
well
we're
almost
out
of
time,
but
I
always
like
to
end
these
meetings
when
we're
in
between
the
we're
done
with
new
features,
except
for
that
user
profile
form
one,
and
then
we
have
this
two
week
period
before
the
next
version
is
released,
where
we
should
be
spending
our
time
if,
if,
if
we're
not
totally
burnt
out-
and
that's
usually
not
in
the
123
queue,
but
in
the
the
bug
fix
queue,
so
122.3
is
the
next
bug
fix
release
and
I'm
super
guilty
of
this-
that
I've
been
super
focused
on
123
and
haven't
been
looking
at
any
of
the
bug
fix
issues.
A
But
I
see
there's
like
almost
a
dozen
rtbc
issues
in
the
122.3
queue
which
is
fantastic
and
then
120
2.3
also
has
30
other
issues
that
could
potentially
be
reviewed
and
actually
having.
We
only
have
41
open
issues
total,
that's
actually
a
lot
smaller
than
our
bug.
Fixed
queue
has
often
been
in
the
past,
so
it's
a
great
place
to
look
if
you're
looking
to
do
some
contribution
in
the
next
couple
of
weeks
and
of
course
big.
Thank
you
to
all
of
our
contributors.
A
A
I'm
excited
about
expanding
our
entity
apis
to
fully
leverage
the
fact
that
we
have
a
chosen
reference
system,
so
we
can
start
doing
things
like
following
references.
A
You
know
through
methods
in
our
and
in
our
entity
api
so
like,
instead
of
like
we've
got
like
get
field
value,
for
example,
but
we
could
start
doing
things
like
you
know,
get
reference
and
just
like
load.
The
reference
directly,
rather
than
needing
to
have
it
be
this
multiple
line,
thing
kind
of
like
entity
metadata
wrappers
like
we
could
start
doing,
that
kind
of,
maybe
not
the
chaining
that
they
have,
but
but
we
could
start
making
it
a
lot
easier
to
follow
references
around
yeah
anyway.
I'm
super
excited
about
that.
A
I
think
it's
a
great
release
and
yeah,
I'm
really
happy
with
with
where
we
are.
Do
we
have
any
any
last
items
for
today.
A
B
I
wanted
to
add
one
more
thing
I
don't
know
so
today
is
september
1st,
so
I
don't
know
if
you're
planning
on
doing
anything
else
for
1
23
today,
but
we
did
have
that
other
issue.
I
was
just
going
to
try
and
find
a
grab
to
it
with
it.
That
was
the
user,
compare
visibility,
role.
A
B
My
disability
rule
it's
issue,
four,
zero,
two
nine
and
this
one
is
it's
the
same
thing.
It's
the
same
kind
of
thing.
It's
like
adds
another
rule,
just
like
the.
What
was
it
the
taxonomy
term
depth
one,
but
this
need
it.
So
it's
in
the
same
sort
of
state
where
it
just
needs
code
review
and
more
people
to
test
it,
and
I
think
it's
ready.
B
So
I
don't
know
I
I
was
thinking
it
would
be
nice
if
we
could
be
like
look.
We
added
several
new
visibility
conditions
in
like
the
pr
announcement,
but
it
would
be
good
to
have
a
core
committer
look
at
it
and
be
like.
Is
this
even
realistic
like?
Is
it
as
close
as
we
think
it
is,
or
just
don't
worry
about
it?.
A
Okay,
it's
possible.
It
hasn't
been
on
my
radar,
but
you
know
it
is
possible
that
it
could
be
completed.
I'm
not
going
to
commit
to
it.
A
Okay,
yeah,
that's
issue:
40
29.,.
A
Okay,
well,
let's
close
out
for
today.
Thank
you,
everybody
for
being
here.
Thank
you
to
our
our
viewers
that
watch
these
meetings.
I
also
really
appreciate
it.
Last
week
several
contributors
actually
watched
the
videos
and
then
went
back
and
updated
the
issues
that
were
mentioned
in
the
videos
with
the
feedback
from
them,
which
I
mean.
Ideally
we
would
do,
but
I
love
that
that
that
happens
and
that
it
came
from
people
that
were
watching
after
the
fact.
So
that's
that's
very
appreciated.
A
Getting
the
information
out
of
the
spoken
version
into
the
written
version,
which
is
really
you
know
the
canonical
source
of
information.
So,
okay!
Well,
thanks!
So
much
everybody
have
a
great
week,
we'll
we'll
continue.
You
know
for
the
remainder
of
the
day,
we
have
some
potential
for
wrapping
up
last
123
items
and
yeah,
we'll
we'll
see
if
one
more
or
possibly
two
more
items
squeezes
in
yet
today,
but
yeah
we'll
see.
I
hope
everybody
has
a
great
week
thanks.
A
So
much
and
great
release
everyone,
so
happy
1,
23
feature
freeze
day
catch
you
guys,
all
later
bye.