# Posts are Broken **URL:** \ **Category:** Website & Forum Feedback\ **Created:** [July 30, 2020, 5:03am UTC](https://forums.powershell.org/t/posts-are-broken/14735 "2020-07-30T05:03:16Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![rob-simmers](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.powershell.org/rob-simmers/32/1010_2.png) [@rob-simmers](https://forums.powershell.org/u/rob-simmers)\ **Post date:** [July 30, 2020, 5:03am UTC](https://forums.powershell.org/t/posts-are-broken/14735/1 "2020-07-30T05:03:16Z")
There is some HTML or something breaking the posts as the post options (e.g. Edit, Quote, Report, etc) are missing and text is not wrapping in the posts. Here are some examples, but it’s popping up more. [https://powershell.org/forums/topic/1-gettype-vs-1-gettype/](https://powershell.org/forums/topic/1-gettype-vs-1-gettype/) [https://powershell.org/forums/topic/skip-after-an-empty-row-in-csv-ignore-last-n-rows-after-a-blank-row-in-csv/](https://powershell.org/forums/topic/skip-after-an-empty-row-in-csv-ignore-last-n-rows-after-a-blank-row-in-csv/) Started within the last couple of days from what I can tell. ---
**Author:** ![krzydoug](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.powershell.org/krzydoug/32/1008_2.png) [@krzydoug](https://forums.powershell.org/u/krzydoug)\ **Post date:** [July 30, 2020, 5:09am UTC](https://forums.powershell.org/t/posts-are-broken/14735/2 "2020-07-30T05:09:00Z")
I was just coming to make the same complaint. I can’t see all the text on the posts. It’s been like that on mobile for a long while, and as Rob said just the last few days everywhere else. The site has been offline off and on as well as slow, which I assume you guys are already aware of. ---
**Author:** ![grokkit](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.powershell.org/grokkit/32/970_2.png) [@grokkit](https://forums.powershell.org/u/grokkit)\ **Post date:** [July 30, 2020, 7:56am UTC](https://forums.powershell.org/t/posts-are-broken/14735/3 "2020-07-30T07:56:50Z")
[pre tag test](https://powershell.org/forums/topic/pre-test/) [code tag test](https://powershell.org/forums/topic/code-test/) So, this issue seems to be due to the interaction between the WordPress theme used for the forum, and the implementation of the **pre** tag. The full quote should be: > Well, the way they make shows is, they make one show. That show's called a pilot. Then they show that show to the people who make shows, and on the strength of that one show they decide if they're going to make more shows. Some pilots get picked and become television programs. Some don't, become nothing. She starred in one of the ones that became nothing. (thanks to [slipsum.com](https://slipsum.com/)) Specifically, the CSS for the preformatted block is not set to wrap text, so it creates a side-scroll area, but when this area is displayed in a post on the forum it extends the display width of the post. However, the theme has a maximum display width that is smaller than the now expanded post width, and as a result the right side of the post is hidden and inaccessible. Interestingly, the side-scroll area also seems to have a width limit, and (at least for me) the entire line isn’t visible, which makes **pre** even less useful. Recently, the plugin that was being used to apply color highlighting and line numbers in the preformatted blocks on our forum was deprecated due to lack of updates, and WordPress removed it, so we no longer have that functionality. Effectively, this means that **pre** and **code** behave the same, except for the text wrapping. For the moment, I recommend using **code** and not **pre** , but be aware that text wrapping will break up long lines (visually). Text in a **code** block _should_ still copy & paste normally - the line breaks added for display on the forum shouldn’t end up in copied text. James has been looking for a plugin to replace the lost functionality, but hasn’t found one yet. ---
**Author:** ![kvprasoon](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.powershell.org/kvprasoon/32/4449_2.png) [@kvprasoon](https://forums.powershell.org/u/kvprasoon)\ **Post date:** [August 2, 2020, 12:56am UTC](https://forums.powershell.org/t/posts-are-broken/14735/4 "2020-08-02T00:56:48Z")
awesome, Thanks @grokkit for nailing it down… ---
**Author:** ![rob-simmers](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.powershell.org/rob-simmers/32/1010_2.png) [@rob-simmers](https://forums.powershell.org/u/rob-simmers)\ **Post date:** [August 6, 2020, 5:16am UTC](https://forums.powershell.org/t/posts-are-broken/14735/5 "2020-08-06T05:16:44Z")
There is still some odd stuff going on. Posted here and I put some JSON outside of the pre tags and there is no Edit for me to fix it. [https://powershell.org/forums/topic/add-json-file-content-to-invoke-webrequest-post-comment/](https://powershell.org/forums/topic/add-json-file-content-to-invoke-webrequest-post-comment/) ---
**Author:** ![rob-simmers](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.powershell.org/rob-simmers/32/1010_2.png) [@rob-simmers](https://forums.powershell.org/u/rob-simmers)\ **Post date:** [August 6, 2020, 7:14am UTC](https://forums.powershell.org/t/posts-are-broken/14735/6 "2020-08-06T07:14:42Z")
Using the code tags I still have content not in the tags not being wrapped, just the text explanation provided is not wrapped. There is no Edit to open the post to see a pre tag was used by mistake: [https://powershell.org/forums/topic/duplicate-names-in-csv/#post-247555](https://powershell.org/forums/topic/duplicate-names-in-csv/#post-247555) ---
**Author:** ![grokkit](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.powershell.org/grokkit/32/970_2.png) [@grokkit](https://forums.powershell.org/u/grokkit)\ **Post date:** [August 6, 2020, 7:43am UTC](https://forums.powershell.org/t/posts-are-broken/14735/7 "2020-08-06T07:43:07Z")
This thread was actually broken by kvprasoon’s reply on Aug 6 (#247408), which had **code** tags inside of **pre** tags. Removing the **pre** tags fixed the thread. ---
**Author:** ![grokkit](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.powershell.org/grokkit/32/970_2.png) [@grokkit](https://forums.powershell.org/u/grokkit)\ **Post date:** [August 6, 2020, 7:48am UTC](https://forums.powershell.org/t/posts-are-broken/14735/8 "2020-08-06T07:48:43Z")
The top block of code in this response was in **pre** tags. Unfortunately, once this problem occurs the only way to edit the post is via the WordPress admin control panel, which means that only moderators will be able to fix it. ---
**Author:** ![grokkit](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.powershell.org/grokkit/32/970_2.png) [@grokkit](https://forums.powershell.org/u/grokkit)\ **Post date:** [August 10, 2020, 1:09pm UTC](https://forums.powershell.org/t/posts-are-broken/14735/9 "2020-08-10T13:09:52Z")
Ok, so there’s a little more to this problem. It’s not just long lines of code in **pre** tags, it’s any unbroken string that exceeds the maximum display width of the forum theme. In this post, a long hyperlink (google search results) breaks the width: [https://powershell.org/forums/topic/meeting-room-statistics/](https://powershell.org/forums/topic/meeting-room-statistics/) And in this test it’s just a long string of text without spaces: [https://powershell.org/forums/topic/div-overflow-hyperlink-test/](https://powershell.org/forums/topic/div-overflow-hyperlink-test/) (it doesn’t matter if bbPress parses it as a hyperlink or not) I tried to adjust this by applying [word-wrap: break-word;](https://www.w3schools.com/cssref/css3_pr_word-wrap.asp) to **div** , **span** and **p** blocks, and even by placing the text inside a table cell, but basically bbPress filters out any CSS that isn’t explicitly allowed (which is good). As you can see in the first example, there are normal use cases that cause the problem, which means that it will occur repeatedly until we deal with it. [We also aren’t the only ones to experience this](https://wordpress.org/support/topic/how-to-best-fix-run-off-text-on-mobile-view/), though so far I haven’t found any really good solutions. I think there’s two possible fixes: 1. Change the forum theme to one that properly handles long strings. Unfortunately, this would probably require testing different themes at random until we find one that works. 2. Edit the CSS for our current theme to apply word wrapping. This should actually be relatively easy, but it would mean that the theme has custom code which would need to be manually carried forward during updates (or we just maintain our own local theme going forward and don't update it from external sources). ---
**Author:** ![rob-simmers](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.powershell.org/rob-simmers/32/1010_2.png) [@rob-simmers](https://forums.powershell.org/u/rob-simmers)\ **Post date:** [August 12, 2020, 8:35am UTC](https://forums.powershell.org/t/posts-are-broken/14735/10 "2020-08-12T08:35:21Z")
There definitely some odd stuff still going on. If you look at this post: [https://powershell.org/forums/topic/remote-query-for-certain-software-and-get-csv-output/](https://powershell.org/forums/topic/remote-query-for-certain-software-and-get-csv-output/) I used the code tag and it breaks the content is pieces jacks up my pretty indention. Cannot make updates as the Edit is unavailable in the menu. ---
**Author:** ![system](https://us1.discourse-cdn.com/flex019/uploads/powershell/original/1X/385e4f9fe133561ad30a814262fe0e0ae6bc3ef0.png) [@system](https://forums.powershell.org/u/system)\ **Post date:** [August 17, 2020, 5:38am UTC](https://forums.powershell.org/t/posts-are-broken/14735/11 "2020-08-17T05:38:08Z")
We are still looking into why this is happening. We were hopeful that we could just add text wrapping into the css file but that wasn’t’ the case at all. We are testing on our staging website. ---
**Author:** ![system](https://us1.discourse-cdn.com/flex019/uploads/powershell/original/1X/385e4f9fe133561ad30a814262fe0e0ae6bc3ef0.png) [@system](https://forums.powershell.org/u/system)\ **Post date:** [August 17, 2020, 7:08am UTC](https://forums.powershell.org/t/posts-are-broken/14735/12 "2020-08-17T07:08:25Z")
I think we have a solution in place and from what I have spot-checked word wrapping is now working and the PowerShell code is being highlighted correctly. Let me know if you all see otherwise.