eltioska

Hullo,

Once I’d followed the steps outlined above (@nicholaszen’s recommendation) the main site was fine. However on the other sites I still got the error message (I’m using WP 3.0.3 with MultiSite activated).

I had assumed that since I’m using one database for different sites, setting up the options from the dashboard of the main site was enough. Not so. I went through the menu (in WP dashboard) in each of the sites and set the options for WP-DB manager and now it’s fine.

cheers

Yeah. What I’m looking for is actually a way to change the name of the wp-login.php file, to make access more obscure & unavailable to automated scripts that would look for a wp-login.php file to log in.

Password-protecting the wp-admin folder is mentioned, which is a good step, but not the one I’m looking at.

@t-p Thanks, had already read it but read it again to check: there’s no mentions of changing wp-login.php & whether it’s affected by an update. But it’s good to have it here in an attempt to make this thread more comprehensive ??

Part of question 2 above answered:

2) Will these (wp-login.php & the database prefix) be affected/changed back to standard on a WP update?

The database prefix is not affected on upgrading (I updated to version 3.0.2 today). Maybe this seems obvious to people who know coding & databases inside out but for people like me who’re still learning, it is helpful to state the obvious :o)

I did exactly as ucarmetin above states.

However I have a WP3.02 installation with MultiSite activated*

On the main site’s dashboard/admin area it’s fine.

But on the subdomains’ dashboard I’m still getting the message, even though I did copy the htaccess.txt to the other folder and renamed it to .htaccess

I also left a copy of the file in the plugin’s folder and renamed it .htaccess, but to no avail. Any ideas?

—
*I’m using WP 3.02 (updated a few minutes ago) with MultiSite activated using subdomains, and domain mapping.

Cheers :o)

Whoa … I just sorted it out :o)

Instead of deleting by: hovering over the user and clicking on the “Delete” button/link that appears;

I clicked the checkbox on the side, went to “Bulk Actions”, chose “Delete” from there and clicked on “Apply” button & voila! the confirmation screen came up and the user was deleted :o)

Cheers

Cheers. That’s exactly what I did. However, the user remains there. I tried it countless times (obviously signed in from the other user!)

It’s a bit weird. There’s a Delete button, the page goes into “loading” mode, as if something will happen, and bang! There the user still is. Maybe it’s got a life of its own :oS

Thanks for your help anyways!

Cool, thanks.

Next point: Any idea how to delete the old user? :o)

Cheers. Seems like my worst fears have been unfounded :o)

So it seems that something like the “Permalinks Migration Plugin” https://www.deanlee.cn/wordpress/permalinks-migration-plugin/ would be of use… Or is this risky with multisite?

@diondeville: Hey, I told you I’m new to this! :o))

Many many thanks for the info, both you and andrea_r. I’m really grateful.

On the user & password thingy, I just wanted to make sure I understood correctly. Now that you explained it, of course that the same user will keep the same password (duh! to me). It just seemed weird that the notification said username: username & password: N/A. But now I got it figured, thanks to you. And I hope that your heart’s got no extra worries due to my na?vety ;o)

Just for better future searches, I’m gonna put this text here (they were searches I was making on google):

“setting up wordpress 3.0 multisite on just host”
“wordpress mu on just host””
“how to set up wordpress 3.0 multisite just host”

thanks a lot
peace and ‘armony
ska

@andrea_r: Thanks a lot!

My subdomain is now working!!! I dunno how, coz I didn’t do any further changes. I guess I had to wait a bit for it to be activated.

I’m using Just Host, shared hosting. So far I’m finding them good, with excellent response time to my queries.

This is my first experience with self-hosted blogs, domains and wordpress :o)

A couple of things:

Just Host support wildcard subdomain. I had asked them about that. I read through a lot of tutorials and on this forum (and your wpmu form as well andrea_r – it’s awesome!).

Finally: another question here, I’m afraid:
In the automated email I received upon creating the subdomain, I have a username and no password. Yet when I go to the subdomain.tld.com/wp-admin I have to enter the same username & password as the super-admin… Shall I just leave it as it is or should I set a different user & password for the subdomain (for security I mean)?

Thanks for the wpmututorials.com link. It explains what I was looking for :o)

Cheers for the info & quick reply!

The guide you proposed was very helpful.

I followed what it said to the letter and also what you told me re the wildcard subdomain setup (set as * on public_html/mysite) and the .htaccess file.

Added the edits as on the WP Tools > Network from the Dashboard.

Went to SuperAdmin > Sites > Add New and created a test site,
received the automated emails informing me that the site has been created on test.mysite.com

Went to the link and got a “problem loading page” message from the browser. Can’t even go to the site dashboard (test.mysite.com/wp-admin) coz it’s not loading.

1. Maybe I need to wait for the subdomain to be activated?

2. Should a subdirectory have been created for my test site? Where? I checked the directory public_html/mydomain/wp-content/blogs.dir and there’s nothing in it.