Topics

User Functions

Events

There are no upcoming events

What's New

Stories

No new stories

Comments last 2 weeks

No new comments

Trackbacks last 2 weeks

No new trackback comments

Links last 2 weeks

No recent new links

NEW FILES last 14 days

No new files

Welcome to Geeklog Sunday, May 19 2013 @ 07:26 PM EDT

> >

Geeklog 1.3.9 (final)

Geeklog
  • Sunday, March 14 2004 @ 05:00 PM EST
  • Contributed by:
  • Views:
    11,682
Geeklog 1.3.9 is now finally available for download.

A quick recap of the new features: Uses PEAR::Mail for emails (so that you can send emails via SMTP), extended content syndication (including a web interface), web interface to rearrange blocks (for admins), supports URL rewriting of story URLs (so that Google can finally pick up the URLs to stories), Static Pages plugin 1.4 and more. Other changes include bugfixes and a much stricter parameter checking for better protection against SQL injection attempts.

This is a recommended upgrade for all Geeklog users. Please note that support for Geeklog 1.3.7 has now officially ceased, so if you're still on 1.3.7, now would be a good time to upgrade.

For those running on the last release candidate (1.3.9rc3): The only code changes were in lib-common.php and admin/user.php, so that you only have to replace those two files (and adjust the version number in config.php).

The following comments are owned by whomever posted them. This site is not responsible for what they say.

  • Geeklog 1.3.9 (final)
  • Authored by:g3cko on Sunday, March 14 2004 @ 09:31 PM EST
Has there been some change to the way plugins work? I had to disable all plugins to make it work.

Something about requiring ....../plugins/plugname/functions.inc
  • Geeklog 1.3.9 (final)
  • Authored by:g3cko on Sunday, March 14 2004 @ 09:51 PM EST
n/m i did a new install into a new dir, but "upgraded" the database, so those files were really missing :-)
  • Geeklog 1.3.9 (final)
  • Authored by:g3cko on Sunday, March 14 2004 @ 10:14 PM EST
