►
From YouTube: Adobe Stock Integration public meeting 14th July 2020
Description
Adobe Stock Integration public meeting 14th July 2020
A
Okay,
so
I
think
we
have
one
demonstration
planned
for
today
on
our
agenda,
but
first
of
all,
okay.
So
if
you
would
like
to
show
your
pull
requests
or
demo
anything
or
if
you
want
to
bring
up
any
question.
B
B
B
I
mean
that
the
f
open
function
or
just
if
open
function
cannot
read
the
file
yeah.
It's
like
very,
very
strange,
but
I'm
working
on
this.
A
C
B
B
Yeah
yeah
and
this-
and
I
also
tried
to
add
debug
message
which
should
help
us
to
analyze
why
we
can
reproduce
this
error
on
the
magenta
test
environment.
But
I
understood
that
this,
the
the
error
we
already
see
on
the
allure
screen
screenshot,
is
completely
what
we
get
from
the
place
you
mentioned,
so
you
are
not
able
just
to
open
the
stream
and
that's
all
why.
B
Okay,
I
will
send
you
the
debug
of
trace,
and
maybe
this
can
highlight
something
for
us,
but
I
have
one
question
or
maybe
a
request.
I
I
know
that
we
have
to
use
the
http
pro
http
interface
and
http
driver.
I
mean
just
http
driver
interface,
sorry,
just
the
end
of
the
day,
a
little
bit
harder
to
concentrate,
but
may
we
have
a
discussion
in
future
and
where
you
can
explain
me
why
we're
not
able
to
use
the
file
system
driver.
I
know
that.
B
Okay,
okay,
then
just
ignore
it
yeah,
so
maybe
that's
all
about
the
stuff.
So
I
continue
my
odc
to
old
decision.
I
hope
that
the
solution
will
be
soon.
I
also
decided
to
ask
to
help
some
of
our
contributors,
and
maybe
we
will
have
a
brainstorm
about
this
problem,
and
you
know
when
you
have
two
or
maybe
three
heads
it's
much
better
than
one.
B
So
this
top
issue
is
the
next
topic
in
our
internal
discussion
with
the
team
cool.
Thank
you.
Yes,
that's
all
from
my
site
and
also
I
updated
the
pull
request
with
the
error
message
which
we
previously
get
when
we
close
the
sign
in
window
yeah.
I
saw
your
comment
yesterday
implemented
changes
and
ask
for
review.
A
Oh
okay,
yeah
thanks
for
that
actually
straight
away,
I
think
we
should
like
we
are
returning
the
error
that
the
notification
window
was
closed,
and
that
is
okay.
From
my
point
of
view,
the
thing
is
that
we
shouldn't
display
the
server
yes
should
be
where
in
the
place
where
we,
where
we
are
displaying
the
error
not
exactly
in
the
model
level.
A
B
You
mean
that
we
should
lift
there,
then
promise
reject
with
a
new
error.
Object
like
it
is
right
now,
but
we
shouldn't
show
this
error
in
another
place
right.
A
D
Okay,
can
I
I
have
one
question:
there
is
one
more
bug
in
this
like
if
you
look
at
the
issue
which
is
mentioned
on
this
pull
request,
there
is
a
this
image
model
is
not
a
function
that
because
there
is
no
image
model,
so
it's
also
like
must
be
fix
it
or
remove
it
or
display
it
like
a
message
in
the
grid.
D
Yeah,
because
the
image
model
there
is
like
is
there
any
fails,
is
a
promise
like
catch
any
fails.
It
pushes
the
message
to
the
image
model
messages
component.
Instead
of
and
this
listens,
I
shall
actions
like
displayed
in
the
media
gallery
grid.
So
we
will
never
see
the
this
error
because
it
will
be
displayed
on
the
image
model
on
the
adobe
stock.
B
B
E
If,
if
the
image
file
doesn't
have
any
text
and
if
you
try
to
save
it,
doesn't
give
any
validation
error
and
it's
just
save
an
empty
empty
field
as
a
null.
So
I
just
only
added
a
simple
validation,
and
here
is
the
implementation.
I
just
added
only
a
mage
validation
in
the
included
image,
validation
and
just
added
a
condition
to
check.
If
is
the
form
is
valid
or
not?
If
it's
valid,
then
it
will
save
that
detail.
E
Otherwise,
it
will
show
the
error
that
this
field
is
required
and
another
changes
I
made
is
the
data
validate
in
which
I
just
added
a
required
proof
for
the
name
for
the
image
title
and
another
pull
request
is
regarding
the
improvements.
E
First,
one
is
the
type
of
adding
the
file
name
in
the
image
detail,
page,
basically,
initially
that
the
file
name
is
not
present
in
the
email
detail
page.
So
I
just
added
a
file
name
here
and
just
and
another
is
the
simple
rename
of
the
name
field
into
a
title,
which
is
also
simple,
and
here
is
the
implementation.
E
This
is
the
implementation
of
the
file
name
path
like
here.
For
this
one
file
name
is
not
in
the
mediator
page,
which
I
have
added
using
just
that
image
and
just
get
path
here
in
the
image
data.
We
are
getting
the
path
we
have
just
patched
that
and
displayed
here
in
the
data
bind
as
a
text
and
another
one
is
just
a
simple
one,
which
is
just
change
the
name
into
a
title.
E
Sorry,
I
am
not
able
to
show
the
demo
right
now,
because
my
local
instance
having
some
issues
so
maybe
next
time.
Oh
that's
it.
A
D
Screen
yeah:
are
you
able
to
see
my
screen?
Yes,
so
the
first
thing
is
I
want
to
demonstrate
is
a
mass
action
mod
for
the
new
media
gallery.
It
was
already
merged.
So
basically
we
have
one
button
now
the
light
images
when
we
click
on
that
button.
We
activate
like
mass
action
mode.
D
There
is
no
any
like
other
sections
like
view
details
on
three
dots
and
there
is
only
check
boxes
to
the
select
items,
images
to
delete
and
there
is
like
count
which
images
you
are
selected
and
the
one
button
for
like
delete,
batches,
which
you
must
selected
and
also
when
we
click
to
delete
selected
it
like
count
and
if
the
images
was
used
in
category
or
product.
D
It
also
displays
that
this
images
is
used
in
count
of
categories
or
product
or
something
like
that,
and
also
like
displays,
a
warning
that
you
really
want
to
delete
and
when
you
click
to
delete
it
like
say
that
assets
have
successfully
deleted
and
yeah.
Probably
that's
it
for
a
section
mode
and
another
like
pull
request,
is
a
asset
filter.
D
I've
lamented
this
filter
for
our
grid
that
we
support
is
like
categories
products,
page
and
block
as
well
this
one
because
they
tested
some
issues
with
a
long
name
category
so
can
be
ignored.
There
is
the
asset
filter.
D
This
is
basically
a
ui
select
component
of
magento.
So
when
you
type
like
image
title,
it
sends
request
to
get
images
from
the
service
which
retrieves
the
assets
to
do
this
functionality,
because
we
have
only
like
services
to
get
assets
by
id
or
by
us
and
we
are
not
able
to
like
search
artists
assets.
D
So
I
introdu
I
was
introduced.
The
service
search
assets
service,
which
works
with
search
criteria.
So
it's
like
out
of
the
search
criteria,
parse
set
it
and
return
the
assets
search,
result
interface
and
it
work
as
the
media
gallery
as
a
stable,
like
have
no
any
resource
model
or
modules.
So
I
created
a
custom
parser
for
the
search
criteria.
D
It
works
the
same
as
like
or
search
criteria.
It's
like
converts
the
search
to
the
sql
link,
and
for
that
we
can
retrieve
like
this
result
so
like
we
can
get
some
image.
D
This
one
apply
this
filter
and
we
will
see
the
category
where
the
image
is
used,
so
the
same
behavior
will
be
to
the
products
grid
as
well
and
other
pages
blocks.
Yeah,
probably
that's
it.
E
Yeah
yeah,
I
have
a
question
regarding
the
first
pull
request
like,
which
is
the
mask,
delete
one.
I
think
we
can
improve
the
messages
in
which
the
asset
has
been
deleted.
You
can
also
add
the
number
of
the
assets
which
are
which
has
been
deleted
like
if,
like
in
their
delete
pop-up
box,
you
showed
that
there
is
like
number.
Four
number
number
of
images
of
port
should
be
are
deleted
and
the
same
should
be
in
the
delete
message.
I
guess
so.
What's
your
thought
about
that.
D
Yeah
sure
why
not
we
can
like
cards
what
which
count
of
images
was
deleted.
So
that's
that's
not
true.
E
D
No
that's
base
select
component,
okay,
select
yeah,
you
can
see.
C
D
Like
introduce
it
in
the
ui
xml
listing
and
use
it
yes,
also
components.
A
Yeah
thanks
shankar
nice
suggestion.
Would
you
like
to
create
an
issue
for
that
idea
in
in
the
repo.
A
Yeah
four
cool
solid
features:
there:
mass
action,
mod
for
media
gallery
the
search
service
like
the
pioneering
in
parsing
search
criteria
without
collection,
processor.
There,
category
grid
that
magento
have
never
seen
and
the
asset.
A
A
Great
any
snails
we'd
like
to
discuss
today.
C
Maybe
I
can
share
the
implementation
for
the
get
asset
id
by
content
field
implementation
that
is
in
progress,
but
I
think
we
can
share
that.
Oh
it's
almost
done.
A
C
Yeah
yeah
cool.
Let
me
share
my
screen.
C
Okay,
so
I'm
just
gonna
introduce
very
quickly
what
was
the
the
problem
here
that
we're
trying
to
solve?
There's.
There
are
two
tasks
here,
which
is
to
introduce
enable
filter
on
media
gallery
and
introduce
the
store
view
filter
on
media
gallery
the
they
are
quite
similar
and
the
challenges
are
also
very
similar
here.
C
We
we
basically
had
to
create
a
filter
that
will
filter
assets,
but
from
conditions
that
will
be
applied
on
content
so,
for
example,
enable
filter
when
you
filter
by
enable
or
disable
you
are
actually
filtering
by
the
the
content
status,
not
the
asset
status
so
and
same
thing
here
on
story
view.
C
Some
entities
like
products
and
categories
they
are
not
directly
assigned
to
starview
products,
are
assigned
to
websites
and
categories
are
assigned
to
store
and
and
then
we
have
blocks
and
pages
that
are
assigned
to
story
views.
So
we
had
to
create
like
a
flexible
structure
that
will
allow
different
implementations
for
this
and
also
allow
as
an
extension
point.
If
another
content,
another
entity
is
introduced
to
the
content
to
the
media
content
module.
So
people
will
be
allowed
to
to
to
use
this
feature
and
add
their
implementation
there,
as
well.
C
C
Yeah,
so
very
quickly,
as
I
said,
there
are
two
filters
that
have
to
be
done
here,
it's
by
status
and
by
store
view
so
to
achieve
the
the
goal
with
status
for
catalog
and
products.
They
are
both
eav
entities
and
both
of
that
information
is
on
eav
attributes.
C
So
we
create
an
implementation
of
the
get
asset
ids
by
content
field
interface
for
eav
content
field.
So
by
dixml
we
can
inject
the
parameters
here
and
we
work
for
catalog
for
product
and
category
to
find
the
status
or
any
other
uav
attribute
that
we
are
looking
for
as
far
as
store
implementation
because,
as
I
said,
category
is
assigned
to
store
and
product
to
stop
to
website.
We
had
to
create
different
implementations
and
but
all
of
them
have
the
same
behavior,
which
is
receive
the
field
and
the
value
and
returns
an
array.
C
As
far
as
for
cms
same
situation,
here
store
and
pay
for
pages
and
blocks,
the
star
implementation
are
a
little
bit
different.
So
we
have
separate
those
and
content
field
for
status
and
it's
using
this
implementation
so
and
then
to
wrap
it
up
very
quickly
to
not
get
too
long.
We,
we
have
a
composite
class
that
we
inject
the
all
the
class
from
the
other
modules
and
that
is
going
to
be
used
on
the
implementation
of
the
filter,
which
is
not
done
yet
and
just
I
just
created
very.
C
Quickly,
example
to
show,
but
essentially
what
it
does,
the
filter
uses
the
interface
which
receives
the
the
composite
and
then
it
just
filters
by
the
feud
and
gets
the
as
a
result.
He
gets
the
ids
and
then
you
filter
by
the
table.
Ids,
that's
that's
pretty
much
it
so
like
a
demo
of
that
would
be
like
we
can
filter
by.
I
don't
know
status
and
it
looks
at
as
I
said,
it
looks
at
the
status
of
the
the
content,
that's
being
used.
C
And
then
you
can
drill
down
and
filter
by,
I
don't
know
star
view
so
and
and
it
just
drills
down.
So
in
the
end
we
are
searching
by
ids
for
these
filters,
but
we
there's
this
extension
point
where
we
allow
other
contents
to
be
introduced
and
then,
if
your
content
has
status
or
story
is
assigned
to
start
view,
you
can
introduce
to
these
filters
or
you
can
even
create
your
own
filter
by
another
type
of
field.
I
don't
know
if
you
want
to
filter
by,
I
don't
know
color
or
something
like
that.
A
A
A
And
and
see
you
next
week,
yes,
thanks
for
your
participation,
thanks
for
contribution
to
the
project
and
have
a
nice
week.