Faulty links

Help with getting the CMS CORE package up and running. This does not include 3rd party modules, PHP scripts, anything downloaded via module manager or from any external source.
Locked
newbie

Faulty links

Post by newbie »

Hi
I am new to this CMS thing. I appeared to install the latest version yesterday with no issues and the default site appears as expected. However if i click a link on the default menu/navagation bar i get the following message

The requested URL /cgi-bin2/cgiwrap/cmsms/index.php/navigation_menus was not found on this server.

The actual path for the link should be and appears to be;

http://myserver.com/cmsms/index.php/navigation_menus:

I cant workout where the /cgi-bin2/cgiwrap bit of the path comes from as this directory does not exist on my server. Any help would be much appreciated as after testing out 4 cms systems so far i like the look of this one.

Thanks

Nick
cyberman

Re: Faulty links

Post by cyberman »

Can you post your config.php (without account information)?
newbie

Re: Faulty links

Post by newbie »

As requested config.php file
#-----------------
#Database Settings
#-----------------

#This is your database connection information.  Name of the server,
#username, password and a database with proper permissions should
#all be setup before CMS Made Simple is installed.
$config['dbms'] = 'mysql';
$config['db_hostname'] = '********';
$config['db_username'] = '********';
$config['db_password'] = '**********';
$config['db_name'] = '*******';

#If app needs to coexist with other tables in the same db,
#put a prefix here.  e.g. "cms_"
$config['db_prefix'] = 'cms_';

#Use persistent connections?  They're generally faster, but not all hosts
#allow them.
$config['persistent_db_conn'] = false;

#Use ADODB Lite?  This should be true in almost all cases.  Note, slight
#tweaks might have to be made to date handling in a "regular" adodb
#install before it can be used.
$config['use_adodb_lite'] = true;

#-------------
#Path Settings
#-------------

#Document root as seen from the webserver.  No slash at the end
#e.g. http://blah.com
$config['root_url'] = 'http://mydomain.com/cmsms';

#Path to document root. This should be the directory this file is in.
#e.g. /var/www/localhost
$config['root_path'] = '/files/home3/mydomain/cmsms';

#Name of the admin directory
$config['admin_dir'] = 'admin';

#Where do previews get stored temporarily?  It defaults to tmp/cache.
$config['previews_path'] = '/files/home3/mydomain/cmsms/tmp/cache';

#Where are uploaded files put?  This defaults to uploads.
$config['uploads_path'] = '/files/home3/mydomain/cmsms/uploads';

#Where is the url to this uploads directory?
$config['uploads_url'] = 'http://ccgi.mydomain.com/cmsms/uploads';

#---------------
#Upload Settings
#---------------

#Maxium upload size (in bytes)?
$config['max_upload_size'] = 16000000;

#Permissions for uploaded files.  This only really needs changing if your
#host has a weird permissions scheme.
$config['default_upload_permission'] = '664';

#------------------
#Usability Settings
#------------------

#Allow smarty {php} tags?  These could be dangerous if you don't trust your users.
$config['use_smarty_php_tags'] = false;

#CMSMS Debug Mode?  Turn is on to get a better error when you
#see {nocache} errors.
$config['debug'] = false;

#Automatically assign alias based on page title?
$config['auto_alias_content'] = true;

#------------
#URL Settings
#------------

#Show mod_rewrite URLs in the menu?
$config['assume_mod_rewrite'] = false;

#Extension to use if you're using mod_rewrite for pretty URLs.
$config['page_extension'] = '';

#If you don't use mod_rewrite, then would you like to use the built-in
#pretty url mechanism?  This will not work with IIS and the {metadata} tag
#should be in all of your templates before enabling.
$config['internal_pretty_urls'] = true;

#If you're using the internal pretty url mechanism or mod_rewrite, would you like to
#show urls in their hierarchy?  (ex. http://www.mysite.com/parent/parent/childpage)
$config['use_hierarchy'] = true;

#If using none of the above options, what should we be using for the query string
#variable?  (ex. http://www.mysite.com/index.php?page=somecontent)
$config['query_var'] = 'page';

#--------------
#Image Settings
#--------------

#Which program should be used for handling thumbnails in the image manager.
#See http://wiki.cmsmadesimple.org/index.php ... ge_Manager for more
#info on what this all means
$config['image_manipulation_prog'] = 'GD';
$config['image_transform_lib_path'] = '/usr/bin/ImageMagick/';

#Default path and URL for uploaded images in the image manager
$config['image_uploads_path'] = '/files/home3/mydomain/cmsms/uploads/images';
$config['image_uploads_url'] = 'http://ccgi.mydomain.com/cmsms/uploads/images';

#------------------------
#Locale/Encoding Settings
#------------------------

#Locale to use for various default date handling functions, etc.  Leaving
#this blank will use the server's default.  This might not be good if the
#site is hosted in a different country than it's intended audience.
$config['locale'] = '';

#In almost all cases, default_encoding should be empty (which defaults to utf-8)
#and admin_encoding should be utf-8.  If you'd like this to be different, change
#both.  Keep in mind, however, that the admin interface translations are all in
#utf-8, and will be converted on the fly to match the admin_encoding.  This
#could seriously slow down the admin interfaces for users.
$config['default_encoding'] = '';
$config['admin_encoding'] = 'utf-8';

#---------------------------------------------
#Use the old stylesheet logic?  It's much slower, but it works with older
#versions of CMSMS.  You'll also need this set to true if there is a module
#that uses a stylesheet callback.  Leave it as false instead you really
#need it.
$config['old_stylesheet'] = false;

#Not used anymore... kept around, just in case
$config['disable_htmlarea_translation'] = false;
$config['use_Indite'] = true;
?>
Last edited by newbie on Fri May 12, 2006 10:55 am, edited 1 time in total.
Ted
Power Poster
Power Poster
Posts: 3329
Joined: Fri Jun 11, 2004 6:58 pm

Re: Faulty links

Post by Ted »

Looks like the internal url handling doesn't like cgi-bin.  Your best bet it to set internal_pretty_urls to false and when you're ready to go live, setup mod_rewrite for better looking urls.
newbie

Re: Faulty links

Post by newbie »

:)Thanks for the help. I will now go read the documentation regards setup mod_rewrite for better looking urls.
Here comes the stupid question though. The links in the menu look fine so what exactly will setting up mod_rewrite do

Thanks again
Nick
Locked

Return to “[locked] Installation, Setup and Upgrade”