►
From YouTube: Backdrop Weekly - April 25th
Description
Today’s development agenda: http://bit.ly/2VV0gCi
A
A
So
what
that
means
is
that,
right
now
the
only
place
you
can
store
your
configuration
files
is
in
the
file
system
and
all
of
your
values
read
off
of
disk
when
they're
needed
and
written
to
disk
when
they're
created,
and
we
wanted
to
add
an
API
so
that
that
was
not
the
only
option.
It
will
allow
us
to
create
a
new
config
storage
class
that
could,
for
example,
save
your
configuration
values
into
the
database
instead
of
into
the
file
system.
So
this
isn't
something
that
is
gonna
affect
anyone
who's
using
backup
messages.
A
Now
it'll
continue
to
work
the
way
it's
always
worked,
but
it
would
allow
people
that
have
more
complicated
infrastructure
to
be
able
to
work
with
backdrop
on
it.
So
it's
one
of
those
things
that
isn't
necessarily
an
80%
use
case,
but
it
also
has
a
pretty
big
impact
on
whether
backdrop
might
be
suitable
for
particular
applications.
For
example,
higher
education
is
one
of
the
people
that
presumed
interest
in
this
in
the
first
place,
and
we
wanted
to
make
sure
that
there
wasn't
a
limiting
factor.
A
So
that's
where
that
landed,
I
have
added
a
comment
in
the
issue
when
you're
discussing
that,
which
is
issue
number
2277,
saying
that
work
can
proceed
there,
because
the
pmc
gave
it
a
thumbs
up.
There's
some
clarification
on
some
technical
details,
a
way
to
work
out.
So
there's
a
new
issue,
the
PMC
to
discuss
that
we
did
at
least
reach
a
decision
that,
yes,
it
should
be
possible
for
you
to
store
configuration
wherever
you
want
all
right.
Next
up
on
our
list
is
backdrop,
so
you
must
org.
A
We
are
working
on
improvements
to
the
modules
themes
and
layouts
pages.
Last
week
I
rebased
the
previous
branch
we
had
for
that.
So
that
includes
the
latest
security
update
to
backdrop
and
I
do
a
little
bit
of
work
on
trying
to
get.
The
module
seems
only
adds
pages
to
list,
not
only
modules,
themes
and
layouts,
but
also
any
placeholder
projects.
So,
for
example,
if
you
searched
for
a
link
module,
it
would
tell
you
hey
you:
don't
need
link
module,
go
back
drop.
Those
pages
also
now
include
instructions
on
your
updating
from
Drupal
7.
A
Here's
what
you
should
do
for
the
upgrade
process,
if
you're
using
link
module
so
hopefully
will
be
able
to
get
that
rolled
out
soon.
Let
me
demo
button
means
you
want
to
give
us
an
update
on
that.
B
So
if
you
visit
bankruptcy,
master
org,
slash,
demo,
slash
create,
but
there's
a
button
there
that
lets
you
spin
up
a
sandbox
or
a
backdrop
demo,
just
by
clicking
the
button
and
her
a
lot
of
testing.
This
has
just
happened
from
Gator.
It's
intermittent
whether
or
not
it
succeeds
in
creating
a
sandbox,
so
we
fixed
it
so
that
it
works
most
of
the
time
you
maybe
even
just
some
of
the
time,
but
it
seems
to
be
a
little
inconsistent
still
feels.
B
B
Yeah
Gregor
is
also
asking
that
the
sandbox
looks
like
it's
out
of
date.
It's
kind
of
running
currently
written
112
one.
It
should
be
running
112,
six,
we're
so
little
bit
new
to
figuring
all
this
out.
It
seems
to
be
the
problem.
I
pushed
up,
1
12
6
2
2
tugboat,
so
it
should
actually
be
using
the
latest
repository
because
or
the
latest
version,
because
the
git
repository
is
all
its
date
but
for
some
reason
the
new
sandbox.
This
aren't
using
that
new
version.
B
Quite
yet
so
it's
supposed
to
pull
it
in
and
rebuild
it
automatically
nightly,
but
it
seems
like
it's
not
actually
doing
that.
So
we
we
made
this
one
might
actually
be
an
issue,
a
tugboat
or
an
issue
with
our
configuration
I'll
to
investigate
a
little
further
on
that
so
still
not
quite
ready
for
primetime.
But
we
have
result
the
you
know
it
not
working
ever
problem
which
is
based
assistive
forward.
B
C
If
we
update
the
vision,
it
should
be,
okay,
I
guess
can't
tell-
is
the
problem.
There
is
an
issue
with
installing
modules
country,
so
people
won't
be
able
to
test
anything
but
core
and
I'm
not
sure
if
this
is
a
problem
with
tag
board
or
with
1.12
funny,
because
I
thought
from
memory
there
was
a
issue
with
that
release,
so
we
updated
I
will
be
able
to
test
if
you
can
install
in
strip
and
if
that
works,
then
it's
good.
So.
A
B
A
Two
issues
here
we
talked
about
in
the
last
meeting
as
well,
which
was
our
usability
meeting
about
upgrading
instructions
or
how
to
get
from
triple
the
backdrop-
and
this
is
particularly
relevant
now
that
we
have
a
huge
box
on
our
homepage,
telling
me
important.
They
could
do
it,
but
we
have
a
documentation
page,
that's
fairly
detailed.
That
tells
you
how
to
get
from
triple
backdrop,
but
as
people
are
using
it
they're
identified
flaws
in
the
documentation,
as
well
as
potential
issues
with
the
upgrade
process
itself.
A
So
there's
just
an
ongoing
issue
here
to
make
sure
that
we
stay
on
top
of
issues
people
run
into
and
making
sure
we
document
that
a
quick
solution
for
the
nation
in
the
page
on
my
drexina
support,
so
if
you
guys
are
doing
upgrade
anytime
soon,
please
refer
to
that
page
and
make
sure
that
everything
we're
telling
to
do
is
accurate.
It
helps
any
sort
of
person
soon.
The
next
issue
is
5:27.
A
This
is
about
documenting
the
upgrade
paths
for
all
of
the
60
plus
modules
that
are
now
in
backdrop,
or
there
is
a
corresponding
issue
ad
later
on
into
the
lower
part
of
singing
about
actually
integrating
all
of
the
upgrade
paths
for
all
of
those
modules
in
the
court,
because
some
of
the
modules
we
didn't
know
about
it
wasn't
like
hey
we're
gonna
take
this
particular
module
called
layout
creepy
and
put
it
in
core.
It
was
like.
A
Oh,
we
need
to
fix
layouts
and
the
later
I'm,
like
okay,
there's
a
module
that
does
that,
and
so
what
we're
gonna
need
to
do
is
figure
out.
If
there
are
any
settings
in
the
control
console
that
map
to
backdrops
way
of
doing
it
or
if
you
just
say,
uninstall
the
module,
we're
gonna,
do
it
differently
in
that
dress,
so
documenting
each
of
those
steps
for
each
of
those
modules
is
important
too.
A
So
there's
a
meta
issue
here:
that's
just
to
review
all
of
those
16
modules
and
see
which
ones
need
upgrade
paths
which
ones
have
them
already,
which
ones
don't
and
then,
if
we
determine
they
do
need
an
upgrade
customer
lien
individual
issue
for
making
sure
admin
module
has
an
upgrade
in
vector
port
and
then,
if
only
some
of
those
values
are
in
backdrop,
we
need
to
explicitly
state
like
your
sticky
status
will
be
migrated,
but
your
other
options
may
not.
So
people
know
what
they're
going
to
be
getting.
A
A
The
same
is
true
for
our
translation
site,
which
is
running
Drupal
7,
so
that
one
we
need
to
keep
a
little
bit
of
an
eye
on.
There
are
a
bunch
of
Drupal
7,
contribute
issues
that
don't
work
real
well
on
PHP
7.
So
if
anyone's
working
on
the
translation
site-
and
you
come
across
a
problem-
we
have
not
yet
seen
the
result.
A
Let
us
know
you
can
file
an
issue
against
the
project
if
you
touch
our
site,
whatever
we
need
to
do,
but
to
just
the
quantico
that
out
there,
because
that
is
like
leading
with
problems
for
all
of
our
record
sites
are
likely
to
not
have
problems.
We
a
for
you
can
I
out
for
problems
all
right
that
is
it
for
our
websites.
I
want
to
turn
it
over
to
Nate,
to
talk
about
backdrop
CMS's,
so.
B
B
112
7
at
this
point,
probably
is
going
to
be
synchronized
with
the
113
release.
As
long
as
there's
not
another
security
release,
it
comes
out
between
now
and
then
so.
112
7
is
probably
going
to
be
kind
of
retire
things
up
from
the
112
version
and
of
course
everything
gets
put
in
the
113
at
the
same
time.
So
the
things
that
we've
got
outstanding
for
the
next
bug
fix
release
include
one
more
RTL
issue.
B
Supporting
multiple
equivalent
security
releases
honestly,
this
probably
won't
be
in
1:12
at
all,
issued
35
24,
because
we
don't
even
have
a
start-up
implementation,
yet
I
think
we
just
want
to
keep
highlighting
it
during
these
weekly
meetings
to
say
we
really
need
to
get
this
figured
out
with
with
113
around
the
corner
and
then
we're
going
to
be
reporting,
112
and
113
for
security
fixes
for
another
release.
That
will
make
it
so
that
we'll
probably
hit
this
problem
again
and
again
that
were
maintaining
two
branches
at
a
time
for
security
fixes.
B
But
whenever
is
a
security
fix
comes
out?
If
you're
running
the
older
version
of
backdrop,
it
will
continue.
Update
module
will
continue
to
tell
you
that
your
site
is
insecure
when
you're,
actually
fine
and
so
yeah.
We
did.
We
have
a
plan
kind
of
outline,
the
35.4,
but
there's
no
no
code
behind
it.
At
this
point,.
B
A
A
So
this
is
the
paired
issue
with
documenting
upgrade
process
from
any
control
poncho
that
marched
into
court.
This
is
bad
upgrade
past
or
modules
integrated
into
court.
So
if
we
find
something
that
doesn't
include
an
upgrade
path,
that
should
we
should
write
the
upgrade
top
and
put
it
in
so
this
is
something
like
panels.
A
So
this
could
be
really
tricky
because
the
layouts
are
a
little
different
and
if
you
had
100
layouts
and
panels,
you'll
need
to
have
all
hundred
of
those
layouts
in
backdrop,
but
for
the
most
common
use
cases
of
having
one
or
two
layouts
and
having
those
one
or
two
layouts
available
in
pack
drop.
It
is
possible
to
map
which
blocks
into
its
regions.
Now
visibility
conditions,
match
the
paths
and
get
those
moved
over
so
I'm,
not
sure.
A
That's
a
good
example
because
it's
probably
the
hardest
one,
our
plate,
but
I,
think
it
would
be
really
great.
If
you
could
tell
people
hey,
you
don't
have
to
rebuild
all
your
panels,
the
backdrop
because
we'll
try
and
get
them
close
for
you.
There
are
some
much
simpler
things
that
need
upgrade
paths
just
like
getting
variables
from
a
contact
form
block
and
over
to
our
contact
block.
That's
in
bedrock.
So
just
we
just
have
to
kind
of
go
through
each
of
these
kinship
projects
and
say
like
did
they
have
any
settings
in
Drupal
7?
A
C
A
B
Sure
all
right,
113
man,
it
is
right
around
the
corner.
We
now
have
less
than
a
week
before
feature
freeze
which
would
be
May
first
Wednesday,
basically
next
week,
and
before
that
time
we
need
to
button
up
these
remaining.
Are
these
feature
items
and
then
I
think
we've
suggested
this
in
releases
past
that
we
would
like
to
have
a
preview
version
at
the
code
freeze
date
that
includes
all
of
the
functionality
that
will
be
coming
out:
May,
3rd,
May,
15th
I.
B
B
B
B
B
Add
a
new
translatable
strings
to
court
config
files.
This
makes
it
so
that
strings
can
be
pulled
out
of
config
files
as
needing
to
be
translated,
and
so,
ultimately,
the
localization
server
will
be
able
to
identify
those
strings
and
and
translate
them
for
corridor
and
compute
modules.
That's
issued
3455
this
one
is
actually
only
a
starting
point
where
it
does.
The
initial
work
for
some
system-wide
settings
and
I
think
the
emails
that
are
sent
out.
Oh
alpha
is
given
that
a
review.
B
C
C
Think
that
this
was
expected,
because
there
were
a
lot
of
people
that
do
not
could
not
do
code
review
or
we're
not
confident
with
that,
but-
and
they
mentioned
it
multiple
times
in
the
excuse
that
I'm
reluctant
to
mark
this
as
BBC,
because
it
works
like
the
sample
sports.
But
my
code
skills
are
so
I
was
actually
expecting
that
to
happen.
I
also.
A
Think
there
are
people
who
are
capable
of
doing
code
of
view,
but
just
aren't
confident
it's
saying
that
something
is
ready
to
be
committed,
but
if
you
say
works
for
me,
it's
a
much
easier
barrier
to
get.
Okay,
I!
Think
it's
good
without
being
like
it's
good.
It
keeps
going
and
so
I
think
that
there's
something
in
terms
of
like
the
psychology
of
the
people.
If
we
want
to
get
them
a
12-1,
give
them
an
easier
label
to
get
them
more
comfortable.
We
learn
things
I
really
like
it.
B
Well,
you
have
a
case
in
point
there
on
34:55
it
hides
its
art
TVC
according
to
Olaf,
but
so
instead
works
for
me.
So
yeah
that
seems
to
it
seems
to
be
successful,
that
new
tag
and,
lastly,
one
more
issue.
This
is
not
going
to
be
done
by
113,
almost
certainly
but
package
signing
issue
1992,
which
would
make
it
so
that
backdrop,
suemez
org
can
sign
packages
that
are
created
to
guarantee
that
they
were
not
tampered
with
or
modified
in
any
way
has
been
moving
forward.
B
Still
like
we
made
some
merges
into
project
module,
which
is
a
good
first
step,
so
we're
giving
back
toka
semester,
org
kind
of
primed
to
be
capable
of
doing
the
signing,
but
still
more
review
is
necessary
to
actually
look
at
the
part
that
actually
confirms
the
signatures.
That
would
go
into
core
itself.
So,
yes,
still
in
progress
there,
yeah
and
anybody
that
has
time
to
take
a
look
at
that
more
help,
but
definitely
be
appreciative
and
reviewing
all
the
functionality
there.
B
That's
it
so
113
looks
like
overall,
it
would
be
pretty
modest
as
far
as
functionality
goes,
they
think
dashboard.
It's
gonna
be
a
big
thing.
Oh,
we
have
had
some
additional
like
conveniences
for
in
the
API
that
has
been.
Did,
let's
see
what
else
have
we
got
here?
Some
minor
UX
improvements
changing
the
way
the
Ahmedabad
can
be
turned
on,
extend
translation
mantra
to
include
a
block
that
could
not
translated
content.
Oh
I
know
that's
kind
of
neat
like
blocks
that
you
place
you
can.
B
If
you
place
the
existing
content
block,
you
can
now
pull
in
translated
versions
of
that
piece
of
content
automatically
and
started,
placing
six
different
blocks
that
are
all
just
the
different
languages.
So
yeah,
it's
gonna,
be
pretty
modest
I.
Think
overall,
but
not
every
release
is
like
huge
one,
so
yeah,
that's
all
I
got
for
one
one.
Thirteen
status
update.
C
B
A
C
A
C
What
what
happens
to
tests?
For
example,
we
said
that,
with
its
release,
we
will
be
including
updating
the
city
editor
or
dick
query,
which
was
done,
but
sick
editor
has
a
few
bug
releases
like
three
of
them
very
small
things,
very
tiny
things
we
still
running
through
the
the
updates
for
that
with
the
previous.
A
Yeah
every
issue
should
be
tagged
with
which
version
is
going
into
and
anything
that's
packed
with
113
and
is
committed
by
the
first
will
be
in
the
pre
routes.
If
the
issues,
because
112
7
it'll
probably
also
be
in
a
pre-release,
but
if
she
gets
tagged
like
113
one,
it
won't
be
in
the
clear
release.
It
won't
be
in
13,
that'll
come
out
in
the
first
bug
fix
release.
Oh
okay,.
C
C
A
Think
it'll
be
up
to
four
main
years
to
like,
if
all
of
the
updates
to
all
the
latest
versions
of
see
Canada
are
super
trivial.
That
could
be
a
bug
fix
that
gets
between
in
between
that
preview
release
and
the
actual
fix.
But
if
there's
anything
in
it,
it
could
potentially
break
can't
rip
that
might
get
like
bumps
to
like
114
so
yeah,
but
I,
don't
think
it
that'll
happen,
but
it'll
be
good
to
actually
see
the
code
so.
C
The
idea
was
that
if
we
do
have
pre-releases,
we
will
be
including
those
fixes
just
to
have
more
sort
of
like
testing
exposure
yeah,
so
I'll
try
to
get
full
requested
filed.
It's
very
trivial
changes.
Actually,
those
three
okay
I
think
one
of
missile
I
would
support
the
other.
One
was
a
fixing
us
change
longer
than
a
very,
very
minor
things.
B
C
A
B
C
I
know
that
this
is
going
to
be
the
first
sort
of
like
teacher
freeze
that
we
have
a
pre-release
as
well
like
a
release
candidate,
but
previously
we
were
sort
of
like
lenient
when
came
to
weekend
or
public
holidays.
So
if
it
was,
the
Future
fridge
was
to
happen
over
a
weekend.
We
would
sort
of
like
give
it
the
whole
weekend
and
do
it.
The
next
Monday
yeah
yeah
yeah
still
doing
that.
Yeah.