Welcome to Geeklog Monday, February 24 2020 @ 03:42 am EST

Geeklog Forums

Paths, what the heck am I supposed to put in them?


Daniel

Anonymous
blank
Erm, the problem with your "installation instructions" is that they still have the effect of appearing to be written by geeks for geeks.

I know that it might look simple to a geek, but it isn't for a newby. Unless you simplify the thing further and use actual examples in your php files, to describe what "paths" are -- as an example, some of us STOOPID people can't make sense of it all and end up taking hours to complete what should be a straight forward install.

At the risk of offending some of you -- well, what the heck, you deserve it because geeklog took so long to install, and now I can't complete the install after all -- many other similar CMSs are a breeze to install and are very friendly to us STOOPID newbies. You might choose to get your mane up because of this message Razz , but whether you like it or not, there are many more like me out there so sooner or later you geeklogians have to make the intsall process better or write better IIs

Now for my problem: what is the "path" supposed to be in the config and lib-common files? my "public" folder is httpdocs, I uploaded all files in the public_html directory here and also the other directories and files (can't really put them elsewhere, the server won't allow me to do so).
However, all my attempts to rename the paths as per the IIs have met with "Site not found" error when I tried to complete the process via http://mysite/admin/install/install.php

Cheers, and I hope you don't take it too hard
Daniel Laughing Out Loud
 Quote

Status: offline

JohnVanVliet

Forum User
Full Member
Registered: 09/10/03
Posts: 161
paths o what fun
this is an edited copy of my config.php file
runing on windows
the "path " is the location of the file on the harddrive
ie. win is {c:/Program Files/geeklog}
linux /usr/bin/geeklog


PHP Formatted Code


config -----
##

$_DB_host         = '127.0.0.1';   // host name or IP address of your DB server
$_DB_name         = 'geeklog';     // name of your database,
                                   // must exist before running the installer!
$_DB_user         = '????';    // MySQL user name
$_DB_pass         = '????';    // MySQL password

// The table prefix is prepended to each table used be Geeklog to avoid name
// collisions with other tables that may already exist in your database.
$_DB_table_prefix = 'gl_';         // e.g. 'gl_'


// +---------------------------------------------------------------------------+
// | (2) Paths                                                                 |
// +---------------------------------------------------------------------------+

// Note for Windows users: It's safe to use the forward slash '/' instead of
// the backslash '' in paths. Make sure each path starts with a drive letter!

// This should point to the directory where your config.php file resides.
$_CONF['path']            = 'C:/??/??/Aeonserv/geeklog/'; // should end in a slash

// You only need to change this if you moved or renamed the public_html
// directory. In that case, you should specify the complete path to the
// directory (i.e. without the $_CONF['path']) like this:
// $_CONF['path_html']      = '/path/to/your/public_html/';
$_CONF['path_html']         = 'C:/??/??/Aeonserv/geeklog/public_html/';


// +---------------------------------------------------------------------------+
// | (3) Site Settings                                                         |
// +---------------------------------------------------------------------------+

// Make sure this is the correct URL to your site, i.e. to where Geeklog's
// index.php file resides (no trailing slash).
$_CONF['site_url']          = 'http://johnscelestiapage.no-ip.com';

// Some hosting services have a preconfigured admin directory. In that case,
// you need to rename Geeklog's admin directory to something like "myadmin"
// and change the following URL as well. Leave as is until you experience any
// problems accessing Geeklog's admin menu.
$_CONF['site_admin_url']    = $_CONF['site_url'] . '/admin';

// This is the return address for all email sent by Geeklog:
$_CONF['site_mail']         = 'johnvanvliet2004@yahoo.com';

$_CONF['site_name']         = 'JohnsCelestiaPage';
$_CONF['site_slogan']       = '"  One Small Step For Man ... "';

//
#
#
lib-common---------------------------------------------------------------------
#
$_COM_VERBOSE = false;

/**
* Configuration Include: You should ONLY have to modify this line.
* Leave the rest of this file intact!
*
* Make sure to include the name of the config file,
* i.e. the path should end in .../config.php
*/


