Advanced search  

News:

cpg1.5.46 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter recently discovered vulnerabilities. It is important that all users who run version cpg1.5.44 or older update to this latest version as soon as possible.
[more]

Pages: [1]   Go Down

Author Topic: Fix for bridge to vBulletin with custom MySQL port  (Read 587 times)

0 Members and 1 Guest are viewing this topic.

Phill Luckhurst

  • Administrator
  • Coppermine addict
  • *****
  • Country: gb
  • Offline Offline
  • Gender: Male
  • Posts: 4357
    • Windsurf.me
Fix for bridge to vBulletin with custom MySQL port
« on: November 20, 2016, 11:16:02 PM »

From Sven Meeus via GitHub
 
I have been running a website with a Coppermine 1.5 to vBulletin bridge integration for over 10 years now. I recently switched to a HAProxy setup for my MySQL connections, running on a different port then the standard 3306.
 This doesn't work with the current Coppermine vBulletin bridge, unless the following fix is applied to bridge/vbulletin30.inc.php (line 64)
64c64
Code: [Select]
<                     'host' => $config['MasterServer']['servername'] ? $config['MasterServer']['servername'] : 'localhost',
---
>                     'host' => $config['MasterServer']['servername'] ? $config['MasterServer']['servername'] . ($config['MasterServer']['port'] ? ':' . $config['MasterServer']['port'] : ':3306') : 'localhost' . ($config['MasterServer']['port'] ? ':' . $config['MasterServer']['port'] : ':3306'),
207c207

It would be nice to see this implemented, not only in 1.6 but also backported to 1.5.

I would assume the same fix could also be applied to other bridges, I leave it at your discretion to implement those.
Logged
It is a mistake to think you can solve any major problems just with potatoes.
Pages: [1]   Go Up
 

Page created in 0.06 seconds with 20 queries.