It looks like you have BE 1.6 on the hiking site. The BE code has two parts to it -- the BE Core and the Web files. When you download BE, there's the "Web" version and the "Source" version. The Source version has the
BE core files in it (and the normal Web files too -- it has everything). Do you have Visual Studio (I think you do, but can't remember).
Assuming you do have VS, the Source version of BE 1.6 is on the
Downloads page. When you extract the ZIP, the BE core files are in the "BlogEngine.Core" folder. In the root folder that you extract, is a file named "BlogEngine.sln" (the VS solution file). If you open this SLN file
in VS, there should be 2 projects in the solution. 1 project is the Core project and the other project is the Web project (the same two projects I mentioned above). You should be able to see both projects in the VS Solution Explorer window (top
Within the Core project is Post.cs. In that file is the "IsVisible" property where the code change will be made. Assuming you get this far (!), and are able to make the code change, you can build the solution under the Build menu.
When you build the solution, it will create a new BlogEngine.Core.dll file in the /bin directory. You can confirm this by checking the timestamp of the BlogEngine.Core.dll file.
If you get stuck, I could make this modification for you and send you the DLL, but it might be most ideal if you could get it working on your end in case you want to make future changes (e.g. change or add the "private" category), or for when you
upgrade to a newer version of BE someday, making this change again to the Post.cs file for the new BE version will be necessary.
It would be nice if this customization could be made outside the BE core. An extension doesn't really fit the bill since it could prevent someone from reading the content of the private blog posts, but the private blog posts existence and their titles
would still be visible (only the content could be hidden). The "IsVisible" property is really a perfect place for this logic.