►
From YouTube: Backdrop Weekly - Jan 2nd 2020
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
Both
of
those
modules,
I
think,
are
actually
pretty
good.
First
port
modules,
the
bootstrap
site
alert
module
is
very,
very
straightforward.
The
only
tricky
part
is
that
it
uses
hook,
page
alter,
which
we
don't
have
in
backdrop,
but
a
hook
page
alter
in
that
instance.
All
it
does
is
add
a
couple
of
javascript
files,
so
that
could
very
easily
be
done
in
pre
process
page
instead
and
in
the
hierarchical
select.
Module
also
adds
JavaScript,
so
I
think
both
of
these.
If
either
of
you
wanted
to
give
that
a
shot
could
be
fairly
straightforward.
A
First
ports
so
could
be
fun.
We
also
have
a
couple
of
new
contributed
projects.
This
week
with
official
releases,
the
CK
editor,
indent
outdent
module
adds
to
missing
and
loved
features
to
the
CK
editor
core
module,
I'm,
not
sure
either
not
in
core,
but
they
aren't
and
then
there's
another
module
called
male
disguise,
which
was
also
really
specific.
So
thanks
everybody
for
working
on
picture
projects.
B
All
right
we
had
an
action-packed
week
this
week
yesterday
was
code,
freeze
or
feature
freeze
for
the
115
version,
and
so
we
were
hurrying
around
and
getting
mostly
the
115
items,
the
ones
that
we
could
completed.
But
before
we
get
into
that
114
the
current
version.
We
have
a
couple
of
issues
that
were
also
fixed
in
the
last
week.
C
B
So
far,
so
good
on
that
which
I'm
excited
to
have
fewer
test
failures
happening
intermittently,
let's
see
a
new
item
that
was
brought
up
or
recently
brought
up.
Is
it
sometimes
menu
items,
especially
in
the
admin
menu?
The
sorting
is
a
little
bit
incorrect
actually,
and
so
we
have
this
issued
26:55
that
it
looks
like
I'm
actually
sure
if
it
was
BW,
panda
or
Olaf
or
Geoff
someone
identified.
The
problem
apparently
is
actually
a
problem.
In
the
backdrop.
B
Sort
function,
like
the
backdrop
start
function
itself,
doesn't
sort
correctly
in
some
situations,
which
is
kind
of
a
big
problem,
because
we
use
that
for
sorting
just
about
everywhere
here
so
issue,
26:55
reworks
backdrop
sort
to
solve
that
problem,
but
it's
also
causing
some
PHP
warnings
and
failing
tests
right
now,
so
so
that
it
looks
like
it's
promising,
though,
and
and
kind
of
interesting
but
yeah.
We
need
that
pull
request,
probably
updated
the
engine
posted
here
and
also
we
need
to
performance.
B
We
need
to
benchmark
it
to
make
sure
that
we're
not
introducing
some
kind
of
regression.
There
I
posted
a
comment
on
there:
how
to
benchmark.
There
are
tools
like
not
xh,
prof
anymore,
but
tide
ways
and
Blackfyre
io
that
you
can
use
to
benchmark
page
requests
in
general,
but
for
something
like
this,
where
it's
one
function
like
will
be
fine,
just
using
like
timer
start
start
and
timer
stop,
and
just
like
measuring
in
milliseconds
like
how
fast
some,
how
fast
calls
to
that
function
occur
when
he
passing
a
variety
of
inputs
to
it.
A
B
A
A
menu
or
where
do
we
then
like?
What
do
you
know
what
circumstances
under
which
it's
used
for.
B
C
B
B
B
So
in
a
little
bit
less
than
two
weeks
that
will
be
coming
out
and
the
things
that
we
got
into
it
this
week
include,
we
did
get
the
image
library
modal
into
image,
fields,
issue
3297,
that's
very
exciting!
That
makes
it
so
that
anywhere
you
have
an
image
field.
You
can
now
enable
the
ability
to
browse
and
reselect
an
existing
image,
and
this
user
interface
matches
that
of
seek
editor.
B
That
allows
you
to
do
something
really
similar
when
you
click
the
image
button
and
seek
editor,
so
the
UI's
look
pretty
similar,
although
the
underlying
code
is,
is
kind
of
different,
because
the
image
field
stuff
is
all
server-side
and
CK.
Editor
is
like
almost
entirely
client-side,
so
there's
some
difference
in
implementation,
but
these
are
interface
ends
up
looking
really
similar
in
both
cases,
which
is
very
cool.
B
The
way
that
also
ended
up
is
is
also
neat
that
the
enhancement
was
made
to
the
managed
file
element.
We
did
an
API
expansion
on
the
manage
file
element
to
make
it
so
that
you
can
specify
a
view
as
a
form.
Api
property
I
think
it's
called
pound
browser
view.
I,
think
that
you
put
on
it
on
a
managed
file
element
and
that
will
make
it
so
any
file
elements
anywhere
can
now
reuse
files
with
any
view
which
is
pretty
cool,
but
the
only
place
that
we're
actually
using
it.
B
So
the
API
is
expanded,
but
the
only
place
you
can
see
it
right
now
is
on
image
field.
So
there's
a
single
check
box
for
enable
browser
and
it
uses
the
out
of
box
image
library
view
by
default,
but
you
could
use
that
on
other
things
like
on
a
file
field
somewhere,
but
right
now,
it's
only
through
the
API.
B
So
that's
really
cool
I'm
very
excited
about
that.
There's
some
other
features
in
there
that
didn't
get
completed,
though
gram
72,
who
was
leading
the
charge
on
this
for
quite
a
while,
also
wanted
to
include
things
like
when
you
click
on
an
image.
It
would
tell
you
information
about
that
image
like
its
dimensions
and
file
size
and
things
like
that
to
distinguish
between
different
versions
of
an
image
that
might
look
similar,
but
we
removed
those
things
because
I
didn't
want
to
introduce
discrepancies
between
seek
editor
and
image.
Fields
will
end
them
to
be
the
same.
B
D
Sure
we
now
have,
we
have
a
content
type
on
bat-crap
CMS,
org
called
public
notifications.
If
we
publish
a
notification
there,
which
would
involve
a
title
snippet
of
descriptor
text
in
a
URL
that
will
show
up
on
a
block,
a
new
block
which
will
be
at
to
the
dashboard
of
any
new
backdrop
CMS
sites.
So
we
have
a
way
to
communicate
rather
than
court
in
advance
to
that.
D
D
B
B
That
makes
a
lot
more
sense.
Okay,
yeah
issues
6:25
in
the
backdrop,
see
messed
up
or
get.
Your
cue
is
policy
discussion
about
what
notifications
who
should
use
and
then
issue
42
54
is
a
follow
up
to
add
caching
to
it,
because
right
now
we're
every
time.
You
view
your
dashboard.
It
hits
backdrop
CMS
org
on
the
fly
which
isn't
great
for
performance,
especially
since
it's
server-side,
and
so
we
have
an
issue
to
switch
that
out
to
to
using
a
cache
and
then
updating
the
news,
announcements
on
cron
jobs
instead,.
B
Okay,
well,
those
are
the
two
issues
that
that
we
did
complete,
that
we
mentioned
every
week,
but
it's
also
worth
covering
some
items
that
got
merged
in
got
Murchison,
that
we
don't
talk
about
all
the
time,
and
that
includes
issue
39
72,
which
is
some
work
for
indigo
gsella
had
been
working
on
regarding
date
and
time
form
elements
that
we
have
this
date,
pop-up
element
that
is
provided
by
date,
module
and
we
had
been
using
that
on
the
node
form
for
the
post
date.
But
we
switched
that
out
now.
B
Issue
3972
adds
html5
date
and
time
elements
instead
of
using
like
a
jQuery
UI
date
popup.
If
you
use
the
browser
native
html5
date
and
time
for
date
and
time
form
elements,
you
get
a
very
similar
user
interface
to
the
old
jQuery,
UI
pop-up
and
it's
less
work
on
our
side
and
it's
better
device
compatibility
for
like
mobile
phones,
and
things
like
that.
So
so
that's
really
cool.
That
issue
only
updates
the
post
date
form
element.
B
It
doesn't
actually
updates
date,
module
date,
pop-up
element
yet,
but
it's
still
a
great
enhancement
and
I
was
surprised
to
actually
see
that
we
had
a
big
hole
in
our
html5
support
that
we
didn't
even
have
pound
type
equals
date
and
pound
type
equals
date/time
previously.
So
now
we
do
so
that's
great.
We
now
have
three
new
html5
form
elements
supported
in
form.
Api
I'm,
Jenna
I
noticed
that
yesterday
you
were
so
nicely
updating
the
form
API
reference
page
to
include
those
new
elements
which
is
great
because
that's
something
that
we
frequently
forget
to
do.
B
Let's
see
next
up
so
a
small
feature
is
issue
4200
that
menus
right
now,
the
drop-down
menu
system
that
we
have
out-of-the-box
on
a
desktop
computer.
When
you
move
your
mouse
over
a
drop-down
it
it
pops
open
an
issue.
4200
is
a
feature
to
make
it
so
that
you
can
choose
now
to
toggle
between
whether
it's
a
hover
behavior
or
click
behavior.
So
on
a
touch
device,
it's
always
touch
to
open
and
touch
to
close
or
touch
wants
to
open
and
then
second
touch
to
to
go
there.
B
But
this
makes
it
so
that
you
can
choose
the
behavior
on
a
desktop
device,
whether
it's
hover
or
click,
so
some
people
prefer
one
way
over.
The
other
always
note
that
possibly
there
might
be
some
accessibility
implications
about
doing
one
way
or
the
other
as
well.
So
that's
really
cool,
but
that
one
has
them
has
a
follow-up
issue.
B
B
Previously,
the
output
of
boolean
fields
was
not
excellent,
and
now
you
can
choose
the
way
that
the
output,
in
the
same
way
that
you
similar
to
the
way
you
can
choose
the
way
they
output
in
views
with
like
checkbox
or
or
checkmark,
or
an
X
yes/no,
enabled
disabled
like
much
better
display
options
for
when
boolean
fields
had
turned
on
and
off
provide
a
UI
to
define
watchdog
severity
levels.
Issue
33:26.
B
This
was
a
hidden
system-wide
setting
that
previously
had
only
been
available
in
Velma
dual.
We
put
it
into
the
logging
pay
primarily
because
now
we
have
this
deprecated
logging
level
that
is
turned
off
by
default
and
that's
a
highly
useful
feature
to
be
able
to
be
able
to
turn
on
and
off,
and
now
it's
exposed
in
the
user
interface
without
needing
to
install
devel.
B
We're
talking
about
this
one
before
the
meeting
disable
comments
by
default
on
new
content
types
issue:
41:56
a
one-liner
changed
by
Tim,
which
is
very
welcome.
Just
that
now,
yeah
creating
a
new
content
type,
doesn't
turn
on
comments
which
is
great,
let's
see
and
lastly,
we
removed
all
stop
words
from
path,
alias
path,
the
alias
out-of-the-box
or
sorry
path.
B
Sorry
and
Drupal
7
is
called
path,
Auto
and
in
backdrop,
it's
just
part
of
path
module,
but
there's
a
section
for
strings
for
strings
to
remove
the
path
on
or
defaulted
to,
removing
words
like
the
and
and
sometimes
prepositions,
and
so
so
things
like
from
or
up
or
by
all
of
these
words
would
get
removed
from
your
URLs.
But
then
that
would
frequently
end
up
changing
the
meaning
of
the
URL
into
something
else
or,
like
keywords,
would
be
left
out
and
then
it
wouldn't
make
any
sense
anymore.
B
Why
is
that?
No
okay,
I
thought
somebody
said
something
anyway,
that's
it!
Those
are
the
set
of
changes
that
just
got
in
recently
for
115
there's
a
couple
of
other
ones
as
well,
but
I
won't
go
over
those
again,
so
things
that
that
didn't
get
put
in
or
quite
a
few
things
better
workflow
States
issue
1475
the
document
was
working
on
would
make
it
forward.
Revisions
would
be
possible
in
core.
B
A
A
B
It
would
be
nice
I'm,
not
sure
if
I
want
to
ask
doc
Wellman
to
do
actually
more
I.
Think
I
think
that
we
really
just
had
some
concerns
about
what
was
left
in
there
like
it
still
was
doing.
It
was
leading
to
some
confusing
situations,
and
so
we're
not
I'm,
not
totally
sure.
If
removing
more
features
is
the
right
way
to
go
or
if
we
need
to
fix
the
features
that
are
left
in
there
and
now
we
kind
of
have
a
choice
to
go
either
way.
With
that
question.
D
B
B
A
Know
because
if
you
can
only
ever
edit
the
active
active
revision,
what's
the
point
of
having
forward
revisions
like
you
need
to
be
able
to
edit
a
draft
before
it
goes
live?
And
so,
if
you
have
a
version
of
the
page,
that's
live
and
you
have
a
version
of
the
page
you're
working
on
you're
going
to
need
to
be
able
to
edit
the
future
version.
A
Right
so
right
now,
there's
no
distinction
between
a
future
one
in
a
past,
one
which
I
think
is
a
problem
like
half
and
we
I
don't
think
we
tracked
like.
Has
this
revision
ever
been
published,
or
has
this
pollution
ever
been
active?
So
it's
just
like
a
little
more
complicated
than
I.
Think
we'd
really
thought
through
until
we
were
trying
to
use
it
and
then
we're.
B
B
Yeah
I
see
what
you're
saying
that
I
was
thinking
the
usefulness
of
it
would
be.
If
you
publish
something
and
then
you
realize
oops,
that
was
incorrect,
then
you
would
just
go
back
to
a
previous
revision
and
instead
of
making
a
copy
of
the
previous
revision,
which
is
what
happens
right
now,
you
would
just
flip
back
to
the
previous
one
and
just
activate
that
one
but
you're
right.
When
you
wanted
to
reintroduce
those
changes
you
wouldn't
be
able
to
edit
the
one
that
was
in
the
future.
A
So
I
think
maybe
like
I'm,
not
against
editing
revisions
entirely.
We
just
need
to
make
that
like
workflow,
more
sensible,
like
there
are
some
weird
things
that
came
up
where
like
when
you
were
editing.
Any
revision
I
always
called
it
a
draft
whether
it
was
a
future
edition
or
past
revision.
So
we
need
some
kind
of
distinction
there
and
then
we
also
need
the
like
workflow
message
to
populate.
A
So
right
now,
when
you
create
a
new
revision,
you
can
add
a
message,
but
the
current
message
doesn't
show
up
when
you're
editing,
something
that
had
a
message
and
then
it
also
gives
you
the
ability
to
create
a
new
revision
from
the
previous
room.
So
it's
a
little
bit
weird
I
mean
I
could
see
that
utility
being
where
it's
like.
Oh
I,
made
one
revision
and
now
I'm
gonna,
throw
this
out,
but
I
want
another
one.
It's
based
on
this
one,
but
like
just
it
gets
really
confusing
to
like.
A
B
Let's
see
other
things
at
sea
Gregory's
issue
of
being
able
to
rename
a
disabled
text
formats
I
think
that
there
was
some
feedback
requested
or
sorry.
Some
changes
requested
that
Gregory
didn't
have
time
to
get
his
PO
request
updated
before
feature
freeze.
So
that's
still
it's
postponed
to
116,
but
it's
still
like
really
pretty
close
and
there's
feedback
there
to
act
on
and
it
currently
needs
it's
poor
request,
updated.
B
Let's
see,
move
contents
of
the
manage
file
display
page.
This
is
consolidating
the
manage
display
and
manage
file
display
pages
together
its
issue,
40
31
I.
Don't
think
that
there
was
actually
any
real
movement
on
this.
Like
all
released
long
was
there
Jen
yeah
so
that
one
that
one's
yeah?
It's
got
some
challenges
on
it.
B
Let's
see
well
keep
going
through
these
lists
of
things
didn't
get
in
signatures.
Digital
signatures
on
packages,
issue
1992.
This
is
the
issue
that
I
was
pushing
forward.
It's
still
it's
not
even
116,
and
the
way
that
we're
approaching
this
is
still
working.
Contribs,
there's
a
module
called
code
sign
that
we're
working
on
building
out
that
functionality
there
and
getting
it
deployed
to
backdrop
CMS
org,
that's
still
where
we
are
today
and
lastly,
entity.
Caching,
core
issue
number
74.
B
B
So
that's
the
sense
of
things
kind
of
as
usual,
the
dead
line
drives
a
lot
of
activity,
so
I
have
to
say
I,
really,
love
deadlines,
because
things
finally
happen
at
that
point,
and
then
there
was
also
a
lot
of
activity
on
things
that
you
know
aren't
aren't
going
to
happen
in
115,
but
we
still
generated
a
lot
of
movement.
A
lot
of
peripheral
issues
related
to
these
other
things
as
well.
So
I
love
deadlines
that
work
really
well.
B
This
next
couple
of
weeks
we
do
have
two
or
three
issues
that
we
have
to
get
fixed
before.
115
comes
out
and
they're
in
the
115
milestone,
but
other
than
that
you
know
now
we're
at
the
point
where
the
only
thing
that
we're
changing
in
115
might
be
like
strings
here
and
there
possible
small
UI
changes
and
things
of
that
sort.
B
So
we
still
allow
UX
changes
even
after
feature
freeze
within
reason,
but
for
the
most
part
from
here
until
two
weeks
from
now,
115
will
just
be
getting
buttoned
up
and
then
then,
once
it's
out,
then
I'll
be
a
free-for-all.
Again.
You
know
working
on
features
in
116,
also
geez
116
we're
really
getting
up
there.
B
D
I
ask
someone
who
will
probably
be
working
in
the
blog
post
for
the
release?
What
like
the
first
two
issues,
that
library
noted
damage
fields
and
recent
news
things
to
highlight
of
these
other
things?
It's
not
clear
to
me
what,
if
any
of
those
are
like
put
in
a
press
release,
does
anybody
have
opinions
on
that,
but.
A
Once
we
put
in
the
preview
release
notes,
we
figured
were
the
most
important
and
I
tried
to
put
them
in
sort
of
like
the
most
exciting,
two
least
exciting
order.
I
would
say
that
would
be
my
preference,
but
maybe
look
at
them
and
if
there's
nothing
that
like
looks
pretty
first
screenshot,
that
might
not
really
be
a
priority
anymore.
Yeah.
B
B
B
I'm
was
taking
a
lot
of
time
off
and
was
you
know,
didn't
put
in
a
lot
of
time
up
until
yesterday,
when
it
was
just
like
everything
kind
of
allocated
yesterday
the
sacrificial
vacation
day
but
yeah,
we
got
a
whole
bunch
of
stuff
done
and
there's
a
lot
of
activity
across
the
board
and
so
yeah.
Thank
you
guys
for
for
all
of
your
efforts
and
for
spending
some
of
your
holiday
with
us
on
backdrop.