# Website bug dumps server internals

**URL:** https://forum.troygrady.com/t/website-bug-dumps-server-internals/68667
**Category:** Site Feedback
**Created:** [August 14, 2023, 3:04pm UTC](https://forum.troygrady.com/t/website-bug-dumps-server-internals/68667 "2023-08-14T15:04:33Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![hddharvey](https://forum.troygrady.com/letter_avatar_proxy/v4/letter/h/779978/32.png) [@hddharvey](https://forum.troygrady.com/u/hddharvey)
#### Post date: [August 14, 2023, 3:04pm UTC](https://forum.troygrady.com/t/website-bug-dumps-server-internals/68667/1 "2023-08-14T15:04:34Z")

</div>

When I load the page from this link:

> **[What is two-way pickslanting, and how does it work?](https://troygrady.com/2018/07/16/what-is-two-way-pickslanting-and-how-does-it-work/)**
>
> You may have heard the term two-way pickslanting in discussions of picking mechanics, particularly when it comes to scale playing. It may even be what brought you to Cracking the Code in the first place. Indeed, the discovery that elite players...

I get the following dumped at the top of the page:

[edit: redacted - TG]

I think I’ve seen this on other pages, but not sure. The full text was:

[edit: redacted - TG]

---

<div class="post-metadata">

### Author: ![Prlgmnr](https://forum.troygrady.com/user_avatar/forum.troygrady.com/prlgmnr/32/740_2.png) [@Prlgmnr](https://forum.troygrady.com/u/Prlgmnr)
#### Post date: [August 14, 2023, 4:14pm UTC](https://forum.troygrady.com/t/website-bug-dumps-server-internals/68667/2 "2023-08-14T16:14:33Z")

</div>

looks like someones cracked the code

---

<div class="post-metadata">

### Author: ![Troy](https://forum.troygrady.com/user_avatar/forum.troygrady.com/troy/32/3_2.png) [@Troy](https://forum.troygrady.com/u/Troy)
#### Post date: [August 14, 2023, 6:33pm UTC](https://forum.troygrady.com/t/website-bug-dumps-server-internals/68667/3 "2023-08-14T18:33:03Z")

</div>

Thanks for reporting — we know what this is, and will take a look. It’s not malicious, it’s just a reporting setting we have turned on for debugging.

---

<div class="post-metadata">

### Author: ![hddharvey](https://forum.troygrady.com/letter_avatar_proxy/v4/letter/h/779978/32.png) [@hddharvey](https://forum.troygrady.com/u/hddharvey)
#### Post date: [August 16, 2023, 2:39am UTC](https://forum.troygrady.com/t/website-bug-dumps-server-internals/68667/4 "2023-08-16T02:39:40Z")

</div>

Also, FYI.

One of the videos on the page I linked does not load for me:

 ![image](https://forum.troygrady.com/uploads/default/original/2X/2/28b15953b91e5aa6bcfb1d27928885dbeb859534.jpeg)

---

<div class="post-metadata">

### Author: ![TheRealMikeD](https://forum.troygrady.com/user_avatar/forum.troygrady.com/therealmiked/32/12366_2.png) [@TheRealMikeD](https://forum.troygrady.com/u/TheRealMikeD)
#### Post date: [August 21, 2023, 3:29pm UTC](https://forum.troygrady.com/t/website-bug-dumps-server-internals/68667/5 "2023-08-21T15:29:49Z")

</div>

As a career web developer, I’ll tell you that this is the server-side scripting language (PHP in this case) hitting an error and printing the error messages to the output. There is a setting that can be changed in the server configuration to prevent error messages from being displayed to end-users (which is recommended, because sometimes the information can be potentially used by those with malicious intentions). You can still configure error messages to be logged to a file on the server, so that the web dev team can see them and use them for debugging.

Cheers!

---

<div class="post-metadata">

### Author: ![Troy](https://forum.troygrady.com/user_avatar/forum.troygrady.com/troy/32/3_2.png) [@Troy](https://forum.troygrady.com/u/Troy)
#### Post date: [August 22, 2023, 7:18pm UTC](https://forum.troygrady.com/t/website-bug-dumps-server-internals/68667/6 "2023-08-22T19:18:58Z")

</div>

Thanks for the note! I’m aware of said settings, I just have verbose output turned on so that we (or users) will notice when these errors pop up in older code and we can fix them. As far as we know we have found and fixed all of these on the actual instructional site pages. So this shouldn’t be an issue for anything important on the site.

This instance is a blog post, where, for various Wordpress-y reasons some of our code won’t work correctly if someone isn’t logged in. It’s a lower prority but we’ll get to it.

TLDR all the items linked to in this blog post actually work fine if you just go directly to those pages. Their display in the blog post itself may be a little janky but that’s just a display issue.

---

<div class="post-metadata">

### Author: ![TheRealMikeD](https://forum.troygrady.com/user_avatar/forum.troygrady.com/therealmiked/32/12366_2.png) [@TheRealMikeD](https://forum.troygrady.com/u/TheRealMikeD)
#### Post date: [August 22, 2023, 9:02pm UTC](https://forum.troygrady.com/t/website-bug-dumps-server-internals/68667/7 "2023-08-22T21:02:50Z")

</div>

Cool, as long as you’re aware of it. Just keep in mind that WordPress sites are under attack from hacker bots all the time ([the stats are fairly dumbfounding](https://www.wordfence.com/blog/2023/08/demystifying-the-wordpress-vulnerability-landscape-2023-mid-year-wordfence-intelligence-wordpress-vulnerability-review-leveraging-chatgpt/#attack-data)). If there’s even a little bit of seemingly harmless info about your server internals visible to attackers, “it is possible, however unlikely, that they might find a weakness, and exploit it.”

Cheers!
