do you mean you have updated to 1.2.1 and still have the issue?

or you have the issue in 1.1.2 but don't want to update currently?

We have the issue in v1.1.2.

As you said you would releas a v1.1.2 update in a couple of days,we want to resolve the issue in 1.1.2.

For,now we can not perform update to v1.2,is there any special patch for v1.12?

Hmm, no you will have to go through all commits to find the specific commit that has the fix for it, as it's made quite a long time ago i can't tell which commit it was anymore

I would simply recommend to update to the latest version (as your quite a bit behind currently).

It seems that there is noway to install a specific patch?

As you know reinstalling SolidCp is a complicated process. I have over 300 domains and databases on my server.  Can you give me a full detailed manual for upgrading SolidCp?

Server reliability and customers domains setting are very important for us

Thanks

Well for this issue i'm fairly sure it was a SQL variable that was off, only problem is finding the fix means going long back between tons of commits which makes it nearly impossible to find.

to update there's several methods, an automated powershell method, aswell as manual ways here:  https://solidcp.com/kb/update/