Mambo Setup - My own pitfalls and problems.

This is a new design section, that I am hoping I will write about more, but who knows. Right now I may be just curious, and forget all about that in the near future.

I am accustomed to writing about things that I find out or learn, but in this case, I am going to post my problems, and then if and when I solve them, post those solutions. So it will be a little backwards, but hopefull will help me learn and remember.

First, real quick. Mambo is an open source software for CMS. Oy, technical jargon. Basically it is a program that anyone who knows how, or understands enough, can edit and make work for them. A CMS is a Content Management System. So what that means is in theory, I could set this up for a client so they could manage as much or as little of their own website as they wanted. With a little basic training of course.

So I moving along in the process right now. I got through uploading and unzipping the correct files. I then went through the setup and made chmod’s on all of the directories that needed it. (See the Linux section to find out what a chmod is.)

The automatic installation with the Mambo installer finished, I realized that I didn’t run my chmod’s Recursively on some of the directories. That means that all of the files inside the directories needed to be changed to the same chmod or Change Mode.

Now I am getting a big ugly message in the default template file for the Mambo site called rhuk_solarflare_ii, and that message says;

Fatal error: main(): Failed opening required ” (include_path=’.:/usr/lib/php:/usr/local/lib/php’).

I think the problem is that it is looking in the wrong directory for where php is installed, since I have installed mambo into a directory one level deep in my site, instead of the root.

So I am currently looking for the solution to this problem. A good place that I have found is on the forum site, which unlike Interchange, has a lot of traffic. Visit the forum site here.

Solution!

The error message I was getting was some sort of included library news file in the upper left of the template. So I read some through some threads online, I found out that maybe my problem was that I never did go through and finish up the rest of my recursive chmod’s to some of the directories.

So I did a ;

chmod -R 775 - on Mambots and Components folders located in the root of Mambo, and everything seemed to chill out.

This was the thread that helped me solve my problem with the php include library error message.

New error - configuration.php is : Unwriteable

I wanted to go in and edit my configuration file in my administrative panel, but it was saying that it was unwriteable.

Solution

I did a chmod on the configuration file. This is what I typed in;

chmod 777 configuration.php

Comments

No comments yet.

Leave a comment

Your email address is never displayed and cannot be spammed. Read our comment privacy policy.