Advanced search  

News:

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

Pages: [1]   Go Down

Author Topic: JUpload, vBulletin, & Coppermine Permission Issues  (Read 4839 times)

0 Members and 1 Guest are viewing this topic.

Forgott3n

  • Coppermine newbie
  • Offline Offline
  • Gender: Male
  • Posts: 13
  • Coppermine User
    • C3Studios
JUpload, vBulletin, & Coppermine Permission Issues
« on: February 10, 2009, 01:49:50 am »

Hello,

JUpload 3.3.1
vBulletin 3.7.4 PL1
Coppermine 1.4.20

We're having some issues with the permissions. I went into the configuration and set the sessionManagement to JUpload. Which makes most sense because we're currently bridged to vBulletin. The problem is that we have Coppermine on bandaids_sunprint database, and vBulletin on bandaids_basilik database. As a result we get this error now when we try to access the upload applet.

http://gallery.avrilbandaids.com/index.php?file=jupload/jupload

Note how its referring to the other database. Any suggestions?
Logged

Forgott3n

  • Coppermine newbie
  • Offline Offline
  • Gender: Male
  • Posts: 13
  • Coppermine User
    • C3Studios
Re: JUpload, vBulletin, & Coppermine Permission Issues
« Reply #1 on: February 10, 2009, 02:14:18 am »

Ahh Sorry for the double post but I just referred to some other people having the same issue. I ran this:

Code: [Select]
-- phpMyAdmin SQL Dump
-- version 2.11.9.4
-- http://www.phpmyadmin.net
--
-- Host: localhost
-- Generation Time: Feb 09, 2009 at 08:08 PM
-- Server version: 5.0.67
-- PHP Version: 5.2.6

SET SQL_MODE="NO_AUTO_VALUE_ON_ZERO";

--
-- Database: `bandaids_sunprint`
--

-- --------------------------------------------------------

--
-- Table structure for table `cpg1411_jupload_session`
--

CREATE TABLE IF NOT EXISTS `cpg1411_jupload_session` (
  `session_id` varchar(40) NOT NULL,
  `jupload_session_id` varchar(40) NOT NULL,
  `ip` tinytext NOT NULL,
  `valid_until` datetime NOT NULL,
  `user_name` varchar(25) NOT NULL,
  `user_data` text NOT NULL,
  PRIMARY KEY  (`session_id`,`jupload_session_id`)
) ENGINE=MyISAM DEFAULT CHARSET=latin1 COMMENT='Used to store JUpload sessions (see sessionManagement JUploa';

--
-- Dumping data for table `cpg1411_jupload_session`
--

On the bandaids_basilik database. It now works perfectly.
Logged
Pages: [1]   Go Up
 

Page created in 0.021 seconds with 19 queries.