How to let it work on the same domainname after database changed

I think you'll have to slow down :-)

There are some things which aren't clear to me. Was it ever working on your system? That is, were you ever able to create a sub-site, and open it?

It sounds like it's not working now, but it's not clear what. You created a new site? If so was there an error (please report it)? Is it when you visit the new site, that you can't see it? If so, what error do you get? Is it a drupal page or an apache error?

So for my own issue. Is this something that's a possible bug in the system (from running update?), or are you trying to recover from your mistake of bringing up a system for test_ instead of test2_?

If the latter, then one possibility is that multisite_manager won't try to create a database if a record already exists in the main site. probably the best thing to do is fix this in the database level. rename all your tables manually or remove the record without the database from the main site.

I'm still confused exactly how you're setup and what the issue is. is abcdefg.com the main site, or another subsite? Can you be more precise about what "it doesn't do anything" means?

--> trying to recover my mistake ;) (therefor i chose support request) ;)
Ah, I knew those categories were for something ;)

--> where's that record? could i simply kill it an try again?
if killing it is an option, then yes, just kill it and try again. The danger is that it could (probably will!) delete your 'good' test_ site. if you can build both, then go ahead. The other way would be to edit the record for hijklmn.com, to set the prefix as test2_ (even though it wasn't when created). After you do that, and then save, then you MIGHT (no guarantees) not delete your other test_ site.

The record exists in the table {drupal_site} (with whatever prefix is in the main site).

well, it's difficult to document something well, when you don't know what kinds of issues people have. I will own up to the state of currently poor documentation, though.

your suggestion about doing something in settings.php is more than possible as well. In that case, make an exception for the db_prefix when the $my_site_base is 'test2'.

In general, you shouldn't be changing the prefix, etc for each site. This is how you may have gotten in this mess. Instead it should be standardized, and the account you create a sub-site should not have advanced access to sub-site creation.

maybe you could email me your settings.php file and the dump of the {drupal_site} table, if you want more help?

i tried to follow the install instruction steps:
0. i went and uploaded & unzipped into modules
1. i was unable to find any apache config file on my web hosting so that's up in the air - maybe you're just used to calling some file an apache config, but i need the exact literal name and it's possible location.
2. copied code and added to the bottom of ./sites/default/settings.php
3. I don't know what a symlink is

maybe you can help?
thanks!

update -

i chose the alternate for .htaccess option since i don't know if and can't find the apache config
looked up what a symlink is, downloaded a program to give me a ssh connection,
found the terminal on my computer, successfully connected to my website, but NOW what?

i type your symcode in my terminal and it bashes me since it's still my computer and doesn't know why i'm giving it strange directories

finally figured out how to make my terminal ssh to the website's terminal, but when i type in the commands and directories i get the same bashing.
what do i do now? haven't done any unix for twelve years, and it was frightening back then...

hope the next release of the multisite manager can make this process less painful!

thank you in advance for help with any of this backend programming hand holding. seriously.

please don't hijack other people's Issues. your issue is independent and should be a different Issue.

Basic information about unix commands, apache file locations, and directory management is way beyond the scope of multisite manager's documentation. These questions should be directed to your host provider and/or your apache/linux distribution documentation/communities and/or google.

From what it sounds like, the .htaccess option is probably best for you. Ask your host provider whether you have shell access, and how to connect to your host (and CD to the drupal directory). Alternatively, they should be able to explain to you how to create a symlink through any web admin interface if they do not provide shell access.

Most of your questions are impossible to answer outside of knowing which linux distribution you have and how your host provider has setup apache, so if I sound dismissive please realize it's because I cannot answer your questions, not because I don't want to.

i thought this was the forum - i didn't realize i was "hijacking" someone else's issues.