►
From YouTube: Backdrop Weekly - Dec 13
Description
Today’s development agenda: http://bit.ly/2RHjd9d
A
So
before
we
get
into
what's
going
on
backdrop,
core
one
contributed
project
update
this
week,
I
thought
was
notable
geo
coder
finally
got
a
release,
and
that
project
is
one
that
has
had
a
ton
of
people
have
their
hands
on
it.
Since
it
was
started,
the
port
was
originally
started
with
ephod.
It
was
then
improved
by
West,
Jones
or
Earth
Day
47,
and
it
was
completed
by
Wan
Walla
and
then
in
order
to
get
it
to
release
done.
A
I
took
over
maintainer
ship
of
it
last
week
and
merged
in
pull
request
from
a
whole
bunch
of
people
and
thought
it
out.
So
I
just
wanted
to
say
thank
you
to
all
of
the
various
people
that
have
had
their
hands
and
getting
geo,
coder,
ported
clinical
backdrop,
and
now
anyone
who
needs
to
use
geo
coder,
particularly
for
plotting
addresses
onto
Maps,
has
a
workable
solution
for
getting
that
done.
A
For
our
website
backdrop,
CMS
org
is
getting
a
lot
of
attention
these
days
around
the
treatment
of
projects
and
I
think
that's
particularly
notable
because
Drupal
9
now
has
an
official
release
date
and
not
sure
whether
it'll
happen
on
time
or
not,
but
it
is
likely
to
which
is
going
to
be
June,
30th
of
2020
and
so
I
think
more
people
are
going
to
start
looking
at
backdrop
as
a
suitable
alternative
to
a
Drupal
8
for
existing
Drupal
7
projects,
and
so
I
would
love
to
be
able
to
get
the
Project
SEARCH
updated
and
be
more
usable
for
those
people
to
figure
out
if
that
rocks
a
good
fit
for
them.
A
The
designs
that
we
had
originally
done
four
years
ago
or
so
have
finally
been
fully
implemented,
but
I'm
working
on
improving
the
actual
results
of
the
search
to
make
sure
that
the
things
that
people
are
looking
for
can
be
easily
found
and
then
forum.
Our
forums
like
is
having
memory,
consumption
problems,
so
I'm
not
sure
exactly
what
the
cause
of
this
is,
but
we're
seeing
out
of
memory
under
two
specific
instances.
One
of
them
is
hitting
preview
on
a
new
forum
topic
and
the
other
one
is
hitting
preview
on
a
comment.
A
So
there's
something
about
our
new
preview
system
that
is
highly
consumptive
of
memory
and
because
the
forum
site
is
on
the
same
server.
As
other
backdrop
properties,
we
tried
increasing
the
memory
limit
on
the
server
within
reason
when
we
still
ran
into
issues
we
just
disabled
the
preview
of
both
comments
and
forum
topics.
In
that
process
we
didn't
realize
there
is
no
option
to
disable
preview
site-wide
for
content,
so
I
had
to
have
found
access
equals
false
the
preview
button.
It
would
be
great
if
dr.
A
B
A
On
top
so
feature
request
came
up
there
too,
but
more
important
than
that.
It
will
be
really
great
if
somebody
who
has
experience
in
memory
profiling
could
volunteer
some
time
to
take
a
look
at
the
forum
site
in
particular
and
figure
out
what
it's
doing
that
may
be
different
from
other
backdrop
sites
and
try
and
catch
these
memory,
consumption
issues
and
fix
them
in
backdrop
core,
because
I'd
imagine
if
our
forums
is
having
these
problems,
probably
a
bunch
of
other
people
who
are
running
back
job
sites
are
going
to
run
to
them.
B
A
C
Okay,
we
had
some
things
happening
this
week.
We
scheduled
the
release
of
one
11.3.
We
didn't
quite
meet
the
schedule
this
week,
but
we
did
get
it
out,
which
is
really
important,
so
one
dot
1103
came
out
just
yesterday,
which
includes
a
huge
bucket
of
fixes,
two
things
that
I
think
are
worth
mentioning.
There
was
a
small
problem
with
the
Installer
that
it's
automatic
detection
between
co-host
and
127.0.0.1.
C
Wasn't
working
correctly
so
that
made
it
so
that
users
of
map
in
particular,
had
to
manually
enter
in
local
hosts
in
order
to
get
back
to
install,
which
was
the
opposite
of
what
we
were
hoping
to
achieve
in
the
1.11
released
to
help
facilitate
a
smoother
installation.
We
accidentally
made
it
a
little
rockier
for
a
short
while
now
that
problem
is
fixed,
so
that
should
make
it
so
that,
no
matter
how
you
have
my
sequel
setup
backdrop
is
likely
to
be
able
to
detect
and
use
the
right
connection.
Information
automatically
now,
let's
say
also
key.
C
C
Transitioning
from
like
hyphens
or
underscores
two
hyphens,
which
is
what
was
happening
before
kind
of
unwanted
class
manipulation.
So
now,
as
long
as
the
class
is
valid,
it
now
passes
through
unmodified.
So
there
are
a
bunch
of
other
it
fixes
as
well
and
one
11.3
we
there's
so
much
I,
don't
know
how
many
issues
that
were
like
20
or
so
that
that's
all
came
at
the
same
time.
So
that
is
now
out.
All
up
streams
are
up
did
except
for
platform
that
one
is
waiting
on
Jeff.
C
Oh,
it
looks
like
he's
found
around
today,
he's
probably
been
occupied
so
but
the
docker
image
is
updated.
Pantheon
has
updated.
The
home
page
link
is
updated,
so
lots
of
up
streams
that
are
all
running
the
new
latest
version
now.
So
that
makes
it
so.
The
items
that
we
didn't
get
done
in
111
3
have
now
been
bumped
into
the
next
book.
Fixed
version
which
is
111
for
this
seems
kind
of
similar
to
you
know
the
items
that
we
had
last
week:
predefined
color
schemes
for
basis
still
no
updates
on
that
one.
That's
issued
3209.
C
We
have
color
schemes
that
are
created
there.
We
said
that
they
all
look
pretty
good
I,
think
we
really
just
kind
of
need
to
move
that
one
forward
we're
hoping
to
pass
it
through
an
accessibility
review
and
a
design
review.
But
these
things
haven't
happened
as
it
is
like
you
know,
it's
really
simple,
just
add
an
array
of
colors
and
we
have
historically
changed
those
in
the
pasts
as
well.
So
I
think.
C
Maybe
we
should
just
proceed
with
you
know
getting
that
one
in
because
the
poor
request
we
have
is
is
working
just
hasn't
gone
through
as
much
kind
of
the
kinds
of
review
that
we
were
looking
for
there,
but
still
butter
did
iterate
than
to
not
do
anything
at
all.
So,
let's
see
also
relate
to
color
module.
C
Safari
is
having
some
troubles
previewing
in
issue
3295,
but
joseph
who
is
here
with
us,
noted
that
his
board
west
on
a
different
issue
32:57,
which
allows
color
fields
to
be
grouped
into
field
sets
so
that
they
can
be
separated
into
like
categories
for
like
header
and
footer,
for
example,
that
pull
requests
that
he
is
create
over.
There
fixes
the
color
preview
issue
in
Safari
I'm,
not
quite
sure
how
those
two
things
are
related,
but
it
is
good
that
one
thing
fixes
another.
C
We
did
find
that
in
32,
95
or
30
32
95,
the
Safari
doesn't
actually
support
color
inputs,
but
the
next
version
does
so
it's
kind
of
one
of
these
things
that
I
think
our
best
approach
is
probably
to
provide
better
graceful
degradation
for
the
time
being
and
then,
as
browsers,
get
updated.
It'll
start
working
in
the
near
future.
B
Just
the
actually
fixed
the
safari
preview
thing,
because
I
actually
saw
an
error
in
Firefox,
basically
like
it,
was
trying
to
call
a
function
on
the
iframe
before
the
iframe
was
fully
loaded
and
it
was
throwing
an
error
in
Firefox,
but
then
like
gracefully
handled
it,
but
in
Safari
it
didn't
throw
an
error
and
just
bails
out
loading.
The
iframe
thanks
Safari.
C
Yeah
I
think
our
best
way
forward
here
would
be
to
untangle
these
issues.
Like
you
know,
3295
is
fixed
by
50
to
57,
but
thirty
to
fifty
seven
has
other
things
like,
and
then
we
found
a
new
issue
at
32
95
regarding
the
fact
that
color
input
is
not
actually
supported,
we
should
start
separating
those
out
like
it
would
be
nicer
if
we
could
just
fix
the
color
preview
issue
in
the
issue.
That
says
that
you
know
it's
for
that
specific
problem,
because
it
sounds
like
that
fix
you
just
described.
This
can
be
self-contained
yeah.
C
C
Let's
see
also,
let's
see
recently,
a
new
version
of
Drupal
7
came
out,
Drupal
761
and
we
have
an
issue
to
track
the
cross
ports
from
the
latest
version
of
Drupal
over
into
backdrop,
and
that
issue
is
33,
70
75,
there's
a
bunch
of
these
that
have
been
had
had
pull
requests
created
and
a
bunch
of
them
that
have
been
marked
are
TBC
and
I,
sadly,
did
not
include
those
in
the
release
this
past
week,
just
because
things
weren't
labeled
in
a
way
that
that
increase
the
visibility,
but
those
things
should
promptly
be
going
through
and
starting
to
get
committed.
D
It's
a
good
thing
that
gideon
gives
you
luck,
the
way
that
we
do
it
we
add
checkboxes.
So
it
gives
you
an
overview
if
you
look
at
the
look
at
how
many
are
done
out
of
the
total
and
what
we
have
been
doing
is
I.
Think
head
was
doing
the
reviews,
so
it's
time
that
we
found
that
something
was
not
applicable.
We
ticked
it
and
it's
time
there
was
a
pull
request
that
was
reviewed.
We
also
take
that.
D
C
D
B
B
C
Pull
requests,
which
is
why
we
have
the
whole
separate
issue:
queue
in
the
first
place:
yeah,
okay,
yeah
that
looks
really
good.
Then
it
looks
like
every
single
one
of
them
has
pull
requests
I'm,
not
sure
if
all
of
them
are
TBC
or
not,
but
lots
of
them
are
so
that
we
can
proceed
in
merging
a
lot
of
those
most.
D
C
Okay,
great
so
lots
of
progress
there,
the
other
issue
that
we've
got
here
in
the
agenda
as
being
one
that
gets
addressed
as
soon
as
possible.
There's
a
there's,
a
problem
with
ckeditor.
When
you
create
a
link
on
an
image,
then
it
causes
a
fatal
error.
Looks
like
current
status.
Looks
like
things
are
coming
along
better,
although
it
looks
like
there's,
some
notices
actually
looks
like
that's,
also
been
addressed
so
current
status
of
that
issue.
3384
is
it
needs
review?
C
Okay,
does
the
key
issues
that
we've
got
for
one
11.4
and
the
status
of
one
11.3
will
close
out
the
111
three
milestone
pretty
imminently.
The
only
thing
that's
left
is
updating
the
upstream
four
platform
and
that's
it
1.12.
We
are
quickly
heading
towards
the
world
of
1.12.
We
have
roughly
a
month
before
it
comes
out,
it
will
be
out
January,
15th,
2019
and
we've
got
a
lot
of
things
that
we
would
like
to
complete
before
January
1st,
which
is
feature
freeze
day.
C
So
issues
of
note
will
run
through
these
there's,
some
of
them
that
haven't
had
updates
in
a
while,
which
is
a
little
sad,
but
then,
as
we
get
to
the
end,
there's
a
lot
of
them
that
are
ready
to
go
so
core
updates
core
updates,
whether
they're
automatic
updates
or
the
UI
for
updating
looks
like
actually
Jen.
You
you've
been
touching
on
this
recently
in
issue
3271.
A
Yes,
if
I
can
find
my
unmute
button,
so
let's
see
what
did
I
do
in
that
issue.
At
this
last
week,
I
think
I
went
through.
There
was
another
issue
that
enabled
automatic
updates,
and
so
what
I
did
is
just
pulled
out
the
part
of
that
issue
that
enabled
the
ability
to
update
it
all
so
before
there
was
like
you
know.
A
What
updates
do
you
want
and
there
was
a
question
about
like
Oh
manual
or
versus
automatic
and
so
I
changed
that
so
it's
a
checkbox
that
says,
allow
manual,
updates
and
then
I
added
another
checkbox
that
says,
allow
automatic
updates
but
I
left
it.
Disabled
and
I
did
that
because
I
didn't
want
people
to
get
confused
between
manual
automatic
manual,
automatic
I
thought
they
saw
the
update
for
manual.
They
might
think
that
was
automatic
and
I
wanted
to
very
explicitly
state
that
we
were
gonna
do
both,
but
that
one
of
them
is
currently
disabled.
A
I
also
chose
the
name
self
updates,
which
I
think
I
could
use
some
feedback
on
to
try
and
indicate
that
backdrop
was
updating
itself
rather
than
his
manual
sounds
like
I'm
gonna
go,
delete
the
files
and
put
them
back,
and
so
I
I
would
like
to
went
back
and
forth
on
what
to
call
these
things,
and
so
it
was
I
would
just
love
more
people
to
give
that
poor
request
to
test
and
see
if
the
language
there
makes
sense.
I
also
did
some
other
clean-up
on
the
on
that
form.
A
I
grouped
things
into
field
sets
to
try
and
make
make
a
little
more
sense
and
I
added
count
estate
so
that
it
wouldn't
ask
for
things
like
the
email
address.
If
you
told
it
not
to
email
anyone,
but
again,
all
of
that
I
think
needs
more
of
you
to
see
if
the
user
experience
is
improved
and
if
the
explanations
of
what
the
check
boxes
do
is
clear,
so
it
should
just
enable
the
user
interface.
So
you
can
click
the
like
apply
for
Update
button.
It
should
make
sure
that
works
too.
A
D
What
one
thing
that
came
up
was
that
even
the
terminology
in
the
help
takes
the
round,
and
the
process
was
mentioning
that
that
the
old
core
Walter
was
being
deleted
and
I
thought
that
maybe
in
the
process,
we
should
just
keep
that
there
and
prompt
the
person
doing
the
maintenance,
like
the
site
administrator
to
manually,
delete
it
themselves
when
they've
verified
that
things
work
as
expected.
So
it
will
be
a
form
of
sort
of
like
keeping
a
backup
until
all
so
that
people
can
read
things.
A
I
think
we
talked
about
that
before
and
then
he
there
were
some
reasons
as
to
why
we
thought
that
wasn't
gonna
work,
because
you
can't
just
have
another
copy.
Of
course,
his
doctor
can
go
and
read
all
those
files
and
you
have
like
multiple
copies
of
modules,
but
we
couldn't
do
something
like
move
it
or
we
could
like
compress
it
or
something,
but
those
would
all
require
that
you
have
sufficient
sufficient
permissions
on
the
machine
in
order
to
do
those
things.
D
Sorry
Jen
what
I've
been
manually
doing
is
like
it's
time
that
core
comes
out:
I,
rename
the
core
folder
to
core
something
something
like
a
version
and
then
I
put
a
new
version
of
core
in
its
place.
I've
never
had
issues.
So
if
there's
a
Inc
on
the
same
top-level
folder,
if
there's
a
second
folder
with
an
old
version
of
core,
it
doesn't
mess
things
up.
D
D
A
C
C
A
A
What
if
your
site
builder,
has
no
access
to
the
codebase
I
just
want
to
make
sure
that
we're
leaving
things
in
the
state
that
will
remain
safe
over
time,
so
I
think
what
the
only
risk
would
be
eating
a
file
space
on
disk
right.
If
we
leave
those
old
files
moving
around
I
feel
like
that's
safer
than
deleting
something
maybe
to
a
point
where
they
can't
get
it
back.
D
It
bad
yeah
out
of
memory,
I
think
it's
it's
like
around
seven
megabytes
compressed
and
like
15
megabytes
unzipped.
It's
compared
to
the
files
that
an
average
side
has
for
images.
That's
that's
very
minimal
yeah,
it's
more
than
there's
more
chances
for
people
to
run
out
of
space
because
there
are
floating
files
literally
yeah,
rather
than
you
know,
old,
old,
copies
of
core.
By
the
time
you.
C
Directly
yeah
yeah
as
a
crazy
idea
you
could,
after
so
you
could
compress
the
old
version
so
put
the
new
version
in
place,
move
the
old
version
out
of
the
way
and
then
once
you're
done
with
that,
then
compress
the
previous
copy
and
then
save
it
as
an
entry
in
the
files
table,
and
then
it
would
literally
show
up
show
up
in
the
managed
files
list.
As
like.
C
A
C
Anyway,
I
think
that's
you
know
something
that
then
we
can
think
about.
I
I
actually
I'm,
not
sure
that
that
needs
to
happen
in
phase
one,
especially
for
the
part
before
it
becomes
automatic
right,
like
the
ability
that
we
have
right
now,
just
like
just
allowing
it
to
update
itself
from
the
easier
interface
probably
doesn't
need
that
capability.
Quite
yet,
especially
if
it's
disabled
by
default,
yeah.
D
The
bit
that
we
back
up
for
archive
you
mean
because
living
living
the
old
core
in
place
as
a
separate
folder.
It
is
probably
a
good
idea
because
deleting
it
is
discretion
destructive,
like
people
cannot
go
back
to
that
or
there's
a
lot
of
manual
work
involved.
So
they
has
to
find
a
previous
release
from
from
github
extracted
and
then
manually
upload
it
to
the
server.
Whereas,
if
we
keep
things
in
place
like
rename
the
core
folder
to
core
something
region,
then
place.
C
Me
yeah
I'm
a
little
bit
hesitant
about
that
because
it
might
leave
craft
that
we
never
would
then
clean
up.
You
know
like
in
a
subsequent
release.
It
would
be
hard
for
us
to
tidy
up
after
ourselves,
because
I
think
we
should
definitely
work
on
the
assumption
that
the
people
are
going
to
be
using
automatic
updates
or
the
people
that
aren't
going
to
be
accessing
their
server
via
FTP
or
SSH.
You
know.
C
B
C
A
C
I
think
that
we
can
do
the
same
thing
where
we
can't
the
capability
to
do
automatic
updates,
but
have
it
not
be
accessible
to
turn
on,
and
these
are
interface
the
same
way.
That
manual
updates
are
possible
right
now,
but
require
a
config
change
to
like
the
JSON
file.
So
there's
no
ability
in
the
user
interface
to
actually
turn
on
so
I
think
we
could
do
the
same
sort
of
thing.
C
A
C
C
A
C
D
C
Yeah
and
that's
the
thing
is
that
right
now,
we're
in
this
position
that
you
know
like
package,
corruption
or
upstream
malicious
behavior
is
not
a
common
problem
for
us.
You
know,
but
the
problem
of
people
aren't
updating
their
sites
fast
enough
is
a
very
real
problem
that
has
affected
us
multiple
times,
and
so,
if
we
can
get
that
solved,
it
would
be
worth
you
know,
delaying
some
other
security
concerns
that
are
less
important
to
us.
I
think
I.
A
Have
a
question
for
the
change
in
the
way
updates
work.
The
manual
updates
right
now,
don't
rename
or
compress
the
core
directory,
and
we
have
an
issue
for
the
user
interface
that
states
what
it
currently
does,
and
we
have
an
issue
for
automatic
updates,
should
I
create
another
issue
to
rename
and
compress
yeah.
A
C
C
D
A
Increasing
for
112,
which
is
making
me
a
little
nervous,
okay,
where
the
line
is,
how
would
you
feel
about
putting
in
the
user
interface
without
any
of
the
other
changes
for
112
yeah?
That's,
okay
and
then
I
can
iterate
and
make
it
like
make
a
backup.
And
then
we
can
degrade
notice.
The
image
files
table
and
oh
yeah.
C
D
D
D
A
C
Yeah
and
so,
and
some
people
might
even
find
that
be
annoying,
you
know,
like
you
especially
updating,
contribute.
There's
you
know
one
archive
for
every
module.
Ten
modules
get
up
to
you
like.
Why
does
all
this
crap
in
my
files
directory
and
then
might
just
delete
it
all
the
time
in
which
case
they
might
decide?
They
don't
want
backups,
and
you
know
theirs
might
be
a
checkbox
for
like
backup
and
you
just
like
it.
Yeah
yeah.
A
C
Well,
this
come
no,
it's
a
different
yeah.
It's
a
new
beat
new
features
for
sure
which
it
means
new
issues.
So,
okay,
yeah,
okay,
let's
see
other
areas
here.
Tags
for
modules
is
issue.
Number
37.
There's
been
some
discussion
on
this
around
what
this
issue
really
gets
us,
but
there's
no
actual
updates.
There,
I
don't
think
as
far
as
implementation.
No.
A
C
Excellent,
let's
see
options
element
in
core
issue:
1005,
there's
no
updates
on
this
one,
although
it
is
still
worth
noting
that
this
one
still
looks
really
good
still
is
neat
and
needs
review
and
is
probably
ready
to
be
transitioned
to
re
TBC.
That's
probably
waiting
on
a
technical
review.
We've
already
had
multiple
confirmations
from
the
front
end
saying
it
looks
great
26:32
is
filled
of
all
file
types
or
file,
bundles,
no
updates
on
that
one
either
they're
still
pull
requests.
C
Let's
see,
config
translation
issue
number
704
we've
had
some
recent
update
and
exciting
progress
on
that,
one,
that
the
pull
request
has
recently
been
updated.
It
it
works,
it
fundamentally
provides
the
new
ap
is
that
we
were
expecting
to
make
it
so
that
config
has
an
officially
sanctioned
way
of
translating
strings
rather
than
you
know.
Just
calling
the
T
function
in
places
stuff
ultimately
does
use
the
T
function,
but
it's
much
more
clear
that
that
is
the
accepted
and
official
way
to
do
translation
and
config.
C
Translatable,
taxonomy
terms,
this
issue,
29
34,
which
is
also
in
our
TBC
currently
and
I'm
gonna,
skip
down
a
little
bit
to
say,
ckeditor,
updating
it
to
the
latest
board
expiration
is
issued
3355,
it's
also
our
TBC
coop.
That's
a
lot
of
our
TV
sees.
Let's
see
this
issue,
495
is
adding
a
dashboard
functionality.
C
A
We
think
we
could
do
to
improve
the
dashboard
long-term
like
adding
new
blocks
or
adding
you
know
redirects
when
you
log
in
or
adding
user
specific
dashboards,
whatever
that
are
sort
of
like
well.
Those
will
come
later,
but
like
just
adding
the
default
config
file,
we
think
well
yeah
and.
C
D
Yeah
and
people
can
clone
the
because
it's
gonna
be
a
layout.
Basically,
they
can
clone
it
and
create
multiple
dashboards
for
different,
because
we
have
the
visibility
things
for
different
users,
for
example.
So
yeah
it
just
happens,
more
visibility,
possibilities
and
it
brings
people
when
when
people
are
getting
they're
gonna
find
something
useful
instead,
instead
of
just
looking
at
the
their
profile
in
thing,
yeah.
C
It
was
the
WordPress
is
better
than
Drupal.
I
was
literally
the
name
of
the
talk
funny
where
how
the
pass
the
leads
to
the
present
is,
and
that's
what's
in
that
in
that
presentation,
Jen
just
went
through
WordPress
and
she
was
like
first
of
all
will
login
and
you
notice
it
puts
us
somewhere
useful,
like
that
was
like
the
very
first
thing
that
was
like
in
the
demo
for
WordPress
is
like
when
you
log
in
it
takes
you
to
something
that
does
something
you
know
as
opposed
to
just
like
your
profile
page.
C
A
E
C
Well,
ok,
well,
yeah.
If
we
think
that
we
can
manage
the
scope,
then
let's
go
for
it
and
of
course,
as
always
like
doesn't
have
to
be
comprehensive,
it's
just
a
starting
point
and
then
we
can
improve
sounds
great.
Ok,
let's
see
that,
does
it
further
1.12
update,
we
don't
have
Jeff
here
for
the
backdrop
for
good
update,
so
that
will
go
into
Q&A.
Then
do
you
guys
have
anything
you.
D
Guys
would
like
to
bring
up
yeah
Nate.
You
mentioned
before
that
the
problem
with
the
Installer
with
localhost
Andy,
and
you
said
that
it
was
fixed
but
I,
see,
issue
32:23
and
I
see
it's
still
not
fixed.
Was
there
anything
that
will
actually
got
merged
for
the
bug
fix
release
because
I
said
so
yeah.
C
C
D
C
C
That
was
actually
the
number
one
thing
I
wanted
to
have
fixed
in
that
really
so
I
didn't
even
realize
that
it
wasn't
think
we
did
wishful
thinking,
noise,
yeah,
okay,
well,
okay,
but
that
gives
us
more
incentive
to
make
another
minor
release
with
some
of
those
cross
ports
from
Drupal
7
that
yep
exactly
what
about
to
say
that
actually
yeah,
because
because
we've
got
actually
have
a
lot
of
things
that
were
kind
of
missed,
you
know
I
mean
that
sort
of
happens
like
in
for
you.
So.
A
I
did
already
do
a
comprehensive
code
review
for
options
element
I'm,
just
looking
through
it
again
now,
but
it
looks
like
herb,
has
addressed
all
of
my
feedback
and
March.
All
of
my
comments
on
the
code
is
resolved,
so
I
don't
know
if
someone
else
wants
to
look
over
it,
but
it
very
good
I
always.