Vbulletin Intergration help needed

Yes, this website is using the "file cache only" option.

Vbulletin Intergration help needed

I might as well just wait until v2 is released.

Out of interest, is the output on the front page cached (when that option is selected) too or does it render the output, even when the information remains unchanged, by querying the DB?

Vbulletin Intergration help needed

Your usergroups seems fine. If you want that I take a look at your installation, please  open a trouble ticket and include all needed login information.

Vbulletin Intergration help needed

I have the following Usergroups, including one custom one at the bottom:

Administrators (id: 6)
Moderators(id: 7)
Registered (id: 2)
Super Moderators 4 (id: 5)
Unregistered / Not Logged In (id: 1)
Users Awaiting Email Confirmation (id: 3)
Users Awaiting Moderation (id: 4)
Banned By Warnings (id: 13)

Vbulletin Intergration help needed

Can you post the Usergroup IDs for registered, administrator, super moderators and moderators.

Vbulletin Intergration help needed

I might well have done, but shouldn't the system look for only the 'Registered', 'admin', 'Mod' and 'Super Mod' ones anyway? Don't want those in the "awaiting registration" group etc. being able to post comments, that's for sure.

Vbulletin Intergration help needed

Did you add any custom user groups in vBulletin?

To view your user groups:
vBulletin CP => Usergroups => Usergroup Manager

Vbulletin Intergration help needed

Yes, I attempted to login using the front page because I wanted to see if forum users could post comments to news items (essential), but no go.

Some of the front page links do connect to the private messages and user CP etc. sections of vbulletin 3.5 now, but the actual user authentication still seems to be based on the CMS's own.

Vbulletin Intergration help needed

I followed the guide, edited the file and uploaded as stated above, but there is no change to my system. The forum URL and CMS login all still remain the systems own and not the forums.

Did you tried to login on the front page? The admin backend will remain on the CMS user table.

Also, all I really want is the news system to replace my existing Coranto output, is there anyway I can just output the main news and headlines to an external .SHTML page (bit of template editing aside)?

No, but it should be quite easy to port an existing Coranto design to the templates. The first HTML part (before the news) of your SHTML page should be copied to site_header and the rest to site_footer. To find out which other templates need to be changed, view the output of the page. Each template name is documented in the source code.

Let me know if you need help porting your current design over.

Vbulletin Intergration help needed

I followed the guide, edited the file and uploaded as stated above, but there is no change to my system. The forum URL and CMS login all still remain the systems own and not the forums.

Unfortunately the system provides no feedback, so I can't see what, if anything, is failing.

Also, all I really want is the news system to replace my existing Coranto output, is there anyway I can just output the main news and headlines to an external .SHTML page (bit of template editing aside)?

Vbulletin Intergration help needed

I have the same thing and note that the other guys question hasn't been answered. I uploaded the vb3-5 or whatever dir and edited bbwrapper to the EB folder. I also uploaded the file right to the root of the EB folder, but nothing.

I didn't answer the question because the author updated the post with "Not needed any further."

Is the login not working at all? A brief guide for setting up the integration is here:  http://www.esselbach.com/review6.html

What really annoys me about EB is that there's so little documentation and despite the system appearing simple, I find myself puzzled by many things because I'm often unable to find answers to usually obvious questions.

I know . The main problem is that it makes not much sense to write longer a full documentation for the 1.x series, after version 2.0 is coming later this summer.

Version 2.0 is basically a whole new script, which is working much different behind the scenes. For example, the vBulletin integration is now an option in the admin control panel and requires no longer to manually edit and upload a file to the root directory. Each section (e.g. news, content etc.) have now their own settings page while in 1.x there is only Other/Config for database related settings and Other/Websites for all other settings.

Like, why aren't the headlines showing in the default style, which clearly shows headlines in its image example. Or.. what do the three different cache systems do - exactly?

You can enable the headline blocks and a few other options under Other / Websites => Edit

The three caching option will do the following:
memory/file cache
In this mode the caching system will write the cached HTML data to the /cache directory as PHP code to allow PHP accelerators such as eAccelerator caching the data in the memory.

file cache only
This mode is doing the same except writing the HTML data as HTML to the /cache directory. This is the recommended option for most configurations.

MySQL cache
In this mode the HTML cache will be written in a database table. This is the best option for Windows based servers.

Let me know if you have additional questions

Vbulletin Intergration help needed

I have the same thing and note that the other guys question hasn't been answered. I uploaded the vb3-5 or whatever dir and edited bbwrapper to the EB folder. I also uploaded the file right to the root of the EB folder, but nothing.

What really annoys me about EB is that there's so little documentation and despite the system appearing simple, I find myself puzzled by many things because I'm often unable to find answers to usually obvious questions.

Like, why aren't the headlines showing in the default style, which clearly shows headlines in its image example. Or.. what do the three different cache systems do - exactly?

Please make proper documentation.