►
From YouTube: Backdrop Weekly June 28
Description
Today’s development agenda: https://tinyurl.com/y7s7y84s
A
Maybe
ok
we're
on
air.
It
is
Thursday
June
28th,
and
this
meeting
is
to
check
in
on
active
development
tasks
for
backpacks
EMS
most
needs
are
for
juice,
but
we'll
get
there
in
a
minute.
First
contributed
project
updates.
We
have
a
Nathan
trim
project
at
Twin,
Cities
triple
camp
Nate
and
I
did
a
live
mods
on
part
of
the
menu
attributes,
module
which
had
actually
been
started
twice
before
and
then
I
think
this
week
someone
else
started
a
fourth
or
it's
module,
I'm
happy
to
announce
that
that
is
now
in
contribs.
A
So
there
are
a
lot
be
at
the
core
of
it.
They
put
the
module
at
least
a
bunch
of
time,
claiming
off
the
mantra
that
we
forked
live
during
the
training
and
put
that
into
the
contributors,
so
I've
reached
out
to
the
person
who
did
the
fourth
court
and
asked
that
they
would
be
interested
in
collaborating
with
me
on
the
third
port.
So
hopefully
we'll
get
everybody
working
together
rather
than
mean
you
do
that
again
and
more
exciting
news
about
that
module.
A
Is
that
was
the
last
one
of
the
top
sixty
eight
modules
in
triple
contribute
at
yet.
So
other
than
things
that
we
are
already
working
on
like
media
in
different
ways,
but
that's
great
because
now
our
beautification
is
going
to
have
only
like
two
red
x's
for
modules
that
don't
exist
and
in
the
top
68.
Something
like
that.
So
thanks
everybody
for
all
of
your
work
on
the
new
attributes
and
I'm
glad
that
we've
got
it
in
context
so
that
everyone
else
needs
it
can
have
it.
B
A
A
Because
that's
how
many
would
have
been
on
my
slide?
I
started
to
talk
with
thee
and
then
I
added,
like
a
couple
more
in
a
couple.
More
I
thought
more
until
they
didn't
fit
anymore,
and
so
it
was
68.
I
keep
going
back
and
trying
to
like
make
my
font
smaller
and
my
columns
different
sizes
and
stuff.
So
maybe
I'll
get
more
I.
Think.
A
Just
you
know
a
number
okay.
Well,
that's
all
oh
wait
website.
We
know
we
need
to
work
on
modulus
themes
and
layouts
on
backups
in
West,
org
I
haven't
had
any
time
to
work
on
that
lately
kind
of
nuts.
Let's
work
on
that
definitely
welcome.
The
things
we
want
to
make
sure
is
to
fix
the
search
so
that
people
can
find
that
which
models,
things
and
Lance
are
available.
A
Things
like
menu
attributes
should
be
easy
for
people
to
find
on
the
site
and
then
also
we
have
some
new
designs
that
can
be
implemented
for
those
pages
that
could
also
use
them
all.
So
anyone
who
wants
to
work
on
that
more
than
welcome
to,
if
is
your
number
442
and
the
backup
CMOS,
thank
you
and
that's
it
for
peripheral
stuff
that
we're
working
on
I
want
to
turn
it
over
to
meet
to
talk
about
backup,
CMS.
B
All
right
all
right,
okay!
Well,
we
normally
start
up
talking
about
the
current
current
release
and
bug
fixes
that
are
going
into
the
next
version,
which
would
be
one
10.2.
The
only
one
that
we
have
for
calling
out
during
this
meeting
is
issue
2904,
which
is
a
problem
with
the
database
credentials.
There
still
hasn't
been
any
update
on
that
that
issue.
We
have
have
code
that
fixes
the
problem,
but
we
need
to
surface
it
in
the
status
report
continues
to
be
pending,
basically
needed
needing
some
additional
work.
B
Let
me
take
a
look
real
quick
here
at
that
list,
so
there's
some
new
items
that
have
been
added
in
there
Gregory
thanks
for
adding
that
one.
Regarding
the
hover
indication
on
selecting
layout
templates
that
has
been
something
is
bothering
me
actually
quite
a
bit
the
way
that
those
statuses
are
shown
when
you're
selecting
a
layout
I
have.
C
Started
a
pull
request
on
that
and
gets
tricky,
so
you
cannot
at
the
same
time
fix
it,
fix
the
the
styling
on
hover
and
when
it
gets
keyboard,
focus
so
yeah
I'll
file,
two
separate
pull
requests.
I'm
asked
some
input
from
Wes.
This
is
the
Guru
there,
but
yeah
it
gets
its
annoying
or
else
I
would
have
already
filed
the
pull
request.
Yeah.
B
It's
tricky.
Let's
see,
there
are
24
current
issues
that
are
in
the
one
that
tended
to
queue
every
single
one
of
them,
with
the
exception
of
that
one
that
we
just
talked
about
has
a
pull
request.
Filed
three
of
them
are
needs
work
and
the
all
of
the
remaining
ones
are
I'm.
Sorry,
three
of
them
need
review
and
all
the
remaining
ones
need
work.
So
there's
a
lot
of
issues
out
there
that
are
of
you
know
substantial
importance
that
all
have
progress
started.
B
It
would
be
really
great
if
we
could
go
through
some
of
those
get
some
of
the
original
authors
that
made
those
four
requests
and
then
have
the
feedback
addressed
and
re-rolled
on
all
of
those
poor
requests.
So
if
you
file
a
pull
request
recently
or
name
and
not-so-rich
link,
please
go
take
a
look
at
it
and
see
if
it
has
been
marked
needs
work
because
there's
an
awful
lot
of
things
that
we
have
a
pull
request
for,
but
then
people
just
didn't
come
back
to
them.
So
that's
it
for
one
about
10.2.
B
There's
a
lot
a
lot
of
things
that
we
are
working
on
all
together
and
as
we
progress
towards
really
probably
some
of
these
things
will
whittle
down
a
little
bit,
but
for
now
we've
got
a
broad
buffet
of
things
to
choose
from,
as
ever
being
we're
done
for
1.11.
The
first
one
is
issue
number
37,
which
is
one
of
our
coldest
open
issues,
which
simply
enables
modules
to
have
tags
or
multiple
categories
in
which
they
are
placed
is
another
way
of
thinking
about
that.
B
We
have
a
an
issue
and
a
poor
request
for
that.
There
aren't
hasn't
been
any
updates
on
it
recently,
but
that
issue
is
currently
the
PO
requests
needs
a
little
bit
work.
There's
some
discussion
and
decision
has
been
reached,
but
we
just
need
to
update
the
PR
to
reflect
the
decision
that
has
been
made.
A
B
B
So
that's
kind
of
turned
that
that's
a
little
bit
of
a
gnarly
issue,
but
there
are
steps
that
we
could
take
to
do
things
iteratively
like
having
a
deal
available
to
authenticated
users
initially,
but
I
think
we
want
to
avoid
anything,
that's
confusing
at
the
same
time.
So
they
already
lots
of
discussion
happening
that
on
contact
module.
Let's
start
at
the
meta
issue
at
30
23
and
then
proceed
to
the
minor
issues
from
that
meta.
D
B
Next
meta
issue
is
1905,
which
is
major
color
module
improvements
and
Joseph
flatnose
here,
and
the
meetinghouse
F
has
been
doing
some
substantial
work
on
color
module.
The
most
recent
work
has
been
in
issue
19:49,
which
previously
was
just
a
cleanup
of
the
existing
color
module
UI,
but
Wes
had
some
substantial
ambitions
around
improving
color
module
and
it
looks
like
Joseph.
You
may
have
picked
up
some
of
those
changes
and
implemented
into
that
issues.
Pull
requests.
B
E
At
the
current
time,
what's
in
that
polar
request
is
converting
the
form
to
use
the
color
input
from
for
html5
and
then
I
also
added
a
polyfill
to
support
color
inputs
in
Internet
Explorer,
and
then
it
also
has
like
a
live
preview.
That
shows
your
actual
site
and
you
can
click
around
inside
of
it
and
see
various
pages
on
your
site
in
the
preview,
and
it
has
the
modified
colors
from
the
forum
with
instead
of
the
colors
from
your
settings.
B
E
E
C
E
E
B
B
E
B
That
seems
pretty
minor,
though
okay,
so
here's
what
we're
looking
at.
Can
you
guys
see
my
screen
now?
Yep,
okay,
and
so
when
I
click
on
the
color
elements,
this
window
pops
up-
and
this
is
Firefox
and
I'm,
guessing
Joseph,
but
this
is
Firefox
doing
this
not
this
is
yeah
normally
Phil,
yeah
yeah.
So.
E
B
E
B
This
is,
this
is
wonderful,
like
an
actual
preview
of
the
actual
site.
This
is
yeah,
Wow
and,
and
the
like
appearance
just
looks
so
much
better.
It
even
occurred
to
me
like
what
kind
of
possibilities
you
get
if
you
remove
the
color
wheel
right,
because
the
color
wheel
was
taking
up
all
of
this
space
and
now
with
it
not
taking
up
so
much
space.
There's
more
opportunities
here
could.
B
Yeah
doing
something
really
similar
to
this
right
yeah
in
the
views
preview,
you
know,
I,
don't
know
you
can
probably
discuss
this
more
in
the
issue.
It
might
be
good
to
remove
the
admin
part,
and
that
made
me
start
thinking
that
maybe
we
should
actually
like
show
the
anonymous
experience
rather
than
the
logged
in
one
okay
in
a
preview
but
yeah
that
get
to
know
all
kinds
of
things.
Well,
this
this
looks
really
promising
very
exciting.
E
B
B
Okay,
great
that
looks
really
fantastic
and
so
exciting.
I
love
the
just
the
UI
updates
just
look
just
tremendously
better.
You
know
that
color
module
interfaces
existed
practically
unchanged
for
almost
like,
probably
more
than
a
decade,
so
that's
it
so
very
exciting.
Well,
what
we
do
about
farm
tastic,
I'm
curious
to
know
what
the
polyfill
looks
like
I.
B
It
almost
makes
me
wonder,
like
we
can
discuss
this
further,
an
issue
too,
but
you
know,
is
a
polyfill
necessary.
Like
you
know,
I,
don't
know,
I
think
we
need
to
take
a
look
at
our
browser
policy
and
see
like
what
our
options
are
there
like
if
a
polyfill
is
unnecessary,
because
you
know,
if
all
that
we
really
need
is
a
you
know,
a
degraded
experience,
you
know
just
the
basic
functionality
where
you
can
enter
in
the
hex
codes.
If
you
don't
support
color
fields,
then
that
might
be
good
enough.
E
E
B
B
Some
things
do
improve
upon
anyway.
It
looks
great
thanks
for
your
work
on
this
Joseph.
If
we
can
push
some
of
these
things
to
fruition,
if,
if
you
feel
like
things,
are
getting
too
challenging
to
fix
entirely
like
scale
back
ambition
just
a
little
bit
and
then
you
know
some
of
these
improvements
like
like,
if
we
could
implement
the
preview
without
the
color
picker,
changes
like
that
would
be
huge,
but
as
it's
all
together
right
now
like
to
keep
pushing
forward
on
it
until
until
you
hit
any
like
robot
this
completely.
C
C
B
D
F
E
G
B
E
B
Okay,
awesome:
what's
can
carry
on
that's
all
very
exciting
and
in
addition
to
just
the
UI
overhaul,
there's
also
the
poor
request
to
colorize
basis,
which
is
it
hasn't
been
merged
in
yet.
But
it's
got
a
pretty
wide
approval
on
making
that
move
forward
so
that
that
also
something
that
we
can
look
forward
to
having
in
and
1.11.
B
A
A
Because
if
you
interpolate,
if
you
navigate
away,
you
lose
your
content
and
backdrop,
you
can
get
your
content
back
by
going
back
to
the
add
forum.
So
it's
not
quite
as
bad,
but
just
in
terms
of
like
do
you
want
to
let
people
get
lost
or
not
in
the
first
place,
and
then
if
he
also
had
a
question
last
week,
which
I'm
not
sure
has
been
entirely
resolved.
A
He
just
wanted
confirmation
on
whether
we
wanted
to
proceed
with
the
tempest
or
idea
earth
we
wanted
to
instead
use
the
save
a
draft
idea
for
the
preview
and
I
said
I
like
the
tempstar
idea,
but
I
think
if
anyone
else
has
other
references,
I
was
so
which
way
to
go
that
might
still
be
open
for
discussion,
so
yeah
I
think
you'd
originally
could
post
that
idea
in
the
comment
thread,
but
it
was
something
that
others
have
been
talking
about
as
well.
Right.
B
Naturally-
and
it
looks
like
if
this
approach
you
know
we
have
it
available,
then
I
think
we
can
move
to
saving
this
draft
later,
possibly
for
the
preview.
But
you
know
I'm,
not
gonna,
I,
don't
I,
don't
think
anybody
should
really
complain
about
having
this
substantial
improvement
based
upon
a
hypothetical
feature
that
we
don't
have
a
timeline
for
it.
Okay,.
B
B
It
needs
feedback,
checkout
issue,
30
62
triumph,
the
sandbox
post,
your
comments
and
feedback
there
on
things
that
could
potentially
be
improved,
looks
like
dark
moments,
mostly
looking
for
looking
for
people
to
try
it
out
and
post
their
opinions,
so
opinions
wanted,
which
is
really
the
easiest
kind
of
feedback
to
get
by
kidding.
Yeah.
B
C
I
will
take
a
look
at
the
figure
as
well,
but
about
the
thing
that
I
mentioned
before,
like
we
have
I'm,
not
sure
if
architecture
leads
they're
the
same
thing,
but
the
the
preview
that
we
have
now
for
color,
this
preview
and
the
preview
of
years.
Are
they
totally
separate
things
or
other
feeling
like
the
underlying
technology?
Is
designed
like
a
pinch
door
thing
they're.
B
All
different
what
yeah
I
mean
they're
all
well,
the
note
preview
is
not
even
really
Ajax
driven,
it's
purely
based
on
like
opening
up
a
new
tab,
and
then
you
see
the
entire
page
of
the
node
in
a
new
window,
the
color
preview
is
an
iframe
and
the
views
preview
is
Ajax.
Requests
that
updates
the
bottom
of
the
page.
B
C
B
The
the
problem
with
using
an
iframe
on
the
page
is
that,
like
we
need
to
figure
out,
each
user
interface
is
different
and
we
need
to
find
a
location
to
put
that
preview
on
the
page
and
I
think
in
the
case
of
this
one,
which
is
a
node
preview,
which
a
node
typically
has
a
page,
it
could
be
a
little
bit
strange.
Looking
at
a
tiny
version
of
the
node
that
had
like
tiny
little
text,
you
know
or
I.
B
A
Different
things
to
like,
in
one
case,
your
previewing
content
that
would
be
in
the
database
and
another
place,
your
previewing
variables.
That
would
be
big
and
would
be,
is
your
Ewing,
it's
equal
theory,
and
so
it's
kind
of
a
even
though
the
it
they're
all
previews
the
mechanisms
for
previewing
whatever
it
is,
are
different
too.
So
I
think
that
you
know
in
the
future.
B
Let's
see
so,
let's
move
on
to
the
next
item,
which
is
adding
an
image
browser
which
is
issue
31
34,
in
which
gram,
72
and
dark
moment
have
been
doing
a
lot
of
really
great
work.
Gregory,
so
you've
been
doing
a
lot
of
great
reviewing
on
that
and
actually
I
haven't
had
time
to
read
over
this
issue,
but
it
looks
like
maybe
you
have.
Could
you
give
us
an
update?
Gregory
is
you're
the
only
one
on
this
call.
I
think
that's
had
a
look
recently
of
reviewing
it
well.
C
Yeah,
the
functionality
in
general
was
like
really
awesome,
the
this
just
minor
things
that
have
been
either
overlooked,
or
just
worth.
Second
priority
like
when
you
double-click
existing
images,
it
switches
by
default
on
the
image
upload
instead
of
the
image
browser
thing,
so
is
finding
things
that
should
be
fixed
and
once
again
it's
real
estate
issues
as
to
where
the
actual
library
of
previews
should
be
placed
like
on
the
side.
C
If
it's
not
that,
if
the
screen
is
narrower
than
it
should
switch
to
be
blended
at
the
bottom
of
that
the
model,
the
dialogue
and
then
also
how
the
previews
of
the
images
themselves,
if
they're,
not
aligned
or
if
they
occupy
a
lot
of
space
and
different
tiles.
So
say
it
looks
a
bit
messy.
But
overall
it's
it's
a
big
improvement.
B
C
B
Yeah,
there
is
some
kind
of
problem
that
happened
with
the
jQuery,
the
last
jQuery
UI
update.
It
seemed
like
you
because
it
worked
prior
to
1.10
coming
out
and
then
afterwards
after
we
did
the
update
it
caused
a
jet
query,
error
or
some
kind.
So
anyway,
that
may
have
some
larger
problem.
This
I
would.
C
B
Okay,
yeah,
that's
still
still
really
really
great
work,
they're
making
it
so
it's
we
have
a
much
much
improved
way
of
reusing
images.
Actually,
this
is
kind
of
the
only
way
to
reuse
images
at
the
moment
like
you
can
hack
in
ways
to
relive
reuse
images,
but
at
this
point,
there's
no
out-of-the-box
capability
to
do
so,
and
this
would
would
empower
that
which
is
great.
The.
C
Other
minor
sort
of
like
usability
is
like
when
you
select
an
image.
It
doesn't
show
you
that
it
doesn't
indicate
that
it's
selected
and
having
in
mind
I
I,
remember
if
it
was
a
screenshot
or
a
video
about
the
respective
Drupal
mode
module
when
you
selecting
I,
think
would
have
been
one
distribution,
maybe
lightning.
When
you
select
images
like
there's
an
overlay
of
a
tick
box.
That
shows
you
that
this
is
what
is
selected,
and
this
reminded
me
of
the
way
that
we,
the
selects
thing
for
that
for
the
layout
template
the
files.
B
B
B
Okay,
so
design
design
folks
definitely
needed
in
this
particular
area
design
and
even
more
important.
The
UX
folks
need
needed.
Let's
move
on
next
up
is
automatic
updates,
which
is
a
big
meta
issue
at
issue.
2018
we've
put
this
into
a
number
of
smaller
issues,
two
of
which
are
in
a
state
that
needs
review.
B
One
of
them
is
allow
core
updates,
via
the
user
interface,
which
is
issued,
3105
Jeff
made
that
pull
request
a
while
back
is
it's
difficult
to
test,
but
the
functionality
seems
like
it's:
it's
all
there
I
think
Gregory
found
it
an
issue
or
two
that
managed
to
break
the
automatic
updates.
Really
I,
don't
think
it's
been
updated
since
then,
so
this
actually
may
really
be
need
to
work
better
than
it
needs
review,
but
that
issue
makes
it
so
that
you
can
update
backdrop
core
via
the
user
interface.
B
In
the
same
way,
you
can
update
that
you
can
update,
contributes
I,
think
that
problem
Gregory
ran
into
was
a
combination
of
when
you
try
to
update
core
and
authorized
dot.
Php
needs
to
be
used,
which
is
when
backdrop
can't
write
to
the
file
system
directly.
It
has
to
use
authorized
PHP
to
basically
act
as
an
FTP
user
to
replace
the
files
so
yeah
that
that
definitely
needs
needs
to
be
addressed.
B
It's
also
kind
of
kind
of
interesting,
noting
that
we
have
a
older
issue
that
says:
I
don't
have
the
number,
but
it's
used
authorized
PHP
for
the
Installer
project,
because
right
now,
if
backdrop
came
right
to
the
file
system
for
the
Installer
module,
it
just
says:
I'm
sorry
I
can't
install.
But
if
you
do
it
for
updating
a
module,
then
it
uses
authorize,
dot,
PHP
and
ask
for
new
credentials
and
then
can
indeed
update
modules.
B
So
we
need
to
kind
of
go
one
way
or
the
other
is
like
either
use
authorize
that
PHP
for
everything
or
remove,
authorize,
dot,
PHP
and
just
say
backdrop
always
has
to
be
able
to
write
to
the
file
system
which,
in
the
case
of
automatic
updates,
is
going
to
be
required.
Like
we
I
mean
it
has
to
be
able
to
write
to
the
file
system
and
storing
your
username
and
password
permanently
for
the
FTP
use.
B
There
would
be
a
very
poor
idea
and
it
would
be
better
to
be
just
have
the
files
directory
or
the
the
PHP
directory
be
writable.
I
would
think,
rather
than
storing
your
password
for
the
entire
SSH
or
FTP
account
on
the
server
so
anyway
that
that
problem
might
go
away
if
we
were
to
just
remove
authorize
stuff.
Yet
to
be
entirely
and
just
say,
you
know,
you
have
to
be
able
to
write
to
the
file
system.
B
D
The
top
I'll
go
ahead.
I
have
a
question
to
JoVE,
because
in
the
issue
we
had
difficulties
to
test
an
improvement
of
theory
of
a
PR,
because
there
in
the
PR
was
unwanted
fire
as
WP
file,
and
it
made
it
mod
district
difficult
to
test
the
further
progress
of
the
PR
and
just
I
wanted
to
ask
you.
If
you
think
you
can
figure
out
how
to
remove
this
swp
part
from
the
patch,
so
that
we
can
further
everything.
G
I
did
so
far,
it
still
runs
through
the
iteration
that
had
it
and
it
first
adds
it
and
then
removes
it.
I
don't
know
if
that's
because
of
it
being
a
github
patch,
but
the
only
other
thing
I
can
think
of
mr2
reroll.
It
mm-hmm
and
I
haven't
had
time
to
do
that.
But
that's
it
that's
the
thing
that
could
be
done.
Yeah.
D
D
D
C
B
Great
so
other
items
and
automatic
updates
issue
25:55,
which
is
just
moving
the
profiles
directory
from
the
root
underneath
the
core
profiles
directory
we've
mentioned
this
past
couple
of
weeks.
It
it's
still
kind
of
just
stuck
there.
It
needs
review
and
I
think
we've
kind
of
reached
consensus
on
whether
or
not
we
should
make
a
root
empty
profiles
directory
as
well.
B
Okay,
more
issues:
okay,
the
last
three
issues
looks
like
Thank,
You
Jennifer,
ranging
with
the
agenda.
In
this
way,
the
last
three
issues
we
don't
haven't
had
any
updates
so
I'll
just
briefly
mention
that
we're
working
on
them,
but
not
recap,
better
workflow
handling
from
making
it.
So
that's
the
status
of
whether
or
not
something
has
had
draft
or
scheduled
or
published,
is
issue.
B
1475,
no
updates,
since
last
week,
better
statistics
tracking,
which
is
separating
the
tracking
of
well
as
a
lot
of
a
lot
of
different
components,
but
making
it
that
we
can
get
better
statistics
about
the
way
people
are
using
their
backdrop
websites.
This
issue
285
no
update
since
last
week
and
making
it
so
that
streams
were
thinkin
fig
files
are
exposed
properly
or
config
translation,
just
in
general,
as
issue
704
and
no
update.
Since
last
week,
there
either
there's
a
bucket
of
other
issues
that
are
in
the
github
issue
tracker
for
1.11.
B
B
Yeah
so
yeah
we
discussed
it
last
week
during
the
UX,
meaning
that
Wes
is
but
taking
a
stab
at
the
view
see
why
I'm
not
even
I'm,
not
even
sure,
if
that's
like
realistic
for
1.11
I,
think
it's
great,
that
that
he's
putting
together
like
prototypes
and
concepts
but
I'm,
not
even
sure
that
we're
anywhere
near
like
trying
to
attempt
an
implementation
there,
so
I
think
maybe
for
one
no
11.
We
should
hold
off
until
we
have
a
clear,
a
more
clear
plan
to
actually
move
that
towards
implementation.
G
Yeah
so
I
think
it
was
last
week
I
mentioned
that
we
had
some
additional
communications
with
the
partner,
which
is
black
lives
matter
Memphis,
and
that
came
to
some
issues
in
the
queue.
So,
if
you're
interested
in
participating,
there's
new
fresh
issues
that
anybody
that
is
interested
can
can
grab
and
take
a
look
at
and
see
if
you
want
to
participate.
G
D
D
Not
a
lot
of
issues
who
asked
for
a
token
support
in
the
global
custom
text
field
of
view
and
in
Drupal
a
lot
of
people
asked
for
it,
but
never
it
was
never
discussed
seriously
to
implemented
and
I
thought
it.
Maybe
would
be
a
good
idea
to
implement
it
in
backdrop
and
because
it
could
be
very
useful
for
a
lot
of
use
cases
and
but
I
can't
I
have
no
idea
if
it's
easy
to
implement
or
not.
B
D
C
It
maybe
to
gregory,
because
yeah
so
you're
displaying
a
node
and
then
on
the
sidebar.
You
have
a
block
that
is
supposed
to
provide
a
permalink,
say,
sort
of
say,
but
a
citation
trembling
for
this
specific
node
that
you
viewing.
So
this
needs
to
include
a
small
short
description.
The
path
to
the
node,
which
are
easy
to
achieve
and
last
should
be
today
like
now
the
day,
so
it's
sort
of
like
a
family
sort
of
like
citation
standard
thing
that
it
enticed
to
other
things
referring
to
that
allocate
yeah.
D
C
B
But
it
would
be
good
global
field
like
you.
Can
there
are
global
fields
for
other
other
things,
I'm
trying
to
think
of
it.
Trying
to
give
an
example
like
some
of
them
are
just
like.
You
know,
just
spit
up
plain
text,
but
we
could
have
a
global
field
for
it.
Just
like
just
today's
date
would
be
a
simple
way.
Also.
B
B
However,
I
just
looked
at
the
implementation
and
there's
only
filters
set
up,
so
you
can
filter
by
when
a
user
last
looked
at
a
piece
of
content,
but
there's
no
field
for
when
you
know
you
last
looked
at
a
piece
of
content,
so
that
would
also
work
as
a
as
an
alternative,
and
then
you
could
actually
usefully
like
make
a
listing
like
a
larger
listing,
saying
the
date
that
you
last
looked
at
every
piece
of
content
and
showed
the
date.
Next
to
each
time.
You
looked
at
something
which,
which
could
be
very
useful,
mm-hm.
D
But
I
think
the
toking
approach
for
the
global
context,
field
and
use
could
also
solve
a
lot
of
other
use
cases
so
because
the
current
date
is
maybe
like
a
quite
special
use
case.
But
there
are
a
lot
of
other
totems
which
could
be
useful
to
display
in
a
view
or
the
site
information,
so
name
of
a
site
and
all
these
January
tokens.
D
The
information
is
there,
but
it's
not
in
views,
and
we
have
other
places
like
URL
patterns,
where
you
can
just
pick
this
tokens
and
use
it
and
why?
Why
not
use
in
the
in
this
field?
Because
it's
it's
also
strange
because
Andrew
I
don't
know
how
it's
in
vector
and
backdrop.
You
can
use
these
tokens
in
the
header
and
in
the
footer
of
the
view,
but
not
in
the
fields.
Oh,
that's
very
strange.
D
B
A
Theoretically
is
for
my
experience
of
adding
tokens
to
things
it's
not
very
hard
to
add
token
something
so
I,
don't
understand
why
we
can
add
to
them
so
a
global
taxi,
LT
but
I
know
that
uses
its
own
tokens
differently
and
that
allows
it
to
pull
stuff
like
out
of
the
view
that
aren't
available
to
the
rest
of
the
token
system.
But
I
don't
know
like
I
can't
imagine
the
reason
why
we
couldn't
do
both
unless
they
can
click
through
each
other.
A
B
Yeah
we
did
that
just
recently
in
1.10,
we
added
token
support
to
the
maintenance
message,
which
was
again
for
consistency,
because
previously
there
was
only
one
replacement
that
was
possible,
and
that
was
the
site
name,
and
so
we
we
changed
that
to
use
you
know
the
site
name
token,
instead
of
admin
site
name,
and
so
this
would
be
really
similar
change.
Basically,
do
it
doing
the
same
thing
that
I'd
like
to
do.
B
D
C
D
C
B
Okay,
all
right
anything
else:
okay!
Well,
we
are
pushing
the
hour-long
mark.
Thank
you,
everybody
for
joining
us
today
and
sticking
with
us
through
this
long
meeting,
lots
of
very
exciting
things
still
progressing,
maybe
not
on
all
fronts
but
on
many
fronts.
So
thank
you,
everybody
for
during
the
meeting
and
thank
you
everybody
for
watching
and
we'll
see
you
guys
online
New.