►
Description
Today’s development agenda: http://bit.ly/2fcjT7S
C
Thanks
it
is
Wednesday,
no,
it's
Thursday,
November
third,
saying
sorry:
honey.
We're
going
to
the
meeting.
Let's
see,
I,
don't
think
we
have
any
updates
from
pnc
this
week.
Unless
anyone
else
is
anything
want
to
add.
Let's
we
can
start
on
infrastructure
Nate
that
isn't
a
meeting.
That's
running
long
right
now,
but
let's
see
if
we
have
any
follow.
Ups
from
the
backdrop,
pantheon
saga,
no,
no
we're
we're
we're
out
of
that
Jeff,
but
you
probably
never
an
idea.
I.
D
Got
a
response
from
someone
I
guess
senior
at
Pantheon
his
pre
detailed
response.
I
read
it.
I
didn't
have
a
chance
to
respond,
but
basically
we
need
to
just
tell
them
our
use
case
in
will
go
after
and
then
we
kind
of
two
courses
of
action
we
can
file
a
feature
request
would
miss
Pantheon,
which
I
guess
takes
a
while
and
there's
no
guarantee
that
it
would
be
approved.
But
that
might
be
a
good
thing
to
keep
in
our
back
pocket
anyways
to
see.
D
Although
I
need
more
testing
on
that,
particularly
in
going
from
from
a
the
dev
environment
to
the
test
environment,
I
don't
have
any
live
sites
on
pink
none,
but
if
we
get
that
far
I
think
theoretically,
it's
going
to
work
out
since
codes
going
to
move
up
to
test,
but
files
are
going
to
pull
down
from
life.
If
you
choose
to
even
poem
at
all,
and
then
you
can
just
do
an
import
which
should
pick
up
your
state's
stop
from
the
code
and
go
to
the
live.
D
D
C
D
Their
third
but
all
kinds
of
weirdness
that
has
occurred
in
Drupal
handing
backdrop
depending
on,
if
you're,
if
and
when,
you're
being
careful
and
how
many
people
you're
working
with
yeah,
there's
so
there's
some
human
workflow
stuff
that
you
have
to
agree
to.
Also,
if
you
know,
if
you
have
it
two
or
three
or
five
person
team
yeah
like
you
in
Drupal,
we
installed
some
modules
and
that
and
the
enabling
of
the
modules
is
starting
to
fig
and
then
so.
We
enabled
the
modules
manually
on
our
dev
site.
Then
we
push
it
up.
D
D
D
Exactly
there
there's
there's
some
workflow
stuff
that
you
have
to
be
the
advantage
that
drupal
has
is.
They
ended
up
with
the
active
storage
being
in
the
database,
so
they
don't
have
the
problem
of
worrying
about
where
and
if
the
active
storage
is
version
than
that,
because
it's
in
the
database,
so
they,
the
only
thing
that's
virgin-
is
the
equivalent
of
our
staging.
D
C
C
They
have
a
feature
request
for
the
Pantheon
yeah
mol
file
to
add
a
new
location
of
the
files
directory,
which
all
I
think
unblock
us
a
little
bit
so
right
now,
backup
sites
have
like
a
custom
implementation
of
where
the
files
directory
is,
but
if
they
can,
if
there
can
be
a
defined
location
of
where
the
file
surgery
is,
that
means
that
they
will
have
the
ability
to
make
wherever
that
is
writable.
So
there
might
then,
after
that,
is
done.
C
The
common
option
for
creating
another
writable
directory
somewhere
for
something
for
whatever
purpose,
so
I
think
we
should
wait
and
see
what
happens
down.
The
road
and
I
think,
like
we've,
said
everything
out
loud
that
the
process
is,
if
you're
on
Pam,
on
the
only
safe
way
to
move
your
config
around
his
toc
user
interface,
which
is
fine,
I,
was
kind
of
hoping.
We
would
be
able
to
find
some
like
hockey
thing.
C
We
could
do
with
this
at
things
I
PHP
file
that
would
make
the
Pantheon
you
I
just
kind
of
work,
but
it
looks
like
that's
not
really.
Gonna
beat
up
just
yet
yeah
I,
think
I
know
you
and
Wes
are
working
on
pantheon
figuring
out,
Pantheon
are
also
figuring
out
Calla
box,
and
why
study
was
interested
in
writing
up
some
documentation
and
kind
of
how
to
do
that.
Best
practices,
I
think,
would
be
great
just
in
general,
once
we
get
figured
out.
C
Thank
you
guys
for
powering
through
on
that
also,
it
sounds
like
the
like
drush
eight
support
stuff
we're
working
on.
It's
not
also
blocked
by
switching
like
the
same
kind
of
issues,
we're
having
with
the
like
waiting
on
the
Pantheon
IAM
will
be
fully
supported
so
that
we
can
make
like
I.
Don't
know
I
feel
like
there's
a
whole
bunch
of
stuff,
that's
kind
of
blocked
on
what
pantheons
working
on,
including
getting
dressed,
support
their
the.
D
Dashboard
functionality
doesn't
work
when
we
reverted
to
get
back
to
the
state
de
rien
that
you
put
install
backups
likes
and
that
stuff
people
can
use
rush
on
pantheon.
They
have
to
use
a
site.
Local
drush,
which
is
I,
think
documented
in
the
pantheon
docs
and
I
wrote
the
blog
post
there
on
backdrop,
CMS.
That
shows
you
how
to
do
that.
So
we
don't
have
it
out
of
the
box
when
they
spin
up
backdrop
of
somebody
wants
to
follow
those
instructions.
D
C
C
But
it
didn't
like
I
couldn't,
like
I,
had
to
use
terminus
in
order
to
get
that
version.
Marketing,
but
I
think
that's
right,
I,
don't
remember,
but
anyway
it
sounds
like
there's
been
a
ton
of
work
done
on
Yancy
and
ration
catalogs
lately
and
I
just
want
to
thank
both
of
you
for
pitching
and
helping
us
figure
out
how
to
get
that
going
so
great
great
work,
guys
next
on
the
agenda
is
backed
up
website.
C
I,
don't
think,
there's
been
any
progress
on
this
since
last
week
we
have
a
content,
type
called
showcase.
So
if
anyone
has
backed
up
sites,
they
want
to
show
off,
you
can
put
them
up
there.
We
need
to
have
words
written
with
them,
not
just
pictures
in
order
for
the
showcase
section
of
the
site
to
be
super,
compelling
I
know:
I
am
guilty
of
just
putting
pictures
of
sites
up
there.
C
I
have
to
go
back
and
write
some
content
and
then,
as
soon
as
we
get
a
handful
of
those,
we
should
launch
the
showcase
section.
I
know
for
right:
now
we
have
a
page
up
at
slashed.
Showcase
with
just
is
like
a
list
of
the
nodes,
that'll
turn
into
a
view,
and
we
have
designs
I'll
turn
into
like
a
landing
page
and
we
have
designs
for
that.
They
just
haven't
been
implemented
yet
so
that's
knit
next
and
last
part
of
that
documentation,
Tom
you're
here.
B
Going
through
wasted
some
time
looking
at
trying
to
get
color
blocks
to
work,
and
then
pilon
just
gave
up
on
that
I'm
up
through
layouts
right
now
and
I'm
on
add-ons
for
modules.
Things
play
out
as
far
as
user
guide
and
stuff,
one
of
the
questions
I
had
was
regarding
to
deep
dives
and
trying
to
keep
those
consistent.
Not
at
sub
topics
like
thunder.
Creating
content
did
we
want
to
keep
those
in
order?
What
was
the
thought
behind
doing
those
the
subconscious.
C
C
What
I
was
thinking
is
that
we
want
to
make
the
the
top-level
pages
the
not
deep
dive
pages
as
unintimidating
as
possible,
so
easy,
just
kind
of
read
the
thing
and
cover
the
most
common
use
cases,
and
when
we
get
to
something
crazy,
like
using
book
module
or
a
more
complicated
example,
we
want
that
too
so
exist
in
in
the
documentation.
But
we
don't
want
it
to
be
so
intimidating
that
when
someone
lands
on
the
front
page,
they
see
all
of
it.
C
C
As
far
as
how
those
are
organized,
I
would
say,
if
there's
a
way
to
keep
them
in
order,
that's
good
if
it
becomes
difficult
as
long
as
people
can
get
to
the
deep
dive
page
from
the
parent
page,
that's
fine,
whether
it's
a
link
in
the
texts
like
see
more
on
this
and
there's
a
link
or
if
it
appears
in
the
menu.
That's
also
fine
I
would
defer
to
you
guys
to
try
and
figure
out
the
best
way
to
organize
all
of
information.
I
just
didn't
want
to
lose
any
of
it.
B
C
I
made
we
might
be
able
to
fix
that
with
the
next
button
like
if
the
next
button
only
went
forward
and
didn't
go
down.
That
would
work
okay.
How
many
levels
are
there
like
like?
Is
it
we
stopped
at
the
second
level
or
like
I,
don't
want
to
make
sure
I
don't
want
to
accidentally
miss
like
an
entire
section,
there's
only
two
levels
for
too
long?
Okay?
So
that's
that's
fine.
We
can
definitely
do
that.
A
You
something
related
in
drupal.org
I
think
they
have
times
for
documentation,
beginner
advanced
intermediate
that
helps
so
before
the
patient
starts.
They.
They
know
what
to
expect.
So
so
if
they
see
something,
that's
tagged
as
as
advanced,
maybe
they
just
skip
it
instead
of
start
reading
and
getting
frustrated,
that's.
C
A
good
idea,
I
know
we
have
one
I
think
we
only
have
one
tag
on
documentation
right
now
and
it's
whether
it's
like
in
progress
are
completed.
We
should
add
another
one
for
what
level
for
right
now.
If
we
only
have
two,
maybe
we
should
just
have
like
introduction
in
advance
and
then,
if
we
start
getting
more
pages
in
here
in
the
future,
we
can
add
additional
levels
as
necessary
to
stop
rock
sound
reasonable
to
you
guys.
C
C
B
How
quickly
a
landing
page
necessarily
this
does
link
to
it
out
of
the
side,
menu
and
and
really
I'd
say
by
the
fun
monday.
It
should
be
able
to
put
it
up
and
matter
how
I
mean
everything:
that's
there
makes
perfect
sense,
and
it's
Lord
correctly,
some,
even
if
we're
in
the
midst
of
changing
as
we
go,
there's
nothing
there,
that's
shown
as
incomplete.
Ok,
that's
great.
C
C
C
That
says,
add
some
text
and
heroes,
but
the
rest
of
it
is
pretty
close,
but
I
would
love
I
just
kind
of
nearer
the
whole
thing
and
then
firefox
ate
the
post,
and
so
then
I
had
him
put
just
the
images
back
up,
because
I
need
to
link
those
into
the
newsletter.
So
now
we
just
have
to
flush
out
the
text
here,
a
little
bit.
So
if
anyone
has
anything,
they
want
to
add
to
this
post
feel
free
edit.
It
will
get
a
publish,
probably
there
tomorrow,.
A
I
mean
generally
started.
I
also
started
writing
one.
Sorry
I
didn't
communicate
that
maybe
double
effort
there,
but
what
stopped
me
and
then
I
got
lost,
was
I,
wasn't
sure
if
I
right
or
mentioned
151,
because
what
would
be
the
dog
post
about,
because
what
125
that
one
was
already
out
so
is
it
1
dot?
500
is
out
for
1
25.
The
one
is
out
if.
C
C
So
right
now
under
important
bug
fixes
the
one
thing
that
were
not
quite
committed
to
is
our
fix
for
the
full
bleed
hero
image.
We
have
four
solutions
for
pull
requests
in
the
queue
one
of
them.
I
think
Wes
has
agreed
to
in
theory,
but
I'm
not
sure
I've
had
a
chance
to
review
the
code,
which
is
creating
a
new
theme
hook,
suggestion
for
the
front
page
when
it
is
using
the
one
column,
Boxton
layout
overriding
that
one
template
in
basis
in
making
the
hero
region
for
woods.
C
Now
that
we
have
temples,
oh
okay,
back
up
1.6,
we
have
added
a
ton
of
things
to
the
list
that
we
want
to
do
a
backed-up
1.6,
I'm
not
sure
we're
going
to
be
able
to
do
all
of
them
just
to
want
run
through
them
really
quickly.
Some
of
the
things
we
shouldn't
talk
about
in
depth
that
we
want
to
do
is:
let's
see
improving
the
rich
text
editor.
We
always
want
to
improve
that.
C
So
if
anyone
finds
any
issues
with
it
in
this
release
cycle,
we
can
work
on
those
and
get
them
in
in
16
trying
to
figure
out
page
title
tabs
and
action
links.
I
think
we
have
a
theoretical
solution
for
those
right
now,
they're
placed
on
the
layouts.
We
could
instead
create
or
in
addition
create
blocks,
and
if
somebody
placed
a
block
one
of
those
items,
we
wouldn't
show
the
variable
in
the
layout
file
that
will
be
backwards,
compatible
way
to
add
those
items
to
the
page
block,
copy
and
region
copy.
C
This
is
a
issue
that
was
introduced
or
became
important
in
back
up
1.5
now
that
we
ship
with
two
layouts
out
of
the
box
for
the
front
page
and
people
are
going
to
notice
really
quick
if
they
change
menu
settings
on
one
they're,
not
changing
menu
setting
from
the
other,
because
those
menu
settings
are
not
recycled
or
inherited
or
copied.
They
are
two
distinct
placements,
but
we
can
come
up
with
a
way
to
make
one
of
those
a
copy,
the
other
one
then
changing
in
one
place
will
change
all
of
it.
C
So
we
can
find
a
way
to
copy
a
block
or
even
better
copy,
an
entire
region
that
would
solve
that
problem
in
any
view
modes.
This
is
a
no-brainer
everybody
loves
in
video
modes.
There's
a
contributor
pool
seven.
We
just
need
to
take
a
look
at
that
and
figure
out
what
that
would
look
like
if
added
too
poor
for
backdrop
file
entity
solution,
some
kind
of
media
type
module.
C
We
want
to
take
the
first
step
towards
media
in
1.6,
which
is
just
building
these
or
interface
little
allow
people
to
access
and
edit
and
delete
their
files
right
now,
there's
a
sort
of
a
major
bug
in
that.
If
you
add
a
block
with
an
image,
then
it
deleted,
you
delete
the
block,
you
don't
ever
double
damage,
so
people
can
still
access
that
image
after
the
fact.
So
we
need
to
fix
that
things.
C
We
might
want
to
talk
about
in
more
detail,
most
important
things
on
here:
adding
NN
v
reference
module,
decor,
Mike,
I,
don't
know
if
you
have
any
update
since
last
week,
I
think.
Last
week
we
were
at
a
point
where
we
needed
more
testing,
so
we
have
a
module
that
you
can
install
and
run
on
your
sites.
I,
don't
know
if
it
has
got
chance
to
test
it,
then
it.
F
Looks
like
it
looks
like
clonise
got
a
chance
to
to
test
it
or
at
least
go
into
the
issue,
queue
and
talk
about
it
and
I'm
not
sure
if
anyone
else
has
master
tested
out.
Obviously,
Kono's
found
the
problem
of
the
the
the
circular
references
right
now.
So
if
you
have
an
entity
reference,
an
entity
that
references
the
additional
regional
entity
and
try
to
render
them
the
system
gets
quickly
bogged
down,
so
we
need
to
figure
out
a
way
to
detect
circular
references
with
the
reference
field.
F
I
haven't
had
a
chance
to
figure
out
a
way
to
do
that.
Yet
so,
if
anyone
has
any
suggestions
on
just
where
in
the
rendering
pipeline
we'd
want
to
try
to
figure
out
if
a
reference
like
we
might
want
to
just
have
it
so
a
reference
field
will
check
the
entity
is
rendering
and
disable
any
other
reference
fields
or
maybe
have
it
when
you
choose
which
View
mode
to
render
not
let
it
choose
view
modes
that
have
an
entity
reference
displayed
or
something
I'm,
not
sure.
C
Okay,
I
have
a
example
for
Drupal
7.
It
might
not
be
relevant
and
where
I
put
a
recursion,
stop
in
a
rendering
note
that
rendered
an
entity
that
was
the
entity
I
originally
started
in,
which
might
be
useful.
It
won't
help
you
to
find
where,
in
the
render.
What
might
I
don't
know
how
similar
your
rendering
is
so
triple
sevens
and
be
rendering,
but.
F
F
F
A
A
F
F
They
have
a
widget
that
selects
items
when
you
submit
the
form
just
based
on
name
because
taxonomy
taxonomy
entities,
unlike
other
entities,
have
to
have
unique
names,
whereas
so
it's
slightly
different
that
and
the
widget
lets
you.
The
widget
currently
lets
you
type
in
New
create
new
taxonomy
terms
just
by
typing
them
into
the
field.
So
like
this
isn't
stuff
that
happens.
We.
F
If
we
want
build
that
into
the
entity,
reference
widget,
that
might
be
the
case,
but
I'm
not
sure
how
much
that
functionality
is
useful
for
non
taxonomy
uses
like
if
we
wanted
to
have
like
you
know,
do
we
want
to
have
it
so,
like
you
know,
if
you
type
a
node
name
into
an
entity
reference
field
and
doesn't
exist,
it
creates
a
note
for
that.
I
mean
I,
guess
that's
that's
something
to
look
at
whatever.
A
F
I,
don't
know
how
they
handle
it.
I
haven't
actually
used
Texada
Drupal
8,
yet,
but
I
I
have
a
client,
so
I
do
is
do
using
that.
So
I
could
take
a
look
at
how
it
works
on
that
okay,
I'll.
Take
a
look
at
that
look.
Quite
frankly,
I
would
just
be
let's
I'm,
not
in
a
rush
to
replace
the
taxonomy
reference
field,
just
because
it
does
have
the
additional
functionality
in
it.
I'd
rather
test
sort
of
the
initial
reference
field,
as
is
before
trying
to
you,
know,
move
more
more
responsibility
onto
it.
C
Anything
that
sounds
good,
I
think
I,
there's
probably
also
a
way
that
we
could
provide
an
additional
widget
that
maybe
remains
part
of
taxonomy
module
or
something
that
can
figure
out
if
a
taxonomy
enna
d
is
referenced
and
only
then
become
available,
but
I
don't
know
for
an
upgrade
path
like
I.
Don't
think
we
should
introduce
an
upgrade
path,
room
that
effect
on
me
to
reference
fields
to
the
entity,
reference
field
after
it
goes
into
court.
So
we
either.
C
F
E
Oh
I'd
tack
onto
that
too,
so
I
looked
at
reference
and
the
issue
queue
over
the
week,
which
is
awesome.
Thanks,
Mike
very
worked
there
I
applied
there,
you
had
a
couple
of
core
requests:
one
was
to
fix
the
return
arguments
from
the
file
inity,
and
that
was
a
trivial
one.
So
I
got
that
fixed
the
make
files
act
the
same
way
as
everything
else.
As
far
as
running
the
return
value
through
the
URL
function,
I
ran
into
a
number
of
snags.
E
E
F
E
We
don't
have
a
Travis
file
anymore,
but
you
you
can
run
tests
locally,
not
through
the
UI
but
through
the
shell
scripts,
and
if
you
attack
on
the
great
documentation
in
the
run
tests
that
Sh
script
and
if
you
tack
on
the
like
dash
dash
cashed,
my
dash
dash
cash
flag.
It
speeds
up
test
running
by
like
20
times.
If
you
run
the
entire
court
suite.
E
So
I
would,
I
would
say,
if
you
need
to
run
tests
locally,
do
what
the
test
spot
does
and
use
the
testing
scripts
with
a
high
level
of
concurrency
and
end
with
the
cash
flag
and
that
that
that's
it's
not
inside
deal
because
you
still
under
run
them
manually.
But
it
shortens
the
test
run
time
from
being
like
an
hour
to
like
five
minutes
even
on
local.
So,
okay,.
F
E
Actually
he
Rogalla
I
know
I
was
thinking
you
might
be
able
to
look
at
a
log
from
the
test
pot
and
get
the
command
out
of
there,
but
it
looks
like
it
doesn't
show
you
two
commands
you
here:
okay,
anyway,
yeah
run
run
that
just
run
that
shell
script
from
the
command
line,
and
then
it
will
give
you
documentation
on
how
to
actually
execute
it.
Okay,.
D
F
F
C
C
C
It's
it's
something.
That's
bothered
me
I,
think
since
the
Drupal
6,
the
change,
the
menu
and
everything
got
all
weird
and
then
they're
all
these
your
menu,
breadcrumb
module
solutions
came
out
and
yeah.
We
should
figure
that
out,
there's
issue
number
5
23
minutes
in
her
student
reading
up
and
helping
them,
and
then
the
other
biggie
for
16
is
adding
a
system
of
page
lists
nodes.
So
how
do
you
create
a
thing
that
has
lots
of
fields
in
his
version
and
has
author
information,
but
does
not
have
a
URL
to
it?
C
We
have
a
lot
of
solutions
for
this
in
Drupal
we
have
a
Joel
I'll
grab
it
hold.
It
will
just
make
the
path
return
like
a
404.
If
you
try
and
go
to
it
or
redirect
you
somewhere
else
or
whatever
else,
there's
a
module
called
beam.
It
creates
a
block.
It's
an
entity,
there's
an
entity,
construction
kit
solution
will
let
you
build
whatever
kind
of
energies
you
want.
C
We
need
to
figure
out
which
path
forward
makes
the
most
sense
for
backdrop
and
try
and
start
moving
towards
getting
something
implemented,
which
we
can
then
number
one
put
in
for
number
two
use
to
build
a
carousel-type
thing
and
then
put
that
carousel
typing
in
core,
as
well
as
an
example
of
how
to
use
these
ageless
note
things
so
I,
don't
know
where
we
stand
on
that.
If
that's
something
we
should
have
a
whole
separate
conversation
about
just
to
try
and
figure
out
what
an
indie
type
thing
we're
going
to
use.
D
C
F
Would
say
the
one
thing
different
that
we
discussed
it
with
past
week
is
Lee
and
one
of
the
issues
started
was
the
one
issues
I
am
I
started
discussing.
Basically
what
one
of
the
things
that
we're
describing
with
these
like
pages
known
things
are
comments
and
leather
comments
become
one
of
these
things,
because,
basically
that's
what
they
are
they're,
like
you
know,
a
entity
type
it
doesn't
have
a
page
is
just
reference
from
another
entity
and
you
know
maybe
convert
comments
to
that
or
whether
we.
C
C
F
F
I
ran
into
this
when
I
was,
you
know,
trying
to
you
know
because
doing
the
reference,
because
you
can
reference
comments
like
you
know,
right
now,
it
is.
It
is
calling
comments,
/,
1
or
something
like
that
as
the
URL,
when
you
link
to
them
and
basically
basically,
we
did
have
a
bunch
of
we
just
have
tickets
in
the
queue
about
comments,
and
it
seems
like
and
I'm,
not
sure,
I'm,
not
sure
if
this
can
actually
be
done.
F
It's
still
backdrop
to
because
you
know
speaking
of
API
changes
but
like
the
way
that
comments
work
and
the
fact
that
they're
only
able
to
be
added
onto
nodes
and
not
arbitrary
entity
types
is
kind
of
weird
and
the
fact
that
each
it
creates
a
new
bundle
for
comments
for
each
different
content
type,
because
you
want,
because
it
just
assumes
that
you
want
to
be
able
to
set
different
fields
for
each
content
type.
A
comment
is
on
and
all
those
assumptions
seem
like
ridiculous,
that,
like
you
shouldn't,
you
know
you
should
be
able
to.
F
If
you
are
going
to
create
different
bundles
of
comments,
just
be
able
to
choose
between
like
several
standard
ones
or
one
standard
one,
and
you
should
be
able
to
link
them
to
any
entities
so
like
we
sort
of
have
to
figure
out
if
we
can
actually
make
a
change
to
this
whole
structure,
which
is
ridiculous
in
backdrop.
One
without
like
breaking
the
API
too
much
I.
C
C
C
F
The
other
question
I
brought
in
the
issue
is
like
for
putting
putting
the
weather,
has
a
page
or
not
aside,
like
would
these
pages
nodes
have
a
different
database
schema
than
nodes
right
now?
Would
they
have
like
you
know?
You
know
we
have
all
the
regular
attributes
in
the
node
table
like
created
the
author
revisions.
F
C
F
C
F
So
I
mean
that's,
that's
the
thing
it's
like
you
know,
I'd
say
whether
it
like
you
know.
If
we're
talking
about
making
nodes
being
able
to
say,
oh,
it
doesn't
have
a
page,
but
I
mean
it
seems
like
if,
if
the
things
that
we're
creating
are
exactly
the
same
in
terms
of
the
base
table,
it
wouldn't
make
sense
to
create
a
new
entity.
It
almost
seems
like
it
makes
sense
to
create
a
new
entity
when
yeah
I,
don't
know
like
in
terms
of
crane
new
entity
with
a
new
database
schema.
D
C
D
C
I
think
I
think
there
are
other
solutions
to
that
problem
right
in
rabbit
hole
is
a
great
example
and
like
like
Darrell
mentioned
this
at
bad
camp.
To
like
just
put
rabbit,
hole
and
core
might
be
a
good
path
forward
for
us
where
it's
like
on
the
path
settings
for
the
content
type
you
just
decide,
doesn't
have
a
path
or
not,
and
if
not
what
you
to
do
right,
just
like
rabbit
hole,
does
now
or
it's
like.
Oh,
we
could
do
a
404.
We
could
do
a
redirect.
We
can
do
it
next
to
nine.
C
F
Here's
the
thing
is:
we
have
this
I
think
the
entity
system
assumes
that
entities
have
a
path.
I
know
that
when,
like
I'm
building
the
reference
module
that,
like
you
know,
we
have,
we
have
the
formatter
that
displays
a
list,
and
it
just
assumes
right
now
that
it
gets
the
entity
pass
from
the
entity
and
create
a
link
to
it.
F
So
if
we
have
sudden,
like
you
know,
sort
of
like
having
entities
without
path
is
actually
not
not
only
just
like
creating
new
any
type
or
editing
node,
it's
actually
sort
of
making
a
change
to
the
entity
system
itself
and
that
we
have
to
actually
look
at
what
it
means
to
the
entity,
the
entire
entity
system.
If
we
want
to
have
an
entity
without
a
path,
we
might
want
to
just
leave
the
entities
with
the
path
and
instead
control
access
to
that
path.
More
stringent
lake,
then
right
now,
yeah.
F
F
C
We
wanted
to
go
that
way.
It
would
be
an
axis
on
existing
path,
which
is
fine
and
also
I'm,
not
sure
cuz
I
haven't
looked
in
to
entities
as
much
as
you
have
Mike,
but
it
might
also
be
possible
that
we
could
just
put
some
change
to
like
the
root
entity
class.
That
says,
if
there's
no
class
return
false
and
then
everywhere
that
expecting
a
path.
We
add
a
behavior
that,
if
there's
if
it
gets
false
back
instead
of
a
path,
it
does
something
different.
Oh
yeah,
I,
don't
know
that
could
break.
C
Okay,
so
it
sounds
like
we
have
a
couple
of
things
to
look
at
Jeff
I,
don't
know
if
you're
gonna
have
time
to
try
a
rabbit
hole,
type
solution
for
that
anytime
soon
and
what
else
who
wants
to
get
into
it?
That
sounds
like
I
agree
like
the
least
effort
going
forward.
It
would
also
be
interesting
to
see
whether
we
should
do
like
an
access
based
approach
or
not
but
yeah.
A
Real
quick,
Mike
Alessi
w
you
yeah
anyways
real,
quick
I,
just
created
an
issue
in
the
reference
queue
because
I
quickly
checked
in
civil
testing.
Google
age
does
have
Tim
their
mother,
the
entity
reference
and
the
autocomplete
does
allow
you
to
create
new
entities
of
that
type.
I,
don't
know
if
they're
special
casing
just
the
term
reference
that
does
or
they
allowed
it
in
general,
but
we
can
look
at
how
they
do
it.
C
D
C
F
C
C
F
I
would
I
would
almost
say
that,
instead
of
an
upgrade
path,
we
almost
like
I,
mentioned
sort
of
the
idea
before
of
a
of
a
conversion
path
and
figure
out
how
to
just
basically
we
did.
We
don't
I,
don't
think
we
want
to
just
automatically
change
everyone's
there
are.
There
are
slight
differences
in
ample
in
how
the
user
interface
and
stuff
works,
with
a
different
user
user
reference
and
node
reference
and
stuff
like
that.