BTW,
I just installed the rhuk_milkyway and it has the same problem. My set up of Multisites is this:
1 master site in the root with the multisites component in DB1
1 slave site with fresh install without multisitescomponent in DB2 (with the standard symbolic links)
Template for copying the 1st slave into DB3 (for all the other slaves)
The images folder and the template folder are copied to the slaves (from the root folder).

Point is that in the copied template folder of every slave there's a params.ini. After changing the colors in the templatemanager of the specific slave site, a params_{site_id}.ini is made. With the correct altered color info. But the old params.ini is still selected for the params variable in the template...

Cheers,
Guy

The files created with the site_id is correct.
Your problem is potentially in your selfmade template that does not READ the appropriate params_{site_id} one.

So you have to check which is the extension that read this params file.
Perhaps like with Rocket Themes and also Yoo Themes, you bypass the standard joomla reading of the params ini files and have re-implemented your own stuff.

NO, As posted previously this template uses the default params.ini It is a bug in your patches which I do not have the time to figure out what patch is causing the issues.

Hi: I had a similar problem with this structure, and was able to solve it this way:

- slaves sites installed on a subdomain like... www.slave.master.com
- documentroot of each slave... public_html/multisites/{site_prefix}
- deploy tempates folder:: {site_dir}/templates
- Folders and Files: templates as copy file or folder

In that case I needed all the templates to be copied so each user owner of slave could modify it.
I´ve realized that with this structure, JMS creates the file... params_site-id.ini which is ok, but I had a problems with params because the template was not detecting it, even saving them correctly on the params.ini file.

So I had to edit the pacth by changing this...

administrator/components/com_templates/controller.php

On that file, I´ve found...

params_' .MULTISITES_ID .'.ini

and replaced it to just...

params.ini

(think was just on 2 lines)

And it started working. I dont know if it works on other enviroments or how the complete structure works, but in this specific case it helped me after hours of trying to find a solution. Hope this is usefull for everybody, greetings from Argentina...

I had the same problem and this also worked for me. Great solution, thanks for posting.
Greeting from Bogota.

The problem is that you have somewhere in your own made template read directly the params.ini file. If this is the case you have to patch it to read the mutlisites "params.ini" file.
Normally the params.ini files is already read when you are in the template and you should not have to read it yourself.