403 Access denied when using https and CB Login

Hi Krileon,

Thanks for the reply.

As mentioned, this new site is a fresh installation of Joomla 3.2.3 and apart from CB, the only other 3rd party add on is Akeeba Backup. I' haven't even changed the design template yet as all I wanted to initially do, was demo the kind of functionality GroupJive would give us, to my client.

I've tried turning off SEF in Joomla Global Configuration, but that hasn't had any affect either.

I've checked and double checked the configuration.php file and that is showing:

public $live_site = '';

...so that should be fine.

I guess my only other option now (as I'm running out of time) is to wipe the site and install Joomla 2.5, which I'd rather not do really.

Just wish I knew what was adding the extra directory name in the URL.;

Any other thoughts would again be gratefully received.

Dave

As my site has no critical or secret content and is basically an empty 'skeleton' of a site. Could I email you or "support@" the connection details so that you can go in and take a look at some point?

I've taken off the CB Login module at present and am using the basic Joomla Login module as this allows you to log into the front end of the site and so lets you see that links to any CB generated page have the extra directory level added to the URLs where as normal non-CB content pages don't.

I've also uninstalled Akeeba for now but that hasn't made a difference either.

Dave

Okay, never mind... I give up!

I just added the Community Builder link to the top menu and it's completely screwed up my site (see attached).

For me anyway, it would seem CB isn't working with the latest Joomla! 3.2.3

Back to the drawing board and another week lost

I just added the Community Builder link to the top menu and it's completely screwed up my site (see attached).

It needs to be set to dropdown mode. This should already be the default when installing the CB Admin Nav module though.

I don't know what more to suggest. I can't duplicate any of your issues and CB is working fine in 3 install tests here. Please PM backend super administrator login credentials as well as FTP login credentials (so I can review your htaccess) as something is likely not configured correctly.