labanex

This is an idea that has just come to me. One, I was thinking that Mamboserver.com people should get involved with your project. I love what you guys are doing, because right now, I am running seven different CMSs on my server. Five of them are Drupal.org and two or them are Mambo 4.5 1.0.9 (Spider).

One of them is:
http://www.ymp.net/antonio/says/

but all of the CMSs are reachable by going to:
http://www.ymp.net/

I am new at CMSs and I really like how Mambo works, better than Postnuke. Drupal is cool and easy to use, but lacks in some many other things.

My idea is to get with Mambo folks to create the main Mambo site by itself but include the capability to creating other sites using your methods. Since the SQL scripts are uploaded to the server anyway, I believe that creating a new site would be as easy as simple untarring the site to whereever the user wants it.

In TELNET or FTP program, the user would create the directories to where he or she wants the second site. Having the mambo installation tar.gz file already on the server makes it easy for the server to access the file. So there is no need to install or upload the second site. The user will then log into in the backend, then select in the menus exactly where he/she wants the second site, by inputting system pathways and URL pathways. At a single click, the server untars the files into that directory. The backend also installed the database, as well as the prefixes renamed as specified by the user/admin.

The main site, http://www.website.com/ (which is site1) is the main Mambo site where all of the main files are located. http://site2.website.com/ or http://www.website.com/site2/ is the second site, but the untarred files are just enough to run the Mambo site. It may not need all of the DOC files, SQL files and such. Get what I am saying. In the same process, the modules, mambots and component files are not transferred either. Since those files never change, site2 can use those files from site1 to work in site2. Remember, site2 just has the basic mambo files.

The database is handled by the different sites, but the modules, components and such are not. In both site1 and site2, as well as siteX (any number of sites), there should be a selection which module, component and mambot is to operate within each individual site, keeping these files in site1. Remember, since these files are database driven, all site2 does is operate from site1 and give that information in return.

Maybe something else can be added. The user can have a choice of whether or not site2 operates from site1 or independent.

Now if site3 is on a different IP address, meaning it has no connection with site1's localhost DB, then there is another option that can be selected. Mambo can FTP the already installed tar.gz core from the site1 server to site3 server, automatically setting site3 up to operated from site1's DB.

I know the whole idea behind mamsites is to have as many mambo's running, but using one database for usernames and permissions. I really think that if Mambo was written from the core, this can work better, especially if the core is installed from the get-go.

Another thing you want to consider is that if several people have a collectiive of five Mambo's running and they decided to migrate their user database, is there a way to do so without messing up the database. Another script can be added, if the user chooses, to include a migration form, asking for their username for each Mambo and then making the change automatically. If that person is not signed with one Mambo but is with the other four, the user can select which one they want to work for all. Sort of how Yahoo! did Yahoo Clubs and Yahoo Groups.

I really believe that Mambo 5.0 can include this feature, or at least, create two different Mambos. One for independent operation and one for multiple site use. However this idea can be used, I would love to see these features.

What do you guys think about this idea? I know I have typos and bad grammer, but the idea is to help Mambo become the premier CMS over any others. I will try out mamsites to see how it works. I can not wait to get into it. Antonio...

tonyskyday

This type of thing is already on the roadmap for Mambo 5.0 actually. 5.0 will be a major rewrite of the Mambo code based around an XML-RPC engine that will bring an unprecidented level of flexibility to this system.

labanex

Thanks for your reply. I did succesfully integrate two already operation sites:
http://www.ymp.net/antonio/says/ (antonio/says)
http://www.ymp.net/us/sj/ (us/sj)

They both use the exact same user tables in my database. It took my five hours, but I successfully did it. First, I shut down both sites n the configuration.php file. Then I change the name of the config file to _configuration.php so in case it messed up, I can reverse back to it. Then I copied the config file to insert the three lines that was instructed by the mamsites install instructions. I did that for both sites, including rewriting he name prefixes for both sites.

Then I went into phpMyAdmin Exported the database for the antonio/says which had more members than us/sj. I started a new database and renamed the prefixes to "says_" and renamed the user tables as instructed to "all_".

I Exported the database of us/sj and opened the us.sql file. I did a Find/Replace... command to find all "mos_" to replace with "us_". Then I added the commands to add the usernames of "us_" to add them onto the "all_" so that the users can be added to the usertables for both sites. I did this because I did not want to loose the members of us/sj I then imported the us.sql file into the antonio/says database. Now I have "us_", "says_" and "all_" in one database now. I then had to delete the usertables for "us_", because I forgot to do that in the us.sql. No problem, because the users of us/sj were integrated right into antonio/says as well, and vice versa.

I then uploaded the two directories as specified by the install instructions from the mamsites.zip file. I rewrote both the configuration.php files to turn my site back on and BANG. I logged in and both sites recongnized it. I logged off and both sites recongnized that. I then logged in under my wife's username and again, it worked. Logged off, and both sites responded with no problems.

NOW, there is a problem though. Both sites ADMIN top menu is gone. It logs in without any problems, but the ADMIN MENU is nowhere to be found. I viewed the source and I noticed that the MENU is a java script that the Mambo folks using the "JSCookMenu.js" script. The script looks okay, but I do not know JAVA so I can not really troubleshoot it. I compared the code that is generated when I logged into antonio/says and with my wife's site which is indenpedently ran:
http://www.serenitee.com/metamorphosis/

I still can not find any discrepencies in the menu code. Somehow, I am not picking up the mistake in the code and I think it has something to do with the new files I uploaded. I tried copying the files from the orginal Mambo script replacing the adminstrator/components/com_fig/*.* files, but that did not seem to help, yet my site is running flawless in the front end and seems to work in the backend, if only I had the TOP ADMIN MENU BAR.

What do you think it can be? I looked all over different forums and I found that no one else had this problem. What can I do to fix this problem? If I successfully integrated two already in operation Mambo sites, but yet my menu bar is gone, there is something I did wrong or something in the mamsites.php file that is not right. Any help will be appreciated. But, I do want to keep my sites the way it is, I just do not have backend access right now. Thank you, Antonio...
http://www.ymp.net/

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 installed three Mambo sites on my server, all three (alpha, beta, and gamma). 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."

I installed the three sites with only three modications. I renamed the prefixes except "all_" to "says_", "us_" and "main_" in respective order. The DB was uploaded and the configuration.php file for all three sites has also been changed. Reading the instructions over and over again and visiting forums like this and Mambers.net, I have not found a solution. No one else is having this problem, or at least not reported.

Before, when I installed Mambo, I was able to install the hack onto two different sites and it worked. The sites were already running independently and I managed to get them to work. The only problem was that the toolbar in the admin menu was not appearing. I was told by someone to install the TRIHACK instead. So I deleted the sites I had and installed the hack straight from the zip file with the exception of changing the prefixes and installing them in different directories on the server.

All three sites are working with the hack I guess because all three of them are doing the exact same thing. But I believe that there is a piece of code that is not working right. I download the trihack from mamboforge.

What can I do to fix this? Can anyone help, thanks!!!? Any help can be appreciated.

mmx

There has to be a prefix naming error in one or more of the tables or in one of your configuration.php files. Otherwise, you are not using the mambo.php and database.php provided with the tripack. Be sure that the sessions table has the all_ prefix.

You might note that their is a Sticky message dedicated to mamSites support under the Developer Discussions area.

__________________
mmx