Welcome to Geeklog, Anonymous Wednesday, December 07 2022 @ 09:57 pm EST

Geeklog Forums

Warning: main failed to openpublic_html/lib-common.php on line 69


Tocotoco

Anonymous
angry
The paths are fundamental. It surprises me how difficult it is to find help on this.. I have solved 10 plus errors on the install for 1.3.8-1sr3 but the one that follows, I coulnd not, I need your help as to WHICH FILE NEEDS FIXING AND HOW.

Warning: main(/home/httpd/vhosts/homeya.com/httpdocs): failed to open stream: Success in /home/httpd/vhosts/homeya.com/httpdocs/public_html/lib-common.php on line 69

Fatal error: main(): Failed opening required '/home/httpd/vhosts/homeya.com/httpdocs' (include_path='.:/usr/share/pear') in /home/httpd/vhosts/homeya.com/httpdocs/public_html/lib-common.php on line 69
 Quote

Status: offline

Dirk

Site Admin
Admin
Registered: 01/12/02
Posts: 13073
Location:Stuttgart, Germany
I just answered this here.

It surprises me how difficult it is to find help on this.

Excuse me? It's covered in the FAQ, for example. Not to mention the postings all over the installation forum ...

In your case, you seem to have missed this comment just above the one line you changed in lib-common.php:
Text Formatted Code
* Make sure to include the name of the config file,
* i.e. the path should end in .../config.php
 

bye, Dirk
 Quote

Tocotoco

Anonymous
Thank you for your repplies. Not really the file lib.common.php was all along like this.
require_once('/home/httpd/vhosts/homeya.com/config.php' );

Now this is happening after going through al mysql stuff and just prior to success. Whould this have anything to do with the location of "ADMIN"?. In my case is under the public_html directory. (I still do not understand why you need httpdocs AND PUBLIC_HTM one after the other)
Thank you again
 Quote

Status: offline

Dirk

Site Admin
Admin
Registered: 01/12/02
Posts: 13073
Location:Stuttgart, Germany
Quote by Tocotoco: (I still do not understand why you need httpdocs AND PUBLIC_HTM one after the other)

Actually, you shouldn't. There's a lengthy paragraph in the installation instructions trying to explain that "public_html" is just a popular name for the public directory of a website (also called the document root) and that it may have a different name for you (e.g. "htdocs" or, in your case, "httpdocs").

So what you probably should do is to move everything from Geeklog's public_html directory into your httpdocs directory and fix the paths in config.php (notably $_CONF['path_html']) accordingly.

bye, Dirk
 Quote

Status: offline

jonimueller

Forum User
Junior
Registered: 11/28/02
Posts: 17
Dirk, I'm bewildered by one thing: What is the specific reason to separate some of the folders/files into the non-public area? Is it a security issue? I am using a Fantastico-installed version of Geeklog. Everything was dumped into the directory I specified (http://www.ro-jo.net/geeklog/ and everything runs fine, but I am worried that the site can be hacked if there are items in there that shouldn't be viewed.

When I tried moving the "non public_html" folders to geekadmin (since my web host already had an admin directory), it hosed the site and I had to reinstall.

What was I doing wrong? And what is the harm in leaving everything in the public_html directory? (I'm not being facetious here, I genuinely want to know.)

My site is here.

Thanks!

Joni
My Geeklog Site:
http://www.ro-jo.net.com/geeklog/
 Quote

Status: offline

Blaine

Forum User
Moderator
Registered: 07/16/02
Posts: 1232
Location:Canada
Any file in the public directory space is accessible to anyone and most likely readable. You really only need files in this directory that need to be accessed by a user directly by URL.

The web server can then include other PHP code via a file name and that can be outside the public space.

The files are separated this way to allow you to isolate the system files from the public files.

If all your files are in the public accessible directory I may be able to write a program and read your config.php. And that has your database username and password in it.
Geeklog components by PortalParts -- www.portalparts.com
 Quote

Status: offline

vegeta9870

Forum User
Newbie
Registered: 11/07/03
Posts: 8
if you want to fix that problem, move config.php to a non-public directory. Then open config.php change the location of the $_CONF['path'] to /path/to/geeklog/(where you put config.php)
Then open lib-common.php and change:
include('/path/to/geeklog/') to where config.php is.
If you wish to taste the ground feel free to attack me.
 Quote

Status: offline

jonimueller

Forum User
Junior
Registered: 11/28/02
Posts: 17
Thanks, guys, for your answer. This helps me out. I'll go ahead and do that this weekend so I will sleep a bit better!

I recall when I first tried to install geeklog on another site back in Nov. 2002, I did attempt to isolate the directories but I couldn't get geeklog to run ... or it did run, but with great difficulty. I now attribute that in part to the fact that I knew even less about what I was doing than I do now (if you can fathom that!).

Again, thanks a bunch. I'm really enjoying this program!
My Geeklog Site:
http://www.ro-jo.net.com/geeklog/
 Quote

All times are EST. The time is now 09:57 pm.

  • 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