With the assistance of "blong5150" I have found (what I consider) a flaw with the database handling within Joomla. Even though I request a unique connection to the database, it seems that the CMS reuses my connection rather than its own.
I will be going through the code set to insure that I have a unique connection to the database for the treasury rather than Joomla being able to reuse mine.
Interesting Idea. I have on the books a somewhat rewrite of my component to include some new features that some other people were asking about. Some of the planned changes would be required in order to make a CB integration possible.
In order to get to the current version, you have 2 choices:
Choice 1 ? Uninstall the old version ? Reinstall the new version. -- Your data will be safe as I do not delete tables, but your settings will be overwritten. You can work around this by downloading the config.mh2treasury.php from your components/com_mh2treasury directory and re-uploading it after you reinstall.
Choice 2 ? download the current component. ? Unzip it to a directory. ? Upload the appropriate PHP files via FTP (Binary Mode!!!) to their respective directories, overwriting the current versions. -- Admin directory: administrator/components/com_mh2treasury -- Main directory: components/com_mh2treasury
If this does not make sense, please pm me information on how to connect via voice mode. Teamspeak, Ventrilo, Phone ... etc
If you are talking about the 1.0 version, you will need to uninstall then install the new version. There is a copy transaction function within the new version so that you do not loose your history.
It is possible that one of the other modules is closing the database, saw that issue prior when I was closing my database.
The apache@localhost does seem strange, if that is not the user name you are using for your database access. I do not use that anywhere in my code.
Not sure what else I can say about it, if you would like to PM me the links, I could possibly take a look at it as time permits. May be a little bit though.
OK --- Let's try this again. I have updated the version to 2.18, please upgrade (May have to do it manually this time only) and try the unbrand check once more.
No problem, that 500 error is typically because your web host is taking a proactive step to hardening their box. I have had to deal with it on a few occasions, that is the reason I am familiar with it, for the typical end user they are always left in the dark.
One of two things is happening based on the fact that your host is running phpsuexec or suexec. (1) The directory/file is set to 777 when it needs to be max 755 (most likely) (2) Your user account does not own the directory/files
Try setting the directories and files within to be 755 and try it again.