Well... its all working awesome! except my gallery :-( it appears that the first COM_siteHeader(); doesn't return anything, but the COM_siteFooter(true); does... I'll see what i can dig up, and post the resolution.

Good work on the url_rewriting, this was a VERY important feature for me!
  • Geeklog 1.3.9 (final)
  • Authored by:g3cko on Sunday, March 14 2004 @ 10:17 PM EST
appears that in the wrapper.header file I only had COM_siteHeader();, changing this to echo COM_siteHeader(); fixed the problems for me.
  • Geeklog 1.3.9 (final)
  • Authored by:bieffe on Tuesday, March 16 2004 @ 07:58 AM EST
hey man! tq.. finally my plugin working .. i just change $display to echo ..& it works!
  • Geeklog 1.3.9 (final)
  • Authored by:amckay on Friday, March 26 2004 @ 07:33 PM EST
What was the change required? Finally got around to trying 1.3.9 and it seems my plugin does not work.
  • Geeklog 1.3.9 (final)
  • Authored by:amckay on Friday, March 26 2004 @ 07:38 PM EST
Never mind ... got it
  • Use of PEAR
  • Authored by:barrywong on Sunday, March 14 2004 @ 09:59 PM EST
Dear Dirk and team,
Thank you for all the effort in bringing Geeklog1.3.9. to the community. It really looks good.

I have a question regarding PEAR and mail. Can anyone tell me where I can find more information regarding this topic (PEAR and Mail settings)?

Config.php suggest the use of PHP4.3.0 or newer for PEAR. What if I am still using php4.1.2? RedHat 7.3 doesn't have any upgrades for php? How will that affect me?

Also, what are the options that I should use? sendmail, SMTP or mail. I know that mail will work most of the time.

But I would really like to understand this a little better so that I can make use of the new facilities that you have so kindly built into GL1.3.9

Thank you.
  • Use of PEAR
  • Authored by:Dirk on Monday, March 15 2004 @ 03:40 AM EST
The Geeklog tarball includes the necessary PEAR classes. Actually, Geeklog will use them by default. If you want to use the PEAR classes installed on your webserver (which you'd usually only want when running on PHP 4.3.0 or later), change the $_CONF['have_pear'] config option to 'true'.

bye, Dirk

  • URL rewriting
  • Authored by:Anonymous on Monday, March 15 2004 @ 01:40 AM EST
Did something change between the release of 1.3.9 and the 1.3.9rc3 that somehow disabled url rewriting?

I could have sworn that I tested geeklog 1.3.9rc3 on my test site, running apache 1.3.28 and using php 4.3.3, and saw URL rewriting work perfectly and it used article.php/storyid as the url. Now when I went and upgraded my main site from geeklog 1.3.8sr4 to geeklog 1.3.9, url rewriting is only working for static pages and not for stories or at least geeklog isn't using the new url's in the story links it creates on the site like in the older stories block. Any ideas on what is up with that?
  • URL rewriting
  • Authored by:Anonymous on Monday, March 15 2004 @ 01:43 AM EST
Ok. I posted too quickly. Geeklog indeed does use the new URL style only for the "Read more" links but not in the Older Stories block and I only noticed this after 1.3.9 was released.
  • URL rewriting
  • Authored by:Anonymous on Monday, March 15 2004 @ 01:46 AM EST
heh.

It also appears to not use the new URL form in rdf feeds either, using the article.php?story=storyid format instead of article.php/storyid/ when $_CONF['url_rewrite'] = true in config.php

  • URL rewriting
  • Authored by:Anonymous on Monday, March 15 2004 @ 01:58 AM EST
Yes. It is me again! I just love replying to myself. ;)

The stats page also doesn't use the new URL form when linking to stories.
  • URL rewriting
  • Authored by:Anonymous on Monday, March 15 2004 @ 01:55 AM EST
Alright. I just found out that geeklog doesn't actually change the URL form in the Older Stories block until you actually post a new story. If no new story is posted, it stays in the old url form.
  • Geeklog 1.3.9 (final)
  • Authored by:samstone on Monday, March 15 2004 @ 01:20 PM EST
Just a thought.

Isn't the Read More page good enough for url rewriting? As long as Google picks up the stories, isn't that enough? Why do you need the url rewriting in other areas like the stats?

I am just curious.

Happy birthday to GL 1.3.9!

Sam
  • Geeklog 1.3.9 (final)
  • Authored by:samstone on Monday, March 15 2004 @ 01:23 PM EST
Sorry, I was posting these questions in response to Somenobody's URL Rewriting issues and got to a new tread.

Sam
  • Geeklog 1.3.9 (final)
  • Authored by:Tony on Monday, March 15 2004 @ 05:20 PM EST
Keep in mind that the 'read more' option onlys shows up if there is something in the bodytext. Thus having it, say, the title like Dirk does is a good idea as all articles will get picked up.

---
The reason people blame things on previous generations is that there's only one other choice.
  • Geeklog 1.3.9 (final)
  • Authored by:Imaginate on Tuesday, March 16 2004 @ 05:25 PM EST
Just tried the gallery integration with the new 1.3.9 - the
gallery install wizard worked fine and then I got his error which i
never have gotten before.

Warning: main(/home/zqjcfhm/gl/public/lib-common.php):
failed to open stream: No such file or directory in /home/
zqjcfhm/public_html/gallery/init.php on line 261

Fatal error: main(): Failed opening required '/home/zqjcfhm/
gl/public/lib-common.php' (include_path='.:/usr/lib/php:/usr/
local/lib/php') in /home/zqjcfhm/public_html/gallery/init.php on
line 261


---- line 261 is
require_once($GEEKLOG_DIR . '/lib-common.php');
global $_USER;
  • Geeklog 1.3.9 (final)
  • Authored by:jokerchaos on Wednesday, March 17 2004 @ 07:07 PM EST
double check the last line of config.php and make sure it's not /path/to/gallery. seems like when u update the gallery it sometimes resets back to /path/to/gallery. if that isn't it it's somewhere in config.php, just do a text match search.
  • Geeklog 1.3.9 (final)
  • Authored by:vbgunz on Tuesday, March 16 2004 @ 09:53 PM EST
Can someone help me out with this (regarding 1.3.9 enabling splash block)

---
Victor B. Gonzalez -
http://aeonserv.com

  • Geeklog 1.3.9 (final)
  • Authored by:K12Dave on Friday, March 19 2004 @ 10:57 AM EST
...

I just upgraded from 1.3.8 to 1.3.9, and almost everything works fine - all in
all it was a very smooth upgrade.

However, My embedded Gallery (1.4.1) is no longer as "neatly" embedded. In
1.3.8, The Gallery would accept Geeklog permissions as well as theme and
block elements. Under 1.3.9, I get a more vanilla page - The authorization is
still working via Geeklog, and the page generates a "Powered by Geeklog" link
at the bottom, but all blocks are gone, and the background is a stark white.

Thoughts? Did I do something wrong?



---
Dave
  • Geeklog 1.3.9 (final)
  • Authored by:jadiepoo on Saturday, March 20 2004 @ 08:33 AM EST
You'll need to go to your gallery folder and edit a line in wrapper.header in the html_wrap folder. Replace
COM_siteHeader();

with

echo COM_siteHeader();

See the forum thread

The Geekbook also has the same problem. I ended up commenting out the old occurences of COM_siteHeader and added the echo statements in 3 files - index.php, gkaddentry.php and geekbadd.php.

Can someone who is more knowledgeable on PHP tell me if that's ok to do? My geekbook works fine with that crude edit.

  • Install Troubles
  • Authored by:tomw on Friday, March 19 2004 @ 04:52 PM EST
I just upgraded my first website to Geeklog 1.3.9 and can say I am very disappointed -- everything worked -- there is nothing to complain about. I didn't read the instructions on purpose and still no problems.

Can someone tell me what I did wrong?

TomW

Good work quys ;)
  • Install Troubles
  • Authored by:samstone on Monday, March 22 2004 @ 12:05 AM EST
