Forum Replies Created

Viewing 4 replies - 16 through 19 (of 19 total)
  • Give the following codex pages a read; Talking to the Database: The wpdb Class, Creating Tables with Plugins

    The codex is one of the most valuable resources you can have as an aspiring WordPress developer.

    It looks like you set all of the display names to County Clerk (where possible). That’s great and all but display names does just as it says; it just displays. For other users, such as for permalinks, the username is used. As such I can easily tell that one of your authors is named after a certain god of thunder.

    The best you can do is just hide the usernames on the posts or if possible, just use one account(a very low permission account) for posting. Anything beyond that is kind of overkill. A username honestly doesn’t do much for anyone. They still need to figure out the password and if you use a good strong unique password they’ll never figure it out.

    There is no PM system in place here as it dilutes discussion.

    I’m not aware of any long standing exploits regarding usernames being visible. Although admittedly it wouldn’t be much of an exploit. Could you provide a link to your website? I’ll give it a quick look to see if I can see any visible usernames.

    PHP 5.2 is EOL. Why should WordPress devs support something that the PHP devs aren’t even supporting anymore?

    In other words: Force the hosts,

    How is anyone going to do that? At this point if they haven’t upgraded its out of sheer incompetence. They’re not going to upgrade unless developers force them to do so.

    My suggestion: Remove support for PHP 5.2 and if a user complains tell them to change hosts. Hosting companies will upgrade real damn fast as soon as they see their numbers drop.

Viewing 4 replies - 16 through 19 (of 19 total)