Advanced search  

News:

CPG Release 1.6.26
Correct PHP8.2 issues with user and language managers.
Additional fixes for PHP 8.2
Correct PHP8 error with SMF 2.0 bridge.
Correct IPTC supplimental category parsing.
Download and info HERE

Pages: [1]   Go Down

Author Topic: [Fixed]: SMF 2 beta 4 and CPG 1.4.x bridge bug  (Read 13211 times)

0 Members and 1 Guest are viewing this topic.

Dragooon

  • Coppermine newbie
  • Offline Offline
  • Posts: 1
[Fixed]: SMF 2 beta 4 and CPG 1.4.x bridge bug
« on: October 08, 2008, 09:57:19 am »

Hello,
I am new here and sorry if this is already covered

There seems to be a bug in the bridge for SMF 2 and CPG 1.4.x which causes the user to be recognized as a guest even if he/she is logged in.

To fix it
Open smf20.inc.php
Find
Code: [Select]
                if (empty($user_settings['ID_MEMBER'])){Replace it with
Code: [Select]
                if (empty($user_settings['id_member'])){
« Last Edit: October 08, 2008, 06:16:24 pm by Nibbler »
Logged

Nibbler

  • Guest
Re: SMF 2 beta 4 and CPG 1.4.x bridge bug
« Reply #1 on: October 08, 2008, 06:16:15 pm »

Thanks for reporting. Fixed as suggested.
Logged

Ramsesx

  • Coppermine newbie
  • Offline Offline
  • Posts: 1
Re: [Fixed]: SMF 2 beta 4 and CPG 1.4.x bridge bug
« Reply #2 on: January 27, 2009, 01:57:27 am »

Just for your information, this isn't fixed in the latest cpg1.4.19 build.
Logged

Paver

  • Dev Team member
  • Coppermine addict
  • ****
  • Country: us
  • Offline Offline
  • Gender: Male
  • Posts: 1609
  • Paul V.
Re: [Fixed]: SMF 2 beta 4 and CPG 1.4.x bridge bug
« Reply #3 on: January 27, 2009, 02:23:29 am »

Just for your information, this isn't fixed in the latest cpg1.4.19 build.
True.  1.4.19 was released in August and this fix was applied in October.

The fix has been applied to the SVN repository for 1.4.x which means it will be in any release of 1.4 from 1.4.20 and up, whenever they may be.  And it was applied to the SVN repository for 1.5.x (although it was since rendered moot due to code changes).

So you need to apply the fix manually in 1.4.19 and earlier, as you suggested.
Logged
Pages: [1]   Go Up
 

Page created in 0.032 seconds with 19 queries.