You made the same mistake I did.

I upgraded a fat and very active site and expected some problem. I read the instruction but didn't follow it.

I am a little irritated because everything went smoothly and have nothing to complain.

Hope this help.

Great job, team!

Sam
  • Geeklog 1.3.9 (final)
  • Authored by:Toby W. Allen on Saturday, March 20 2004 @ 08:05 AM EST
I see that the only version of 1.3.9 is the complete tarball.

Are you not putting up the upgrade files? Will I not need to re-install geeklog completly with the complete tarball?

Slightly confused.

Toby.
  • Also looking for the update files.
  • Authored by:Captain Scurvy on Monday, March 22 2004 @ 03:50 PM EST
I'm similarly interested in the update files, but they don't seem to be available for download; only the full install seems to be up. Are there plans to ever offer the update files, or must I do a full reinstall?
  • Also looking for the update files.
  • Authored by:Dirk on Monday, March 22 2004 @ 04:44 PM EST
We don't usually offer update archives for major releases because so much has changed. If you really need to know, the 1.3.9 tarball includes a file docs/changed-files that lists all the files that have changed since 1.3.8-1sr4 - all 356 of them ...

bye, Dirk
  • Geeklog 1.3.9 (final)
  • Authored by:Agent X20 on Saturday, April 03 2004 @ 06:47 PM EST
I held off doing the 1.3.9 upgrade for a while seeing as I have a fairly active site with loads of gallery content and some folder permission restrictions seeing as it's on a commercial server.

However, despite starting with some trepidation I have to say the upgrade went very smoothly and everything seems to be working very very well.

Great job Dirk and friends! GL is great!
  • Geeklog 1.3.9 (final)
  • Authored by:Merlisk on Thursday, June 03 2004 @ 11:26 PM EDT
Love the upgrade!

I do have one issue: Sending a mass mail to my Logged-in users. I got:

Fatal error: Call to a member function on a non-object in /var/www/
html/mikesrants/lib-common.php on line 3268


However, if I just mail the root, it works fine.

Any ideas?

Please keep up the great work!

---
Merlisk

Post a Comment

Your Name
Create Account
Allowed HTML Tags:
 

Security code
This question is for testing whether you are a human visitor and to prevent automated spam submissions.

What code is in the image?
Enter the bolded text, case sensitive!
Important Stuff
  • Please try to keep posts on topic.
  • Try to reply to other people comments instead of starting new threads.
  • Read other people's messages before posting your own to avoid simply duplicating what has already been said.
  • Use a clear subject that describes what your message is about.
  • Your email address will NOT be made public.