[Closed]: Integrating VBulletin 3.6.x header with coppermine 1.4.18 [Closed]: Integrating VBulletin 3.6.x header with coppermine 1.4.18
 

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

[Closed]: Integrating VBulletin 3.6.x header with coppermine 1.4.18

Started by soaker, July 21, 2008, 02:02:28 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

soaker

For the life of me, I cannot get it. I've searched EVERYWHERE. All over this forum. All over vbulletin.org. Hours.

I simply want to know what needs to be done to implement the vbulletin header with coppermine.

Nothing seems to work.

I wont even explain how much i've tried as its gotten me nowhere.

Nibbler

Unless the header has been specifically designed to be embedded into other pages you probably won't be able to accomplish it. Even more so since vb is proprietary software.

soaker

Well, VBAdvanced, which I have, does provide the possibility.

I'm not sure how familiar you are with it.

I'm just hoping someone here has had success incorporating VB headers some way or another. VBadvanced or not.


Nibbler

If you post the relevant documentation for this feature maybe we can help you adapt it for Coppermine.

soaker

Well, I dont even know where I'd start.

Are you familiar with vbadvanced at all? Its purpose?

Basically, it works "around" vbulletin and its database to add features.

You can use it to create pages. The header and footer are default. You then can "inject" code into the template.

Nibbler

I'm not familiar with it. Post a link to its instructions.


soaker

I tell you what nibbler........ nevermind that issue.

How about the "scrolling issue" when viewing individual pictures? (everytime I load an image, it starts from the top, and I have to scroll down)

I've seen the issue posted, tried the solutions in code with an anchor, but had no real success.

Any ideas?

Joachim Müller

We have a strict "one issue per thread" policy that you agreed to respect when signing up. You closed the initial issue - you mustn't create thread drift with a totally unrelated issue. Marking thread accordingly and locking it.