►
From YouTube: Backdrop Weekly Dec 6th
Description
Today’s development agenda: http://bit.ly/2SsawQi
A
B
So
we
have
an
announcement
going
on
today,
but
you
guys
get
to
hear
it
first,
if
you're
watching
the
broadcaster
in
this
meeting,
that
we
have
a
new
cork
emitter,
we
have
invited
herb
dual
into
the
corps
commander
team
and
he
has
been
in
the
queue
and
he
is
merging
your
poll
requests.
So,
okay
welcome,
herb,
we're
so
excited.
Of
course.
B
Adding
new
pull
requests,
but
also,
like
he's
just
a
really
excellent
reviewer,
and
so
we're
really
pleased
to
empower
him
to
empower
you
to
make
it
so
that
we
can
get
more
full
requests
through
the
review
bottleneck
as
quickly
as
possible.
So
very
exciting,
he's
already
added
to
the
leadership
page
and
we'll
be
posting
a
blog
post
later
today,
hopefully
so
yay,
that's
it
hey.
A
Great
next
up,
we
wanted
to
welcome,
have
been
mountain,
maybe
for
working
on
the
prism
module,
and
hopefully
we
get
them
into
the
backdrop
and
trip
through
shortly.
So
thanks
for
new
people
joining
an
opportunity
to
do
their
book
all
right
or
the
website
backdrop
CMS
board,
we
did
a
lengthy
review
in
the
design
and
user
experience
meeting
about
the
module
students
and
layouts
pages.
You
want
to
take
a
look
at
that
video.
You
can
see
where
we
are
at,
but
there
is
progress
and
hopefully
we'll
get
that
update,
pushed
out
soon
forum
sites.
A
We've
been
having
a
lot
of
memory,
consumption
issues
on
the
forum
site
lately,
both
with
previewing
and
new
forum
posts
and
with
posting
comments.
So
we
disabled
the
preview
for
comments,
but
it
doesn't
look
like
there's
an
option
to
disable
to
preview
for
notes.
So
we
added
an
elitist
version
of
back
Java
code.
A
We
added
the
ability
to
preview
content
again,
but
apparently
it
takes
a
lot
of
memory,
and
so
we
need
to
figure
out
why
that
operation
is
so
expensive
and
hopefully
fix
it
for
all
backdrop
sites,
so
that
once
the
aren't
on
servers,
SBP
adds
ours
can
actually
preview
their
content.
I
don't
know,
what's
going
on
the
comments,
but
whatever
it
is,
it's
probably
similar,
but
there's
some
kind
of
out
of
control.
A
Wrinkle,
but
if
anyone
has
any
interest
in
looking
into
performance
or
memory,
consumption
issues,
that's
definitely
something
or
we
could
use
someone
who
has
some
profiling
abilities
to
fire
up
the
virtual
backdrop.
We
can
give
you
a
sanitized
version
of
the
forum
database.
That's
helpful,
just
try
and
create
some
forum
topics
or
some
comments
and
see
if
you
can
generate
the
same
sort
of
memory.
Consumption
comments
we're
seeing
on
that
site.
A
C
A
We
should
do
is
just
put
a
pound
accesses
false
on
the
preview
button
and
then
no
one
be
able
to
see
the
button
right.
So
that
might
be
a
quick
fix.
But
that
would
prevent
that
the
whole
of
frustration.
A
Another
thing,
though,
is
that
we
have
discovered
a
use
case
for
disabling
the
view
of
notes:
okay,
where
there
isn't
an
option
to
do
that
before
right
now,
so
it
might
be
valuable
to
have
that
either
feed,
maybe
not
permission
based
I,
don't
know,
but
some
some
kind
of
way
that
you
could
prevent
people
from
doing
this.
A
So
if
you,
how
does
I
think
is
working
fine
and
then
we
push
this
fix
in
our
growth
review
and
they
can
take
down
their
site,
but
it
for
quick
fix
for
everybody
to
be
able
to
turn
off
that
freebie
button
might
be
beneficial,
so
I,
don't
know
where
that
setting
should
live
if
it
should
be
on
the
content,
type
form
like
a
mean
comment
settings
where
you
could
have
like
it
or
not
content
with
it.
If.
D
A
D
A
A
D
D
A
D
A
Alright,
if
there's
no
updates
or
anything
else,
let's
go
ahead
and
jump
into
backup,
CMS
issues.
B
My
goodness
yeah
there's
so
many
things
that
are
happening,
I'll,
probably
try
to
skim
over
the
ones
that
we've
mentioned
a
lot
recently.
So,
okay,
so
let's
stick
get
started
so
backdrop.
One
11.3
is
the
next
bug
fix
release.
We've
really
queued
up
a
large
number
of
fixes
and
one
dot.
11.3
release
is
probably
imminent,
because
we
really
need
to
get
out
some
rather
large
fixes
that
are
included
in
there,
including
an
issue
with
the
Installer
I
think
is,
is
a
big
big
deal
and
now,
as
of
this
week,
there's
a
bunch
more
stuff.
B
That's
gotten
merged.
In
so
things
that
have
been
completed
at
least
the
info
status
message
had
we
added
a
new
status
type
called
info
and
it
was
affecting
the
available
updates
page
that
got
merged
in
this
past
week.
Let's
see,
we
have
an
issue
with
paragraphs
module
that
paragraphs
module,
the
port
of
it
was
having
a
problem
with
the
function
path,
entity
insert,
and
so
that
has
been
merged
in
core
to
help
facilitate
the
port
of
paragraphs
module.
B
There
is
an
issue
at
layouts
that
removing
the
main
content
block
causes
some
other
page
elements
not
display.
So
a
layout
related
problem.
If
you
have
removed
the
main
content
block,
it
affects
other
things
like
page
title,
I
think
that
has
now
been
merged
in
as
well.
So
that
is
great,
so
lots
of
good
fixes
this
week
in
the
category
of
things
that
are
pretty
much
ready
to
go.
B
Let's
see
and
there's
two
issues
related
to
color
module
and
we've
covered
these
in
the
past
couple
of
weeks
and
in
the
design
and
UX
meeting
regarding
color
schemes
and
the
color
preview
in
Safari.
Those
two
issues:
3209
for
predefined
color
schemes
and
basis
and
3295
for
the
color
preview-
does
not
work
in
Safari.
Both
of
those
issues
no
updates
this
week.
So
I
won't
recap
them.
B
Let's
see,
we've
got
a
rather
serious
regression
that
there
was
a
security
release
that
came
out
for
one
dot
11.1
and
it
broke
some
class
names
used
within
blocks.
That
underscores
are
being
converted
to
hyphens
and
so
the
satis
that
one
we
think
the
through
discussion
I
think
that
we
have
a
solution
that
we're
using
the
right
function
to
do
the
escaping,
but
we
need
to
pass
parameters
to
that
function.
B
That
allow
underscores
if
they've
been
typed
in
by
a
user,
and
so
the
approach
seems
clear
as
to
the
way
forward,
but
there's
no
pull
request
yet
for
fixing
that
issue
and
the
issue
number
for
that,
one
is
3365,
so
I
think
we
have
a
way
to
conclude
me
wrong,
but
I
thought
we
did
submit
Apple
English.
For
that
don't
know
it
might
be
just
that
the
label
isn't
applied
and
there's
no
link
up
at
the
top
of
it.
So
maybe
if
I
scroll
through
the
whole
thing,
maybe
I
would
find
one
we'll.
B
C
D
D
B
Yeah
I
see-
and
so
it
looks
like
the
suggested
things
here-
is
that
we
have
a
class
to
the
regions
to
make
it
so
that
the
contextual
link
doesn't
float
outside
of
it.
It
looks
like
that
seems
to
be
what's
happening
right
now,
so
this
affects
a
number
of
template's
layout
templates,
so
I
think
we
should
probably
take
a
look
at
that
and
see
if
the
current
fix
is
suitable.
B
It's
a
little
bit
weird
because
it's
like
whenever
we
modify
template,
template
files
you're
not
really
sure
that
it's
actually
one
to
affect
every
site
equally,
because
those
template
files
could
have
been
overridden.
So
if
we
might
have
a
larger
problem
with
our
templates
that
we
need
an
area
to
dump
any
classes,
not
necessarily
just
only
the
contextual
link
class,
okay,
well
yeah,
that
issue
is
26.90.
It
currently
has
a
pull
request,
but
it
needs
needs
work.
We
believe,
okay,
that
does
it
I
think
for
the
one
dot
11.3
list.
B
B
31St
and
looks
like
that's
a
Monday
will
be
the
last
day
of
feature
development
with
feature
freeze
happening
on
January
1st,
so
the
feature
freeze
basically
means
we
won't
be
adding
in
any
new
functionality,
but
will
still
be
tightening
up
things
for
the
1.12
release
on
the
15th,
the
list
of
features
that
we
have
trying
to
get
completed
here
for
by
the
end
of
the
month.
This
is
quite
long,
so
let's
go
over
some
of
these
things.
So
first
one
is
core
updates,
there's
a
meta
issue
at
2018
and
a
more
specific
issue
at
414.
B
That
is
where
a
lot
of
the
current
work
is
happening
right
now,
last
we
saw
Jeff
is
taking
the
lead
on
that
saying,
deputy
and
he's
got
a
current
question
and
problem
regarding
loading
files.
I
think
that
we
actually
talked
about
this
last
week,
I'm,
not
sure.
If
he's
made
more
progress
there,
the
right
now,
you
can
only
update
backdrop
core
if
you
enable
a
hidden
option
that
it's
not
exposed
in
the
user
interface.
B
That
issue
414
turns
on
the
option
for
everybody
and
also
includes
some
of
the
automatic
portions
of
things,
but
currently
needs
some
more
testing
and
some
more
work.
Putting
that
together,
I
think,
let's
see
also
on
the
automatic
updates,
keep
mentioning
this
package
signing
issue
1982
that
would
increase
the
security
of
or
the
guarantee
that
packages
you've
downloaded
were
signed
by
the
backdrop
CMS
Borg
servers,
so
they
had
Midtown
within
transit
that
is
you're
still
in
progress,
still
kind
of
just
in
prototype
phase,
though,
let's
see
long-running
month,
issue
issue
number
37
tags
for
modules.
B
No
updates
on
that
one.
So
I'm
not
going
to
recap
that
one
options
element
in
core
issue
1005
this
one
is
pretty
much
ready
to
be
committed,
but
it's
still
currently
in
a
needs.
Review
state
I.
Think
that
we're
looking
for
another
code
review
on
that
one
and
is
going
to
frequently
become
the
case.
The
reason
why
that
one
is
not
moat
armed
TBC
is
because
herb
dual
was
the
one
that
rolled
the
patch
and
he
feels
like
he
can't
move
it
his
own
issues
to
our
GBC.
B
B
Really
exciting
this
past
week,
config
translation
has
picked
back
up
again
issue
704
has
a
new
poll
request?
Actually
maybe
the
first
four
requests
that
gets
that
off
to
a
great
start.
The
poll
request
makes
it
so
that
translating
configuration
is
officially
supported
right
now
we
just
run
certain
labels
like,
for
example,
the
label
of
a
field
is
just
run
through
the
t
function
to
get
it
to
be
translated,
and
that
will
continue
to
be
the
case
once
this
config
translation
functionality
lands.
B
The
difference
will
be
that
locale
module
will
actively
check
config
files
for
what
strings
need
to
be
translated
and
then
run
through
T.
So
it
increases
the
discoverability
of
strings
that
need
to
be
translated
and
makes
it
so
that
sites
like
the
localized
website,
localized
feedback
type
CMS
org,
could
read
through
the
default
install
of
backdrop
and
pull
out
from
config
files
strings
that
need
to
be
translated
so
that
they're
included
in
the
Pio
files
that
are
downloaded
from
the
translation
server.
B
So
it's
off
to
a
great
start.
The
the
poor
request
has
all
of
the
concepts
that
I
think
we
were
expecting
or
that
we
had
discussed
hypothetically.
It
now
is
actually
a
reality,
but
one
thing
needs
to
be
done
in
that
it
adds
the
api's
for
getting
the
translated
strings,
but
it
doesn't
add
the
proactive
discovery
of
finding
strings
in
translation
files.
Yet
so
it's
off
to
a
great
start,
but
we
still
have
more
things
to
be
added
there
to
get
that
to
continue
it.
B
Let's
see
some
more
things
that
are
TB
seed,
translatable,
taxonomy
terms
issued
2934.
This
adds
a
language
column
to
taxonomy
terms,
just
to
make
it
so
that
when
content
is
created,
in
particular
language,
the
terms
that
are
automatically
created
matched
the
same
language
as
the
content,
so
really
helpful
and
simple
functionality
there
in
29:34
that
one
is
currently
our
QVC
rendered
term
formatter.
That
makes
it
so
that
you
can
print
out
a
taxonomy
term,
not
just
as
a
label
but
as
a
full
display
mode.
B
B
The
display
of
that
listing
has
been
tweaked
slightly
in
3395
and
that
one
is
also
our
TBC
with
a
little
asterisk.
You
say
mostly
our
deviancy,
because
it's
we
think
that
it's
rgbc
but
is
officially
been
labeled
as
such.
Yet
let's
see
somebody
slipped
them
on
in
here
at
the
last
minute.
Here
it
says:
dashboard
exclamation
point,
so
it's
issue
495
I
time
to
come,
clean,
whoever
added
dashboard
and
to
my
list
here.
It.
A
Was
needed
added
it
but
Gregor.
He
asked
me
to
add
in
so
yeah
there's
been
a
ton
of
great
progress
happening
on
the
dashboard
issue.
My
intent
is
just
add
a
new
layout
and
to
place
a
bunch
of
blocks
on
the
layout
and
call
it
good.
There
are
a
lot
of
other
things
we
could
do
with
a
dashboard
I
think.
Maybe
all
those
should
be
postponed
for
a
later
core
version
like
we
could
automatically
redirect
people
when
they
log
in.
We
could
create
like
special
block
types
specifically
for
the
dashboard.
A
We
could
do
much
other
stuff,
but
I
thought
a
good
first
step
would
be
another
default
layout
place,
a
bunch
of
the
admin
bucks
we
already
have
on
it,
make
it
a
little
bit
more
useful,
I
think
we,
you
know
with
no
dad
like
add
and
no
to
add
links
like
stuff
like
that.
We
can
just
drop
on
there
and
then
iterate
and
see
what
what
features
people
want
once
it's
in
there
for
them
to
use.
So
it
looks
like
dr.
moments
been
working
on
that
and
he's
got
a
default
layout
he's
quickly
blocked
on.
A
D
No
I
also
agree
with
the
approach
of
having
a
dashboard,
and
we
can
just
add,
put
specific
blocks
along
the
way
as
people
request,
specific
features
and
and
it's
not,
the
consensus
seems
to
be
that
they're
not
going
to
be
something
special.
It's
just
gonna,
be
blocks,
interpret
fixed
with
the
text
dashboard
so
that
it's
easier
for
people
to
find
them
when,
with
the
add
block,
dialog
and
I,
think
that
it
makes
sense.
So
even
contribute
modules
can
add
to
that.
A
D
C
A
Yeah
there's
a
little
debate
about
that
in
the
issue
too,
like
we
don't
have
a
standalone
module
called
a
homepage
then
adds
a
config
file.
So
if
we
aren't
gonna,
add
anything
else
like
permissions
or
special
block
types
or
anything,
there's
really
a
reason
to
have
a
standalone
module
four
dashboard:
either
people
don't
want
a
homepage,
they
can't
delete
or
disable
layout.
We
can
do
the
same
thing
for
dashboard,
mm-hm.
B
It
does
make
it
so
that,
if
it's
owned
by
a
module,
then
it
can
be
reverted.
You
know
back
to
its
default
state,
which
you
can't
do
if
it's
just
part
of
the
install
profile,
because
it
would
just
be
like,
like
the
home
page,
is,
doesn't
have
any
ability
to
revert,
because
it's
just
intended
to
be
owned
by
the
user,
not
sure
if
that
makes
any
difference.
Free,
yeah,.
A
I
think
that's
a
different
issue
with
like
being
able
to
revert
everything
to
its
default,
State
and
I.
Think
there
is
an
issue
on
that.
Like
any
config
that
comes
from
core,
we
have
the
ability
to
revert
it
because
we
have
this
initial
State
in
whatever
module
it
came
from
so
there's
another
issue
about
just
like
added,
revert
link
that
can
take
it
back
to
the
way
the
copy,
the
file
from
its
original
location
back
into
it,
standing
nurturing
imports
or
whatever
so
I,
don't
think.
That's
necessarily
special
for
dashboard.
A
D
Related
to
that
now
that
you
mentioned
it,
Drupal
South
was
on
this
week
and
one
of
my
previous
colleagues
was
presenting.
He
built
a
module
that
provided
revisions
and
what
you
call
it
workflows
for
raishin
so
for
webforms,
and
it
seems
like
a
really
it's
a
it's
d8
related.
But
since
we
have
configuration
in
back
shop,
I
thought
that
one
cool
feature
would
be
to
have
revisions
for
configuration
which
would
allow
people
to
undo
things
like
if
they
mess
up
of
you.
They
reverted
to
not
to
its
default
back
to
a
previous
version.
D
D
D
A
Does
sound
awesome
I
also
think
it's
definitely
something
that
would
live
in
can
trim
or
backdrop
to,
but
I
think
we
should,
and
the
implementation
will
probably
be
significantly
different
than
it
is
in
Drupal
8,
because
we
don't
have
the
same
sort
of
architecture,
but
I
could
see
that
being
really
handy,
especially
if
you
have
like
a
super
complicated.
It's
like
you
make
a
bunch
of
changes
to
use
all
the
times.
A
Having
that,
like
revision,
history
of
what
happened,
each
one
would
be
handy,
I,
don't
know
whether
that
stuff
should
end
up
in
the
database
or
there
should
just
have
like
you
just
like
file
directory,
here's
all
the
Jason
history
or
whatever
like
it,
might
be
different
in
backdrop.
The
solution
for
that
than
it
wasn't
written,
but
I
could
see
you
telling
me
that
yeah.
A
D
B
Okay,
well
I'll
continue
on
from
the
dashboard
discussion.
You
guys
are
cool
with
that.
So
the
last
item
that
we
have
here
in
the
1.12
docket
is
keeping
core
libraries
up
to
date
and
jQuery
and
jQuery
UI
we're
still
in
the
latest
version
of
one
dot
X
concerned.
There
aren't
going
to
be
any
more
releases
of
one,
not
X.
There's
some
discussion
about
how
to
get
us
on
to
jQuery
3
at
issue
24,
93
c,
canada
kind
of
the
other
main
external
library
that
we
have
within
backdrop.
B
D
B
A
So
we
have
this
enabled
the
UI
for
manual
updates
thing,
but
we
don't
actually
have
an
issue
for
that
one.
The
issue
that's
linked
in
here
for
14
is
for
auto
updates.
A
Now
it
has
a
pork
what's
on
it,
but
I
don't
know
I,
don't
think
this
is
the
full
request
from
manual
updates
and
so
I
know
that
if
we
want
to
get
that
done
for
112,
we
probably
need
to
have
a
designated
issue
where
we
can
be
like
all
we
do
here
is
an
equally
Qi
and
that's
what
the
fork
West
says.
We
can
close
that
issue
and
I
want
to
close
the
auto
up
to
issue
when
we
do
the
manual
on
say
thing
create
an
issue
for
that.
We've.
A
B
From
2018
but
I
read
it
back
in
September
and
then
I
post
a
comment
saying
that
this
is
being
included
in
414.
So
it's
a
good
good
point
that
maybe
414
is
trying
to
do
too
much,
because
it's
trying
to
do
the
automatic
part
and
the
user
interface,
and
maybe
we
should
separate
those
two
so
that
we
could
at
least
get
these
interface
enabled
and
the
event
auto
updates
doesn't
happen.
Well,.
A
D
Yeah
related
to
that
there
was
the
other
issue
of
merging
the
update,
the
update
modules
of
date,
layouts
of
late
Sunday
things
end
core
into
a
single
panes
and
I
think
they
also
have
an
issue
for
that
might
be
a
great
chance
now
that
we're
introducing
that
to
sort
of
like
a
solid
date,
because
everything
all
over
the
place
you
go
to
the
update
module
page
and
you
see,
updates
for
things
and
layouts
and
core
so
yeah
I
remember
the
ticket
for
that's.
That's
the
number
plan,
though
oh.
B
D
Was
a
really
old
issue
was
one
of
the
things
that
was
annoying
me,
but
recently
there
was
the
suggestion
that
we
should
use
the
available
update
space
to
convert
that
into
a
single
page
where
people
have
an
overview
of
what
updates
are
pending
and
also
be
able
to
action.
It
just
get
about
them,
selects,
select
things
hidden
button
and
then
embed
so
I
just.
A
D
D
B
D
B
A
I
do
that
all
the
time
I
like
I
have
a
patch
that
fixes
a
problem
and
so
I'm
running
a
version
of
the
module
of
problem
fixed.
But
then
a
new
version
of
the
module
comes
up
doesn't
have
the
problem
fixed.
We
need
to
go
back
and
fix
the
problem.
The
new
version,
so
I
update
everything,
except
with
the
module.
A
A
It
in
the
issue
so
there's
another
issue
that
was
like
move
the
update
settings
where
I
can
find
them
because
right
now,
they're
under
their
own,
like
a
tab
on
the
reports
page,
which
is
a
little
weird
for
settings
and
so
I'd
recommend
we
move
them
into
brother.
All
the
other
development
settings
are,
and
then
you'd
mentioned
upon
us
that
we
wanted
to
move
off
other
stuff
around
anyway.
A
I
think
we
still
need
to
report,
regardless
of
whether
we
have
one
page
of
the
three
pages
we
have
now
for
actually
doing,
updates
and
I
still
think
we
need
to
move
the
settings
and
I
don't
know
like.
If,
if
we
end
up
having
another
page
for
installer,
we
still
need
to
have
a
place
to
put
the
settings
of
our
plates
and
installer
so
I.
Don't
think
it
should
be
tied
to
that
modules
like
I.
A
D
A
D
A
A
Are
we
still
going
to
have
a
report
where
you're
gonna,
where
we
gonna
put
those
settings
I'm
just
figuring
out
like
how
that
all
fits
the
other
with
or
without
massive
updater,
and
then
also
like
I,
don't
know
what
the
where
the
settings
are
currently
for
the
Update
button.
I'll
go.
Take
a
look
at
that
issue
and
see,
but
if
they're
on
this
page,
we
also
need
to
make
this
page
easier
for
people
fine.
So.
A
D
A
A
So
that's
it
for
issue
discussion.
It
looks
like
we
have
one
other
things
on
the
agenda,
which
is
just
to
say
if
you
want
to
get
involved
in
backdrop
for
good,
there
is
an
issue
queue
on
github,
PLM,
20/20,
there's
a
link
in
the
agenda.
If
anybody
wants
to
grab
some
money
through
issues
there
and
not
goes
up,
that's
great,
then
that
brings
us
to
our
open
general
discussion
and
section
of
the
meetings.
Is
anyone
have
anything
there's
my
talk
about
in
our
one
remaining
minute
of
time,
yeah.
D
Just
a
final
thing:
another
we
mentioned
that
one
dot
11.3
is
imminent,
but
if
we
have
any
roadmap,
the
the
reason
why
I'm
asking
that
is
a
because
I
need
to
know
if
I
can
help
in
them.
Traveling
tonight
look
if
it's
happening
over
the
weekend
and
then
it
was
specifically
to
users
that
had
some
of
the
bugs
that
were
fake.
That
specifically
asked
that
like,
when
is
the
next
release,
and
that
was
before
the
Thanksgiving
things.
So
it's
been
a
couple
of
weeks
now
we
have
any
rough
ideas
when
this
will
be
happening.
A
Anyone
wants
to
help
with
the
release,
maybe
we'll
go
ahead
and
create
the
release,
meta
issue
or
checklist
today
and
we'll
assign
some
holes.
So
if
you're
available
on
Sunday,
let
us
know
we
can
put
your
name
on
that.
You
want
to
help
us
with
tweeting
or
posting
or
whatever.
It
is.
The
mother
thinks
releases
are
not
as
big
a
deal
as
the
minor
issues.
They
don't
usually
have
a
blog
post
rate,
but
we
do
tweet
and
otherwise
let
people
know
things
fixed
and.
D
I
call
out
for
help
if
anyone
is
aware
of
what
the
process
is
for
unblocking
or
unlike
listing
articles
from
wikipedia
this
is
related
to
the
release.
We
would
love
to
know
how
to
go
about
doing
that.
I'll
try
to
figure
out
if
there's
the
commendation
on
the
internet,
but
it
seems
as
if
the
article
that
was
blocked
is
now
under
the
it
has
been
moved
under
the
personal
account
of
one
of
the
wikipedia
main
moderators.