►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
B
It's
a
small
consistency
problem
with
the
API
when
we
create
categories
bar
when
we
rename
your
alkies
of
categories,
our
customer
would
like
to
get
redirects
automatically
created
similar,
like
you
can
do
in
the
admin
panel
by
checking
that
box
create
permanent,
redirect
for
the
old
URL
key
and
it
is
working
for
four
products,
but
not
for
categories
I.
Think
it's
not
hundred
percent
a
deaf
experience
issue.
It's
more
like
you
know
a
regular
feature
request,
but
it's
because
it's
all
related
to
the
API
I
thought
it
might
fit
in
here
yeah.
B
C
D
B
D
D
A
A
D
A
D
D
B
Not
yet,
but
as
old
old
pull
request,
which
which
tries
to
fix
it
in
a
way
which
is
not
backward-compatible,
because
they
just
creates
a
redirect
for
all
the
all
the
your
elke
changes
which
might
not
be
wanted.
Sometimes,
though,
we
don't
have
yet
a
fix
for
the
save
revise
history
flag
to
use
the
flag
but
yeah.
We
I
mean
if
it's,
if
it's
trashed
and
if
it
has
chances
to
be
much,
we
would
try
it
probably
to
make
a
pull
request
because
the
other
option
would
have
been.
B
D
A
C
D
Know
it's:
no,
we
still
don't
have
support
of
products
attributes.
We
said
some
JSON
string
and
we
try
to
work
with
it.
I
cannot
say
that
it's
bug
it's.
It
should
be
for,
but
like
feature
request
with
some
scheme
proposal,
and
we
need
to
approve
this
him,
this
architect,
identities
architect
with
our
product
owners
and
honestly,
it's
not
look
like
so
easy
because
need
to
introduce
him
to
introduce
a
cup
of
resolvers
and
we
need
to
follow
some
backwards-compatible
way
so
for
me,
first
of
all
need
to
have
some
scheme
proposal.
A
D
I
see
proposal
solution,
but
there
are
a
couple
of
some
terminology
issue
which
can
be
rise
visit,
so
I
am
sure
that
it's
so
easy
to
implement
and
we
can
involve
its
I
can
assess
it.
It's
not
technical
issue.
First
of
all,
we
need
to
move
this
tickets
to
our
functional
issues
triage
and
we
need
to
involve
our
product
on
our
missions,
because
maybe
a
mistake
may
be
no.
They
was
going
to
work
on
improvements,
Hema
related
to
product
attributes,
but
fortunately
I
did
know
status.
So
for
me
it's
not
technical
issue.
D
D
D
D
D
D
A
A
D
A
D
A
D
D
Let's
I
can
I
would
recommend.
I
would
ask
to
provide
more
clear
step
because,
honestly,
a
little
bit
dot
understand
all
of
step
like
when
you
try
to
do
in
translation.
Does
that
means
that
you
have
called
on
some
store,
but
at
I
said?
Is
there
a
description
like
I
have
even
tried
to
add
in
price
to
the
payload
data
is
a
great
current
price.
This
steel
also
don't
work
and
three
steals
the
price
to
zero.
So.
D
D
A
D
Hard
because
if
it's
related
to
first
step,
it's
really
if
it's
related
to
scripts
that
perform
for
the
following
turn
skin
disorder.
So
maybe
it's
some
problem
how
you
create
this
product
in
this
case?
It's
no
so
big
priority.
If
you
talk,
if
you
can
change
price
during
product,
updating,
it's
my
big
priority,
so
for
me
it's
have
to
provide
at
this
moment
cos.
If
you
can't
change
price,
it's
looks
like
p1
at
least
p1.
D
A
D
Import
new
products
update
existing
product,
but
how
is
this
Porto
post
create
if
you
create
this
product
with
some
script?
Maybe
you
are
you
mrs.
Thomson
in
this
script,
so,
first
of
all
to
YouTube
great
to
know
like
I
create
product,
we
add
mint
panel
or
I,
create
product
create
default
import
and
after
that,
I.
D
Need
to
help
a
lot
how
how
did
create
this
product
need
to
help
a
lot?
Maybe
there
was
some
mishap
disease
during
this
bellow,
so
at
this
moment
I
cannot
understand.
Is
it
miss
configuration
or
it's
real
big
problem
is
price
because
after
steps,
one
two
three
product
existed
DB
but
unfortunately
steps
one
two
three,
it's
not
clear:
okay
example
import
products
via
REST
API.
We
need
to
help
a
lot.
How
do
you
try
to
do
this?
Maybe
there
are
it's
real
issue
with
some
steps.