►
From YouTube: Virtual User Group: Upgrading from D7
Description
Link to resources mentioned in video can be found at:
https://backdropcms.org/news/events/virtual-user-group-moving-from-drupal-7-to-backdrop-cms
A
Okay,
we're
live
welcome
to
the
live,
a
virtual
youth
back,
wrap
virtual
user
group
today,
we're
talking
about
with
Jen
Lambton,
about
doing
rupal,
7
to
backdrop
upgrades
and
just
a
quick
know:
we've
been
doing
almost
month,
pretty
much
monthly
user
groups
for
about
almost
a
year
now.
So
if
people
have
ideas
for
future
topics,
let
us
know
we
try
to
do
them
about
something
like
the
first
Tuesday
of
each
month.
But
it's
it's
married
a
bit
so
watch
out
for
future
topics.
We
don't
have
the
next
topic
selected
yet,
but
I'd
love
idea.
A
The
plan
for
today
is
that
gems
just
going
to
do
the
presentation.
My
understanding
is
people
should
feel
free
to
ask
questions
today,
but
we
also
do
have
we're
going
to
do
office
hours
tomorrow
in
a
chat,
but
we
could
also
open
up
the
Zoomer
other
people
come
I,
assume
and
share
screens
and
actually
help
people
troubleshoot
specific
problems
if
we're
having
them.
So
there's
a
link
online,
but
backdropped
org
under
events
is
the
information
about
the
chat
tomorrow.
So
Jen
you
go
ahead
and
start
and
introduce
yourself.
B
My
name
is,
and
I've
done,
great
I
started
in
the
early
days,
doing
updates
from
Drupal
6
and
to
get
from
Drupal
6
to
backdrop.
I
usually
went
from
triple
six
to
triple
7,
which
was
the
hard
part
and
then
in
triple
7,
a
bactrim
which
was
the
easy
part,
but
now
I've
gotten
through
my
backlog
of
Drupal
sites
projects
and
now
I'm,
starting
to
upgrade
a
lot
of
the
triple
7
projects
that
I
work
on,
and
so
my
focus
for
the
next
year
is
going
to
be
specifically
taking
on
work.
B
That
is
upgrades
from
Drupal
7
to
backdrop
and
trying
to
smooth
out
the
process
of
you
know
where
there
are
little
kinks
and
in
the
process
right
now
to
try
and
make
those
easier.
So
there
are
a
couple
of
things:
I
want
to
talk
about.
First
I
guess
one
thing
Tim
brought
up
is
that
there
is
this:
like
upgrade
versus
migration
terminology
in
many
systems,
migration
is
a
pretty
common
term.
B
That
just
means
you
like
take
all
of
your
data
out
of
one
thing,
and
then
you
put
it
into
another
thing
and
it
doesn't
really
matter
what
the
two
things
are:
that
migration
process
happens
usually
with
a
lot
of
custom
code
and
custom
work
to
take
things
out
from
one
format,
transport
them
and
transform
them
into
other
format.
You
need
and
then
put
them
into
another
thing,
and
that's
how
upgrades
are
happening
if
you're
on
Drupal
7,
you
need
to
go
to
Drupal
8.
B
You
usually
have
to
architect
your
Drupal
8
system
first
and
then
pull
it
in
you
want
out
of
your
drupal
7
system
and
put
it
into
your
drupal
8
system.
So
that
would
be
the
same
so
that
you
win
triple-eight
are
really
going
to
really
going
to
some
custom
Ruby
on
Rails
system.
The
migration
process
is
very
similar.
Previous
versions
of
a
Drupal,
though,
had.
B
Upgrade
process
built
in
and
it's
never
been
perfectly
smooth.
That's
what
we're
trying
to
we're
trying
to
improve
that
process
in
backdrop,
but
in
theory,
what
you're
supposed
to
be
able
to
do
is
take
an
brand
new
abdi
website
without
any
configuration
at
all
and
import
database
from
the
previous
version
of
the
software
and
then
run
a
script.
That's
built
in
called
at
the
URL
update,
dot
PHP.
We
call
it
upgrade,
update
script
and
then
Drupal
will
go
through
and
it
would
tape
all
of
your
content.
B
That
was
in
the
previous
format,
and
it
would
transform
into
the
new
format,
and
it
would
do
that
migration
for
you.
So
in
this
particular
session
and
usually
when
I'm
talking
about
updates.
What
I'm
talking
about
is
not
the
migration
where
you
have
to
do
all
of
the
work
of
transforming
that
data
yourself
from
one
system
to
another,
but
where
you're
allowing
backdrop
in
this
case
to
do
that.
Data
translation
for
you.
B
So
most
of
the
data
formats
that
were
stored
in
a
database
in
Drupal
7
are
almost
identical
to
what's
in
backdrop,
and
so
that
script
that's
built
into
backdrop.
That
does
that
transformation
has
very
little
to
do
to
your
actual
data.
The
thing
that
it
does
most
is
take
things
out
of
the
database
and
write
them
into
configuration
files,
because
backdrop
now
has
configuration
management,
so
I'm
gonna
walk
through
today,
importing
a
Drupal
7
database
several
times
and
running
that
upgrade
script
and
testing
the
site
that
comes
out
at
the
other
end.
B
I
think
that
this
is
in
general,
a
good
way
to
handle
updates,
but
we
have
to
submit
out
the
kinks
in
the
process
before
the
meeting
Peter
mentioned
that
there
there
are
some
kinks,
especially
around
modules
that
were
contributed
modules
in
Drupal,
7
and
now
we're
in
core
4
backdrop.
Trying
to
get
those
transitions
to
be
seamless
is
a
little
tricky.
B
I
think
is
going
to
be
really
helpful
for
people
coming
in
in
terms
of
any
individual
project
like
if
you're
doing
your
own
upgrade
a
lot
of
times.
When
you
get
to
one
of
those
snags.
You'll
find
that
it'll.
Take
you
like
four
hours
to
find
the
problem
fix
the
problem
and
you
can
clean
up
that
upgrade
for
the
next
person.
But
it
would
take
you
four
minutes
to
go
to
the
user
interface
and
click
together.
B
What
you
had
in
Drupal,
7
and
so
a
lot
of
times
those
little
details
get
overlooked,
because
it
is
so
easy
to
just
reproduce
them
so
I'm
gonna,
try
and
fix
them.
But
if
you're
working
on
figuring,
like
an
estimate
for
a
site
that
you're
working
on
you,
don't
need
to
budget
in
the
four
hours
for
getting
the
fix
in
there.
If
there
is
a
simple
5-minute
fix
and
one
of
the
stuffs
I'm
going
to
show
you
guys
today
is
how
to
handle
that
click.
B
B
Okay,
we'll
give
it
a
go.
You
guys
can't
ever
can't
see
something
I'm
doing.
Let
me
know
I
have
a
lot
of
desktops
okay.
So
what
we're
looking
at
now
is
the
website
that
I
upgraded
from
Drupal
7
to
backdrop
I
did
this
upgrade
in
one
day
it
is
a
fairly
simple,
straightforward
website
in
Drupal,
7
Drupal
was
chosen
because
at
the
time
it
was
an
ecommerce
site
they
wanted
to
do
so.
B
This
is
a
work
web
site,
so
apologies
in
advance
to
all
the
vegetarians
and
vegans
on
the
call,
but
the
company
really
wanted
to
promote
taking
care
of
agriculture
in
the
food
chain
rather
than
just
having
it
be
like
mass-produced
things
where
animals
were
mistreated,
so
that
seems
like
it
was
right
along
my
idea
of
things
that
I
wanted
to
support
in
the
world.
So
here's
to
this
pork
web
site,
the
name
of
the
company,
is
Stone
Valley
Farm.
B
They
raise
all
their
pigs
here
in
California,
they're
cute
happy
pigs,
as
you
can
see
from
out
the
pictures.
Their
web
site
is
pretty
straightforward.
They
have
a
couple
of
about
pages,
and
this
is
the
backdrop
version.
So
again,
it's
done
in
a
day,
not
entirely
perfect.
It
has
a
couple
of
view
pages.
It
has
maybe
not
the
right
version.
I
also
have
like
eight
versions
of
the
site
enjoy,
show
you.
Let
me
show
you,
the
Drupal.
7
site
seems
yeah.
It's
supposed
to
look
like.
B
Can
you
guys
see
a
different
website
now
and
you
saw
a
minute
ago,
zoom
thing
in
the
way:
okay,
I,
don't
know
what
you're
saying
I
hope,
you're
saying
the
same
thing,
I'm
saying
anyway,
here's
the
Drupal
7
web
site.
It
has
a
About
section
with
a
couple
of
sub
pages
that
has
a
product
section
with
a
couple
of
sub
pages.
B
It
has
a
couple
of
fairly
rich
content
types
because
they
have
a
list
of
like
all
the
people
that
they
sell
products
you
and
where
they're
located
it
has
a
recipe
content
type
where
they
wanted
to
have
rich
data
exposed
to
Google
so
that
they
could
get
results
for
those
being
recipes
and
they
have
a
blog.
So
they
have
a
person
who
the
very
beginning
of
the
website
was
very
motivated
to
keep
writing
blog
posts,
and
then
they
have
a
contact
form.
B
So
obviously,
if
you
wanted
to
buy
meat
for
your
restaurant,
you
could
reach
them
that
way.
So,
in
terms
of
architecture,
this
is
a
fairly
straightforward
site.
It's
slightly
more
complicated
than
your
average
WordPress
site,
but
probably
could
have
been
done
in
WordPress
today
if
they
needed
to
so.
My
goal
for
the
upgrade
for
them
was
to
prove
to
them
that
it
would
be
faster
and
more
efficient
for
them
to
move
there
perfectly
good
group
11/7
website
on
to
backdrop
than
it
would
be
to
rebuild
it
in
WordPress.
So
that
was
my
goal.
B
I
wanted
and
they
were
really
happy
with
how
it
functioned.
They
didn't
really
care
about
doing
a
rebrand,
so
it's
exactly
the
same
website
from
one
system
to
another.
So
in
order
to
start
upgrade
and
oh
I
also
shouldn't
mention
I
have
written
down
sort
of
extensive
documentation
on
this.
One
particular
upgrades
that,
if
you
guys
want
to
follow
along
later-
or
if
you
you
don't
want
more
details
about
a
particular
part,
I
might
not
go
into
a
lot
of
detail
in
here.
B
I
can
definitely
do
that,
but
we
can
post
this
link
and
get
her
on
the
meeting
on
backdrop,
so
you
master
order
and
still
up
or
wherever
we
think
that
might
be
valuable.
There
is
a
link
to
the
document
at
the
bottom
here.
So
in
this
document,
one
of
the
things
I
start
talking
about
is
how
to
prepare
for
doing
an
upgrading.
B
So
I
have
one
tap
or
modules,
and
this
is
where
I
can
keep
track
of
all
of
the
modules
that
I
was
running
on
the
Drupal
7
site
and
their
status
in
backdraft.
So
a
lot
of
them
of
the
move
decor,
which
means
the
number
of
contributors
to
the
BACtrack
project,
is
gonna,
be
pretty
low
and
then
there's
a
couple
of
modules
that
I'm
not
gonna
need
any
more
better
formats.
B
So
I
have
not
completed
the
estimate
section
of
this,
because
I
haven't
sent
an
estimate,
but
this
is
where
you
can
plug
in
like
how
many
hours
you
think
it
might
take
you
to
do
the
things
that
you
think
and
then,
when
you're
done.
If
you
wanted
to
see,
if
you
how
close
to
I
usually
have
an
actual
column
in
here,
then
I
have
a
section
here
for
custom
modules,
where
I
can
indicate
what
anything.
B
Almost
every
one
of
my
projects
ends
up
with
at
least
one
custom
module,
but
trying
to
write
down
what
it
is
that
that
module
is
stealing
and
whether
it's
gonna
be
needed.
In
fact,
wrap
is
useful
in
this
case.
I
had
one
that
set
up
date
formats,
one
that
set
up
in
image
style,
one
that
had
all
the
default
views
in
code
and
all
of
those
were
replaced
by
configuration
management
and
backdrop,
and
then
I
had
one
module
that
did
a
bunch
of
like
form,
altars
and
provided
a
custom
block
and
stuff.
B
So
that's
the
kind
of
thing
that
I
would
also
need
to
port
to
get
to
work
for
backdrop.
So
I've
got
that
noted
in
here.
I,
usually
take
a
look
through
the
module
and
see
how
complicated
it
is.
It's
not
very
complicated.
There's
nothing
in
there,
that's
very
different
between
Drupal
and
backdrop.
It
doesn't
take
a
lot
of
time
to
figure
out
how
long
it's
going
to
take
I
usually
also
note
the
layouts
that
are
on
the
site,
and
this
is
something
that
is
a
little
tricky.
B
This
site
was
using
panels
in
Drupal
7,
so
I
had
a
couple
of
panel
pages
and
it
had
a
note
override
which
for
those
views
in
panels,
you
know
we
have
something
settin
backdrop.
So
my
architecture
on
my
spreadsheet,
for
what
layouts
to
use
was
based
on
what
panels
were
setup
before
I
thought.
That
would
just
be
easiest
in
terms
of
placing
blocks
and
pages
with
the
same
rules.
It
was
there
before
exactly
the
same
as
what
it
was.
Some
people
when
they're
doing
a
new
site
might
choose
to
architect
it
differently.
B
The
second
time
around,
but
I
didn't
spend
any
time.
Thinking
about
that
here,
so
I
have
chosen
a
template
from
the
templates
that
are
provided
in
backdrop
core.
That
was
a
close
match
and
then
you'll
see
in
my
theme,
I
overridden
that
template
file
to
make
it
look
like
what
it
did
on
the
old
site
and
then
I
have
one
page.
It
uses
a
different
template
which
is
the
home
page.
B
This
is
boxed
in
and
then
I
just
noted
on
here
the
regions
that
were
provided
to
make
sure
that
they
match
what
was
provided
in
backdrop,
score
layouts
and
the
types
of
blocks
that
were
placed
into
different
places.
And
then,
if
that
block
came
from
the
particular
part
of
core
or
if
it
was
something
custom,
so
I
could
get
an
idea
of
what
kind
of
work
would
be.
I
also
tried
to
highlight
the
differences
between
the
default
layout
and
what
might
appear
on
other
pages.
B
So,
for
example,
the
only
difference
between
the
default,
oh
yeah
and
the
blog
page.
Is
that
there's
a
blog
view
and
the
same
thing
for
the
recipes
page
there's
going
to
be
a
recipes
view
and
then
on
my
individual
node
pages.
A
lot
of
them
had
views
added
in
addition
to
the
node
content,
and
so
those
would
all
be
placed
into
the
sort
of
main
content
area
with
specific
visibility
conditions.
B
So
I
noted
here
what
those
visibility
conditions
would
be
and
I'll
just
make
it
a
little
faster
for
me
to
get
in
there
and
do
the
building
of
layouts
when
I
get
around
to
doing
it.
So
one
of
the
reasons
that
I
map
out
all
the
layouts
like
this
is
because
we
do
not
yet
have
an
upgrade
path
from
panels
and
the
configuration
you
get
panels
to
the
layout
system
and
backdrop
and
I
could
spend
a
bunch
of
time
working
on
that.
B
But
I
also
know
that
these
layouts
are
really
simple
and
I
can
have
them
done
in
less
than
an
hour.
I
just
rebuilt
them
myself
so
for
this
particular
project,
since
I
was
hoping
to
prove
to
them
that
it
was
cheaper
to
upgrade
to
backdrop
than
to
rebuild
the
WordPress
I'm
going
with
sort
of
a
low
end
of
how
fast
can
I
get
this
done.
B
So
I
also
sometimes
make
additional
layouts,
depending
on
the
complexity
of
my
site.
I
might
want
to
note,
like
all
the
different
content
types
and
how
many
pieces
of
content
there
are
this,
as
you
can
see,
as
a
very
simple
site,
only
has
60
content
items
for
more
complicated
sites.
Doing
a
breakdown
of
the
types
of
content
gives
me
an
idea
of.
What's
most
important,
for
that
particular
site,
like
is
a
huge
blog
site
with
millions
of
blog
posts.
This
one
only
has
five,
it's
not
obviously.
B
Well,
it's
not
the
most
important
thing
to
them,
and
then
I
can
spend
more
time
testing
the
things
they
think
are
most
important
here.
It
looks
like
they
are
primarily
using
this
site.
10
manage
a
listing
of
their
resellers,
so
that
was
kind
of
what
I
was
focusing
on
for
making
making
sure
that
we
got
all
of
those
features
to
be
an
exact
match
for
what
they
were
before.
B
If
I
had
a
bunch
of
really
complicated
fields,
and
this
website
doesn't
I
usually
have
another
tab
that
just
talks
about
how
I'm
gonna
manage
field
types
in
this
particular
spreadsheet
and
I
can
share
this
with
you.
Guys
too.
If
you
want
I
left
an
example
from
more
complicated
website,
because
for
this
website,
there's
nothing
in
here
where
I
might
have
fields
from
field
types
that
aren't
supported
in
backdrop.
B
So
if
you
have
two
modules
or
two
field
types
in
in
Drupal
7,
it
can
convert
one
field
to
another
and
they
move
all
the
data
from
one
field
type
to
another.
And
then
you
can
delete
the
field.
That's
problematic
in
Drupal,
7
and
then
backdrops
upgrade
can
handle
the
update
from
the
Drupal
7
format.
To
the
backdrop
format
for
you,
so
I've
had
a
couple
of
sites
where
I
did
that?
B
That's
what
this
set
of
notes
is
from,
but
there
are
some
field
types
that
have
built
in
transitions
from
one
type
to
another
when
you
go
from
Drupal
7
to
backdrop.
So
references,
for
example,
is
the
backdrop
reference
module,
but
in
Drupal
7
we
had
both
entity
reference
and
node
reference.
This
particular
spreadsheet
shows
a
website
that
had
both
types
of
fields
on
it
and
so
for
that
project.
I,
used
I
think
there's
a
poor
request
for
the
references
module
that
converts
all
fields,
no
reference
or
entity
reference
into
reference
fields
for
backdrop.
B
I
sometimes
build
a
sitemap
I
left
this
tab
empty
because
the
site
didn't
really
need
one,
but
I
left
the
column
headers
here
in
case
anybody
else
wanted
to
see
what
I
would
usually
do
for
that,
and
sometimes
what
I
would
do
is
go
through
like
every
node
type
and
make
sure
I
had
a
layout
template
chosen
for
how
that
will
be
displayed.
What
that
would
map
to
in
Bac
trap
and
any
particular
nodes
I
needed
to
have
about
that
type
of
page?
So
sometimes
it's
an
o-type.
B
Sometimes
it's
a
landing
page
I
just
want
to
make
sure
I
have
all
that
stuff
noted,
especially
if
you're
trying
to
come
up
with
a
realistic
estimate
for
someone
for
how
long
it's
gonna
take
to
move
the
site.
You
want
to
make
sure
you
have
anything.
That's
standalone
special
document
somewhere,
so
it
doesn't
catch
you
later
as
a
surprise.
B
So
that's
the
spreadsheet
so
step
one
in
my
upgrade
is
always
make
a
spreadsheet.
That's
what
I
do
I
usually
find
making
that
spreadsheet
takes
know
that
so
this
particular
spreadsheet,
for
this
site
took
me
maybe
an
hour
just
studying
of
the
existing
architecture
on
the
site
through
the
administrative
interface
I
also
usually
like
to
get
a
ramp.
Get
access
to
the
code
before
I'll
make
this
to
make
sure
that
there
aren't
any
surprises
in
the
code
that
you
might
see.
B
One
thing
that
this
spreadsheet
does
not
include
and
I'm
not
sure
Timothy,
so
I
just
popped
on
there's
anything
about
the
theme
and
part
of
that
is
because,
in
this
particular
site
the
theme
is
going
to
be
exactly
the
same.
The
trick
is
just
the
layouts
I'm
separating
a
theme
into
the
different
layouts.
It's
that's
why
I
have
a
tab
specifically
for
handling
layouts,
but
I
don't
have
one
for
the
theme
alright,
so
that
was
my
prep
work
for
how
to
do
the
upgrade.
B
The
next
step
I
have
is
just
to
make
a
backup
copy
of
everything.
That's
on
the
production
site
and
I
like
to
make
copies
of
everything
all
the
time,
especially
when
I'm
doing
upgrade
so
I
want
to
make
sure
I've
got
the
most
recent
version
of
anything.
In
fact,
most
recent
version
the
database
from
illustration
version
of
the
files
most
recent
version
of
the
code
and
I
get
a
copy
of
it
into
a
safe
place.
B
So
I
usually
do
all
of
my
upgrades
locally
a
bunch
of
times,
first
to
make
sure
that
they're
gonna
go
exactly
as
I
smash
there
and
then,
when
I
get
the
deploy,
I
usually
put
like
two
directories
on
the
production
server
and
then
I'll
just
switch
from
pointing
the
live
site
at
one
pointing
line
site
at
the
other.
If
you
have
content
constantly
being
added
on
your
production
site,
you
can
also
do
the
upgrade.
You
can
put
a
freeze
on
your
life
side.
Do
the
upgrade
in
the
directory.
That's
right!
B
Next
to
it
and
and
switch
it
really
quickly.
So
I
find
that
the
last
step
of
the
upgrade
can
be
done
there
table
if
necessary,
all
right
so
on
my
local
site.
I
only
did
a
couple
of
changes,
making
sure
that
you
can
access
the
update
page.
That's
the
URL
update
dot
PHP,
even
when
you're,
not
logged
into
the
site
is
important.
B
B
B
B
I
just
run
it
and
make
sure
that
my
content
moves
over
in
in
the
ways
that
I
expect
and
making
sure
I
can
still
log
into
the
site
and,
if
nothing
explodes
which
usually
it
doesn't
then
I
start
adding
in
all
the
controls,
depending
on
how
complicated
this
site
is.
I
might
add
them
one
at
a
time,
so
the
process
wouldn't
be
import.
B
Your
database
run
an
update,
drop
in
a
module
run,
an
update,
jump
into
module,
run
an
update
job
in
the
module,
an
update,
and
you
can
do
that
once
for
every
module
and
that
way
you'll
know
exactly
which
module
will
cause
problem.
If
you
have
a
problem,
this
site
was
simple
enough:
that
what
I
did
was
did
core
only
ran
an
update
dropped
in
all
the
modules
ran.
Another
update.
It
worked
out.
B
Okay,
so
I
didn't
bother
going
through
all
of
them
one
at
a
time,
and
also
because
most
of
them
already
had
stable
backdrop
versions
that
have
been
around
for
a
while.
My
concern
about
whether
there
was
gonna
be
an
issue
was
rather
low.
If
I
did
run
into
an
issue,
I
probably
would
have
gone
back,
intend
them
all
one
at
a
time
to
make
sure
I
knew
exactly
where
the
problem
was
created.
A
B
B
So
I
have
one
code
base
that
as
I've
been
walking
through
making.
These
updates
I
have
created
separate
branches
at
different
steps,
and
this
is
on
github
and
publicly
available.
If
you
guys
want
to
see
it
later,
if
we
can
post
a
link
to
that
somewhere
and
so
I
have
a
bar
until
its
core
only,
which
is
what
I'm
going
to
do.
The
first
upgrade
I
have
a
branch
that
has
the
country
of
modules,
which
is
going
to
be
the
second
update.
I
have
a
branch,
it
has
configuration
changes
only.
B
B
B
B
B
B
B
From
my
Drupal
7
site,
so
it's
sort
of
a
starting
copy
of
exactly
what
the
files
look
like
on
Drupal
7,
so
I
have
a
default
version
of
files
and
an
empty
config
directory
and
then
I've
just
imported
a
database.
That
was
a
version
maybe
should
document
this
too
I
think
it
might
be
in
in
the
file.
But
in
turn,
in
terms
of
preparing
my
a
triple7
site
for
exactly
that,
getting
the
database
ready.
B
What
I've
imported
right
now
is
a
version
that
doesn't
have
the
theme
enables-
and
that's
because
at
this
point
in
the
process,
I
usually
wouldn't
have
a
backdrop
theme
ready
for
the
site.
Yet
I
like
to
build
the
site
in
sort
of
it's
like
naked
site
and
then
make
it
state
and
then
take
the
theme
from
Drupal.
7
drop
it
in
update
it
for
backdrop
and
then
I
and
then
I
run
the
update
again
at
the
end,
with
all
of
the
stuff
ready.
B
So
in
the
very
beginning,
I,
don't
have
anything
for
backdrop
other
than
backdrop
core,
so
I
have
removed
the
disabled.
The
theme
of
the
Drupal
7
site
and
exported
the
database
so
I
have
a
database
called
start,
no
theme
that
I've
imported
and
now
I'm
going
to
run
the
first
update.
So
the
first
update
is
only
should
show
only
the
changes
in
core
and
that
should
be
a
hundred
seventy-five
updates.
B
But
if
it
doesn't
it's
a
great
baseline
for
like
where
to
start,
you
often
see
undefined
index
errors,
as
the
update
is
running,
sometimes
because
it
ends
up
calling
stuff
that
like,
for
example,
in
this
case,
we
removed
a
couple
of
field
modules,
and
we
did
this
update
so
because
of
this
isn't
the
end
update.
This
is
just
sort
of
my
first
step.
I'm
gonna,
ignore
it.
If
it's
a
notice,
it
was
a
fatal.
I
would
probably
look
into
it,
but
a
PHP
notice,
I'm
gonna
ignore
for
now
I'm
at
the
end.
B
If
we
still
have
them,
then
I'll
be
concerned,
but
for
now
I
just
want
to
see
it
did
we
get
through
this
entirely
and
it
looks
like
it
did.
It
said
that
you
know
the
updates
that
needed
to
do
and
so
far
so
good.
So
if
I
go
back
to
my
home
page
you'll
see
it
looks
a
lot
like
Bartok,
that's
because
on
my
Drupal
7
site,
a
switch
it
back
to
Bartok.
D
B
Here,
I'll
just
do
some
really
basic
testing
like
make
sure
I
can
log
in
and
if
I
get
along
again
and
like
okay
good
looks
fine
I'll
go
to
my
content
list
make
sure
its
site
isn't
empty
because
there's
nothing
I
saw
on
that.
Last
page
looks
like
all
my
content
is
here.
So
I
can
read
a
little
sigh
of
relief
and
I
might
go
check
out
like
make
sure
I
have
users
or
make
sure
I
have
I,
don't
know
anything.
That's
important!
Texana
me
to
my
site.
B
Is
it
there
and
not
doing
a
really
extensive
search,
because
we
obviously
don't
have
all
the
modules
that
we
need
to
make
it
work,
but
just
to
run
that
first
step
of
the
upgrade?
So
then
the
second
step
moving
on
very
quickly
is
to
put
all
of
the
kinship
modules
back,
and
so
here
I
went
to
my
backup
site
and
I
did
I
used
rush,
so
I
did
a
rush
download
of
every
contributed
module
that
I'm
gonna
need
on
my
back
drop
site,
so
I
got
those
again
from
the
module
list.
Tab
on
my
spreadsheet.
E
B
B
All
right,
so
what
I
would
do
just
go
through
here
and
take
like
Google
Analytics
on
the
web?
References
SMTP
views,
accordion
webform,
that's
it
drop
them
in
all
of
these
other
modules
that
are
in
core
the
upgrade
path
should
be
provided.
This
is
again
something
we'll
need
to
test
once
it's
done
to
make
sure
it's
there,
but
for
the
most
part,
those
the
modules
I've
added.
So
the
go-to
backdrop
to
this
should
be,
and
let's
do
a
sanity
check
here
backdrop
to
what
contribs
can
trim
here,
we
go.
I
just
feel.
B
Developers
only
makes
all
my
references
so
that
that's
what
I've
copied
from
from
backdrop,
so
you
must
at
work
or
using
dress.
So
here,
I'm
gonna
run
the
update
again
and
when
I
run
this
update,
it
should
show
you
more
updates
than
what
you
saw
for
backdrop
core
alone,
which
is
175
in
core.
Now
I've
got
211.
That
means
that
the
module
so
they're
put
in
there
also
have
update
so
they're.
Also
gonna
be
converting
data,
so
I
will
go
ahead
and
do
those
next,
and
this
should
be
interesting.
B
All
right
so
now
the
PHP
notices
that
we
saw
before
are
gone.
That's
because
we
have
all
the
modules
there
now,
which
is
good,
a
nice
happy,
green
aromat
or
not
error,
just
message,
and
then
it
says
all
of
the
modulus
updates
that
we're
done
is
necessary.
So
that's
good
again.
If
I
go
to
my
home
page
it'll,
look
like.
B
I
don't
want
to
make
sure
I
had
those
features
still
here
so
special
address
field
type
is
something
that
I
wanted
to
check.
So
I
know,
I,
have
addresses
on
my
restaurants,
so
I
might
check
and
make
sure
that
I
didn't
had
the
ability
to
update
and
say
about
that
as
I
was
doing
my
first
upgrade
through
this
yesterday,
I
ran
into
a
problem
with
the
address
field.
Module
so
I
was
able
to
go
and
fix
it,
or
at
least
finally
an
issue
in
the
queue
and
make
sure
that
it's
all
working
as
expected.
B
B
You
need
to
get
your
data,
which
is
currently
in
the
backdrop
to
look
like
your
website
that
was
in
Drupal
7
and
usually
that
missing
piece
right.
There
is
configuration
a
lot
of
the
data
that
was
converted
to
figuration
configuration
when
it
went
from
Drupal
7
to
backup
is
already
there
like
content
types
fields.
All
of
that
stuff,
that's
associated
with
your
content,
but
there
are
some
things
that
aren't.
One
of
the
things
you
probably
noticed
is
that
my
WYSIWYG
editor
is
not
on
my
content
anymore.
B
That's
a
big
one,
because
in
backdrop
core,
we
have
CK
editor,
but
in
Drupal
7
people
often
use
the
WYSIWYG
module.
That's
what
this
site
was
using
before
and
so
in
order
to
get
my
same
content,
editing,
editing
experience
as
I
had
before
I
have
to
make
sure
that
I
have
a
rich
text,
editor
enabled
for
my
content
and
right
now:
I,
don't
and
part
of
us,
because
I
disabled,
the
rich
text,
editor
module
in
Drupal
7
and
there's
no
WYSIWYG
module
name
cozy
weekend
backdrop.
B
So
what
I
need
to
do
is
go
and
enable
this
module
here.
It's
called
the
CK
editor
and
then
I
need
to
configure
my
input
format
to
use
the
editor.
So
in
this
case
the
editor
was
on
the
filtered
HTML
format.
So
if
they
can
figure
that
I
can
turn
on
the
CK
editor
editor
and
then,
if
you
had
any
specific
button
configurations
that
you
didn't
CK
editor
that
you
needed
here
like
I,
don't
know
the
ability
dab
in
line
images.
You
can
make
those
changes
here
and
make
it
match
what
you
had
before.
B
There
are
a
lot
more
buttons
available
for
this
UK
editor
module
in
Drupal
7
there
in
backdrop.
So
there
are
some
controls
that
will
give
you
back
some
of
those
features.
So,
in
this
case,
I
didn't
really
need
a
rich
text.
Editor
for
any
particular
reason.
I
was
just
using
it
to
make
editing
easier
on
my
editors,
so
I
think
the
default
one
in
a
backdrop
probably
has
more
features
than
when
I
actually
exposed
to
my
editors
in
Drupal
7.
B
So
what
I've
just
done
is
I've
saved
a
form
that
writes
to
a
configuration
file
on
disk
and,
as
you
would
imagine,
if
I'm
gonna
throw
out
this
website
upgrade
and
run
the
upgrade
again
I
don't
want
to
lose
this
configuration
very
beginning.
We
first
started,
you
saw
me
just
go,
delete
all
the
config
files
that
we're
currently
in
that
directory
and
run
the
upgrade
again.
If
I
were
to
do
that
right
now,
I
would
lose
this
configuration
that
I
just
made
for
this
text
editor.
So
usually
what
I
do
at
this
point
is.
B
There
might
be
some
other
things,
I
think
in
my
documentation,
I
mentioned
date
formats,
that's
the
kind
of
thing
that
should
translate
perfectly
from
Drupal
7
to
backdrop,
but
sometimes
it
doesn't
end
up
matching
perfectly.
So
this
is
something
I
like
to
check
on
my
gerbil
site.
I
had
a.m.
and
p.m.
on
the
end
of
all
of
my
patterns
and
backdrop.
I
don't
seem
to
have
that,
so
that
sets
off
a
red
flag
to
me
that
these
didn't
upgrade
appropriately,
so
I've
opened
in
a
core
issue
and
we're
gonna
try
and
get
that
result.
B
B
Interesting
I
wonder
where
these
came
from
I'm
like:
where
does
this
homepage
extra
homepage
them?
Why
are
there
too
I?
Don't
know
how
this
got
here.
This
didn't
happen
yesterday,
anyway.
Layouts
are
a
thing
where
I
tend
to
spend
a
lot
of
time,
placing
on
my
blocks
in
two
different
places,
especially
if
you
have
a
lot
of
different
layouts.
B
You
want
to
make
sure
that
those
configurations
aren't
lost
because
I
did
the
upgrade
here
when
I
had
the
Bartik
theme
enabled
the
layout
that's
gonna
be
my
default
layout
is
the
Simmons
layout
and
that
exactly
matches
the
placement
of
regions
in
the
Arctic
theme.
In
this
case,
I
would
want
to
change
this
to
a
layout
that
more
matches
what
my
site
is
doing,
which
would
be
something
like
Harris
and
then
move
all
of
the
box
around
to
the
regions
where
you'd
like
to
have
them.
B
B
So
it's
still
in
the
wrong
theme,
but
I
now
have
like
a
quote
in
the
sidebar
and
if
my
content
at
all
and
it's
starting
to
get
closer
to
what
I
want
so
I
would
spend
some
time
right
now
in
this
particular
stage.
Even
when
it's
using
the
wrong
with
you
building
out
all
of
my
layouts
and
getting
them
to
have
the
blocks
that
I
need
in
the
places
that
I
need,
then
the
tricky
part
is
trying
to
figure
out
how
to
get
your
configuration
not
to
get
lost,
and
so,
in
my.
B
B
All
the
files
from
dev
active
into
staging
and
I
would
commit
them,
and
now
I
have
a
place
where
I
can
delete
all
the
configuration
from
dev,
active
I
can
run
the
upgrade
again
and
then
I
can
do
a
config
sync
and
it
will
copy
all
of
my
configuration
from
staging
in
a
dev
active,
and
it
will
show
me
this
is
what
I'm
gonna
change.
So,
if
there's
something
that
what
happened
differently
in
that
upgrade
from
the
first
time,
I
made
it
to
the
second
time.
I
can
do
a
little
sanity
check
on
that
you're.
B
Like
oh,
you
know,
it
looks
like
there's
a
new
upgrade
for
address
field.
That's
gonna
fix
the
problem
that
I
ran
into
yesterday,
so
I
want
to
make
sure
that
I
keep
that
changed.
So
I'll
copy
the
file
from
dev
active,
the
new
correct
one
into
the
staging
directory,
and
then
it
will
show
that
that's
not
a
change
anymore
in
the
configuration
UI
and
so
that
I
can
run
a
sync
from
staging.
So
it
gives
me
a
good
place
to
save
all
the
configuration
that
I've
just
created
manually
on
my
site.
B
B
B
In
the
active
directory
and
in
the
staging
directory,
it
should
have
a
copy
of
all
of
my
configuration,
and
so
this
version
of
my
site
I'll
do
the
upgrade
again
same
database
on
a
version
of
all
the
core
modules,
the
Kindred
modules
and
all
all
the
configuration
I'll
run
it
again
and
then
after
I
run
it
I'll
do
a
configuration
sync
and
it'll
take
all
of
my
configuration
files
that
I
spent
a
bunch
of
time
clicking
together
mostly
yesterday
and
import
them
into
the
site.
So,
hopefully,
I'll
run.
This
it'll
still
be
happy.
B
B
Management-
and
it
will
show
me,
there's
a
whole
bunch
of
stuff-
that's
changed,
there's
a
whole
bunch
of
new
things,
like
all
the
layouts
that
I
built
and
some
menu
items
for
those
layouts
that
I
felt
and
then
it'll
show
stuff.
That's
been
changed
in
various
ways,
so
I'm
gonna
know
I
spent
some
time
configuring
these
views
to
make
them
work
a
little
differently
on
the
new
site.
This
is
the
date
format.
The
default
layer
I
changed
the
template
that
was
being
used.
B
B
B
It
looks
like
it's
complaining
cuz.
My
theme
is
missing,
which
is
fine,
because
I
don't
have
a
theme
yet
then
I
should
have
all
of
the
content
where
I
want
on
the
page,
and
the
next
step
would
be
to
build
the
theme.
So
since
I
have
a
theme
for
Drupal
7
that
they
wanted
to
be
exactly
the
same,
I
think
we
did
a
session
before
on
how
to
port
a
theme.
B
So
I
won't
talk
about
any
of
the
code
that
was
in
those
and
that,
but
all
I
do
is
just
copy
to
Drupal
7
theme
into
the
back
truck
theme,
remove
or
rename
the
layout
template
file
and
then
start
working
through
all
the
other
template
files
to
make
all
the
PHP
notices
go
away
in
general.
That's
the
thing
I
start
with
and
then
I
check
the
DP
blog
to
make
sure.
B
B
So,
eventually,
I
did
a
complete
code
base
of
exactly
what
your
backdrop
site
will
look
like
when
you're
done
with
it,
you
throw
out
the
database,
you
take
a
database
from
Drupal
7.
You
can
even
take
the
one
with
the
theme
enabled
you
imported
into
your
backdrop
site,
and
you
run
that
update
script.
A
final
time
and
it'll
do
all
of
the
conversions
and
leave
your
theme
enables
at
the
end,
so
I
always
run
the
update
script.
B
At
least
three
times,
depending
on,
if
I
hit
any
problems,
usually
with
every
problem
with
upgrade
I'll
run
it
again.
So
if
I
like
right
into
run
with
the
address
field,
there
would
be
an
extra
updated
on
the
address
field
or,
if
it
took
me,
two
or
three
tries
to
fix
that
there
are
be
two
or
three
extra
updates
that
I
ran
and
so
depending
on
the
projects
at
the
time,
as
sometimes
will
script
that
process
too,
so
that
I
can
have
multiple
copies
of
the
site.
B
You
know
deleting
all
the
configuration
files
copying
the
files
over
importing
the
database
running
the
update
and
doing
the
config
sync,
and
so
I
can
say:
ok,
do
it
again
and
then
I
go,
do
something
else,
row
out
and
then
I
come
back
and
I
have
another
site,
that's
ready
for
me
to
test,
and
so
that
process
is
more
Burnham's
in
them
than
I
would
like
it
to
be
right
now,
but
the
easier
we
can
get
it
to
get
from
start
to
finish.
The
better
I
would
love
it.
B
If
you
didn't
have
to
do
your
configuration
and
a
separate
step
for
everything
else,
I
would
love
it.
If
you
didn't
have
to
do
your
control
separately,
I
just
don't
think
we're
quite
there.
Yet,
in
terms
of
you
know
enough,
people
have
done
enough
upgrades
that
all
of
the
snacks
that
you
run
into
might
have
been
resolved.
B
Yet
we're
still
seeing
some
issues
in
court
like,
for
example,
date
formats
that
aren't
you
know
the
date
format
system
and
backdrop
has
been
improved,
but
that
means
we've
introduced
a
problem
with
the
conversion
of
the
formats
from
Drupal
7
to
backdrop.
So
there's
gonna
be
stuff
like
that,
where
we're
gonna
be
hitting
it.
B
Anyway,
this
particular
website
I
did
the
entire
upgrade
in
one
one
day.
I
can
Karen
update
script
a
total
of
six
times,
because
I
arranged
some
issues
with
address
field.
I
was
able
to
get
the
theme
done
pretty
quickly
because
it
was
a
fairly
simple
theme
to
start
with.
There
were
only
two
layouts,
this
home
page
layout,
which
was
one
column,
and
then
the
sub
page
layouts,
which
had
two
sidebars.
The
content
itself
was
fairly
straightforward.
There
weren't
too
many
different
types
of
fields.
B
The
only
other
thing
I
think
that
kept
me
up
a
little
bit
with
this
site
is
because
it
was
using
panels
for
all
of
its
layout
needs
in
Drupal
is
that
all
of
the
blocks
were
actually
content,
panes,
which
are
panels
versions
of
blocks
that
are
context-aware.
So
when
I
did
the
conversion
of
views,
I
also
had
to
make
sure
that
they
were
raising
block
displays
in
that
paint
displays
and
there's
also
an
issue
in
the
queue
to
make
that
happen
automatically.
B
E
Question
go
ahead,
so
the
triple7
site,
you
used
views
and,
as
a
result
of
having
views,
you
would
have
had
see
tools.
So
what
do
you
do
is
something
like
see
tools
where
there's
no
module
thread
in
backdrop?
Do
you
install
it
in
Drupal,
7,
first
before
any
upgrade,
or
do
you
leave
it
there
or
what
happens
with
that.
B
You
could
probably
do
it
either
way:
I
usually
leave
C
total
one
like
I,
don't
uninstalled
in
Drupal
7
I.
Let
the
database
update
script,
handle
disabling
that
module
when
it
converts
the
database
from
Drupal
the
backdrop
and
because
it
recognizes
the
tools
it'll
do
that
for
me,
there's
a
couple
of
other
things
like
token
and
pathauto
like
if
you
had
modules
that
were
individual
modules
in
Drupal.
That
are
just
now
part
of
backdrop
core,
there's
a
list
of
modules
that
it
knows
to
identify
and
disable
as
part
of
that
gray
path.
B
So
if
like
ste
tools,
for
example,
if
you
remove
C
tools
from
a
Drupal
site,
it
causes
a
huge
problem,
because
so
much
in
Drupal
7
contribute
ends
on
it
and
it'll
for
all
these
errors
and
be
like
I
can't
find
the
C
tools
whatever.
So
you
would
notice
immediately
if
that
was
problematic
in
backdrop,
and
it
hasn't
been
so
I've
just
left
it
on
in
Drupal,
7
meet
the
expert
and
run
the
update,
and
it's
been
fine
in
fact
turns
that
for
me,.
A
B
I
didn't
have
to
worry
about
it
in
this
upgrade
process,
because
it's
always
really
bothered
me
in
Drupal
that
it
puts
the
files
directory
inside
the
site's
default
folder.
So
when
I
build
triple
sites,
I'm
of
the
directory
up
to
the
dock
room.
So
for
this
particular
project,
the
file
structure,
it
was
already
in
da
crew
and
so
I
didn't
have
to
worry
about
it.
B
But
if
your
public
file
system
was
sites
default
files
instead
of
files,
you
would
need
to
have
created
a
sites,
folder
a
defaults
folder
and
then
a
symlink
from
the
files
directory
inside
there
up
to
the
files
directory
in
the
dock
root
in
order
to
make
sure
like
any
embedded
images.
You'd
had
that
we're
pointing
at
the
old
direction
directory
to
point
in
a
new
one
and
you'll
also
need
to
update
this.
You
could
also
have
left
here
files
two
levels
deeper
and
left.
B
This
is
what
as
what
it
was
before,
and
that
would
also
work,
but
because
I
had
gotten
into
a
habit
of
moving
it
in
Drupal
7.
It
made
my
upgrades
a
little
easier.
There
is
also
like,
if
you
get
into
a
pickle
with
your
files,
locations,
Drupal
7
I,
think
has
removed
the
complete
path
from
database,
so
there
shouldn't
be
anything
in
your
database.
That
needs
to
be
changed.
The
only
thing
is
like
one,
those
con
images
do
get
embedded
in
content
and
there's
like
an
image
tag.
B
That's
the
only
place
where,
where
it's
got
that
in
most
places
it
uses
a
URI
and
the
or
I
will
look
up
the
actual
location
of
the
database
and
add
the
public
file
system
path
to
it.
And
so,
if
you
can
change
this,
this
one
configuration
setting
public
file
system
path
and
make
sure
on
your
desk.
You
have
that
same
link
that
should
cover
all
the
instances
of
like
this
is
what
builds
it
automatically
and
anything
was
pointing
to
where
it
was
before
should
get
fixed
by
this
and
link.
D
So
when
I
didn't
necessarily
follow
all
the
correct
steps
when
I
started
and
now
I
mean
it's
now,
I'm
going
to
place
six
months
later,
that
we're
gonna
use
it.
So
I'm
worried
that
I've
spent
six
months
time
six
months
playing
around
with
this
and
I
may
have
screwed
something
up
when
I
initially
did
it.
When
I
didn't
know
what.
B
The
only
thing
that
I
would
advise
this
like
if
you
are
running
that
update
with
controls
that
might
have
gotten
better
upgrade
paths
since
the
last
time
you
did
it,
and
now
that
would
be
one
thing
that
might
be
different.
Another
thing
might
have
been.
If
you
had
run,
can
trim
up
dates,
one
at
a
time,
instead
of
all
at
once.
Sometimes
they
need
to
like
stick
their
updates
between
each
other,
and
so
they
could
happen
in
the
wrong
order.
B
B
I
would
imagine
you'll
find
out
when
you
start
using
it
for
real
but
like
if
there
weren't
a
serious
problems.
You
probably
would
know
about
it
the
little
things
that
you
know
you
might
have
missed
like
another
update.
That's
also
not
the
end
of
the
world
to
run
that
update
later,
like,
even
if
you
have
like
a
bunch
of
new
content
whatever
coming
in.
If
you
were
in
that
update.
Most
of
the
backdrop
updates
are
smart
enough
to
Billy
K.
Does
this
update
need
to
be
run?
B
Yes,
no
and
it
won't
run
it,
but
if
there's
something
that
like
needed
to
be
serialized
your
unsterilized
or
something,
it
could
still
fix
that
after
the
fact.
So
I
wouldn't
say
that
there's
anything
that
you
can't
recover
from.
Even
if
you
have
missed
a
stuff
in
terms
of
your
in
database
conversion.
A
I
certainly
ran
in
to
that
issue
when
I
was
doing
and
I
think
it
just
was
a
mind
shift
for
me
to
figure
out.
This
is
the
first
time
I've
done
it
upgrade
so
I
sort
of
get
used
to
it
and
just
recognizing
that
stuff
was
there
not
necessary
I,
don't
know.
Do
you
have
anything
to
say
about
how
to
handle
layout
yeah.
B
B
True,
in
terms
of
you
know,
moving
from
Drupal
the
backdrop,
I
would
probably
say
it's
less
dangerous
than
previous
versions
of
the
site,
where
I'd
moved
from
6
to
7,
there's
likely
to
be
a
lot
more
craft
left
over
in
general.
Those
crafty
tables
are
not
gonna,
be
very
big
and
I
would
say
unless
it's
really
causing
a
problem,
don't
touch
it,
because
if
it's
fine
with
extra
data
in
there,
it's
fine,
but
if
you
accidentally
delete
something
is
using.
That
might
be
a
problem.
B
So
if
you
want
to
try
cleaning
it
up,
that's
fine
make
lots
of
backups
make
sure
you
have
a
version
at
least
one
copy
from
before
you
started
tinkering
with
it,
so
that
if
later
on,
you've
deleted
it,
you
thought
it
was
fine.
You've
started
using
the
site
six
months
from
now.
You
realize
oh,
that's
what
it
was
for.
If
you
still
have
that
copy
of
that
previous
database,
you
can
like
pull
out
that
table.
B
You
delete
it
and
put
it
back
into
the
site
you're
using
now,
so
in
general,
I
feel
like
unless
it's
some
massive
cache
table.
That's,
like
you,
know
a
third
of
the
size
of
your
database
or
something
some
of
them.
Are
they
get
really
big?
I
wouldn't
worry
about
it
and
cache
tables
in
general.
You
can
truncate
anyway,
so
yeah
I,
don't
know,
but
I
haven't
I
haven't
like
there
are.
Some
modules
that
didn't
have
uninstall
hooks
associated
with
them,
so
it
might
not
even
be
associated
with
your
upgrade.
B
C
Your
the
process
that
we
went
through
today
is
the
update
script
and
I'm
curious.
What
if
the
trade-offs
between
that
versus
a
a
more
traditional
ETL
extra
translate
load
format
is
where
you
first
dump
the
data
into
some
intermediate
format.
Look
around
it
and
then
bring
it
in
like
you,
do
have
circumstances
where
you
prefer
to
use
needs,
for
example,
or
other
kinds
of
things
for
getting
data,
and
rather
than
let
the
update
script
handle
it.
So.
B
I
use
feeds
when
I'm
pulling
in
data
from
external
sources
or
formats
that
don't
exactly
match
to
what's
in
my
database,
but
because
coming
from
Drupal
7
to
backdrop,
we
know
the
exact
format
that
it
was
before
and
the
exact
format
that
it
is
after
it
seems
silly
to
make
every
single
person
who's.
Doing
that
update.
Do
all
the
extra
work
of
Tran
like
export,
translate
import.
We
can
just
do
it
for
them.
So
that's
really
what
the
update
is
supposed
to
do
is
make
it
easier
on
everyone
else.
B
If
I'm
pulling
a
date
of
something,
that's
not
Drupal
or
backdrop,
then
I
use
feeds,
because
that's
where
you're
like.
Oh,
this
is
a
JSONP,
don't
need
to
import
it,
or
this
is
an
atom
feed
or
RSS
feed
or
whatever
I
need
to
pull
in
the
data
from
one
source
for
another,
and
then
you
can
do
that.
Mapping
of
like
this
goes
into
this
field
that
goes
into
that
field
and
in
in
that
most
of
the
sites
that
I
have
done
this
site.
B
That
they've
wanted
at
the
end
is
nearly
identical
to
the
start
they
had
at
the
beginning.
There
are
some
cases
where,
like
they
want
a
completely
different
site
and
the
only
thing
that
they
want
from
their
Drupal
7
site
is
like
all
their
blog
posts,
where
it
might
just
make
more
sense
to
build
a
new
site
and
then
use
something
like
feeds
just
like
ingest,
an
RSS
feed
off
the
old
site,
all
the
content
and
then
you're
done
or
you
know,
use
some
other
system
like
that,
but
that
hasn't
been.
B
It
was
having
the
site's
that
I've
been
working
on
the
sites.
I've
been
working
on
her.
We
like
it
just
fine.
Unfortunately,
Drupal
6
is
dead.
What
do
I
do
and
usually
I
don't
want
to
invest
very
much
in
it
there.
You
know
a
lot
bigger
agencies
are
like
I,
have
a
huge
budget.
Let's
build
a
new
website,
oh
by
the
way,
but
we
need
the
content
from
over
there
and
that's
a
much
better
fit
for
you
know
feets
or
migrate,
or
you
know
any
other
tool
you
can
use
to
like
extract
translation
are.
C
B
Update
script
should
like
batch
appropriately
and
it'll
just
carry
on
for
as
long
as
needed.
The
one
thing
that
I
would
say
is,
if
you
have
to
do
continuous
integration
right
like
if
you
have
a
dev
site
and
a
website,
and
you
your
website
is
getting
lots
of
content
all
the
time
you
need
to
like
keep
importing
all
the
content
from
your
live
site.
That
might
be
a
circumstance
where,
like
you,
wouldn't
want
to
run
the
upgrade
on
all
of
the
content
all
the
time.
C
A
B
Hoping
it'll
get
better
I
feel
like
every
time.
I
do
it.
It
gets
slightly
easier.
Part
of
that
is
that
more
modules
reported
and
more
people
are
using
that
pre
pass
and
they're
getting
their
kinks
worked
out.
I
would
hope
that
we
would
also
do
more
for
backwards.
Compatibility
like
between
backdrop,
one
and
backdrop
I
would
love
to
see
you
and
that
green
and
everything
just
works,
but
there's
some
logs
and
your
watchdog
there,
like
hey
by
the
way
you
might
want
to
change
these
things.
B
That
would
be
my
ideal
scenario,
but
yeah
I
feel
like
that.
We
I
would
also
like
to
see
like
it
may
be
a
better
user
interface
for
some
of
this
stuff.
So
it's
not
so
like
command
line
copy
like
like.
We
have
a
pretty
good
interface
for
doing
module
updates
through
the
we
have
a
questionably
good
interface
module
of
a
food
UI.
We're
gonna.
Have
this
core
self
update
feature.
B
I
would
love
to
see
some
way
that
you
could
do
major
version
upgrade
using
that
also,
but
we
probably
won't
work
on
that
until
we
get
to
the
back
job
or
shortly
before
backup
yeah.
That's
that's
what
I'd
like
to
see.
I
also
think
like
this
is
the
way
I
do
upgrades
it's,
because
it's
the
way
I've
done
Drupal
upgrades
since
four,
seven
or
whatever
I
don't
know.
That's
the
only
way
to
do
it
like
I.
B
Just
config
work
does
theme
work
as
imported
modules,
work
whatever
and
by
the
end,
I'm.
Very
confident
that,
like
the
core
update,
is
good
because
I've
done
it
eight
times,
and
so
if
it's
also
like
a
confidence
thing
where
I
feel
like
there's,
probably
some
people
there
like
I'm
just
gonna,
do
the
whole
thing
right
on
my
new
code
and
then
I'm
just
gonna
run
the
whole
thing
and
then
I'll
just
do
bug
it
and
maybe
that's
better.
B
D
A
Well,
we've
been
over
an
hour
any
final
questions,
or
should
we
we
can
wrap
it
up.
Jen
I
think
is
going
to
be
around
tomorrow
afternoon
again
for
our
office
hours
as
well,
hopefully,
maybe
a
couple
of
other
people
from
the
background
community.
So
if
you
are
working
on
a
upgrade
and
or
planning
one
and
you'd
have
more
specific
questions
that
would
feel
better
for
that
kind
of
format.