| Re: Multisite HACK for 2.2.3 Final |
| by zimmi88 on 2006/9/3 5:12:22 PLEASE READ NOTE AT BOTTOM BEFORE MAKING ANY CHANGES TO YOUR FILES! Okay, from my analysis of the file, the lines that need to be changed in the kernel/profilefield.php file are: LINE 343: Change le="color: #000000"><?php if (!empty($force_update) || !file_exists(XOOPS_CACHE_PATH."/profilefields.tmp")) { to le="color: #000000"><?php if (!empty($force_update) || !file_exists(XOOPS_CACHE_PATH."/profilefields".XOOPS_SITE_ID.".tmp")) { LINE 346: Change le="color: #000000"><?php $s = implode("", @file(XOOPS_CACHE_PATH."/profilefields.tmp")); to le="color: #000000"><?php $s = implode("", @file(XOOPS_CACHE_PATH."/profilefields".XOOPS_SITE_ID.".tmp")); LINE 567: Change le="color: #000000"><?php $fp = fopen(XOOPS_CACHE_PATH."/profilefields.tmp", "w"); to le="color: #000000"><?php $fp = fopen(XOOPS_CACHE_PATH."/profilefields".XOOPS_SITE_ID.".tmp", "w"); PLEASE NOTE!!! These changes have not been thouroughly tested yet. Please check them on a test site first before taking them live! I make no gurantees that this will work correctly or suit your needs. Also, if you do test these changes, please post back with your results. Thanks! -zimmi88 =) |
| Re: Multisite HACK for 2.2.3 Final |
| by zimmi88 on 2006/8/19 7:06:47 The only contrasting file between Multisite 2.2.3 and the upgrade from 2.2.3a to 2.2.4 is kernel/profilefield.php. I'm finishing up a crosscheck right now between the files in 2.2.3, 2.2.4, and Multisite. As far as I can see, there are three lines that need to be edited for compatibility. I'll finish the crosscheck up and see if I can find someplace to put the file up at tomorrow. When I have it up and I have thouroughly tested it for blatent errors, I'll let ya all know. -zimmi88 =) |
| Re: Multisite HACK for 2.2.3 Final |
| by sceilig on 2006/6/18 18:30:57 Hmm....I would probably spend ages trying to get it working for 2.2.4 and with much hairpulling and frustration. I would be willing to pay for someone to get the multisite hack working for my system and with what my needs are for managing many subsites from a single source code with either 1 or many databases. Either that or to contract out a project where someone builds a multisite module for my needs at whatever the going programming rate is for creating such a module/hack. Anyone interested or know of a good place where I could post this project to XOOPS freelancers? |
| Re: Multisite HACK for 2.2.3 Final |
| by draj on 2006/6/18 12:28:16 Hallo! Quote:
Did you find the files that have changes in it from 2.2.3? Sinply use a good utility to compare the files. I suggest: http://www.Ghisler.com First mark the files. You can have the 2.2.4 on the left and new/multisite files for 2.2.3 on the right. Then apply the changes or transport the changes marked in the red, as vilualised in the windows/total commander. There are some files that have very minimal difference. I do not have the time to play with it, unfortunately. But if you are successful, do post it here. However, as said by the developers, I would rather wait for the newer 2.3 and hope that there is also a multisite. I can however imagine, that the concepts in many areas would be different and using multisite wold paralise you in the update that you cant update at all. |
| Re: Multisite HACK for 2.2.3 Final |
| by sceilig on 2006/6/18 9:02:32 Deepy or anyone else, I realize this thread is for the Multisite Hack for 2.2.3 but what changes would need to be made to get it to work for 2.2.4. I think you mentioned that for instance the includes/common.php file would have changes but I couldnt really see the changes between the common.php for the Hack and the one for 2.2.4? I would dearly love to be able to get the hack working for 2.2.4 so I can start to experiment with just how far I can go with the hack i.e. managing hundreds of sites from a single source code, handling the domain parking correctly and tweaking the table sharing to meet my needs. If I knew what the steps were in how the hack/xoops interprets a site/subsite and serves up the relevant content, I could probably delve into the code myself and find out where my problem is. |