Jetpack: VideoPress Videos assigned to User ID 0

Created on 21 Nov 2018 · 10Comments · Source: Automattic/jetpack

When uploading a video to VideoPress via the three methods listed at https://jetpack.com/support/video-hosting/#uploading-videos the upload is assigned to User ID 0, meaning no author is attributed to it:

screen shot 2018-11-21 at 11 20 53 am

When videos are uploaded to WordPress normally _without_ VideoPress, they are properly attributed to the user who uploaded them:

screen shot 2018-11-21 at 11 22 35 am

VideoPress [Pri] Low [Status] In Progress [Type] Bug [Type] Happiness Request

Source

macmanx2

All 10 comments

Also reported here:
https://github.com/Automattic/sensei/issues/2128

And in #10536

jeherve on 21 Nov 2018

👍1

If I am right JetPack API doesn't use Author ID. Therefore it is set to 0.
We are waiting to be fixed. :)

amroland on 10 Dec 2018

We received another report of this issue. Any update or anything we can recommend in the meantime?

RCowles on 1 Apr 2019

👍1

I am afraid we have made no progress on this just yet; the latest can be found here: pxWta-N4-p2

anything we can recommend in the meantime?

If this conflicts with the Sensei plugin, this can help:
https://github.com/Automattic/jetpack/issues/10536#issuecomment-435899602

If this conflicts with another plugin, I am afraid there is no workaround right now.

jeherve on 2 Apr 2019

Thanks, Jer! It doesn't appear they're using Sensei in this latest report (1886029-zen for reference).

RCowles on 3 Apr 2019

also reported in 2071225-zen

ntpixels on 30 May 2019

User in 2071225-zen noted:

This wasn’t an issue until a day or two ago, users were being assigned to videos without a problem. Why has it all of a sudden changed?

Double-checking on this point as this thread seems to indicate it never worked correctly when it comes to assigning a user.

a8ck3n on 30 May 2019

This issue has been marked as stale. This happened because:

It has been inactive in the past 6 months.
It hasn’t been labeled `[Pri] Blocker`, `[Pri] High`.

No further action is needed. But it's worth checking if this ticket has clear reproduction steps and it is still reproducible. Feel free to close this issue if you think it's not valid anymore — if you do, please add a brief explanation.