Permissions problem when bridged with SMF2 RC3 Permissions problem when bridged with SMF2 RC3
 

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

Main Menu

Permissions problem when bridged with SMF2 RC3

Started by lurkalot, April 26, 2010, 10:11:03 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

lurkalot

I have the following issue after bridging coppermine and SMF2 RC3:

I can't seem to set permissions in the gallery using a custom group.  Even though I have set my group called "Support" so they can't have a personal gallery, cannot rate/ or comment/ send ecard etc, they still can.

Coppermine install: http://cctestsite.info/gallery/
Bridging app install: http://cctestsite.info/forums/
Coppermine version: cpg1.5.3 RC
Bridging app version: bridge/smf10.inc.php 1.5.3 revision 6985  unmodified
Test user account: support / support

BridgeManager settings:
Bridge app URL:  not sure what this is.
Relative path to your bridge app's config file:  ../forums/
Cookie name or prefix:  in Coppermine =  cpg15x  in SMF2 RC3 = SMFCookie805
Use post-based groups?:  yes
SMF2 RC3 and Coppermine have seperate databases.

This issue is in addition to another bridging problem with the member list, here, Critical error when clicking Memberlist
Running SMF 2.1.4  / Tinyportal 3.0.1, bridged with Coppermine 1.6.25, plus cpmfetch 2.0.0

Joachim Müller

Least restrictive permissions apply: make sure that the members of the group you refered to aren't members of another group that has got more permissions. Usually is the case for the group "registered".

lurkalot

Thanks for the reply Joachim.

I've checked and double checked all my settings to no avail.   I only have 4 members, one is a mate of mine, two of them are me for testing and your test account, support.

I deleted the original support account and started over again to get my head around the permissions.  I'm stumped now to be honest. :(

Do any of you guys have the same setup to test with?  I'd be quite happy to grant your support team admin access if need be.

As both softwares are release candidates, I'm not sure if it's SMF, Coppermine, or the bridge file to blame.  (or me being an idiot of course).  ???
Running SMF 2.1.4  / Tinyportal 3.0.1, bridged with Coppermine 1.6.25, plus cpmfetch 2.0.0

lurkalot

Quote from: lurkalot on April 26, 2010, 07:17:02 PM

Do any of you guys have the same setup to test with?  I'd be quite happy to grant your support team admin access if need be.


SMF2 RC3 bridged with Coppermine 1.5.3 RC  running on separate databases.
Running SMF 2.1.4  / Tinyportal 3.0.1, bridged with Coppermine 1.6.25, plus cpmfetch 2.0.0

lurkalot

Ok, here's an update.  Tried everything I could to resolve this within my SMF / coppermine permissions to no avail.

So un-bridged and re-bridged again, and permissions are working as expected. 

Sorry for wasting everyone's time.  :-[
Running SMF 2.1.4  / Tinyportal 3.0.1, bridged with Coppermine 1.6.25, plus cpmfetch 2.0.0