Geeklog Forums

I have just set up geeklog and it works great!!! I have one problem. I cannot e-mail out when I register a new user. I get the message below:
Fatal error: Failed opening required 'Mail/RFC822.php' (include_path='.:/usr/lib/php') in /home/sites/site4/web/lib-common.php on line 3166


the lib-common.php is definitely in the path correctly. I have checked it a thousand times. Can you help? Thanks

---

be cool

Any error messages in Geeklog's error.log? Also try

$_CONF['have_pear'] = true;

in config.php.

bye, Dirk

Thanks Dirk,

I have cut and pasted the section of my config.php below.
As you can see, I have pear is set to true and I am getting the error you just replied to.

$_CONF['have_pear'] = true;

// Geeklog comes with the necessary PEAR packages and will pick them up from
// the following directory if $_CONF['have_pear'] = false (above).
$_CONF['path_pear'] = $_CONF['path_system'] . 'pear/';

Please help.

I think you need to have

$_CONF['have_pear'] = false;

That way geeklog will use the PEAR packages included with the geeklog installation.

Good luck,
Carter

$_CONF['have_pear'] = true; will tell Geeklog to use the PEAR packages installed on the server. That only works, though, if the server is running on PHP 4.3.0 or newer versions (as older versions of PHP didn't include PEAR).

As caltman explained, setting it to false will tell Geeklog to use its own copy of the PEAR packages.

bye, Dirk

One more note about using the PEAR packages on the server. My server is running PHP 4.3.9, but I was told by the sysadmin that the PEAR repository was empty.

Carter

Ok, Guys,
Since we cannot reach a concensus, hows about I just re-install this bad boy. But, before I do, I would like to know if there was a way I could talk to you Dirk. I may be able to solve this in a couple of minutes if I knew some critical things. Again, everything works perfectly and I have the Geeklog just like I like it. It just won't send an e-mail.
Leroy
254-776-7490

LOL. No, I'm not doing any trans-atlantic phone calls

Join us on IRC: irc.freenode.net, channel #geeklog

bye, Dirk

Ok, I did not know you were so far away.
1. If I have already erased the admin directory, how do I get it back?
2. What is the Herarchy of Geeklog? In other words, How much of Geeklog is in the "/web" directory? Is it just index.php? Can you list the layout of the files? I have probably messed it up but, I have a /geeklog folder and 23 different files in the /web directory. Is there a whitepaper anywhere (or can you tell me the proper file locations? (assuming that www.me.com will find index.php)
3. what tests can I run to determine the status of the installation?

Thanks
Leroy

---

be cool

Oh by the way, If I do re-install, what do I move to keep from trashing my current install?

Leroy

---

be cool

From the tarball ...


Unpack the tarball locally and compare ...


There's a script to test the permissions, admin/install/check.php

bye, Dirk

Ok, Guys, this is starting to get old.
I still can't e-mail a new members password info .
I have done the following: I have done a fresh unpack of the tarball and a fresh install of the geeklog. I ran the installation check and the results are cut and pasted below:
Testing your Geeklog installation ...

Testing logs directory /home/sites/site5/web/logs/ ...
logs directory and the error.log and access.log files are okay.

Testing backend directory /home/sites/site5/web/public_html/backend/ ...
backend directory and the geeklog.rdf file are okay.

Testing userphotos directory /home/sites/site5/web/public_html/images/userphotos/ ...
userphotos directory is okay.

Testing articles directory /home/sites/site5/web/public_html/images/articles/ ...
articles directory is okay.

Results: 4 of 4 tests performed: 4 successful, 0 failed.
Test passed

Congratulations! Your Geeklog site is set up properly and ready to go.

Now for the meaty stuff. If I set PEAR=false the result is pasted below:
Fatal error: Call to undefined function: is_a() in /home/sites/site5/web/system/pear/PEAR.php on line 248

If I set PEAR =true the result is pasted below:
Fatal error: Failed opening required 'Mail/RFC822.php' (include_path='') in /home/sites/site5/web/lib-common.php on line 3166

What am I to do. I have now spent eleventy billion hours trying to figger it out. I must be doing something stupid. Help.

---

be cool

Which version of PHP do you have on the server?

It seems when you try to use the PEAR packages installed on the server, it doesn't find them. So you're probably on a PHP version older than 4.3.0.

The function is_a, that can not be found when using Geeklog's copy of PEAR, was introduced in PHP 4.2.0, so your PHP version appears to be even older.

I'm not sure why PEAR would require PHP 4.2.0 - I'll have to check that.

In the meantine, is there a chance you could upgrade to a more recent version of PHP?

bye, Dirk

I am having this problem too (PHP 4.0). Is there any solution that does not require upgrading PHP? I have no control over the PHP installation.

Thanks in advance to anyone who posts a workaround.

--Rafe

Dear Rafe,
I think I tried everything. Nothing worked. I really tried to use sendmail but I could not get it configured correctly either. So I spent a couple of weeks trying to build another machine to be upgraded to PHP 4.3.8. It worked perfectly and all testing of the installation worked and e-mailed through PEAR. I am sorry that I couldn't get sendmail to work because that would have been a great workaround. Maybe sombody knows how to configure the sendmail on your server. I would really like to know how to do that too.


Leroy

The fix for this issue is described here.

bye, Dirk

Would this fix work with 1.3.9sr2?

getting same error on W2k 2003 server that has php 4.3
and have been tweaking mail settings to this point

lib-common if block ends at 219 with 1.3.9 version and I plan to insert at 220 in lieu of moving to 1.3.10

Hello

Posted previous anonymous "Would fix work in 1.3.9sr2" and registered today, because this blog setup is great.

Decided to install latest version on a different server!

This is an excellent product!

Thanks

The above-mentioned issue exists only with PHP 4.1.x, not 4.3.x (and is fixed in 1.3.11 anyway).

What exactly is your problem?

bye, Dirk