require_once( 'C:/??/??/Aeonserv/geeklog/config.php' );


// Before we do anything else, check to ensure site is enabled

#
#
httpd.conf------------------------------------------------------------
#
#   this one is more fun the public folder is what the server hands out
#
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
#
# If this is not set to valid DNS name for your host, server-generated
# redirections will not work.  See also the UseCanonicalName directive.
#
# If your host doesn't have a registered DNS name, enter its IP address here.
# You will have to access it by its address anyway, and this will make
# redirections work in a sensible way.
#
ServerName johnscelestiapage.no-ip.com

#
# UseCanonicalName: Determines how Apache constructs self-referencing
# URLs and the SERVER_NAME and SERVER_PORT variables.
# When set "Off", Apache will use the Hostname and Port supplied
# by the client.  When set "On", Apache will use the value of the
# ServerName directive.
#
UseCanonicalName Off

#
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
#DocumentRoot "C:/??/??/Aeonserv/webroot"
DocumentRoot "C:/??/??/Aeonserv/geeklog/public_html"
#
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
#
# First, we configure the "default" to be a very restrictive set of
# features.  
#
<Directory />
    Options FollowSymLinks ExecCGI
    AllowOverride None
</Directory>
#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#

#
# This should be changed to whatever you set DocumentRoot to.
#
<Directory "C:/??/??/Aeonserv/geeklog/public_html">

#
# Possible values for the Options directive are "None", "All",
# or any combination of:
#   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
#
# Note that "MultiViews" must be named *explicitly* --- "Options All"
# doesn't give it to you.
#
# The Options directive is both complicated and important.  Please see
# http://httpd.apache.org/docs-2.0/mod/core.html#options
# for more information.


 
 Quote

Status: offline

Dirk

Site Admin
Admin
Registered: 12/01/02
Posts: 13073
Location:Stuttgart, Germany
There's also an FAQ entry on that topic as well as gazillions of forum posts ...

bye, Dirk
 Quote

Daniel

Anonymous
Thanks for the feedback. I managed to get it to the next stage, where it asks me to enter the path. But then it gives me the following message:
Geeklog Installation - Error

Geeklog could not find config.php in the path you just entered: /home/httpd/vhosts/ozcarparts.net/httpdocs/admin/install/install.php
Please check this path and try again.
>>

I then tried to re-write the paths in the config and lib-common files (even changed in the configinfo in the admin/install folder) but with no joy.

After many hours of stuffing around with it, I am now officially sick of trying to install geeklog. I will now uninstall it from the server and upload e107 or xoop either of which, from a non-geek perspective, is vastly superior to this piece of crap when it comes to installation. Pity, as geeklog looks ok online but ... if the install process is such a pain what can one do?

Cheers, thanks for the feedback, and I will check back in here in the future to see if there is a better II provided.

PS:

