►
From YouTube: Backdrop Weekly - Jan 31
Description
Today’s development agenda: http://bit.ly/2B9DYEA
A
All
right
today
is
January
31st
last
day
of
January.
This
is
a
meeting
to
check
in
on
active
development
tasks
for
backup,
CMS
Before.
We
jump
into
court
I
wanted
to
thank
int
reporting,
the
imce
renamed
module,
so
we've
got
some
new
people
in
our
config
key
working
on
imports.
So
thanks
for
that,
and
we
will
work
on
making
you
part
of
backup
contribute.
A
Also,
since
last
week
we've
got
two
new
contribs
photos,
swipe
which
is
integration
with
a
JavaScript
library
and
webform
registration.
So
thanks
everybody
for
working
on,
contributed
modules,
things
and
Lance
I
appreciate
that
for
website
practice,
a
master
org
stuff.
We
covered
a
lot
of
issues
in
the
design
usability
meeting
earlier
this
morning.
So
if
you're
curious
about
what
we
talked
about
there,
particularly
around
mantra
seams
and
layouts
pages
and
the
demo
buttons,
you
can
go
ahead
and
watch
the
video
from
an
hour
ago
and
then
it'll
update
there
and
then
our
translations
sight.
A
Olaf
said
he
wasn't
going
to
make
the
meeting
today,
but
he
also
mentioned
that
he
was
gonna
start
working
on
the
localization
server
I
think
when
he
left
this
message.
It
was
yesterday,
so
that's
actually
today
so
he's
going
to
be
doing
testing
with
language
files
and
trying
to
figure
out
what
we
need
to
do
next,
which
is
exciting
all
right
backdrop,
CMS
itself.
A
We
have
a
handful
of
bugs
with
fixes
that
are
ready
for
112,
and
that
includes
a
change
to
the
github
system
that
prevents
the
module
installer
from
installing
modules
properly
and
a
whole
bunch
of
right-to-left
issues
where,
if
you
change
to
a
different
language,
the
CSS
wasn't
working
quite
right
in
basis
and
seven
and
we've
got
a
bunch
of
those
that
are
our
TBC
and
those
will
go
in
soon
and
stuff
that
needs
review.
We
have
a
core
update
issue
where,
if
you
have
a
test
file,
that's
missing
a
type
line.
A
A
We
added
for
fuse
grids
where,
if
you
had
previously
themed
of
use
grid
item
that
had
a
structured
array,
syntax
and
then
you
updated
to
the
latest
version
of
backdrop,
the
structure
to
write
syntax
is
gone
because
the
view
is
assuming
you're
using
a
CSS
grid
and
not
the
old
table
style
grid.
So
the
theming
will
break
on
any
site.
That's
updated!
There's
a
fix
there.
A
That
includes
an
update
hook
that
will
sort
of
check
the
box
that
says,
use
legacy
tables
for
any
old
views,
but
I
tested
that
once
on
one
of
my
sites
and
it
didn't
work,
I
tested
on
a
second
site
and
it
did
work
so
I
need
to
figure
out
what
the
steaming
changes
are.
That
would
cause
it
to
work
and
what
they
are.
That
would
cause
it
to
not
work.
I've
got
that
for
my
list
today
to
figure
that
out,
because
I
would
love
to
get
these
fixes
in
and
get
a
release.
A
A
This
one
is
not
super
urgent,
but
it
would
be
great
if
we
could
get
it
in
the
only
thing
that's
remaining
for
that
issue
is
for
someone
to
find
a
website
that
does
a
contrast,
check
and
check
that
our
colors
are
high
enough
contrast
that
everyone
will
be
able
to
see
them
in
our
default
palettes,
so
I
think
I
had
a
link
to
one
from
a
long
time
ago.
I
could
dig
it
up
I'll,
throw
in
the
issue
queue
if
I
can
find
it.
A
But
if
anyone
does
accessibility,
work
and
knows
about
that
resource
and
could
do
that
color
checking
that
would
be
fantastic
and
then
issues
for
113.
We
have
dashboard
module,
which
is
coming
along
really
nicely.
It
has
a
pull
request
that
could
use
a
review,
we're
also
looking
for
feedback
from
people
as
to
what
really
useful
dashboard
items
might
be.
A
We're
currently
working
off
of
what
was
provided
in
the
total
control
can
triple
for
Drupal
are
also
looking
at
some
of
the
blocks
that
were
provided
in
Drupal
core,
but
I
think
would
also
be
good
to
hear
from
people
who
use
other
tools
like
WordPress
and
Joomla
and
mentioned
what
they
really
appreciate
about
having
on
those
dashboards
and
make
sure
that
we
cover
sort
of
you
know
what
is
it
you
always
wanted
on
your
dashboard.
That
hasn't
yet
been
done
in
Drupal
my
backdrop,
and
we
also
have
the
next
step
for
translating
config
files.
A
This
is
issue
34:55.
In
the
last
version
of
backdrop,
we
included
the
ability
to
translate
config
files
and
now
I
just
need
to
go
through
those
config
files
and
identify
which
strings
should
be
translated.
So
I
don't
know
if
this
is
going
to
be
a
tedious
task
or
not.
Somebody
already
has
a
backdrop.
Admin
interface
translated
that
probably
got
us
most
of
the
way
there
we
are
gonna
have
to
go
through
all
of
the
config
files
and
identify
translatable
strings
I,
wonder
if
definitely
we
could
automate
that
yeah
we'll
see
anyway.
A
That's
what
comes
next
and
then
other
major
things
for
113.
We
have
package
signing,
so
this
is
something
that
I
think
we
need
to
get
done
in
conjunction
with
automatic
updates.
It'll
be
great
if
we
could
get
it
done
sooner.
It's
just
sort
of
an
extra
security
measure
to
make
sure
that
the
package
that
your
site
is
installing
is
the
package
that
backdrop
CMS
tour
delivered.
A
So
they
prevents
something
from
getting
in
the
middle
and
swapping
out
your
code
with
something
else
that
might
be
malicious
so
most
of
the
times,
it's
not
a
huge
risk
but
I
think
having
as
much
security
in
there
as
possible
is
gonna,
be
good.
Before
we
get
the
automatic
updates
happening
for
people
and
then,
let's
see
that's
all
I
had
for
backdrop
core
Gregory
you're.
Here
now
we
did
talk
about
in
the
design
usability.
This
morning,
I
tried
to
summarize
your
issues
on
user
role.
A
Confusion
specifically
coming
from
the
usability
studies
that
we're
done
in
Drupal,
7
and
potential
recommended
fixes
to
that
I.
Don't
know
if
you
want
to
add
anything.
You
know
you
weren't
available
earlier
today,
but
I
don't
know
if
there's
anything
you
like
one
specifically
champion
behind
those
before
we
move
on
to
general
discussion
items
yeah.
B
B
B
It's
it's
sort
of
like
see
how
we
have
the
ability
now
to
specify
an
administrator
role,
which
role
is
the
administrator,
it's
something
similar
to
that
for
anonymous
and
authenticated
user
roles,
and
there
is
already
a
putz
some
work
that
has
been
done
for
Drupal
I
need
to
test
that
and
see
like
from
reading.
A
summary
did
make
a
lot
of
sense.
Now.
I
need
to
sort
of
like
I,
actually
use
it
and
see.
B
We
already
have
a
setting
for
anonymous
users,
we
call
them,
but
we
had
called
the
specific
labels
for
tick
boxes
and
radius
and
also
there,
the
header
of
the
column
for
permissions.
So
we
asked
the
the
admin
how
they
want
to
call
the
anonymous
users
on
the
side.
But
then
we
keep
using
the
word
anonymous.
Those.
A
Are
due
different
settings,
though,
and
I
think
we
need
to
just
change
the
language
on
the
check
box
so
that
people
don't
think
they're
the
same
thing,
so
one
of
them
is
the
name
for
the
role,
which
is
something
that's
only
shown
to
administrators
on
the
site,
anytime,
you're,
managing
the
role
and
the
other
one
is
the
actual
username.
So
it'll
show
up
in
a
comment
where
it
says
like
posted
by
blank,
and
so
that
is
something
that
is
shown
to
everybody.
C
A
B
A
B
Which,
by
the
way,
the
if
we
end
up
implementing
or
if
Drupal
ends
up
implementing
what
is
being
discussed
on
35
10,
which
is
remove
the
hard-coded
anonymous?
And
if
indicated
user
roles,
and
because
the
main
argument
behind
it
was
that
these
things
are
States
and
not
roles
and
they
can
be
sort
of
like
assigned
to
people
buy
things
triggered
like
whether
their
user
has
logged
in
or
not.
It's
sort
of
like
being
flags,
so
decide.
Yeah.
A
B
It's
an
interesting
discussion
and
then
other
than
that,
although
the
UX
around
roles
there's
a
Marty,
so
we
hadn't
a
lot
of
RTL
issues
and
we
fixed
quite
a
few
of
them.
Most
of
them
were
sort
of
like
cosmetic.
There
was
one
that
was
annoying.
It
was
preventing
users
from
clicking
the
third
level
menus
in
admin
menu,
and
we
fixed
that
because
they
were
overlapping
with
the
second-level
bending
menu.
Now
there's
another
one.
B
B
But
it
doesn't
have
to
do
with
that
specifically
because
some
of
the
icons
do
get
rendered
bogus,
don't
anyways,
but
it
is
quite
annoying,
it's
good
that
we
have
at
least
one
user
that
is
extensively
using
the
RTL
now
because
they
report
such
issues
but
yeah
other
than
that.
Nothing
else
comes
to
mind.
Okay,.
A
B
B
A
A
B
Logic
that
picks
up
the
names,
because
the
file
names
of
the
actual
icons-
if
they
we
have
some
of
them
that
are
specifically
RTL,
so
they
have
a
desire
DL
on
the
name.
So
the
logic
is
PHP
is
not
JavaScript,
but
I.
Just
couldn't
put
my
finger
on
it
where
the
logic
was
going.
Well,
that's
not
just
because
we
have
our
TL
and
then
we
have
I.
Don't
know
like
there's,
not
a
lot
of
comments
like
code
comments
in
that
specific
section
of
the
code,
so
there's
a
an
alternative.
That's
alternative!
B
B
A
Then
I
was
hoping
we
could
get
another
bug
fix,
release
out
soon,
112
too,
but
we'll
have
to
talk
to
me
or
Jeff
or
herb
and
see
what
their
availability
is
like.
I
would
look
to
get
some
of
these
issues
at
least
marked
our
TBC
and
potentially
merged,
even
if
we
can't
get
a
really
set
so
that
people
who
are
having
problems
can
download,
like
the
latest
version
of
1
by
X
and
still
have
fixes
to
them.
A
A
We
had
a
lot
of
major
improvements,
but
there
are
also
a
couple
of
bugs
that
we
missed
somehow
in
our
testing
before
the
release,
and
so
now
there
are
bugs
were
trying
to
fix
in
the
post
release
before
we
push
the
code
to
Pantheon
and
make
everybody
update
and
before
we
sent
the
newsletter
to
tell
everybody
about
it.
Like
hey.
A
Look
at
backdrop
like
that's,
we
don't
want
them
to
see
anything,
that's
broken
and
in
a
perfect
world
we
would
push
the
update
go
a
week,
have
anything
wrong
and
then
be
able
to
do
all
these
things.
She's,
like
okay
and
so
I
would
love
to
come
up
with
a
way
that
we
can
have
that
release
cycle
happen
not
have
anything,
go
wrong.
I!
Don't
think
that
it's
possible
to
do
100%,
nothing
or
a
long
time,
but
I
would
love
to
get
closer
than
we
did
this
particular
release
and
I.
A
Don't
really
know
how
to
do
that,
because
the
more
improvements
we
put
in
the
more
changes
we're
going
to
make
the
more
likely
we're
going
to
cause
something
to
not
work
correctly
and
the
one
thought
that
I
had
is
that
if
we
could
do
a
release
on
the
first,
that
was
a
preview
release.
Before
we
did
the
official
release
on
the
15,
then
we
could
have
everybody
updated.
A
The
pre
group
preview,
everybody
who
wanted
to
update
to
the
preview
release
and
do
a
pretty
thorough
testing
on
that
and
I
think
that
might
be
a
much
easier
way
to
ask
people
to
test.
It
then
asking
them
to
update
to
the
latest
version
from
github
if
we
could
have
a
packaged
version,
I
think
they'll
be
much
better.
A
At
least
I
know
from
my
experience,
it's
really
easy
for
me
to
download
a
package
and
update
a
site,
but
if
I
have
to
like
go
check
it
out
copy
it
over,
it's
just
it
seems
like
more
work,
even
though
it
might
not
actually
be
able
to
work
and
I.
Think
what
make
me
I
know:
I
only
updated
two
of
my
sites.
Today's
version
before
the
release
came.
A
I
would
like
to
encourage
myself
to
do
more
and
I
think
having
a
release.
I
think
that
easier,
so
I'm
wondering
if
other
people
are
feeling
the
same
way,
and
that
was
one
idea
you
came
up
with
and
then
another
one
is
just
very
much
a
better
test
coverage,
particularly
in
JavaScript.
This
is
something
that
we've
you
know:
Drupal
doesn't
have
JavaScript
testing
for
Drupal
7
either
it's
something
that
we've
known
for
a
long
time
would
be
really
great
to
have.
We
don't
have
it
set
up,
but
maybe
on
github.
A
There
is
already
solutions
out
there.
That
would
enable
us
to
do
better,
JavaScript
testing
or
any
job
script
testing
for
a
backdrop-
and
we
should
do
some
more
research
today
into
where
we
are
because
then
we
looked
at
it
four
years
ago
and
back
to
first
the
amounts
that
oh,
it's
still
hard
but
I'm
not
sure.
We've
done
an
exhaustive
search
of
other
possible
JavaScript
testing
solutions
and
what.
A
B
Of
the
tools
that
we
use
in
our
agency
quite
extensively
is
visual
regression
tool
and
it
does
allow
you
to
authenticate.
So
we
can
visually
test
the
back
and
see,
for
example,
that
ckeditor
left
to
right
issue
that
came
up
could
have
been
picked
up
and
I
think
that
there
are
some
solutions
out
there
that
are
sponsoring
open-source
projects
that
we
could
use.
B
B
But
then
their
site
kept
complaining
that
there
is
a
security
update,
which
is
a
similar
issue
to
what's
happening
with
d8
now
with
semantic
versioning
and
the
way
that
releases
work
in
d8
now.
So
they
may
release
security
updates
for
the
current
minor
release.
But
then
they
also
back
ported
to
the
previous
minor
and
there's
a
lot
of
sites
that
do
not
quite
update,
but
even
if
they
update
to
the
minor
the
previous
minor
they
still.
B
A
A
I
have
a
feeling
this
is
you
know,
not
a
new
problem
that
people
haven't
thought
about
before,
but
yeah
I
mean
I.
Think
what
we're
doing
right
now
is
we're
just
pulling
like
hey.
What's
the
latest
secure
version,
and
then
we
compare
the
numbers
we're
like?
Is
this
number
bigger
than
the
that
number?
Yes,
no,
but
there's
a
probably,
we
could
say
like
what
are
all
the
latest
versions
and
then
what
is
the
version
you
haven't?
Do
a
little
smarter
checking
on
the
like,
okay.
B
A
B
A
B
A
Think
we
need
to
first
set
in
the
policy.
We
should
open
an
issue
in
the
PM
CQ,
it's
like
hey
many
designs
and
then
mine
are
already
vanished.
This
sounds
familiar,
but
I
don't
know
if
there's
an
issue
or
not,
but
it's
already
just
so
that
we
can
state
it
and
then
we
need
to
figure
out
where
we
write
the
policy.
So
then
we
would
need
an
issue
on
dr.
CMS
tie
or
commute.