Please Log in to join the conversation.
Please Log in to join the conversation.
I have been a programmer since the eighties. I currently specialize in PHP/MySQL (and have for the past six years). I only mention this to show where I am coming from when I say that this CB Connector - "PHPBB Connector Plugin" is - in my opinion, a piece of junk.
After two attempts to install into a Joomla 1.0 (Joomla! 1.0.13 Stable [ Sunglow ] 21 July 2007 16:00 UTC) following the instructions step-by-step. When I got the aforementioned xml missing file error on two attempts (and yes I was installing from the CB component page), I finally resorted to ftp to get the files and folders uploaded, which got me past that error only to find new errors.
I could examine all the code and make corrections if I had the time to spend but it will be easier to write my own plug-in to bridge PHPBB with Joomla's users. If a PHP developer has this much trouble with this extension, how can you expect users to handle it? I think it should be removed until it is properly fixed.
Please Log in to join the conversation.
I have been a programmer since the eighties. I currently specialize in PHP/MySQL (and have for the past six years). I only mention this to show where I am coming from when I say that this CB Connector - "PHPBB Connector Plugin" is - in my opinion, a piece of junk.
After two attempts to install into a Joomla 1.0 (Joomla! 1.0.13 Stable [ Sunglow ] 21 July 2007 16:00 UTC) following the instructions step-by-step. When I got the aforementioned xml missing file error on two attempts (and yes I was installing from the CB component page), I finally resorted to ftp to get the files and folders uploaded, which got me past that error only to find new errors.
I could examine all the code and make corrections if I had the time to spend but it will be easier to write my own plug-in to bridge PHPBB with Joomla's users. If a PHP developer has this much trouble with this extension, how can you expect users to handle it? I think it should be removed until it is properly fixed.
Please Log in to join the conversation.