paulgweb

I too am interested in this! I need to hide everything on the blog except from registered users… and this blog is hosted on my site.

I didn’t find any WP-endorsed privacy-related plugins that would do what besaprocurement mentioned (that the hosted WP offers to wp users) except on:

https://wp-plugins.net/?filter=privacy

There’s one there that’s perfect… anyone use?

Hi HandySolo, I think the site’s instructions are not quite comprehensive enough. And your comment didn’t clarify anything for me personally – here’s why:

I installed the software on my own hosting account, and in the process I made a WordPress support login.

I know that WordPress.COM is “not my blog”. I also know that I don’t have a WordPress.com “account” because (as I see it, maybe wrongly) I don’t *want* a blog on WordPress; it seems odd that i would need to create an account i don’t plan to use in order to get an API Key for use on my site.

But the instructions at: https://wordpress.com/api-keys/
do say I can “leverage the power of WP.com while still hosting your blog elsewhere” — so perhaps I must have an account after all. But wait… why would that be? I’m not hosting on WordPress.COM… and will I need a new account for every blog i install elsewhere?? Hmm, unclear.

So logically I then think maybe I can get an API Key for MY blog via my Support identity, which is more universal. But no; there’s no mention of the API Key in my profile.

Which leads me to this forum to see what other users did *before* I create an unwanted .COM account.

See the issue? Where is it explained that a Support account is insufficient to get an API Key, or what to do about one API Key handling several installations?

This said, i’m creating an account now ??

…
Okay, I’m back – i see now that wordpress.com offers an option to just create a *username* (not a blog) for seemingly just this purpose of getting the API Key. Nice…. everything was thought of.

Now the instructions could be updated a tiny bit!

Hope this post helps someone.

kristinaheinen, you would add the new API key in the plugin section of your Admin area. I’m trying to activate Akismet, and i see a “tab” for Akismet Configuration.

Hi all, my host found the cause! He confirmed that localhost was indeed correct (subdomains are still local to the server)… the issue was that PLESK 7 was truncating the db user password to less than 14 characters, and my pwd was 16 characters. Apparently a bug in Plesk, since it didn’t flag that long pwd as prohibited.

Now the blog is working fine!

Thanks everyone…

hi all, glad to see your input… to answer the questions: yes, the db user is correctly set up. phpmyadmin confirms this. the control panel is PLESK 7 (not cPanel) and so makes it very easy to set up db users. I can vouch that the db is usable. I’ve added tables to it to test.

So… the mystery remains. I think it’s localhost vs the subdomain. but i don’t know what WordPress is expecting for the server path. ??

my host reseller doesn’t have weekend tech support, so i’m on my own for now.

Line 5 is the database pwd entry… i wonder if you must have a password? that’s unusual (to me) to not have that required.

Too bad: changing the config to:

define('DB_HOST', 'mysite.com');

didn’t work…

Thanks very much for the help! i think the subdomain that my control panel Plesk7 creates is a “true” subdomain, not a dns trick.
so, on the server, there is an outside-the-httpdocs directory called “subdomains”, within which is a unique “httpdocs” directory. This subdomain cannot be viewed by pointing to domain.com/blog.

Hmm, no, there seems to be no problem with a database named “WordPress”… i just renamed to “blog”

The server is running MySQL 4.1.12

Another thought: is there a problem with naming the database “WordPress” ?

Hi DianeV – looks like we both replied at the same time… and said the same thing. Can you look at my support question too?

I see, your script is complaining: “or we can’t contact the database server at remotemysqlhost.”

maybe your host was saying to change the install.php server address to “localhost”

Are you referring to the setting needed in “install.php” ?

If this helps, phpinfo reports:

https://blog.saltwater.org/testphp.php

There seems to be an ioncube loader module. is that year-old bug still affecting WP ?