Basic new field publication confusion

Hi,

I have created a new field with a "video" type.
The field is connected to a specific tab.
I have declared "Yes, on one line" in the "Show on Profile" as well as in the "Show on Profile Edit" dropdown field menus

I have two issues :

1/ I can uplooad a video when editing my profile, but once done, nothing appear when consulting my profil : why is that ?

2/ I can't find where to declare the access levels for this field: I need to tune precisely who can edit this field and who can see videos published by my users.

Any help ?

Thanks,

1/ I can uplooad a video when editing my profile, but once done, nothing appear when consulting my profil : why is that ?

Is the tab visible on your profile? Once uploaded you should see it on your profile on the tab the field is on.

2/ I can't find where to declare the access levels for this field: I need to tune precisely who can edit this field and who can see videos published by my users.

Only way to do that is CB Privacy and/or CB Conditionals. Fields themselves don't have access controls.

Hi Krileon,

yes the tab is published, BTW I have other fields published in it that are visible, but not this one

I look with the privacy plugin to tune access level then.

Strange, it's possible the video uploaded isn't encoded right and won't playback in HTML5. Turn on linking in your video field if you haven't already and try linking a youtube video to see if that displays fine.

I found where the problem was from.

The size of the file was biger than the one authorized for this VHOST (upload_max_filesize specific low value in the the apache vhost configaration file).

May be a suggestion : that could be usefull if cb could return an error message when this happens...

Thanks anyway.

It gets rejected by the server before it even reaches CB in that case. We can't add an error for that. This causes the _FILES global to be empty so it's as if you never uploaded anything and unless the field is marked as required it's not going to error for an empty video field. Best way to avoid this is to be sure to properly configure the maximum file size validation rule on your video field so CB can attempt to validate its size before it is sent to the server using client side validation.