jessepacker

Yes. It's a bit arbitrary why portfolio's in 7.1 can't be password protected yet pages can. A entirely plausible usage-case is you have a body of work, not just a single project, that requires it be hidden.
This ought to be addressed.

Yes. It's a bit arbitrary why portfolio's in 7.1 can't be password protected yet pages can. A entirely plausible usage-case is you have a body of work, not just a single project, that requires it be hidden.
This ought to be addressed.

Yes. It's a bit arbitrary why portfolio's in 7.1 can't be password protected yet pages can. A entirely plausible usage-case is you have a body of work, not just a single project, that requires it be hidden.
This ought to be addressed.

Yes. It's a bit arbitrary why portfolio's in 7.1 can't be password protected yet pages can. A entirely plausible usage-case is you have a body of work, not just a single project, that requires it be hidden.
This ought to be addressed.

Yes. It's a bit arbitrary why portfolio's in 7.1 can't be password protected yet pages can. A entirely plausible usage-case is you have a body of work, not just a single project, that requires it be hidden.
This ought to be addressed.

Yes. It's a bit arbitrary why portfolio's in 7.1 can't be password protected yet pages can. A entirely plausible usage-case is you have a body of work, not just a single project, that requires it be hidden.
This ought to be addressed.

Try remove @import code, add this to Code Injection > Header
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.1.1/css/all.min.css" integrity="sha512-KfkfwYDsLkIlwQp6LFnl8zNdLGxu9YAA1QvwINks4PhcElQSvqcyVLLD9aMhXd13uQjoXtEKNosOWaZqXgel0g==" crossorigin="anonymous" referrerpolicy="no-referrer" /> If the site is Personal plan, edit Site Footer > Add a Code Block > Paste this line
<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/font-awesome/6.1.1/css/all.min.css" integrity="sha512-KfkfwYDsLkIlwQp6LFnl8zNdLGxu9YAA1QvwINks4PhcElQSvqcyVLLD9aMhXd13uQjoXtEKNosOWaZqXgel0g==" crossorigin="anonymous" referrerpolicy="no-referrer" /> If it still doesn't work, keep the code & let me know. I will check it again

Yes. It's a bit arbitrary why portfolio's in 7.1 can't be password protected yet pages can. A entirely plausible usage-case is you have a body of work, not just a single project, that requires it be hidden.
This ought to be addressed.

Yes. It's a bit arbitrary why portfolio's in 7.1 can't be password protected yet pages can. A entirely plausible usage-case is you have a body of work, not just a single project, that requires it be hidden.
This ought to be addressed.

Thank you, btw 🙂
 

They use this video tag config, you could try place it on an embed block?
<video autoplay="" loop="" muted="" playsinline="" preload="" disablepictureinpicture="" poster="https://media-www.sqspcdn.com/images/pages/featured-customers/dolly-parton/hero/mobile-poster-2-750w.jpg" src="https://media-www.sqspcdn.com/images/pages/featured-customers/dolly-parton/hero/mobile-2-500.mp4" type="video/mp4"> </video>  

Likely this will filed automatically under "unanswered" but here goes…
A well documented flaw in Squarespace (still) is how video banners don't play on mobile.
Squarespace has a fairly misleading answer to this on their Support site:
The reality is that banner videos won't, under any circumstances, play on a mobile device (that I've seen)
This a huge drawback to the platform that at least two other CMS (Content Management Systems) have seemingly solved — Cargo and WordPress.
Examples of these two working on mobile are here:
https://www.ricardolandim.com/ (WordPress) https://creator-destroyer.com/ (Cargo) Obviously Squarespace provides a host of other wonderful features but as video becomes (I would say is) the common visual language it seems like something they should be able to devote some time and energy to fixing.
Fallback images are a poor substitute, especially if say, you are a video production company. GIFs as Fallback images while clever are large files and won't play nearly as smoothly.
Finally, what's really infuriating is they've gone to the trouble of solving this for their own marketing on their their 5to9 campaign site, the irony being they're selling the service with a feature you can't actually use on it.
C'mon guys.
Rant over.

Yes. It's a bit arbitrary why portfolio's in 7.1 can't be password protected yet pages can. A entirely plausible usage-case is you have a body of work, not just a single project, that requires it be hidden.
This ought to be addressed.

Yes. It's a bit arbitrary why portfolio's in 7.1 can't be password protected yet pages can. A entirely plausible usage-case is you have a body of work, not just a single project, that requires it be hidden.
This ought to be addressed.

Yes. It's a bit arbitrary why portfolio's in 7.1 can't be password protected yet pages can. A entirely plausible usage-case is you have a body of work, not just a single project, that requires it be hidden.
This ought to be addressed.

Yes. It's a bit arbitrary why portfolio's in 7.1 can't be password protected yet pages can. A entirely plausible usage-case is you have a body of work, not just a single project, that requires it be hidden.
This ought to be addressed.

Yes. It's a bit arbitrary why portfolio's in 7.1 can't be password protected yet pages can. A entirely plausible usage-case is you have a body of work, not just a single project, that requires it be hidden.
This ought to be addressed.

Yes. It's a bit arbitrary why portfolio's in 7.1 can't be password protected yet pages can. A entirely plausible usage-case is you have a body of work, not just a single project, that requires it be hidden.
This ought to be addressed.

Yes. It's a bit arbitrary why portfolio's in 7.1 can't be password protected yet pages can. A entirely plausible usage-case is you have a body of work, not just a single project, that requires it be hidden.
This ought to be addressed.

Yes. It's a bit arbitrary why portfolio's in 7.1 can't be password protected yet pages can. A entirely plausible usage-case is you have a body of work, not just a single project, that requires it be hidden.
This ought to be addressed.

Yes. It's a bit arbitrary why portfolio's in 7.1 can't be password protected yet pages can. A entirely plausible usage-case is you have a body of work, not just a single project, that requires it be hidden.
This ought to be addressed.

Yes. It's a bit arbitrary why portfolio's in 7.1 can't be password protected yet pages can. A entirely plausible usage-case is you have a body of work, not just a single project, that requires it be hidden.
This ought to be addressed.