# Platoon walls were part of the forums?

**URL:** <https://battlefieldforum.co/t/platoon-walls-were-part-of-the-forums/104688>\
**Category:** PC\
**Created:** [June 17, 2016, 6:06pm UTC](https://battlefieldforum.co/t/platoon-walls-were-part-of-the-forums/104688 "2016-06-17T18:06:00Z")\
**Posts on this page:** 13\
**Page:** 1

<div class="post-metadata">

**Author:** ![esf-BurtHOOLIGAN](https://battlefieldforum.co/letter_avatar_proxy/v4/letter/e/f19dbf/32.png) [@esf-BurtHOOLIGAN](https://battlefieldforum.co/u/esf-BurtHOOLIGAN)\
**Post date:** [June 17, 2016, 6:06pm UTC](https://battlefieldforum.co/t/platoon-walls-were-part-of-the-forums/104688/1 "2016-06-17T18:06:00Z")

</div>

Why? Why are platoon walls locked out now?

---

<div class="post-metadata">

**Author:** ![Verta-Sneaky](https://battlefieldforum.co/user_avatar/battlefieldforum.co/verta-sneaky/32/106021_2.png) [@Verta-Sneaky](https://battlefieldforum.co/u/Verta-Sneaky)\
**Post date:** [June 17, 2016, 6:19pm UTC](https://battlefieldforum.co/t/platoon-walls-were-part-of-the-forums/104688/2 "2016-06-17T18:19:00Z")

</div>

What do you mean by platoon wall? Where people comment?

---

<div class="post-metadata">

**Author:** ![esf-BurtHOOLIGAN](https://battlefieldforum.co/letter_avatar_proxy/v4/letter/e/f19dbf/32.png) [@esf-BurtHOOLIGAN](https://battlefieldforum.co/u/esf-BurtHOOLIGAN)\
**Post date:** [June 17, 2016, 6:25pm UTC](https://battlefieldforum.co/t/platoon-walls-were-part-of-the-forums/104688/3 "2016-06-17T18:25:00Z")

</div>

Yes. In Battlelog on platoon walls. They’re locked now and my guess is platoons were coded as part of the forums which have been locked

---

<div class="post-metadata">

**Author:** ![Verta-Sneaky](https://battlefieldforum.co/user_avatar/battlefieldforum.co/verta-sneaky/32/106021_2.png) [@Verta-Sneaky](https://battlefieldforum.co/u/Verta-Sneaky)\
**Post date:** [June 17, 2016, 6:29pm UTC](https://battlefieldforum.co/t/platoon-walls-were-part-of-the-forums/104688/4 "2016-06-17T18:29:00Z")

</div>

Oh yeah, it looks as if you can post but it won’t let you submit. This new forum is the most boring looking thing I’ve ever seen, it’s just grey. Also, the navigation is horrible, another good job by DICE/EA.

---

<div class="post-metadata">

**Author:** ![esf-BurtHOOLIGAN](https://battlefieldforum.co/letter_avatar_proxy/v4/letter/e/f19dbf/32.png) [@esf-BurtHOOLIGAN](https://battlefieldforum.co/u/esf-BurtHOOLIGAN)\
**Post date:** [June 17, 2016, 6:54pm UTC](https://battlefieldforum.co/t/platoon-walls-were-part-of-the-forums/104688/5 "2016-06-17T18:54:00Z")

</div>

> [@Verta-Sneaky](#):
>
> Oh yeah, it looks as if you can post but it won’t let you submit. This new forum is the most boring looking thing I’ve ever seen, it’s just grey. Also, the navigation is horrible, another good job by DICE/EA.

It’s functionally better than the Battlelog forums. Looks is just css changes which could be changed with a plugin

---

<div class="post-metadata">

**Author:** ![hockeeyyyyyyyyyy](https://battlefieldforum.co/user_avatar/battlefieldforum.co/hockeeyyyyyyyyyy/32/102219_2.png) [@hockeeyyyyyyyyyy](https://battlefieldforum.co/u/hockeeyyyyyyyyyy)\
**Post date:** [June 17, 2016, 6:56pm UTC](https://battlefieldforum.co/t/platoon-walls-were-part-of-the-forums/104688/6 "2016-06-17T18:56:00Z")

</div>

I’m very confused as to what the hell DICE / Battlelog Developers are thinking. It appears to be somewhat similar to a Battlelog ban – everyone is locked out, save for being able to edit their own profiles.

What a joke. How did this get through the QA testings?

---

<div class="post-metadata">

**Author:** ![llll-Rogue-llll](https://battlefieldforum.co/user_avatar/battlefieldforum.co/llll-rogue-llll/32/102653_2.png) [@llll-Rogue-llll](https://battlefieldforum.co/u/llll-Rogue-llll)\
**Post date:** [June 17, 2016, 7:03pm UTC](https://battlefieldforum.co/t/platoon-walls-were-part-of-the-forums/104688/7 "2016-06-17T19:03:00Z")

</div>

wow yep no access to our own platoon wall, maybe they should have just released BF3/4 with the “ole skool” IN GAME Browser, then we wouldnt have needed battlelog in the first place, i guess the platoon page was just on loan …

---

<div class="post-metadata">

**Author:** ![esf-BurtHOOLIGAN](https://battlefieldforum.co/letter_avatar_proxy/v4/letter/e/f19dbf/32.png) [@esf-BurtHOOLIGAN](https://battlefieldforum.co/u/esf-BurtHOOLIGAN)\
**Post date:** [June 17, 2016, 7:11pm UTC](https://battlefieldforum.co/t/platoon-walls-were-part-of-the-forums/104688/8 "2016-06-17T19:11:00Z")

</div>

> [@hockeeyyyyyyyyyy](#):
>
> I’m very confused as to what the hell DICE / Battlelog Developers are thinking. It appears to be somewhat similar to a Battlelog ban – everyone is locked out, save for being able to edit their own profiles.
> 
> What a joke. How did this get through the QA testings?

It got through q and a because it worked at the time. Platoons were just a subsection of the forum code so when the forums got locked the platoons did too. The only difference is the forum text submission field has the option to be functionally removed when a thread is locked and the platoon text field did not which is why it looks functional but it is in fact broken and locked

---

<div class="post-metadata">

**Author:** ![Neubaufahrzeugg](https://battlefieldforum.co/user_avatar/battlefieldforum.co/neubaufahrzeugg/32/102719_2.png) [@Neubaufahrzeugg](https://battlefieldforum.co/u/Neubaufahrzeugg)\
**Post date:** [June 17, 2016, 7:28pm UTC](https://battlefieldforum.co/t/platoon-walls-were-part-of-the-forums/104688/9 "2016-06-17T19:28:00Z")

</div>

qa testing? that exists within anything ea related?  
apparently getting a web designer was also out of ea’s reach, as this forum looks like something made by a disabled monkey

---

<div class="post-metadata">

**Author:** ![HELLGHOST-E6](https://battlefieldforum.co/letter_avatar_proxy/v4/letter/h/ce73a5/32.png) [@HELLGHOST-E6](https://battlefieldforum.co/u/HELLGHOST-E6)\
**Post date:** [June 17, 2016, 7:33pm UTC](https://battlefieldforum.co/t/platoon-walls-were-part-of-the-forums/104688/10 "2016-06-17T19:33:00Z")

</div>

> [@esf-BurtHOOLIGAN](#):
>
> > [@hockeeyyyyyyyyyy](#):
> >
> > I’m very confused as to what the hell DICE / Battlelog Developers are thinking. It appears to be somewhat similar to a Battlelog ban – everyone is locked out, save for being able to edit their own profiles.
> > 
> > What a joke. How did this get through the QA testings?
> 
> It got through q and a because it worked at the time. Platoons were just a subsection of the forum code so when the forums got locked the platoons did too. The only difference is the forum text submission field has the option to be functionally removed when a thread is locked and the platoon text field did not which is why it looks functional but it is in fact broken and locked

That makes no sense though, why use the same class and functions to operate two different things, why not make a derived class from the original and separate the functionality, this is a huge flaw in process design.

---

<div class="post-metadata">

**Author:** ![esf-BurtHOOLIGAN](https://battlefieldforum.co/letter_avatar_proxy/v4/letter/e/f19dbf/32.png) [@esf-BurtHOOLIGAN](https://battlefieldforum.co/u/esf-BurtHOOLIGAN)\
**Post date:** [June 17, 2016, 7:51pm UTC](https://battlefieldforum.co/t/platoon-walls-were-part-of-the-forums/104688/11 "2016-06-17T19:51:00Z")

</div>

> [@HELLGHOST-E6](#):
>
> > [@esf-BurtHOOLIGAN](#):
> >
> > > [@hockeeyyyyyyyyyy](#):
> > >
> > > I’m very confused as to what the hell DICE / Battlelog Developers are thinking. It appears to be somewhat similar to a Battlelog ban – everyone is locked out, save for being able to edit their own profiles.
> > > 
> > > What a joke. How did this get through the QA testings?
> > 
> > It got through q and a because it worked at the time. Platoons were just a subsection of the forum code so when the forums got locked the platoons did too. The only difference is the forum text submission field has the option to be functionally removed when a thread is locked and the platoon text field did not which is why it looks functional but it is in fact broken and locked
> 
> That makes no sense though, why use the same class and functions to operate two different things, why not make a derived class from the original and separate the functionality, this is a huge flaw in process design.

It’s probably the only way they knew how to get the platoons to work.

@Pepe8D Q&A for dice seems to be “does it work in some instances? Yes? OK release it”

---

<div class="post-metadata">

**Author:** ![StarscreamUK](https://battlefieldforum.co/letter_avatar_proxy/v4/letter/s/a87d85/32.png) [@StarscreamUK](https://battlefieldforum.co/u/StarscreamUK)\
**Post date:** [June 17, 2016, 7:53pm UTC](https://battlefieldforum.co/t/platoon-walls-were-part-of-the-forums/104688/12 "2016-06-17T19:53:00Z")

</div>

it has been escalated to the team, other than that, I can’t say anything more.

---

<div class="post-metadata">

**Author:** ![esf-BurtHOOLIGAN](https://battlefieldforum.co/letter_avatar_proxy/v4/letter/e/f19dbf/32.png) [@esf-BurtHOOLIGAN](https://battlefieldforum.co/u/esf-BurtHOOLIGAN)\
**Post date:** [June 17, 2016, 7:59pm UTC](https://battlefieldforum.co/t/platoon-walls-were-part-of-the-forums/104688/13 "2016-06-17T19:59:00Z")

</div>

> [@StarscreamUK](#):
>
> it has been escalated to the team, other than that, I can’t say anything more.

Awesome. Thanks for the feedback