Here is an example of what the install part should look like (courtesy of the readme file in e107:

""""
Installation Instructions
Fresh Install ---
e107 needs a mysql database to store all your site content, you can either create one manually, or the install script will create one for you if you have the correct permissions. e107 can also share a database with other scripts if you so wish (use a table prefix to avoid conflicts).
Upload all the files to your server, leaving the file structure intact.
In your FTP client, change the file permissions of the following files ...
e107_config.php : 777
e107_files/backend/news.xml : 777
e107_files/backend/news.txt : 777
e107_files/public/ : 777
e107_files/public/avatars : 777

Open your browser and navigate to install.php (ie http://yourURL.com/install.php). Follow the instructions to install e107. If there are any problems you will be informed.
During the install process you will be asked to set up the main site admin, please write the details you enter down as for security purposes they cannot be retrieved later.
""'""
Notice any geek-lingo here? If they can do it, why can't geeklogians do it as well?

 Quote

Status: offline

r_f_o_t

Forum User
Full Member
Registered: 30/07/03
Posts: 241
Location:Illinois
Quote by Daniel:
e107_config.php : 777
e107_files/backend/news.xml : 777
e107_files/backend/news.txt : 777
e107_files/public/ : 777
e107_files/public/avatars : 777


777=Anybody can read and write, not very secure.

Chuck
Too many hands on my time.
 Quote

Daniel

Anonymous
angelic
No, after install you're prompted to change as appropriate and kill the intsall files, but the process is very user-friendly and fool (i.e., like me Neutral ) proof, for instance, if you've left the install files you get a nag message in the admin screen. Neat, and indicative of good and elegant design (that is, there is sufficient refelection on what you, as the designer, encumber the end user of your product with)

Have fun
 Quote

Status: offline

Dirk

Site Admin
Admin
Registered: 12/01/02
Posts: 13073
Location:Stuttgart, Germany
Quote by Daniel: Geeklog could not find config.php in the path you just entered: /home/httpd/vhosts/ozcarparts.net/httpdocs/admin/install/install.php
Please check this path and try again.

So Geeklog asked for the path to config.php and you gave it the path to the install.php - and you're wondering why it doesn't work? Eek!

bye, Dirk
 Quote

Daniel

Anonymous
blah
Thanks Dick, but I took the "hint" that geeklog provided at the bottom of the screen (and you pointed out as a FAQ in a previous post). But I also tried /home/httpd/vhosts/ozcarparts.net/httpdocs/config.php
and many other varieties. I repeat my original question:
What am I supposed to put in the path it asks for? If you can help, I would be grateful, and so please provide some constructive suggestions, otherwise don't try to make me look like I am stupid.
 Quote

Status: offline

Dirk

Site Admin
Admin
Registered: 12/01/02
Posts: 13073
Location:Stuttgart, Germany
Quote by Daniel: I repeat my original question:
What am I supposed to put in the path it asks for?

It's not very clear where you actually put the config.php. If you really put it in the same directory as the lib-common.php and index.php (which is not a good idea), then the path would be

/home/httpd/vhosts/ozcarparts.net/httpdocs

(when installing 1.3.8, that would be the correct way to enter the path - 1.3.9 would also accept a path ending in "config.php")

bye, Dirk
 Quote

Daniel

Anonymous
blank
Thanks, that's been very helpful because it hinted at having the config.php file separated by the directory structure. So I moved the directories/files so that I had a public_html directory similar to how the structure was when I unpacked the download. This, of course is not made clear in the II, which provides the convoluted statement involving ("htdocs" and "www" are other popular names), which should definitely be left out. Instead, there should be a clear direction, like: "Ensure you upload the files/directories to the public folder on your server space so it retains its structure".

And so, I provided the path to the config file as:
/home/httpd/vhosts/ozcarparts.net/httpdocs/

Ok, this got me past the next stage of the install. However, now I get the following messages:

"1050: Table 'gl_access' already exists" and no other options or instructions or hints of what to do.

When I attempt to upload the site the following message appears:

"Forbidden
You don't have permission to access to this document on this server.

Apache Server at ozcarparts.net "

and the saga goes on. I'm sticking with it so I can hopefully learn a few things
 Quote

Status: offline

Blaine

Forum User
Moderator
Registered: 16/07/02
Posts: 1233
Location:Canada
"1050: Table 'gl_access' already exists" and no other options or instructions or hints of what to do.
This error is caused by the tables now already existing. You can only run the install.php once to create the tables. You can certainly delete the tables and or database and just create an empty database and re-run install.php but I think you should now try to access your site.

If your site does not appear - there may be a problem with the URL that you entered for $_CONF['site_url']. This should point to where your lib-common.php or more specifically the index.php is located.

Geeklog components by PortalParts -- www.portalparts.com
 Quote

All times are EST. The time is now 03:42 am.

  • Normal Topic
  • Sticky Topic
  • Locked Topic
  • New Post
  • Sticky Topic W/ New Post
  • Locked Topic W/ New Post
  •  View Anonymous Posts
  •  Able to post
  •  Filtered HTML Allowed
  •  Censored Content