►
From YouTube: Backdrop Weekly Apr 12
Description
Today’s development agenda: https://bit.ly/2EnNuCF
A
All
right
we
are
on
air,
it
is
Thursday,
August,
12,
sorry,
April,
12th
very
minute.
One
starts
with
a
12
today
we're
doing
this
is
a
check-in
on
active
development
tests
for
vector
of
CMS.
Before
we
get
into
tasks,
I
wanted
to
welcome
VIN.
So
three,
it's
a
new
community
member.
We
have
who's
working
on
the
CSS
injector
module.
This
is
something
that
we
had
a
core
issue
about
a
long
time
ago,
and
we
said
we
were
late
for
it
of
often
contra,
but
if
it
became
highly
adopted,
we
would
consider
it
for
core
inclusion.
A
So
it's
fantastic
that
it
now
is
going
to
exist
for
contraband,
we'll
actually
get
to
see
how
it
evolves
there
first
and
we
can
count
it,
which
is
great.
So
thanks
events
for
working
on
that
I
think
it's
something
that
a
lot
of
people
in
Drupal
7
I'm,
currently
using.
It's
also
something
that
people
in
our
target
market
are
going
to
expect
because
they
get
that
in
WordPress.
A
So
having
a
comprable
colon
and
backdrop
will
give
us
a
chance
to
do
the
kind
of
refinements
we
might
need
in
order
to
potentially
put
something
like
that
in
court
on
websites
were
working
on
for
backup,
CMS
or
we
are
currently
working
on
some
changes
that
would
help
improve
the
selection
of
modules
and
themes
and
layouts.
Some
of
those
are
designed
to
changes.
A
Some
of
those
are
functionality,
changes
and
some
of
them
are
sort
of
significant
like
we
need
to
fix
the
way,
search,
works,
sort
of
changes,
so
I,
don't
know
if
that's
gonna
be,
let's
fix
core
search
or
let's
set
up,
search,
API
or
Apache
Solr
or
some
other
kind
of
module
takeover.
Our
core
searching
my
instinct
on
that
is,
we
probably
should
fix
core,
because
most
backup
sites
won't
be
using
something
like
Apache,
Solr
or
any
kind
of
external
search
service.
So
as
much
as
that,
we
can
do
on
our
own
site.
A
I
think
would
help
everyone,
the
forum's
site.
We
are
still
waiting
for
a
search
box.
I'll,
try
and
get
that
done
today.
Shouldn't
be
too
much
work
to
get
that
knocked
out.
It
should
be
some
yes
changes
and
hopefully
that's
it
and
that's
it
for
our
projects
and
meet.
Do
you
want
to
do
a
review
on
backdrop
itself.
B
B
The
last
bug
fix
release
for
one
point:
nine,
but
we'll
see
it
is
possible
that
we
might
make
one
point
nine
forward
and
then
one
point:
nine
five
or
something
like
that
outstanding
issues
of
note
issue
2904
still
dealing
with
the
regression
that
was
introduced
in
1.9
regarding
the
encoding
of
database
credentials
and
southern
stuff.
Php
there's
still
pull
requests
there.
That
needs
work.
B
Actually,
this
could
happen
just
as
likely
that
if
someone
did
a
new
installation
of
backdrop
and
installed
it
or
typed
in
the
database
credentials
manually
and
setting
stuff,
PHP
and
included
the
percent
symbol,
it
won't
work
currently
and
with
the
patch
it
will
work,
but
we
need
to
make
it
so
that
we
report
to
the
user
via
the
status
report,
that
something
is
wrong
with
their
settings
of
PHP.
The
percent
symbols
need
to
be
encoded
so
that
one's
still
in
a
state
that
means
work.
B
Let's
see
recently,
we
had
this
minor
issue:
29
71,
that
when
you
upgrade
from
Drupal
7
the
emails
that
are
upgraded
into
config
files,
they
lose
all
of
their
line
breaks
as
part
of
the
upgrade
process,
and
that
was
marked
our
TBC
earlier
today
and
I
just
a
couple
of
minutes
ago.
So
yeah,
that's
nice.
That
bug
is
now
corrected.
B
We
have
a
bunch
of
other
issues
for
one
point:
9.4
just
higher
priority
items.
Let's
see
how
many
there
are
in
the
list
right
now,
they're
currently
32
issues
that
are
of
importance
looks
like
a
couple
of
these
got
marked
back
up
to
needs
review,
which
is
awesome,
looks
like
five
or
so
our
vacuum
meets,
review
and
I'll
take
a
look
at
those
as
soon
as
I
get
a
chance.
B
Let's
see,
that's
it
for
1.9.
The
next
bug
fix
release
for
one
point:
10
the
next
minor
version
that
that
will
be
coming
out:
May
15th,
so
that
gives
us
a
little
just
tad
over
a
month
to
get
one
point
10
and
put
together
and
in
particular
I
guess.
We
actually
only
have
let's
see
10
days
until
aside
one
of
my
st.
10
days,
two
weeks
roughly
to
get
one
point.
10
feature
complete
right
now.
The
things
that
are
in
1.10
are
fairly
minor.
B
B
So
it
just
needs
every
role
and
then
I
think
that
one
is
pretty
much
good
to
go.
Config
translation,
adding
the
ability
to
not
really
adding
the
ability,
but
adding
a
central
mechanism
for
translating
strings
those
sort
of
configuration
is
issue
704
that
one
we
haven't
seen
any
progress
on
anytime
recently.
We
still
have
a
good
plan
there,
but
no
implementation.
B
B
But
things
to
the
efforts
of
bjorn
st
he's
put
together
a
really
excellent
pull
request
that
I
reviewed
earlier
this
week,
and
now
it's
back
in
fairness,
teas
court
to
do
some
minor
changes
to
block
translation.
He
called
out
there
that
he
could
use
some
help
writing
tests
as
he's
not
familiar
with
that
process.
So
if
anyone
out
there
like
to
help
assist
there,
some
tests
facilitating
would
be
highly
appreciated.
B
There
are
a
bunch
of
other
items
for
1.10.
I
rewrote
an
issue,
for
example,
on
adding
description,
capabilities
to
blocks
or
to
custom
blocks
so
that
you
can
set
a
custom
description
as
well
as
the
administrative
titles
that
that
one
is
currently
in
a
needs
review,
although
it
should
be
RTB,
see
here
shortly,
opening
and
closing
comments
like
a
common,
auto,
closer
capability.
B
It
looks
like
that
has
been
updated
and
rear
old,
so
that
issue
I'll
take
another
look
at
that
issue:
3001
yeah
and
there's
a
bunch
of
others
actually
there's
a
whole
bucket
of
items
here.
There
are
now
marked
needs
to
review
again
in
the
1.10
queue,
so
I'll
be
taking
some
time
to
go
through.
Those
I
think
that
I
did
go
through
all
of
the
are
TBC
issues
this
past
week
and
either
merged
or
mark
those
back
down
to
meets
work.
B
C
B
A
Think
in
general
it
will
be
great
if
our
update
instructions
for
any
problem
would
be
just
copy
the
core
directory
and
that's
it,
however,
I
think
some
of
these
files
don't
work
that
way
like
I,
think
the
htaccess
file
has
to
be
here
or
it
won't
work
properly
and
I.
A
Think
if
you
like,
if
we
did
some
kind
of
assembling,
it
might
not
work
the
way
we
would
expect
it
to,
because
there
would
be
one
htaccess
file
for
the
root
and
then
one
for
core
and
I,
don't
and
especially
because
htaccess
is
something
that
you're
supposed
to
change
on
your
own
site.
A
Like
you,
don't
want
to
blindly
merge
in
core
changes,
we
would
need
to
explicitly
state
if
there
was
a
change
in
HT
access
that
you
wanted
to
include
in
your
site,
so
I
think
we
should
also
have
a
process
for
anything
we
can
put
in
that
core
directory.
That
would
work,
that's
fine.
We
should
do
it,
but
for
those
files
that
are
gonna
create
a
problem
by
copying
into
the
core,
we
should
have
that's
like
with
every
core
release.
We
just
stayed
somewhere.
A
No
changes
were
made
to
the
htaccess
file
or
whatever
it
is
that
we
end
up
believing
outside
of
core
I
noticed
when
I
was
looking
at
the
Drupal
8
update
instructions.
It
was
like
copy
the
core
directory
check
this
one
file
copy
the
vendor.
It
was
very
complicated
thing
where
I.
C
A
Our
side
of
the
leaf
that
we
don't
have
a
situation
that
dot
that
complicated,
but
it's
already
a
little
bit
messy,
where
we
can't
just
tell
people
to
copy
the
core
directory,
which
is
I,
think
what
we
want.
Sony
I,
don't
know
if
you
want
to
take
a
look
at
the
list
of
files
there,
that
if
you
w
pandas
enumerated
and
see
like
one
of
those
what
we
can
move
into
core
and
what
we
can't
look,
we
already
have
I
think
like
index.
A
B
Yeah,
the
only
one
fit
well
and
the
profiles
directory
is
outside
of
court
currently
and
I.
Think
the
profiles
directory
is
probably
actually
the
biggest
problem
we
have,
because
we
actually
do
change
the
profiles
pretty
regularly
like
that
the
default
install
profile.
However,
that's
not
super
important
for
sites
updating,
because
they've
already
installed
right.
So
you
know
it's
not
terrible
that
the
install
profiles
are
not
updated,
although
that
that's
definitely
a
weird
gotcha
and
so.
A
Yeah
I
also
think
it's
like
you
don't
want
to
include
any
changes
if
we
added
changes
in
there
for
the
site
like
without.
Thank
you
know,
so
that's
another
one
where
it's
like.
We
it
designed
these
files
to
be
yours
and
not
changed,
and
so
those
need
to
not
be
in
core
because
we
don't
want
them
getting
over
it,
but
I
think
like
get
ignore
it.
A
That's
also
something
you're
gonna
or
right,
editor,
config,
I,
don't
know
if
people
are
gonna
overwrite
that
one
or
not
cuz
I,
don't
use
it,
but
I
think
it's
another
thing.
That's
like
we
put
it
there
because
it's
helping
you,
but
it's
a
starting
point
and
there
shouldn't
be
any
changes,
we're
making
to
what
they're
gonna
change
the
way
the
software
works.
Yeah.
A
B
Ya
know
the
read
the
remains
to
stay
there,
because
that's
where
github
looks
for
it.
You
know,
that's
what
you
see
when
you
visit
the
backdrop
github
page
and
it's
also
like
we
did
move
everything
other
than
the
readme.
Even
things
like
the
license
file
and
everything
I
cut
into
just
the
core
directory
I
think
that's
where
the
text
file.
Sorry.
A
B
And
even
then
we
wouldn't
actually
move
it.
We'd
probably
just
take
all
of
its
contents,
then
no,
we
wouldn't
send
link
it.
We
leave
index
dot,
PHP
exactly
where
it
is,
and
index
up
a
tree.
Rollin
contained
one
line,
which
is
include
another
file
that
would
live
within
core
I.
Don't
think
they'd
want
to
get
into
some
ways
because
symlinks
our
operating
system
dependent
and
they
won't
work
on
Windows,
for
example.
Ok,.
A
We
would
explicitly
say
like
this.
Particular
change
includes
a
change
to
HT
access.
Please
see
lines
46
to
48
or
whatever
it
is,
and
not
way.
People
have
over
in
their
HT
access
will
get
specifically
pointed
to
a
part
they
might
want
to
glued
in
their
own.
That
would
make
that
more
clear
for
people.
Upgrading,
so
I
think
the
problem
right
now
is
uncertainty.
People
don't
know
what
these
files
do.
They
don't
know
if
they
need
the
changes
or
not.
C
C
C
A
Your
assumption
is
like
hard
before
it's
fine
and
then,
if
there's
when
it's
not
it'll,
be
in
the
release,
notes
or
it'll,
be
you
know
somewhere
I,
don't
I,
think
the
release
notes
a
good
place
for
that,
but
anywhere
else
you
think,
might
be
better
mate.
We
could
do
that
too,
but
as
long
as
we
have
a
way
of
like
telling
people
when
something
like
that
does
change,
so
they
can
at
least
look
at
the
differences.
Yeah.
B
B
B
Just
I
guess,
primarily
we
can
update
the
procedures,
documents
that
are,
in
the
backdrop,
issues
for
posit
ori
and
the
steps
to
create
a
new
release.
You
know
when
we
say
draft
release
notes.
We
should
put
some
bullets
underneath
draft
release,
notes
indicate
we
should
it
actually
indicate
a
couple
of
things
we
should
indicate
where
they're
up,
running,
update
PHP
is
necessary
and
we
should
indicate
if
any
files
outside
of
core
have
been
changed
in
every
time.
We
do
it
release
notes
and
maybe
we
should
say
explicitly,
update
dot
PHP.
B
C
C
B
Yeah
a
good
example
actually
like
we
could
change
those
files
to
make
to
make
improvements
to
the
way
that,
like
rewrites
work,
for
example,
cuz
I,
know
Jen
hates
the
the
way
the
HTTP
rewrites
work.
For
example,
break
me
local
sites
yeah,
but
we
actually
even
even
then
like.
Thank
you,
say
it's
not
actually
required
that
people
update
their
HDX
s
files.
It's
it's
optional.
You
know
like
if
you
like
the
new
method
more
than
an
update
anytime,
there's.
B
With
that
issue
that
I
mentioned
earlier
about
how
the
database
credential
format
changed
like
that's
exactly
the
same
problem
where
something
changed
in
the
way
setting
stop
PHP
functions,
and
so
we
need
to
add
to
the
status
report
an
indicator
that
something
had
changed
if
if
the
user
is
affected
by
it,
so
hopefully
we'll
continue
that
pattern.
I
think
you
know,
the
convention
is
already
there
and
we've
already
done
it
multiple
times
and
we're
in
the
middle
of
something
exactly
like
this.
So
hopefully
people
can
feel
a
little
bit.
B
Opposed
to
come
in
here,
I
think
that
the
comments
are.
You
know
that
the
issue
itself
is
is
legitimate,
like
it's
a
good
concern,
but
I
think
we'll
solve
it.
The
way
that
other
people
are
describing
here,
basically
through
processes
and
documentation
updates,
rather
than
rather
than
changing
the
code
or
in
the
structure
I
just.
A
Updated
our
documentation
page
on
how
to
upgrade
or
how
to
update,
which
does
specifically
say
only
replace
the
core
directory
I,
just
added
a
little
bullet
there.
That
says,
if
any
of
the
files
outside
the
core
directory
can
change.
They'll
be
explicitly
mentioned.
The
release
notes
so,
hopefully
that'll
help
clarify
anyone
who
does
go
to
that
page
to
look
for
how
to
do
updates.
A
B
A
Yeah,
it's
a
little
silly
I!
Think
it's
fine!
What's
a
let's
see
if
we
can
fix
the
process
that
makes
people
confused
about
it
and
then
re-evaluate
whether
we
need
to
move
the
file
or
not,
if
there's
any
ever
any
changes
to
it.
That
would
be
a
good
indication
that
we
do
need
to
move
the
file,
but
if
there
aren't
any
changes
to
it,
if
you're
like
the
whole
one
dot
X
cycle
like
maybe
it's
not
worth
it.
If
it's
only
three
lines,
the
likelihood
of
us
having
to
change
for
it
are
pretty
slim
so.
B
Yeah
yeah,
the
only
time
we
changed
setting
index
dot
PHP
in
the
entire
history
of
the
project
was
when
we
Drupal
to
backdrop
all
that
time
it
was
jaoa
to
change.
Drupal
bootstrap
to
backdrop
bootstrap,
that's
pretty
funny
wow.
This
goes
all
the
way
back
to
the
original.
You
can
see
back
in
May
5th
May
18th
mm
line,
number
2
in
index.
Dot
PHP
is
commit
number
1,
but
the
commit
message
imported
sources
from
Greece
I.
Guess
it's
not
surprising.
I
mean
index
dot.
Php
is
kind
of
an
important
file
for
PHP
application.
B
A
Agrees
thanks
for
agreeing
that
I'm,
okay.
Well,
that
was
all
we
had
for
today's
meeting.
Unless
there's
anything
else,
you
guys
want
to
talk
about.
No
okay.
Well,
we'll
see
you
in
the
queue
I
want
to
make
a
bunch
of
progress
on
modules.
Today,
that's
my
goal,
so
yeah
thanks
for
coming
and
meeting,
and
thanks
for
watching,
live,
and
hopefully
others
will
watch
later
and
thanks
for
watching
that.
So
thanks
everyone.
My.