Hi wjlow,

I'm glad you got this working. Someone else reported this the other day and we actually managed to fix the issue. On his Joomla installation (don't know if yours is the same) he had actually been having troubles with installation of components even before installing Chameleon, so it was a chain of events...

If you search in the Joomla forums, there are lots of other people reporting related problems with other components. It appears to be a bug in Joomla itself.

If you want to find out how we got around that for Chameleon installation, check out this thread:  http://www.metamodpro.com/forums/topic?id=745


Hope that helps,
Stephen

Hi scatternoise,

the info in the thread mentioned above did fix the issue for Chameleon. I'm still none the wiser about how it happens in the first place, but because it has happened to many other people with different components, I don't think it's something that's intrinsically wrong in Chameleon. I haven't had the problem on any of my own installations during development, and I have not been able to replicate the problem.

Therefore the fix for now is to go into the database (e.g. via phpMyAdmin) and perform the steps in the other thread, particularly in this reply:

http://www.metamodpro.com/forums/topic? … ;p=2#p3522

I'll look at incorporating a check for this into the installation procedure in Chameleon, but that does feel like a gross work-around...

Best regards,
Stephen