tomwoods

Uh, I don't think it will be that simple, so I would suggest to back everything up in case you want to roll it all back to how it was before.
Hope you get it running!
Tom

labanex

DB function failed with error number 1146
Table 'ymp.session' doesn't exist SQL=SELECT session_id FROM session WHERE session_id=MD5('761e58bfc7a86e5046e2f0df3333610a')
SQL =

SELECT session_id FROM session WHERE session_id=MD5('761e58bfc7a86e5046e2f0df3333610a')

I went ahead and deleted my files on the server and backup the database onto my hard drive. I installed the new database, then installed three Mambo sites on my server, all three (alpha, beta, and gamma). I decided to install a whole new set-up from scratch using the tri-multisite hack zip file. Now the only problem is, I am not successful at all in my installs. As you can see:

http://www.ymp.net/antonio/says/
http://www.ymp.net/us/soulmates/
http://www.ymp.net/

Both sites come up with the same error as shown above. In the admin area, I log in and it displays "You cannot login. There are no administrators set up."

What can I do to fix this? Can anyone help, thanks!!!?

Mercury

Just curious, with your tripack, what would be needed to be done to add 2 more to that? I want to use 5 sites, and linked, but not related, one using main domain, other 4 using sub-domains.

Also, do i need to dig through and rename everything, like if i want Alpha to be named main, do i need to dig throught the database and change 'alpha' to 'main'?

Thanks.

mmx

The tripack is based on Mambo 4.5.1.0.9. The code changes will not work with 4.5.1.

To remove a site, just delete one of the installations and remove the associated tables from the database.

To rename the existing sites, change the configuration.php file for each site to reflect the desired urls, paths and database prefix. Then rename the table set to match the database prefix.

To add another site, copy one of the existing sites into a new directory. Change configuration.php to account for the new path, url and database prefix. Use something like phpMyAdmin to copy one of the existing table sets within the same database and rename the tables to reflect the new prefix. I tested with as many as 20 sites running from a single database.

__________________
mmx

mmx

For some reason, the session table does not have the all_ prefix. Check the $mosConfig_shared_dbprefix parameter in your configuration.php file. It should be set to all_.

__________________
mmx

Mercury

I looked over the .sql file and saw that it was almost like 3 different DB's (alpha, beta, gamma) , and dug through the config files, and I see exactly what you mean, and how to do it, thanks a bunch.

mmx

It's pretty simple. If you copy the SQL code for a single site multiple times and change the database prefixes, you can create your own SQL file for installing any number of sites.

I have a 4.6 version that needs to be ported back to 4.5.1 but have not had the time to work on it lately. It uses three new tables (mos_sites, mos_tables, and mos_tables_to_sites). Global Configuration includes an extra tab for mapping shared tables. The main site is installed first and additional sites can be installed from Admin. Switching between sites from Admin is handled using a menu similar to the Content menu (dynamically builds a list of sites). setQuery in database.php was changed in 4.5.1, so some experimentation is necessary to make it work.

__________________
mmx

mmx

The attached file is the screen capture image of a hack called sectors that may become the next version of mamSites given no performance or security problems. This is an experiment at the moment, but it appears to have a lot of potential. This was going to be the mamSite version for 4.6 if RAMBO did not enter the scene.

This hack uses a single file set, a single database without multiple table sets, and a separate configuration.php for each sector (site). Sectors are treated as a new kind of element with their own installer. Rather than uploading files, the installer displays a screen that imports the main site's configuration.php data as seed information and allows the file to be saved (with modest changes) as configuration.php for an individual sector. Sectors can be accessed via the menu system using a new Sector menu type that appears in the list when creating a menu option.

This hack adds a sectorid field to certain key tables with a default value of zero (0). The id and sectorid fields of these tables jointly form the primary key for each table. Thus, each element and content item has a unique key relationship formed by its id and sectorid. The Zero value is associated with the main site, so Mambo runs normally with no problems when the $mosConfig_sector variable is set to 0. When set a value other than zero, the new menubar item (and menu) and new cpanel tab appear. These are shown in the accompanying image. When disabled, the menubar and tab disappear.

The mos_sectors table includes fields for associating the sector data with domains and subdomains. The goal is to write a sector map file that could be used to handle domain and subdomain redirection from a single index.php.

The above effectively allows a single site to use multiple instances of elements. Each sector is basically a special interest group within a parent site and can each can have its own content, components, modules, mambots, and templates. The mos_sectors table includes a parentid field for allowing site sectors to be created using a network-like topology. Thus, individual sectors and sub-sectors can have a parent-sibling relationship.

I'm planning to integrate the above with MambelFish to allow optional multilanguage support (ready to go if needed).

Keep in the mind that the above is experimental. Any feedback or advice about possible performance or security problems would be appreciated.

__________________
mmx

leduytien

Finally, I found the perfect solution for my project. Thanks alot.

Is what in the screenshot the current version of Mamsite in MamboForge? (I mean, If I download the current Mamsite from MamboForge, will I get the same result as the screenshot? - because in MamboForge, the version of Mamsite is said for 4.5.1.0.9 but the screenshot is of the Release Candidate version of 4.5.1)

mmx

The screen shot is work in progress. The version on mamboforge will only work with the 4.5.1.0.x series. Different code is required for 4.5.1 because of changes to setQuery in database.php. I may release a version based on the original if the project below does not work as well as expected.

The screen shot shows an experimental version that may be another edition for 4.5.1 based on an entirely different approach.

__________________
mmx