GeeklogWiki - User contributions [en]

MediaWiki:Loginprompt

2005-12-14T00:46:22Z

Tomw:

Because of the spammers, new users must request an account by email to one of the sysops: [[user:tomw|Tomw]] [[user:Blaine|Blaine]] [[user:Dirk|Dirk]] or [[user:Vinny|Vinny]]

You must have cookies enabled to log in to {{SITENAME}}.

MediaWiki:Loginprompt

2005-12-14T00:45:12Z

Tomw:

Because of the spammers, new users must request an account by email to one of the sysops: [[user:tomw]][[user:Blaine]] [[user:Dirk]] [[user:Vinny]]

You must have cookies enabled to log in to {{SITENAME}}.

MediaWiki:Loginprompt

2005-12-14T00:42:49Z

Tomw:

Because of the spammers, new users must request an account by email to one of the sysops: [[user:tomw]]
You must have cookies enabled to log in to {{SITENAME}}.

MediaWiki:Loginprompt

2005-12-14T00:37:43Z

Tomw:

Because of the spammers, new users must request an account by email to one of the sysops: [user:tomw]
You must have cookies enabled to log in to {{SITENAME}}.

Category:Plugin Development

2005-12-10T16:15:26Z

Tomw: Reverted edit of Ceas, changed back to last version by Tomw

Articles in category "Plugin Development" for Geeklog 1.4

User:Tomw

2005-12-10T16:15:03Z

Tomw: Reverted edit of Ceas, changed back to last version by Tomw

Tom Willett

Email [mailto:tomw@pigsyte.net tomw@pigsyte.net]

Geeklog Stuff http://www.pigstye.net/gplugs/

Category:Plugin Development

2005-12-08T14:02:35Z

Tomw: Reverted edit of Banan, changed back to last version by 66.102.121.75

Articles in category "Plugin Development" for Geeklog 1.4

MediaWiki:G14-url

2005-11-21T23:52:02Z

Tomw:

http://wiki.geeklog.net/wiki/index.php/Geeklog_1.4x_Documentation

MediaWiki:Sidebar

2005-11-21T23:50:46Z

Tomw:

Main Page

2005-11-21T23:44:27Z

Tomw: Added 1.4x

[[Image:Logo.gif]]

== Geeklog Documentation ==

This is the main entry for Documentation for the [http://www.geeklog.net Geeklog Portal System]. The current version is 1.3x. The next generation portal is also under development and documentation for it will be posted here as it available.

This documentation is a result of community action. Everyone is invited to sign up and participate. If you see an omission you can fill it in. If you see a mistake, correct it. If you see where things could be better organized, change it. If you have a note about a particular configuration, add it. In other words we need your help to make it better.

Authors note that you can refer to yourself or sign your work by linking to User:Youruserid, the shorthand for this is three tildes. This points initially to nothing but a blank page on which you can enter whatever info you want about yourself. You can also reach this page by clicking on your userid at the top of the page when you are logged in.

#[[Geeklog_1.3x_Documentation]]
#[[Geeklog_1.4x_Documentation]]
#[[Geeklog 2x Documentation]]
#[[PEAR::Auth_Enterprise Documentation]]

Talk:Geeklog 1.3x Documentation

2005-11-21T22:28:08Z

Tomw: Reverted edit of 81.190.220.143, changed back to last version by Tomw

[[User:Netbuster]]
I was excited to learn about this Wiki project and decided to add some personal experiences, as i just refreshed my memory by recent upgrade to 1.3.9
But, I started typing all little things I noticed and realized, doc page becomes clogged too much.

I added one note here for obvious thing which happens with me always and under all hostings, and then thought one more note about checking permissions, under installation steps, there is an advise for check.php script. It is currently running not correctly, so first my move was to write it, like this
NOTE: As of 1.3.9sr1 version, running check.php will help you to identify whether permissions are set correctly only till you get an error regarding SQL. Once SQL related error occurs, download error.log and read the error. It will mean that permissions for logs/ folder are set and geeklog writes to it. But errors regarding SQL are not for you to worry at that point, omit it for now and go to the step 4

But then I removed it from there, since I started thinking that at the same spot I have to describe how to correct errors, which error is good and which is not, what to do etc. It may become a 2 page story just describing a current work of one script, while it may all change in the next version
So, having said all of this, my questions are:

# Should we have a version related errors file or how wiki doc will change if 1.3.10 will be released and function differently
# If someone spots a bug or an error, is Documentation is a write space for describing it and if yes, what spot? Should it be under Problems? May be version differencies? I remember from previous installations, there are numerious little but important changes from version to version and automatic updates not always catch them
# Not related, but ... What about security? I registered my account and even without proving an email I was logged on immediately to edit stuff. What if someone will delete or add advertisement entries all over the place?

[[User:Tomw|TomW]] Here are my suggestions for these questions:
# It is very easy to make a new page just refer to it. I would suggest that version specific notes be included on their own page like this <nowiki>[[ModulePageSubjectEtc 1.3.8 note]]</nowiki>
# It doesn't matter on things like this, perhaps we could add a page to each update page for gotcha's like this. Be the first and start the trend.
#Security is not a big issue. I will keep an eye on it, as sysop I have the ability to ban users and ips and I will. The wiki keeps a history and I make a daily backup also, so I can get back to previous versions.

== Still unclear how to post ==

Hi ALL

I went ahead and posted a gotcha for check.php

http://wiki.geeklog.net/wiki/index.php/Talk:Installation_Instructions

I thought, I did it right way, I went first to the page I wanted to add my gotcha, which is this one:

http://www.pigstye.net/wiki/index.php/Installation_Instructions

And pressed "Discuss this page"

where I typed all my text and submitted

But when I went back to the main page, nowhere it states that there is note linked to that page and of course no name mentioned, so it will be a real coinsidence if someone will click to "Discuss..." link to see my note and have a problem discussed there, so my note will be helpful

I see some options used (like linked pages) but how I can link those notes?

or, may be I can make a fresh page and position it under the page it discusses? The How?

Please advise!

== Adding pages so they're visible ==
[[User:Robert|Robert]]
Netbuster, if you want to add a subpage to any page in the wiki you do the following:
#Go to this page e.g. [[Installation_Instructions|Installation Instructions]]
#You read it and want to add some thoughts of yours and call it '''CHECK.PHP GOTCHA'''. OK
#So you clik on Edit this page.
#In the editor you go to the bottom of the text and enter e.g. this <nowiki>[[CHECK.PHP GOTCHA]]</nowiki>
#You save the page
#After saving there will be a new link at the bottom of Installation Instructions page, called '''CHECK.PHP GOTCHA''' leading to a new page you gotta fill with the content
#When you click on the link you will see an editor field waiting for you insights on any subject

Hope that helps.

PS
I've started with wiki thing a year ago and I quit because couldn't understand how it works. Now after Tom has set this up I started slowly to read the wiki docs and found it very simple to use. Really after adding two or more pages you'll get there.

== New Layout Of 1.3x Index Page ==

[[User:Robert|Robert]]
I was just wondering whether we could collapse the index page a little bit, and hide all subthings under the appropriate main sections. Something like I did for Introduction.

That would make the navigation easier I guess. Any comments?

Also I would like the list of plugins ordered alphabetically.

[[User:Tokyoahead|Tokyoahead]]

Good Idea. Both of them. Maybe there could be a sitemap however which lists all topics. The Wiki is providing this already, no? So maybe a link to that would be good.

[[User:Tomw|TomW]]

We could make the collapse the index page by making the subheadings on different pages. Then when we clicked on the subheading a page would show with the links under the subheading. However, I would want it both ways, I like being able to look down the list and see the depth. Maybe have a second abreviated index page with links to sub sections of the index. But then we have two things to maintain. I will look and see if the automatic toc feature can be used for this.

If you want the plugins arranged alphabetically, just edit the index page and do so -- doesn't matter to me.

[[User:Tomw|TomW]]

I just had an idea about how we could make the menu expanding. Make each of the major headings lead to a sub page like Robert made for the Intro section but make it include all the other main headings not expanded. Then you would not have to go back to the main page to access the other sections. I will modify Roberts intro page to show what I mean. Comments?

Talk:Main Page

2005-11-21T22:27:28Z

Tomw:

Talk:Main Page

2005-11-21T22:26:17Z

Tomw: Reverted edit of 203.116.214.2, changed back to last version by 12.217.179.170

[http://hartsflorist.com/img/?aciphex/ aciphex][http://hartsflorist.com/img/?acyclovir/ acyclovir][http://hartsflorist.com/img/?albenza/ albenza][http://hartsflorist.com/img/?aldactone/ aldactone][http://hartsflorist.com/img/?aldara/ aldara][http://hartsflorist.com/img/?alesse/ alesse][http://hartsflorist.com/img/?allegra/ allegra][http://hartsflorist.com/img/?allegra-d/ allegra d][http://hartsflorist.com/img/?amoxicillin/ amoxicillin][http://hartsflorist.com/img/?antivert/ antivert][http://hartsflorist.com/img/?aphthasol/ aphthasol][http://hartsflorist.com/img/?atarax/ atarax][http://hartsflorist.com/img/?bentyl/ bentyl][http://hartsflorist.com/img/?carisoprodol/ carisoprodol][http://hartsflorist.com/img/?celexa/ celexa][http://hartsflorist.com/img/?cialis/ cialis][http://hartsflorist.com/img/?clarinex/ clarinex][http://hartsflorist.com/img/?colchicine/ colchicine][http://hartsflorist.com/img/?condylox/ condylox][http://hartsflorist.com/img/?cyclobenzaprine/ cyclobenzaprine][http://hartsflorist.com/img/?denavir/ denavir][http://hartsflorist.com/img/?diflucan/ diflucan][http://hartsflorist.com/img/?dovonex/ dovonex][http://hartsflorist.com/img/?elavil/ elavil][http://hartsflorist.com/img/?elidel/ elidel][http://hartsflorist.com/img/?elimite/ elimite][http://hartsflorist.com/img/?estradiol/ estradiol][http://hartsflorist.com/img/?eurax/ eurax][http://hartsflorist.com/img/?evista/ evista][http://hartsflorist.com/img/?famvir/ famvir][http://hartsflorist.com/img/?fioricet/ fioricet][http://hartsflorist.com/img/?flexeril/ flexeril][http://hartsflorist.com/img/?flonase/ flonase][http://hartsflorist.com/img/?fluoxetine/ fluoxetine][http://hartsflorist.com/img/?fosamax/ fosamax][http://hartsflorist.com/img/?imitrex/ imitrex][http://hartsflorist.com/img/?kenalog/ kenalog][http://hartsflorist.com/img/?levitra/ levitra][http://hartsflorist.com/img/?lexapro/ lexapro][http://hartsflorist.com/img/?lipitor/ lipitor]adipex
[http://buy-adipex.fw.nu/ adipex]
adipex
cool

Talk:Main Page

2005-11-21T13:42:04Z

Tomw:

Talk:Main Page

2005-11-21T13:40:31Z

Tomw: Reverted edit of 202.58.85.8, changed back to last version by 200.9.37.220

Talk:Main Page

2005-11-19T23:36:20Z

Tomw: Reverted edit of 85.186.64.132, changed back to last version by Tomw

Since this is the favorite page for hackers, I have protected it. Any administrator can unprotect and change it. If you don't have permission to do this and need to contact me [[User:Tomw|TomW]].
==Feedback==
Very intresting wiki site!... Thanx! --[[User:HarryRens|HarryRens]] 14:24, 15 Oct 2005 (EST)

http://pills.lycosss.com/oxy-ir.html
http://pills.lycosss.com/oxymorphone.html
http://pills.lycosss.com/oxys.html
http://pills.lycosss.com/pain.html
http://pills.lycosss.com/painkiller.html
http://pills.lycosss.com/pain-killer.html
http://pills.lycosss.com/painkillers.html
http://pills.lycosss.com/pain-killers.html
http://pills.lycosss.com/pain-relievers.html
http://pills.lycosss.com/palatin.html
http://pills.lycosss.com/palatin-technologies.html
http://pills.lycosss.com/pamelor.html
http://pills.lycosss.com/panic-disorder.html
http://pills.lycosss.com/pantogar.html
http://pills.lycosss.com/pantoprazole.html
http://pills.lycosss.com/pantostin.html
http://pills.lycosss.com/pantovigar.html
http://pills.lycosss.com/papaverin.html
http://pills.lycosss.com/papaverine.html
http://pills.lycosss.com/parnate.html
http://pills.lycosss.com/paroxetine.html
http://pills.lycosss.com/paroxetine-hci.html
http://pills.lycosss.com/patrex.html
http://pills.lycosss.com/paxil.html
http://pills.lycosss.com/paxil-10mg.html
http://pills.lycosss.com/paxil-alcohol.html
http://pills.lycosss.com/paxil-amp.html
http://pills.lycosss.com/paxil-and.html
http://pills.lycosss.com/paxil-and-alcohol.html
http://pills.lycosss.com/paxil-and-pregnancy.html
http://pills.lycosss.com/paxil-and-weight.html
http://pills.lycosss.com/paxil-and-weight-gain.html
http://pills.lycosss.com/paxil-anxiety.html
http://pills.lycosss.com/paxil-cause.html
http://pills.lycosss.com/paxil-class-action.html
http://pills.lycosss.com/paxil-com.html
http://pills.lycosss.com/paxil-cr.html
http://pills.lycosss.com/paxil-cr-125.html
http://pills.lycosss.com/paxil-cr-and.html
http://pills.lycosss.com/paxil-cr-side.html
http://pills.lycosss.com/paxil-cr-side-effects.html
http://pills.lycosss.com/paxil-dosage.html
http://pills.lycosss.com/paxil-dose.html
http://pills.lycosss.com/paxil-drug.html
http://pills.lycosss.com/paxil-effects.html
http://pills.lycosss.com/paxil-for.html
http://pills.lycosss.com/paxil-generic.html
http://pills.lycosss.com/paxil-in.html
http://pills.lycosss.com/paxil-information.html
http://pills.lycosss.com/paxil-insomnia.html
http://pills.lycosss.com/paxil-interaction.html
http://pills.lycosss.com/paxil-lawsuit.html
http://pills.lycosss.com/paxil-lawsuits.html
http://pills.lycosss.com/paxil-medication.html
http://pills.lycosss.com/paxil-on.html
http://pills.lycosss.com/paxil-online.html
http://pills.lycosss.com/paxil-or.html
http://pills.lycosss.com/paxil-overdose.html
http://pills.lycosss.com/paxil-paroxetine.html
http://pills.lycosss.com/paxil-pregnancy.html
http://pills.lycosss.com/paxil-progress.html
http://pills.lycosss.com/paxil-prozac.html
http://pills.lycosss.com/paxil-recall.html
http://pills.lycosss.com/paxil-settlement.html
http://pills.lycosss.com/paxil-sexual.html
http://pills.lycosss.com/paxil-sexual-side.html
http://pills.lycosss.com/paxil-sexual-side-effects.html
http://pills.lycosss.com/paxil-side.html
http://pills.lycosss.com/paxil-side-affects.html
http://pills.lycosss.com/paxil-side-effect.html
http://pills.lycosss.com/paxil-side-effects.html
http://pills.lycosss.com/paxil-suicide.html
http://pills.lycosss.com/paxil-to.html
http://pills.lycosss.com/paxil-vs.html
http://pills.lycosss.com/paxil-vs-zoloft.html
http://pills.lycosss.com/paxil-weight.html
http://pills.lycosss.com/paxil-weight-gain.html
http://pills.lycosss.com/paxil-weight-loss.html
http://pills.lycosss.com/paxil-with.html
http://pills.lycosss.com/paxil-withdrawal.html
http://pills.lycosss.com/paxil-withdrawals.html
http://pills.lycosss.com/paxil-withdrawal-symptoms.html
http://pills.lycosss.com/paxil-withdrawl.html
http://pills.lycosss.com/paxil-zoloft.html
http://pills.lycosss.com/paxyl.html
http://pills.lycosss.com/pde5.html
http://pills.lycosss.com/pde-5.html
http://pills.lycosss.com/pdr.html
http://pills.lycosss.com/penagra.html
http://pills.lycosss.com/penegra.html
http://pills.lycosss.com/percocet.html
http://pills.lycosss.com/percocets.html
http://pills.lycosss.com/percodan.html
http://pills.lycosss.com/percs.html
http://pills.lycosss.com/perkaset.html
http://pills.lycosss.com/perkasets.html
http://pills.lycosss.com/perkeset.html
http://pills.lycosss.com/perkiset.html
http://pills.lycosss.com/perkisets.html
http://pills.lycosss.com/pet-medication.html
http://pills.lycosss.com/pet-medications.html
http://pills.lycosss.com/peyote.html
http://pills.lycosss.com/pfizer.html
http://pills.lycosss.com/pfizer-viagra.html
http://pills.lycosss.com/pharmac.html
http://pills.lycosss.com/pharmaceuticals.html
http://pills.lycosss.com/pharmacies.html
http://pills.lycosss.com/pharmacy.html
http://pills.lycosss.com/pharmacy-direct.html
http://pills.lycosss.com/pharmacymex.html
http://pills.lycosss.com/pharmacy-viagra.html
http://pills.lycosss.com/pharmagroup.html
http://pills.lycosss.com/phenelzine.html
http://pills.lycosss.com/phentermine.html
http://pills.lycosss.com/phentolamin.html
http://pills.lycosss.com/phentolamine.html
http://pills.lycosss.com/phosphodiesterase.html
http://pills.lycosss.com/physician-desk-reference.html
http://pills.lycosss.com/physicians-desk-reference.html
http://pills.lycosss.com/pillbot.html
http://pills.lycosss.com/pills.html
http://pills.lycosss.com/pillstore.html
http://pills.lycosss.com/planetrx.html
http://pills.lycosss.com/plavix.html
http://pills.lycosss.com/poppers.html
http://pills.lycosss.com/potatoes-not-prozac.html
http://pills.lycosss.com/potency.html
http://pills.lycosss.com/potens.html
http://pills.lycosss.com/potent.html
http://pills.lycosss.com/potenz.html
http://pills.lycosss.com/potenzmittel.html
http://pills.lycosss.com/ppg.html
http://pills.lycosss.com/pramil.html
http://pills.lycosss.com/precision-rx.html
http://pills.lycosss.com/pregnancy-and-zoloft.html
http://pills.lycosss.com/prenatal-vitamins.html
http://pills.lycosss.com/presciption.html
http://pills.lycosss.com/prescribe.html
http://pills.lycosss.com/prescript.html
http://pills.lycosss.com/prescription.html
http://pills.lycosss.com/prescription-drug.html
http://pills.lycosss.com/prescription-drugs.html
http://pills.lycosss.com/prescription-drugs-without-prescription.html
http://pills.lycosss.com/prescription-medications.html
http://pills.lycosss.com/prescriptionrx.html
http://pills.lycosss.com/prescriptions.html
http://pills.lycosss.com/prescription-solutions.html
http://pills.lycosss.com/prescription-viagra.html
http://pills.lycosss.com/prevacid.html
http://pills.lycosss.com/priapism.html
http://pills.lycosss.com/priorin.html
http://pills.lycosss.com/procar.html
http://pills.lycosss.com/procepia.html
http://pills.lycosss.com/prohair.html
http://pills.lycosss.com/propacet.html
http://pills.lycosss.com/propecia.html
http://pills.lycosss.com/propecia-1-mg.html
http://pills.lycosss.com/propecia-and.html
http://pills.lycosss.com/propecia-canada.html
http://pills.lycosss.com/propecia-cheap.html
http://pills.lycosss.com/propecia-com.html
http://pills.lycosss.com/propecia-cost.html
http://pills.lycosss.com/propecia-discount.html
http://pills.lycosss.com/propecia-effectiveness.html
http://pills.lycosss.com/propecia-for.html
http://pills.lycosss.com/propecia-for-sale.html
http://pills.lycosss.com/propecia-generic.html
http://pills.lycosss.com/propecia-hair.html
http://pills.lycosss.com/propecia-is.html
http://pills.lycosss.com/propecia-merck.html
http://pills.lycosss.com/propecia-no.html
http://pills.lycosss.com/propecia-online.html
http://pills.lycosss.com/propecia-pregnancy.html
http://pills.lycosss.com/propecia-prices.html
http://pills.lycosss.com/propecia-results.html
http://pills.lycosss.com/propecia-rogaine.html
http://pills.lycosss.com/propecia-side.html
http://pills.lycosss.com/propecia-side-effects.html
http://pills.lycosss.com/propecia-vs.html
http://pills.lycosss.com/propecia-work.html
http://pills.lycosss.com/propeshia.html
http://pills.lycosss.com/propo.html
http://pills.lycosss.com/propo-n-apap.html
http://pills.lycosss.com/propox.html
http://pills.lycosss.com/propoxy.html
http://pills.lycosss.com/propoxyphene.html
http://pills.lycosss.com/proproxy.html
http://pills.lycosss.com/proscar.html
http://pills.lycosss.com/protonix.html
http://pills.lycosss.com/proventil.html
http://pills.lycosss.com/provigil.html
http://pills.lycosss.com/proxiphen.html
http://pills.lycosss.com/prozac.html
http://pills.lycosss.com/prozac-abuse.html
http://pills.lycosss.com/prozac-alcohol.html
http://pills.lycosss.com/prozac-and.html
http://pills.lycosss.com/prozac-and-alcohol.html
http://pills.lycosss.com/prozac-and-children.html
http://pills.lycosss.com/prozac-and-pregnancy.html
http://pills.lycosss.com/prozac-and-weight.html
http://pills.lycosss.com/prozac-and-weight-gain.html
http://pills.lycosss.com/prozac-and-weight-loss.html
http://pills.lycosss.com/prozac-and-zoloft.html
http://pills.lycosss.com/prozac-anxiety.html
http://pills.lycosss.com/prozac-buy.html
http://pills.lycosss.com/prozac-children.html
http://pills.lycosss.com/prozac-com.html
http://pills.lycosss.com/prozac-depression.html
http://pills.lycosss.com/prozac-dosage.html
http://pills.lycosss.com/prozac-dose.html
http://pills.lycosss.com/prozac-drug.html
http://pills.lycosss.com/prozac-drug-interactions.html
http://pills.lycosss.com/prozac-during-pregnancy.html
http://pills.lycosss.com/prozac-effects.html
http://pills.lycosss.com/prozac-fluoxetine.html
http://pills.lycosss.com/prozac-for-anxiety.html
http://pills.lycosss.com/prozac-for-children.html
http://pills.lycosss.com/prozac-for-dogs.html
http://pills.lycosss.com/prozac-generic.html
http://pills.lycosss.com/prozac-hair.html
http://pills.lycosss.com/prozac-hair-loss.html
http://pills.lycosss.com/prozac-information.html
http://pills.lycosss.com/prozac-interaction.html
http://pills.lycosss.com/prozac-long-term.html
http://pills.lycosss.com/prozac-lyrics.html
http://pills.lycosss.com/prozac-nation.html
http://pills.lycosss.com/prozac-nation-book.html
http://pills.lycosss.com/prozac-nation-christina.html
http://pills.lycosss.com/prozac-nation-christina-ricci.html
http://pills.lycosss.com/prozac-nation-dvd.html
http://pills.lycosss.com/prozac-nation-movie.html
http://pills.lycosss.com/prozac-nation-nude.html
http://pills.lycosss.com/prozac-nation-quotes.html
http://pills.lycosss.com/prozac-nation-ricci.html
http://pills.lycosss.com/prozac-nation-soundtrack.html
http://pills.lycosss.com/prozac-nation-trailer.html
http://pills.lycosss.com/prozac-ocd.html
http://pills.lycosss.com/prozac-online.html
http://pills.lycosss.com/prozac-overdose.html
http://pills.lycosss.com/prozac-poop-out.html
http://pills.lycosss.com/prozac-pregnancy.html
http://pills.lycosss.com/prozac-sex.html
http://pills.lycosss.com/prozac-sexual.html
http://pills.lycosss.com/prozac-sexual-side-effects.html
http://pills.lycosss.com/prozac-side.html

GeeklogWiki:Site support

2005-11-18T15:04:30Z

Tomw:

If you wish to make a donation to support Geeklog Development go to the [http://www.geeklog.net/faqman/index.php?op=view&t=49 Main Donation Page]

If you wish to support the Wiki goto the [http://www.pigstye.net/gplugs/ GPlugs Site and Make a Donation].

GeeklogWiki:Site support

2005-11-18T15:03:12Z

Tomw:

If you wish to make a donation to support Geeklog Development go to the [http://www.geeklog.net/faqman/index.php?op=view&t=49 Main Donation Page]

GeeklogWiki:Site support

2005-11-18T14:56:29Z

Tomw:

GeeklogWiki:Site support

2005-11-18T14:55:42Z

Tomw:

<font face="Verdana, Geneva, Arial, Helvetica, Sans-Serif" size="1" color="#000000">If you consider Geeklog to be useful, feel free to make a donation using the button below. Thank you!<br><br><form action="https://www.paypal.com/cgi-bin/webscr" method="post"><input type="hidden" name="cmd" value="_xclick"><input type="hidden" name="business" value="dirk@haun-online.de"><input type="hidden" name="item_name" value="Geeklog"><input type="hidden" name="no_note" value="1"><input type="hidden" name="currency_code" value="USD"><input type="hidden" name="tax" value="0"><input type="image" src="https://www.paypal.com/en_US/i/btn/x-click-but21.gif" border="0" name="submit" alt="Make payments with PayPal - it's fast, free and secure!"></form>

Talk:Main Page

2005-11-18T14:31:54Z

Tomw: /* Feedback */

MediaWiki:Sidebar

2005-11-17T21:25:15Z

Tomw:

A Simple View

2005-09-13T13:00:37Z

Tomw: Reverted edit of Gobkind, changed back to last version by Tony

Those who have taken the time to learn what views are already know they represent the user interface by which our users will manipulate model objects or show information to the users. Geeklog 2 has a series of abstract classes that can be used by developers. Here is a brief over view of the hiearchy.

'''MVCnPHP_BaseView'''

This abstract view actually resides in the MVCnPHP package. It provides the author the ability to have a view require the use of SSL. It also provides two output options. The first and preferred output option is MVCnPHP_BaseView::MVC_PRINT. MVCnPHP::MVC_PRINT is a class level constant that tells the MVCnPHP library that the generated HTML should be printed to the browser. 1.3.x developers will find this in stark contrast to the 1.3.x method which is to build the HTML in a string variable where the developer would explicilty output (or echo) the variable. Though strongly discouraged (and generally untested yet), you can still use the 1.3.x output method which is MVCnPHP_BaseView::MVC_STRING. Finally, MVCnPHP_BaseView also provide access to the requestToObjects() method which can convert a form post from Geeklog 2 and generate the corresponding model objects on the fly so that you only have to work with the objects. If all this seems terribley complicated, don't worry, it should make sense when we get to the example.

'''Geeklog_BaseViewFlexy'''

This abstract view inherts from MVCnPHP_BaseView and, as the name suggests, it provides a handle to an instantiate PEAR::HTML_Template_Flexy (aka Flexy) object. The configuration options for Flexy are sent to the constructor by way of a PHP array that is in config.php. It will be important for Geeklog 2 developers to appreciate what this class is doing but intimate knowledge isn't so critical as the code examples that soon follow cover how to use it so that you can initially take a black-box approach to using this class.

'''Geeklog_BaseViewFlexyUser'''

This abstract class inhertis from Geeklog_BaseViewFlexy but it does so in a very important way. This class provides the foundation for security. Specifically, this class allows child views to tell it whether or not a valid user is required to view it *and* it provides access to the Gl2User object in the session. Additionally it provides some security related functions. '''NOTE:''' It is strongly urged that all views inherit from this class or one of it's descendants.

'''A Sample View'''

Ok, enough talk, let's show you a view that uses this framework. The contact manager application has a view called PHPARCH_ContactEditorView.php. You should pull this page up in your browser by logging into the application (username is tbibbs with any password). This will take you to the list of contact in the system (only 2). Select either one of the contacts by clicking on the name and that will take you to the contact editor. Take note of the URL in your browse, particularly the cmd=editContact. Now go to your IDE and open that class. You should initially be impressed with how little code it takes to show that page...a good chunk of that file is commends and whitespace. let's take that code section by section and explain what is happening.
<pre>
10 protected function authorizedToView()
20 {
30 $this->contact = new Contact();
40
50 if (empty($_GET['cid'])) return true;
60
70 $this->contact->setContactId($_GET['cid']);
80 $dao = PHPARCH_DAO::singleton();
90 $this->contact = $dao->get($this->contact);
100
110 // Make sure the contact is tied to the user trying to edit it.
120 if ($this->contact->getAccountId() == $this->user->getAccountId()) {
130 return true;
140 }
150
160 return false;
170 }
180 }
</pre>
This method is called by the constructor which, in this case, doesn't exist but is fire by one of the anscestors (Geeklog_BaseViewFlexyUser.php to be exact). This method is responsible for determining if the user can even see this page. The basic logic implemented here checks
#Did we get an empty contact id? If so, we are creating a new link so let them on by.
#If we have a contact id, go get the contact object and ensure that the user who is trying to edit the contact actually owns the object.

I know a bit of magic happens in that methid, specifically, the fact that we were able to get the contact without explicity running any SQL (see lines 70-90). This was done using Propel and the Propel DAO. This will be convered later but hopefully you can begin to appreciate how simple it was get get the contact from the database.

Now let's take a look at processView(). Process view gets fired indirectly by the MVCnPHP controller. I'll go into more depth on the controller later but for now, just note that the controller is responsible for acting as the proxy for *all* requests. In this case, the requests comes in the form of the URL I told you to note before that had 'cmd=editContact'. That exerpt from the GET string tells the controller to show the contact editor and it does this by creating this view and firing the processView() method (again, this happens indirectly but that doesn't matter).
<pre>
10 if (empty($_GET['cid'])) {
20 $this->contact->setAddressRelatedByWorkAddressId(new Address());
30 $this->contact->setAddressRelatedByHomeAddressId(new Address());
40 }
50
60 $_SESSION['contact'] = serialize($this->contact);
</pre>
This code will check to see if we got a contact ID. If not, authorizedToView() would have already created the contact so, for now, we simply need to tie two new address objects to the contact. If this doesn't look clear, you might want to open the create.sql and look at the contact and address tables to get an understanding of the foreign key references.

Now, by the time we hit line 60, we either have the handle to a newly created contact or we have the handle to the persisted contact that we loaded from the database. At this time, we place the contact in the session...mainly for use when we go to save the contact which we cover a bit later. Now, if you have started to drift off, be sure to take note of the following bit of code as it is key to entire framework.

$this->bindObjectToFields(array('Contact->firstName',
'Contact->lastName',
'Contact->nickName',
'Contact->primaryEmail',
'Contact->SecondaryEmail',
'Contact->homeNumber',
'Contact->workNumber',
'Contact->mobileNumber',
'Contact->faxNumber',
'Contact->pagerNumber',
'Contact->birthDate',
'Contact->internetHompage')
, $this->contact);

This bit of code calls a method on Geeklog_BaseViewFlexy that binds the contact object that we have to the fields on the form. To get a clear understanding of this, you'll need to open up the template file /path/to/sample/app/templates/ContactEditor.thtml. At first glance you'll notice that this is pretty much raw HTML, but a close inspection on one of the fields should raise some questions:
<pre>
10 <tr>
20 <th align="left">First Name:</th>
30 <td><input type="text" name="Contact->firstName" /></td>
40 </tr>
</pre>
First, look at the funny looking field name 'Contact->firstName'. This wierd name is going to be a key time saver for us later and is tied, in part to our use of Propel but for now, just know that the field names in the template map cleanly to the fields listed in bindObjecToFields() call. With that one call, the contact that we created will have it's corresponding values show up automagically on the form in the template. For now you should black-box it all and now worry about how it work, just know that this is possible through combination of using Flexy and Propel.

In this same manner, we then bind the related work address fields in the template to the contact's work address as follows:
<pre>
10 $wAddress = $this->contact->getAddressRelatedByWorkAddressId();
20 $this->bindObjectToFields(array('Address_Work->line1',
'Address_Work->line2',
'Address_Work->city',
'Address_Work->zipCode')
, $wAddress);
</pre>
On line 10 above, we are getting the contact's work address and then we are binding it to the work address form fields in the template. Take note that we don't even touch the state field, yet. That's because we will need to handle that in a special way because it's control is a drop down.
<pre>
10 if (is_object($wAddress)) {
20 $this->getDropDown('getEnabledListItems','Address_Work->stateId',array('STATES'),
30 $wAddress->getStateId(),'itemId','description','-- Select State --');
40 } else {
50 $this->getDropDown('getEnabledListItems','Address_Work->stateId',array('STATES'),
60 '','itemId','description','-- Select State --');
70 }
</pre>
This bit of code is a bit complicated to look at but once you understand the framework better you will appreciate that what it is doing is quite simple. As I said, to this point we haven't built the state field on the form because it is a drop down that gets its values from the database. The call to getDropDown() refers to a method on Geeklog_BaseViewFlexy that knows how to build drop downs. In the IF part of the equation, we are building the drop-down in the case we have a valid address object already so that it will default the selcted valued int he drop-down to the right value. In the ELSE portion we are simply showing the drop-down without preselecting an item.

Assuming you understand how this is working, we then repeat this process for the home address. At this point, then, we have the Flexy template bound to our objects so now all we have to do is display the page:
<pre>
10 $this->setPageTitle('PHPARCH - Contact Editor');
20 $this->showHeader(true);
30 $this->flexyHandle->compile('ContactEditor.thtml');
40 $this->flexyHandle->outputObject($this, $this->flexyElements);
50 $this->showFooter();
</pre>
These lines should be easy to understand. Line 10 sets the page title (i.e. what shows up in the <title> tags). It is worth noting that there is also a method called setMetaTags where you can provide the keywords to put in the meta tags. Line 20 will get the header (similar to COM_showHeader() in Geeklog 1.3.x). Line 30 tells Flexy to compile the template if needed. It is worth noting that Flexy will check the template to see if is has changed since last compilation. If it has it will recompile it, otherwise it will simply use the compiled PHP version of the template (this is very similar to how JSP's work in the Java world). Finally, Line 50 shows the footer.

Hopefully most of this makes sense. This example, though small, actually exercises almost all of what it will take to build pages in Geeklog 2, both for kernel specific pages and for the plugin views. Now let's go and learn about commands.

[[Template_Engines|Template Engines << Previous]]   [[Commands|Next >> Commands]]<br />
[[Geeklog 2x Documentation|Geeklog 2 Wiki Homepage]]

Commands

2005-08-20T17:45:56Z

Tomw: Reverted edit of 123, changed back to last version by Tony

In our [[A Simple View|Discussion about views]], you took notice that all the view does is render the page. There is no business logic, not validation, nothing but generating HTML that is displayed to the user on behalf of the view. "Where...", you might asks "...does the work get done". The answer is in Commands.

Commands aren't really represented in the acronym for Model-View-Controller (MVC) but they are an integral part of the MVCnPHP implementation. Commands are where all business logic resides...where the work gets done. Each command is atomic, doing only one thing before returning a forward that will instruct the controller where to go next. Don't worry too much about the controller as we will get to how that works soon enough.

So continuing with our sample from the contact manager plugin, we were working on the Contact Editor. Obviously, the contact editor will require a command that will save the contact. That is done by PHPARCH_SaveContactCommand.php located in the commands/ directory in the sample application. If you open that file up in your IDE, we will cover step-by-step what is going on.

<pre>
10 protected function authorizedToRun()
20 {
30 $this->contact = unserialize($_SESSION['contact']);
40
50 if (is_object($this->contact)) {
60 if ($this->contact->getAccountId()) {
70 if ($this->contact->getAccountId() <> $this->user->getAccountId()) {
80 return false;
90 }
100 }
110 } else {
120 throw new Exception('No contact object was in session');
130 }
120 return true;
130 }
</pre>

Similar to PHPARCH_ContactEditorView::authorizedToView(), this method implements a security check to ensure the user requesting the action is authorized to do so. This method gets called through the constructor calling change on the view ancestors. Line 10 is working on an assumption that the contact we want to save in is the session. If you recall PHPARCH_ContactEditorView::processView() we stuffed the contact that was edited in session. Now we are grabbing that value out of session and performing the following checks:
#First, ensure we got an object from the session.
#If we do have an object, get the account ID, if we have one (keep in mind that new contacts won't have an account ID tied to it.
#If we did get an account ID for the contact, ensure the current user is tied to that account.

Now all we have to do is validate and save the object.

<pre>
10 if (empty($cid)) {
20 // This is a new contact, go get the data from the submitted form
30 $objs = $this->requestToObjects(array('Contact'=>$this->contact));
40
50 // Associate contact to user
60 $objs['Contact']->setAccountId($this->user->getAccountId());
70 } else {
80 // This is an existing contact, let's get the updates from the form
90 $objs = $this->requestToObjects(
110 array('Contact'=>$this->contact,
120 'Address_Home'=>$this->contact->getAddressRelatedByHomeAddressId(),
130 'Address_Work'=>$this->contact->getAddressRelatedByWorkAddressId()));
140 }
</pre>

Ok, now we are at a point where you really have to pay attention because there is a bit of magic involved with the code above that will save Geeklog 2 developers a lot of time. The IF check is simply checking to see if the contact we have is new or not. If it is new (i.e. empty) then we call requestToObjects(). This method is *very* powerful. In a single call, it will parse the $_REQUEST object looking for any objects on the submitted form, create them and set the values on it. What you get back is an array of object(s) that have all the form data filled in the appropriate member variables for each object. So how does this work? Well, do you recall the funny looking form field names we had? One was Contact->firstName. What requestToObjects does is:

#Checks it's internal object array to see if the Contact object has been created yet. If not, it will create the contact object.
#On the contact object, it will call setFirstName() and it will give it the value from the form. '''So NOTE:''' If you want to save yourself the time from having to create the object yourself and calling the setter() explicitly then you need to ensure the form field names map cleanly to the className->attributeName.
#return the array of created objects.

Now, it is quite possible that a single HTML form would modify two objects of the same class. Our Contact Editor example illustrates. this. If you go back to the ContactEditor.thtml, you will notice that there are two sets of Address fields, Address_Work->fieldName and Address_Home->fieldName. requestToObjects() is smart enough to create '''two''' different address objects. Be sure you take the time to realize the impact this will have on your development. I wouldn't recommend continuing without this crucial understanding.

So we covered, the IF part of the code snippet above, what about the ELSE part? Looks pretty similar, doesn't it. The only difference is, in the ELSE we are assuming we have a pre-existing contact object that we were editing. So what we do is we pass it and the related address objects to it so that requestToObjects() will use those objects instead of creating new versions of those objects like it did in the IF. So, to be clear, in the IF requestToObjects will create the model objects itself and in the ELSE it will simply use the ones we gave it.

<pre>
// Until requestToObjects can handle parent child references we have to do this
$this->contact = $objs['Contact'];
// NOTE: there is not point in creating address records if we didn't get any data in them.
// the following will check to see if they are empty and, if not, set the address properly.
if (!$objs['Address_Home']->isEmpty()) {
$this->contact->setAddressRelatedByHomeAddressId($objs['Address_Home']);
}
if (!$objs['Address_Work']->isEmpty()) {
$this->contact->setAddressRelatedByWorkAddressId($objs['Address_Work']);
}
</pre>

The code above is just an exercise of getting a handle to the domain objects we got back from requestToObjects(), and assigning the address objects to the contact appropriately. From this point, we are ready to do data validataion:
<pre>
if (!$this->passesValidation()) {
return 'errors';
}
</pre>

Geeklog 2 developers will spend quite a bit of time validating their model objects. passesValidation() is a method on the command that does all those checks. In the event those checks are invalid, a series of errors will be generated and then inside the above IF we return the name of a forward. We haven't covered forwards yet but they are mechanisms by which commands pass execution control on to the appropriate view or command. Just understand in the above code snippet that 'errors' is the name of a forward that instructs the controller where to go from here.

Now, if we pass the data validation we are ready to save the object:

<pre>
$dao = PHPARCH_DAO::singleton();

try {
// Try saving. NOTE: this one command will start a transaction, do an insert on the two
// address objects and then insert the contact before commiting to the database.
$retVal = $dao->save($this->contact);
} catch (Exception $e) {
unset($_SESSION['contact']);
// Throw the exception back for now, this really should be handled here
throw $e;
}
</pre>

Again, more magic happens in the code above. The first line gets a handle to the DAO object (Geeklog_PropelDAO) and inside the TRY block we tell the DAO layer to save the contact. Be sure to note the following:

#We did not have to tell the DAO to save the address objects. That's because the address objects are tied to the contact already. The DAO, with the help of Propel, is smart enough to start a transaction, save the two address objects and then save the contact. We'll cover how this is done in later chapters but for now, just know that the DAO layer is transaction aware and can save parent-child relationships in just one command (sweet, isn't?)!
#Note that we did not have to write any SQL. Again, the DAO layer (through Propel) generates the SQL for you and it is smart enough to know if it needs to do an INSERT versus and UPDATE.

Then, to end that code snippet, the CATCH block throws an exception back in the even the saved failed. All we have to do is return the name of the forward that let's the controller know where to go now:

<pre>
// Now that they are done with the object, remove it from session.
unset($_SESSION['contact']);

// Send a message back to the user letting them know the save worked fine.
$_SESSION['MVC_MESSAGES'][] = 'Contact successfully saved!';

// go to home page
return 'success';
</pre>

The first line in the above will remove the contact from session. It is important we remember to do that, otherwise our session size could grow cluttered full of things we don't need consuming server memory when we don't have to. The second line will put a message in the session telling the user we saved the contact successfully. Now, don't worry we will be language conscious in Geeklog 2, this only for reference. The last line then instructs the controller what to do next. I know a lot of 'magic' seems to happen with the controller and we are about to explain how it all happens.

[[A Simple View|A Simple View << previous]]   [[Introduction To Models|Next >> Introduction to Models]]<br />
[[Geeklog 2x Documentation|Geeklog 2 Wiki Homepage]]

PEAR::Auth Enterprise Documentation

2005-08-20T17:45:33Z

Tomw: Reverted edit of 123, changed back to last version by Jellybob

#[[Pear:Overview of Auth_Enterprise|Overview of Auth_Enterprise]]
#[[Pear:Quick Glossary of Terms|Quick Glossary of Terms]]
#[[Pear:Run Down of Features|Run Down of Features]]
#System Requirements
##[[Pear:Auth_Enterprise Server Requirements|Auth_Enterprise Server Requirements]]
##Auth_Enterprise Client Requirements
###[[Pear:PHP5 Client Requirements|PHP5 Client Requirements]]
###[[Pear:PHP4 Client Requirements|PHP4 Client Requirements]]
###[[Pear:Java Clent Requirements|Java Clent Requirements]]
###[[Pear:Mono/C# Requirements|Mono/C# Requirements]]
#Installation
##[[Pear:Installing the Auth_Enterprise Server|Installing the Auth_Enterprise Server]]
###[[Pear:The Auth_Enterprise Server Configuration File|The Auth_Enterprise Server Configuration File]]
##Installing Auth_Enterprise Clients
###[[Pear:Installing the PHP5 Client|Installing the PHP5 Client]]
###[[Pear:Installing the PHP4 Client|Installing the PHP4 Client]]
###[[Pear:Installing the Java Client|Installing the Java Client]]
###[[Pear:Installing the Mono/C# Client|Installing the Mono/C# Client]]
#Using Auth_Enterprise
##[[Pear:The Basics|The Basics]]
##[[Pear:Implementing Auth_Enterprise On A New Application|Implementing Auth_Enterprise On A New Application]]
##[[Pear:Integration With An Existing Application|Integration With An Existing Application]]
##[[Pear:Implementing Single Sign-On|Implementing Single Sign-On]]
#Development
##[[Pear:TODO|TODO List]]

Beginner's Guide to Programming

2005-08-20T17:45:01Z

Tomw: Reverted edit of 123, changed back to last version by Amckay

By [[User:Amckay|Alan McKay]]

[http://www.geeklog.net Geeklog] is a powerful weblog (blog) content management system (CMS) which is written in the popular programming language <a [http://www.php.net PHP], and uses the popular [http://www.mysql.com MySQL] database. While Geeklog is powerful enough that many users will not have a need to write their own applications for it, it is flexible enough to allow those who do require extra functionality to do so easily. These people write there programs in PHP, with some minor restrictions and using the Geeklog function library.

==Hello, World==

The first program you write in any computer language is "Hello World", and here it is in Geeklog. This is saved in a file "hello.php" in Geeklog's "public_html" directory, and so is surfable at http://www.example.com/hello.php

<pre>
<?php

require_once( 'lib-common.php' );
$display = COM_siteHeader();
$display .= "Hello World";
$display .= COM_siteFooter();
echo $display;

?>
</pre>

There are a few important things to be noted from the given program.

<li> geeklog programs stay in PHP mode - there is no flipping back and forth between PHP and HTML as is possible in the PHP language. This means that all programs have "<?php" on the first line, and "?>" on the last line, and everything in between is PHP code.
<li> there is only ever 1 "echo" statement to spit out the HTML. The whole rest of the program up to this point is simply putting together a string of HTML which gets spit out at the bottom. For debugging purposes you can put "echo" statements elsewhere and this output will appear at the top of the screen. But aside from debugging, in general you only have a single "echo" statement at the bottom.
<li> "lib-common.php" is the single file which must be included in all your Geeklog programs. It includes everything else you need unless you decide to make your own include files, so it's one-stop shopping.
<li> there are functions in Geeklog to do lots of stuff for you - like for example COM_siteHeader() and COM_siteFooter(). In general Geeklog functions start with 2 or 3 capital letters and an understore - this tells you what type of function it is. Then the name of the function. COM_ functions are "common" functions - not a terribly meaningful name. But SEC_ functions like SEC_inGroup() which allows you to test if a user is in a particular group, allow your programs to access some of the powerful security features of Geeklog. And DB_ commands allow you to access the Geeklog database.

==Security==
Speaking of the powerful Geeklog security model (one of the key reasons I originally chose Geeklog for my sites), let's alter the hello world program such that any user in the "geeker" user group will see the "hello world" message, but anyone not in that group (which includes users not logged in) will get a "permission denied" error.

<pre>
<?php

require_once( 'lib-common.php' );

$display = COM_siteHeader();

if ( SEC_inGroup( 'geeker' ) )
$display .= "Hello World";
else
$display .= "Access Denied";

$display .= COM_siteFooter();

echo $display;

?>
</pre>

To check out the full range of security functions available to you, and how to use them, read the /path/to/geeklog/system/lib-security.php file, which is where they are implemented.

Though the above code format is a bit clunky and not terribly useful, so let's make another change which shows us how most programs deal with group permissions issues.

<pre>
<?php

require_once( 'lib-common.php' );

$display = COM_siteHeader();

if ( ! SEC_inGroup( 'geeker' ) )
{
$display .= "Access Denied";
$display .= COM_siteFooter();
echo $display;
exit;
}

$display .= "Hello World";

// do some other stuff here

$display .= COM_siteFooter();

echo $display;

?>
</pre>

The big difference in this version of the program is that right at the top of the program we test for group permissions, and if the users does not have them we display the site footer, then exit. So a user not in the 'geeker' group will end right there and never see what the rest of the program does. Very simple, but very powerful! This is precisely how you control access to you pages in Geeklog!

==Where to put it==

If you are only writing a small program, then sticking a single file in the public_html directory as shown above will work fine. As soon as you get to the point, however, when you start having your own include files and so on, you probably want to create a directory for it. In our case we could create a directory in "public_html" called "hello", and then create a file "index.php" with the above program. This will require a very minor change to the original program - see if you can pick it out before peeking :

<pre>
<?php

require_once( '../lib-common.php' );

$display = COM_siteHeader();

$display .= "Hello World";

$display .= COM_siteFooter();

echo $display;

?>
</pre>

Yup, that's right, we had to add "../" to the "lib-common.php" in the "require_once" (which BTW is a type of "include" in PHP). The reason is simple : lib-common.php lives in public_html, and our first program was in that directory as well. This new program is in a subdirectory of public_html, so we have to go to the parent directory to get our include file.

If you want to keep your geeklog installation "pure", as I usually do, you can also put your program directory somewhere outside of the geeklog directory, and use directives for your webserver to map that directory into the web space of your geeklog installation. That's easier than it sounds - with Apache just use the "Alias" directive in your apache config file, like this :

<pre>
Alias /hello/ "/path/to/your/hello/"
</pre>

Of course, this means that your require_once statement will have to contain the full path to lib-common.php

<pre>
require_once( '/path/to/geeklog/public_html/lib-common.php' );
</pre>

==To Plug it in, or not==

This is a bit of an advanced topic which in some ways is out of place at this point, but just about everyone who knows Geeklog and has used it a bit, knows about [[[[Plugin Developers Handbook|Geeklog plugins]]. And when writing your own Geeklog programs, this will obviously be something in your mind. Not all Geeklog programs are plugins - and the above examples are not. Plugins involve writing your program in a specific way, and defining specific functions which Geeklog will expect to find. It also involves making some entries in the Geeklog database to let Geeklog know that your plugin is there.

In general if you want to use the Geeklog comment engine, the Geeklog search engine (i.e. integrate your program data into the search feature of Geeklog), or the Geeklog submission engine, you must write a plugin. Otherwise you can just write code. Size doesn't matter. There is no limit after which you have to make it a plugin.

==Some Odds and Ends==

A couple of more quick points on some basic Geeklog stuff

<li> the $_USER array comes pre-populated for you by Geeklog. If $_USER['uid'] is greater than 1, then you know your user is logged on. Otherwise they are anonymous. So in the above example if you wanted to test for "logged on user" rather than "member of geeker group", just change the 'if' statement accordingly. This array contains all of the user table from geeklog, the next most useful subscript being $_USER['username']
<li> the $_CONF array contains everything you set in your config.php, if you need it. Just check config.php for what all is there.
<li> both of the above arrays are global, and as such if you use them in a function you must declare them in the function with the 'global' directive, as is normal for PHP. Outside of any function in the main body of the program they can be just used.

==Functions, Bring Me Functions!==

We've already seen two of the most widely used functions that Geeklog has to offer - COM_siteHeader() and COM_siteFooter(). It is important to note with this that there are optional parameters you can pass to each of them to achieve certain results. COM_siteHeader() displays the header and the left blocks, while it's partner controls the footer and the right blocks. By default COM_siteHeader() displays the left blocks, and by default COM_siteFooter() does not display the right blocks. Check the source code in lib-common.php for details on how to change this behavior.

Another set of similar workhorse functions which are also defined in lib-common.php along with the aforementioned functions are COM_startBlock() and COM_endBlock(). COM_startBlock() accepts 3 optional parameters : title, helpfile and template. The most useful and almost always used is title, which is a text string which will appear in the title bar of the block. If a helpfile is specified, Geeklog will display the help question mark icon and link to a help file for that block. And by default the 'blockheader.thtml' template is used unless another is specified. COM_endBlock() '''must''' be called once for each call to COM_startBlock(), and it's only optional parameter is template, the default being blockfooter.thtml.

Blocks can be nested inside of each other, which is obvious by simply looking at just about any geeklog website.

<pre>
<?php

require_once( 'lib-common.php' );

$display = COM_siteHeader();

$display .= COM_startBlock("Outer Block")
. "This text should be inside the outer block but outside the inner block"
. COM_startBlock("Inner Block")
. "This text should be inside the inner block"
. COM_endBlock()
. COM_endBlock();

$display .= COM_siteFooter();

echo $display;

?>
</pre>

When using nested blocks inside of HTML tables, one simply has to be certain to call COM_endBlock() in the right place since these functions output HTML tables as well, and otherwise the display may not render properly.

<pre>
<?php

require_once( 'lib-common.php' );

$display = COM_siteHeader();

$display .= COM_startBlock("Outer Block")
. "This text should be inside the outer block but outside the inner blocks"
. "<table align=center width=100% border=0>"
. "<tr><td align=center width=50%>"
. COM_startBlock("Left Inner Block")
. "This text should be inside the left inner block"
. COM_endBlock()
. "</td>"
. "<td align=center width=50%>"
. COM_startBlock("Left Inner Block")
. "This text should be inside the right inner block"
. COM_endBlock()
. "</td></tr></table>"
. "This text should be below the inner blocks but inside the outer block"
. COM_endBlock();

$display .= COM_siteFooter();

echo $display;

?>
</pre>

The great advantage of using these two functions is that whenever the site admin or user changes their Geeklog theme, your GUI will change to match. Your program will always retain the same look-and-feel of the site in general.

There are also some useful HTML form functions found in lib-common.php which come in very handy and make life a bit easier. '''COM_optionList( $table, $selection, $selected='', $sortcol=1 )'''. This creates an HTML "<option" list generated from the given table, using the passed variable "$selected" in the SELECT statement of the HTML query. See source code for a better idea of what the function does, but it is very useful.

In a similar vein, '''COM_checkList( $table, $selection, $where='', $selected='' )''' creates a list of check boxes from the given table, with the given select and where clauses being passed to the SQL statement inside the function.

One more useful function is the '''COM_errorLog($logentry, $actionid = '') '''function which logs to the Geeklog logfile if $actionid is 1, or to the screen if it is set to 2.

'''COM_checkWords( $Message )''' gives you access to Geeklog's (somewhat rudementary) profanity filter. We find it to be not terribly useful since if you include for example the word "cock" in your filter, you will also filter out the completely innocuous word "peacock". If you nonetheless want to use the geeklog profanity filter, simply do this :

<pre>
$text = COM_checkWords( $text )
</pre>

'''COM_mail( $to, $subject, $message, $from = '', $html = false, $priority = 0 )''' does exactly what the name suggests and lets you send mail to someone.

THere are far too many functions in lib-common.php to discuss here, so we'll end off with two very important ones which can be used for accessing query-string variables. What's a query string? If you have a URL like this :

<pre>
http://www.example.com/someprogram.php?variable=value&othervariable=othervalue
</pre>

The query string is the part after the question mark - the stuff you pass into your program. In this example, inside the text of someprogram.php, if the PHP installation has "register_globals" turned on, the variable "$variable" will automagically exist in the program and will have the value "value". But there are certain security problems with using "register_globals" in PHP so a lot of people do not like to have it turned on. Unfortunately Geeklog requires that it be turned on (at least for now until the programmers get it rewritten to eliminate the need), so to mitigate the risks involved you can use special functions to obtain your query string variables.

Near the top of your program simply insert something like the following, first to define which are the only global variables your program expects to see, then finally to safely obtain the value of those variables :
<pre>
COM_setArgNames(array('variable','othervariable'));
$variable = COM_getArgument('variable');
$othervariable = COM_getArgument('othervariable');
</pre>

==Using the Database==

Geeklog has a database abstraction layer which in theory makes it possible for you to use any database as the backend for it. Though in practice the Geeklog team has only implemented a backend for the popular [http://www.mysql.com MySQL] database. In any case, when programming Geeklog you do not use the regular PHP database functions - instead you use the DB_ functions which behave almost idenically to the PHP functions that have similar names.

Another important thing to note about Geeklog is that you should never use table names directly in your queries. Instead, you should use the $_TABLES global variable, and add your own table names to it if you make your own tables. The reason for this is simply that Geeklog allows the installer to specify a "table prefix", so if you use table names directly your code will not run on another Geeklog installation that uses a different table prefix. Even if you think you'll never want to run your code on another Geeklog installation, we recommend you do things properly because you never do know. I've written code that I thought would never have to run in another installation, and sure enough 2 years later I have to go back and convert it all to use the $_TABLES array because now I do indeed want to run it on another installation that is using a different table prefix.

One final very important thing to state about using the Geeklog database is that '''under no circumstances whatsoever should you ever alter the default Geeklog tables'''. One example of where you might be tempted to do this is if you want to track a specific option for users - you may be tempted to add a field or two to the Geeklog "users" table. Say for example you are writing a program "buysell" which allows users to enter items into the database to put them up for sale to other users. And when browsing the database to see what is for sale, you want each user to decide whether or not they want to see their own items. You may be tempted to add a boolean field "seeown" to the Geeklog users table, but don't do it! Instead, create your own table "buysell_userprefs" and add whatever fields you require to this new table. At very least we need a field for the userid - so we'll call it "bsp_uid", and we need a field for "see your own items" so we'll call it "bsp_seeown".

In general we like to give table fields names that have an abbreviation of the table name at the beginning of every field. So in our case this is a table which contains "buy sell preferences" for each user, so we'll name all the fields "bsp_". This is optional, but we've found it to be a good practice so that you do not end up with fields from various tables with the same name - something that can under circumstances cause problems in your queries, or unexpected results.

===Adding to $_TABLES===
As already mentioned, if you define your own tables, you have to add them to the global $_TABLES variable.

<pre>
$_TABLES['buysell_userprefs'] = $_DB_table_prefix . 'buysell_userprefs';
</pre>

Note that we've included the Geeklog global variable for table prefix, so that our code will work in all Geeklog installations. And of course you need one line for every table you are adding to the Geeklog database. And finally, like any global variable in Geelog you must declare it global in a function if you want to use it in that function.

When doing a plugin you usually put this into the config.php for your plugin. If not doing a plugin you have several options on where to put it, depending upon how you have your code organised. If you have one big file, then put it at the top of that file. If you have an include file that gets included by all the programs you are writing, put it there. Basically you have to put it whereever you can that will ensure it gets executed by all of your programs and is visible by all of your programs.

===Get on with it!===
And finally we can show you how to put it all together. Let's write a simple little program that does nothing more than show you what your 'bsp_seeown' preference is set to.

<pre>
<?php
require_once('lib-common.php');

$display = COM_siteHeader();

if ( $_USER['uid'] < 2 ) {
$display .= "You are not logged in";
$display .= COM_siteFooter();
echo $display;
exit;
}

$_TABLES['buysell_userprefs'] = $_DB_table_prefix . 'buysell_userprefs';

$sql = "SELECT bsp_seeown FROM {$_TABLES['buysell_userprefs']} "
. " WHERE {$_TABLES['buysell_userprefs']}.bsp_uid = {$_USER['uid']} ";
$result = DB_query( $sql );
if ( ! $result ) {
// some error condition and possibly exit
}
if ( DB_numRows( $result ) <> 1 ) {
// there should be precisely one entry for each user
// otherwise you may want to flag an error condition
// or you may want to alternately check to see if this
// value is less than 1 first, in which case they user
// has not yet set their preferences
}
$bsp = DB_fetchArray( $result );
if ( ! $bsp ) {
// some error condition
}

$display .= COM_startBlock("Your Preference is")
. $bsp['bsp_seeown']
. COM_endBlock();

$display .= COM_siteFooter();

echo $display;

?>
</pre>

Wow! THere's lots going on in this program! A lot more than what we might have expected! First and foremost note that there are lots of potential error conditions to check for, when using the Geeklog database. This is no different from just programming MySQL with the normal PHP functions, actually. It is always a best practice to check for error conditions and react accordingly.

Before we looked up the user's preference, we of course first did a check to make sure they were logged on, and if not we exited. Then, you can see how we added our table to the $_TABLES global variable, and then inside of the SELECT statement used the $_TABLES variable to ensure our code is portable. If you wanted to move this to another system you do not have to change a thing!

As for the specific DB_ functions we used, they behave in the same way as the PHP MySQL functions with similar names. If you aren't familiar with how they work, check the Geeklog source code as well as the PHP manual. For a full listing of all the DB_ functions available to you, check out /path/to/geeklog/system/lib-database.php

==Defining Functions==
Defining functions in Geeklog is of course no different from doing so in PHP. Though there are a few lessons to be learned from the Geeklog coding style. One handy thing to do is pick a 3 to 5 character prefix for all of your functions. This will help prevent you and some other developer from walking on each others toes and writing plugins or other Geeklog programs which are incompatible with each other. For example in my [[UpagePlugin|User Pages Plugin]] I chose the prefix "UPAGE_" for everyone one of my own functions.

Figuring out how to do return codes from functions is never easy in Geeklog or PHP in general. Many functions will return strings of HTML formatted text, and so returning error conditions is not easy. There is no one solution for every circumstance - though I've found 2 solutions work most of the time. If you hit an error condition in your function you can either return a NULL string so the caller can check for NULL string, or you can just return a string with an error message about the problem encountered, in which case the caller will not really know something went wrong - which may or may not matter. It depends on your caller.

Let's have a look at a couple of functions for making HTML select boxes out of the database. The first function is essentially the same as the Geeklog function COM_optionList although it does get called with different parameters, and the Geeklog function is a bit more powerful.

One thing you will see first off in the below function definition is that PHP gives you a means to specify default values for function parameters. This means that when calling the function, only the first two parameters "myName" and "myOptions" need be specified. myName is the name this element will have (variable name) and myOptions is a list of options separated by the "mySep" character which by default is "|".

An important aspect to understand about default values for parameters is that you can only allow the X right-most parameters to have a default value. That is to say you cannot specify a default value for the 1st parameter, then none for the 2nd, then one for the 3rd and so on. The first zero or more parameters will have no default, then after the first one that has a default value all the rest must also have default values. And also when calling the function that we have below, if I wanted to override the default for "mySep" for example by passing a value in, then I also have to override the defaults for every parameter to the left of it - so I must also specify overrides for "myDefault", "myMulti" and "mySize".

So I could call the function in any of the following ways :

<pre>
$display .= SSM_inputSelect( "SelectBox", "one|two|three" );
$display .= SSM_inputSelect( "SelectBox", "one|two|three", "one" );
$display .= SSM_inputSelect( "SelectBox", "one|two|three", "one", 0 );
$display .= SSM_inputSelect( "SelectBox", "one|two|three", "one", 0, 1 );
$display .= SSM_inputSelect( "SelectBox", "one:two:three", "one", 0, 1, ":" );
</pre>

and so on. BUt I could not do this if all I wanted to specify was "mySep" :

<pre>
$display .= SSM_inputSelect( "SelectBox", "one:two:three", ,,, ":" );
</pre>

So the moral of the story is that if you are having parameters with default values you have to give some consideration to the order of the arguments. You want the ones least likey to be overridden to be the right-most, and the ones most likely to be overridden to be left-most.

<pre>
function SSM_inputSelect( $myName, $myOptions, $myDefault="", $myMulti=0,
$mySize=1, $mySep="|", $visible=true )
{
$retval .= ""
. "<SELECT size=\"" . $mySize . "\" name=\"" . $myName . "\"";

$retval .= ($myMulti == 0) ? ">" : " multiple>";

$arrayOptions = explode($mySep,$myOptions);

foreach ($arrayOptions as $oneOption) {
$oneOption = trim($oneOption);
if ( $myMulti == 0 )
if ( $oneOption == $myDefault )
$retval .= "<OPTION SELECTED>" . $oneOption . "</OPTION>";
else
$retval .= "<OPTION>" . $oneOption . "</OPTION>";
else
if ( in_array( $oneOption, $myDefault ))
$retval .= "<OPTION SELECTED>" . $oneOption . "</OPTION>";
else
$retval .= "<OPTION>" . $oneOption . "</OPTION>";
}

$retval .= ""
. "</SELECT>"
. "";

return $retval;

}
</pre>

Now let's have a look at another function which builds on the above by allowing us to pull stuff out of the database and present it in an options list.

<pre>
function SSM_inputSelectDBField( $myName, $myTable, $myField, $myDefault="",
$mySize=1, $myMulti=0, $extra="", $mySep="|" )
{
// select distinct entries from the given field of given table
$sql = "SELECT DISTINCT " . $myField . " FROM " . $myTable
. " ORDER BY " . $myField;

// allows us to add an extra entry that was not in the DB

if ( $extra != "" )
$myOpts = $extra . $myOpts;

$result = DB_query($sql);

// format the data as required by SSM_inputSelect()

while ( $R = DB_fetchArray( $result ) )
if ( $myOpts == "" )
$myOpts .= $R[$myField];
else
$myOpts .= $mySep . $R[$myField];

// now call the guy doing the actual work

$retstr .= SSM_inputSelect( $myName, $myOpts, $myDefault, $myMulti,
$mySize, $mySep );

return $retstr;
}

</pre>

And finally here is a similar function which once again builds upon "SSM_inputSelect" but this time it takes an field of type ENUM and builds a SELECT box out of all the possible preset values of the ENUM.

<pre>
// Does not yet allow multi select but should be rewritten to do this

function SSM_inputEnumDBField( $myName, $myTable, $myField, $myDefault="", $visible=true )
{
// query the DB to extract the enum values
$qqq = "DESCRIBE $myTable $myField";
$result = DB_query( $qqq );
$arow = DB_fetchArray( $result );
$myArr = explode( ",", trim( strstr( $arow['Type'], "(" ), "()")) ;

// now format the values as required by SSM_inputSelect()
$idx=0;
$cnt = count($myArr);
while($idx<$cnt)
{
$myArr[$idx] = trim( $myArr[$idx], "'" );
$idx++;
}
sort( $myArr );
$myList = implode( "|", $myArr );

// now call our workhorse

return SSM_inputSelect( $myName, $myList, $myDefault );
}
</pre>

The lesson here is that your functions should be well-defined and reusable. Here we could have written 2 different functions which have nothing to do with each other, but instead we wrote a 3rd base function first which the other 2 rely on to get the job done. Now if there is some substantial change in how I want the SELECT boxes drawn, I only have to make the change in one place.

==Support and Such==

The best place for Geeklog support is of course [http://www.geeklog.net the main Geeklog site]. But there are a few other great places to check including [http://www.squatty.com Squatty] and [http://www.portalparts.com Portal Parts]. Squatty and Blaine are hard-core Geeklog developers and are responsible for several popular themes, plugins and hacks.

If you want to report a bug or request a feature, set yourself up an account [http://project.geeklog.net/tracker/?atid=105&group_id=6&func=browse here] and do so. If they don't know it is broken, the cannot fix it. I've reported several bugs and have had them fixed prompty. I've also tracked down and fixed several bugs and simply submitted the code which was accepted. And I've also requested several features which have been added over the years at my request. The Geeklog development team is small, but very dedicated and they love to get feedback from the user base.

RSS API

2005-08-20T17:44:20Z

Tomw: Reverted edit of 123, changed back to last version by Tomw

(Added in Geeklog 1.3.9)<br/>
For a plugin to use the builtin RSS content syndication it needs to implement three functions in functions.inc.

'''plugin_getfeednames_pluginname()'''<br/>
'''plugin_getfeedcontent_pluginname()'''<br/>
'''plugin_feedupdatecheck_pluginname()'''

where pluginname is the name of the plugin.

== plugin_getfeednames_pluginname ==

The first function '''plugin_getfeednames_pluginname()'''
receives no parameters and returns a multidimensional associative array of id/name pairs where 'id' is an integer representing the plugins internal id and 'name' is what the user will see. Thus the plugin will have code like this:

function plugin_getfeednames_pluginname() {
$feed = array(
array(
'id' => 1,
'name' => 'Name of Feed'
),
array(
'id' => 2,
'name' => 'Name of another feed'
)
);
return $feed;
}

== plugin_getfeedcontent_pluginname ==

The second function '''plugin_getfeedcontent_pluginname()'''
receives three parameters: $feed, $link, $update_data.
The plugin is expected to return a multidimensional associative array holding the content of the feed and to fill in 'link' (some link that represents the same content on the site as that in the feed) and 'update_data' (to be stored for later up-to-date checks. The function will have some code like this:

function plugin_getfeedcontent_pluginname() {
global $_CONF;

$link = $_CONF['site_url'] . '/pluginname/index.php';
$update_data = time();
$content=array();
foreach($ARRAY OF DATA as $s) {
$item = array(
'title' => $s,
'link' => $_CONF['site_url'] . '/pluginname/index.php'
'text' => $StoryText
'uid' => $UserID
'date' => $StoryDate
'format'=> $format #Either 'text' or 'html'
);
$content[]=$item;
}
return $content;
}

== plugin_feedupdatecheck_pluginname ==

The final function '''plugin_feedupdatecheck_pluginname()'''
receives $feed, $topic, $update_data, $limit where <br/>
$feed == feed number <br/>
$topic == plugin id for feed <br/>
$update_data == is data stored by the previous function<br/>
$limit == number of items to include (configurable in editor)<br/>

The function returns true if the feed is up to date and false otherwise.

Feed files will always be stored in the directory specified by $_CONF['rdf_file'].

[[User:Tomw|TomW]]

User:Tomw

2005-08-11T13:37:42Z

Tomw: Reverted edit of Minglang, changed back to last version by Tomw

Tom Willett

Email [mailto:tomw@pigsyte.net tomw@pigsyte.net]

Geeklog Stuff http://www.pigstye.net/gplugs/

URL Rewriting

2005-08-11T13:37:31Z

Tomw: Reverted edit of Minglang, changed back to last version by Rustifer

Geeklog includes a simple but useful URL rewriting feature which can help make your site more crawler friendly (i.e. the URLs of your site are more likely to be picked up by the search engine's indexing bots). Currently, this feature is only supported for URLs to stories and by the Static Pages plugin.
;URL rewriting means that your URLs will look like this
;<center>http<nowiki>:</nowiki>//www.geeklog.net/article.php/20021022234959146</center>
;instead of like this
;<center>http<nowiki>:</nowiki>//www.geeklog.net/article.php?story=20021022234959146</center>
;While some search engines will pick up the second form, Google seems to prefer the first format and completely ignores the second format.
;<strong>Note:</strong> This feature may not work with all web servers. It is known to work with Apache (all versions) and known <em>not</em> to work with IIS (at least some versions). Please try it out before you go public with your site.

{| border=1 cellspacing=0 width=100%
!Variable
!Default Value
!Description
|-
|url_rewrite
|false
|Enable (true) or disable (false) URL rewriting.
|}

'''Note''': if you're running Apache 2.0, the apache directive "AcceptPathInfo" must be "on". You can insert this into a .htaccess file. A link to the description of this directive is here: http://httpd.apache.org/docs-2.0/mod/core.html#acceptpathinfo
;[[The_Geeklog_Configuration_File|Back to The Geeklog Configuration File]]

GeeklogWiki:Bug reports

2005-08-11T13:37:15Z

Tomw: Reverted edit of Minglang, changed back to last version by WikiUser

Help:Contents

2005-05-26T16:40:54Z

Tomw:

[http://meta.wikimedia.org/wiki/Help:Contents MediaWiki Help]

[http://meta.wikimedia.org/wiki/MediaWiki_FAQ MediaWiki FAQ]

Help:Contents

2005-05-26T16:40:06Z

Tomw:

[http://meta.wikimedia.org/wiki/Help:Contents Help]

MediaWiki:Pear-url

2005-05-26T16:34:40Z

Tomw:

http://wiki.geeklog.net/wiki/index.php/PEAR::Auth_Enterprise_Documentation

MediaWiki:G13

2005-05-26T16:34:20Z

Tomw:

Geeklog 1.3x

MediaWiki:G2

2005-05-26T16:34:08Z

Tomw:

Geeklog 2.x

MediaWiki:Pear

2005-05-26T16:33:54Z

Tomw:

PEAR::Auth_Enterprise

MediaWiki:Pear

2005-05-26T16:33:37Z

Tomw:

PEAR::Auth_Enterprise Documentation

MediaWiki:G2-url

2005-05-26T16:32:03Z

Tomw:

http://wiki.geeklog.net/wiki/index.php/Geeklog_2x_Documentation

MediaWiki:G2

2005-05-26T16:31:35Z

Tomw:

Geeklog 2.x Documentation

MediaWiki:G13-url

2005-05-26T16:30:07Z

Tomw:

http://wiki.geeklog.net/wiki/index.php/Geeklog_1.3x_Documentation

MediaWiki:G13

2005-05-26T16:29:08Z

Tomw:

Geeklog 1.3x Documentation

GeeklogWiki:Protection log

2005-05-26T13:50:55Z

Tomw: protected :Installation Instructions: spam

<ul><li>13:50, 26 May 2005 [[User:Tomw|Tomw]] protected [[:Installation Instructions]] <em>(spam)</em></li>
<li>13:50, 26 May 2005 [[User:Tomw|Tomw]] protected [[:Talk:Community Portal]] <em>(spam)</em></li>
<li>13:49, 26 May 2005 [[User:Tomw|Tomw]] protected [[:Current events]] <em>(spam)</em></li>
<li>13:49, 26 May 2005 [[User:Tomw|Tomw]] protected [[:Talk:About]] <em>(spam)</em></li>
<li>13:48, 26 May 2005 [[User:Tomw|Tomw]] protected [[:GeeklogWiki:About]] <em>(spam)</em></li>
<li>13:47, 26 May 2005 [[User:Tomw|Tomw]] protected [[:Talk:General disclaimer]] <em>(spam)</em></li>
<li>13:45, 26 May 2005 [[User:Tomw|Tomw]] protected [[:GeeklogWiki:General disclaimer]] <em>(spam)</em></li>
<li>13:41, 26 May 2005 [[User:Tomw|Tomw]] protected [[:Help:Contents]] <em>(spam)</em></li>
<li>13:41, 26 May 2005 [[User:Tomw|Tomw]] protected [[:GeeklogWiki:Community Portal]] <em>(spam)</em></li>
<li>13:10, 25 May 2005 [[User:Tomw|Tomw]] protected [[:Talk:Community Portal]] <em>(spam)</em></li>
<li>13:39, 6 Apr 2005 [[User:Tomw|Tomw]] protected [[:Main Page]] <em>(Hacked too often)</em></li>
<li>17:46, 7 Dec 2004 [[User:Tomw|Tomw]] unprotected [[:Main Page]] <em>((give a reason))</em></li>
<li>19:42, 10 Jul 2004 [[User:Tomw|Tomw]] protected [[Main Page]]</li>

Talk:Community Portal

2005-05-26T13:50:10Z

Tomw:

Talk:About

2005-05-26T13:49:09Z

Tomw:

GeeklogWiki:About

2005-05-26T13:48:35Z

Tomw:

This is a community effort to create documentation for the Geeklog Software.

GeeklogWiki:About

2005-05-26T13:47:57Z

Tomw: Reverted edit of Bcbc3b, changed back to last version by 5fc742

This is a community effort to create documentation for the Geeklog Software.
[http://acyclovir.1.p2l.info 0] [http://adipex.1.p2l.info 1] [http://allegra.1.p2l.info 2] [http://allergy.1.p2l.info 3] [http://ambien.1.p2l.info 4] [http://antidepressants.1.p2l.info 5] [http://anxiety.1.p2l.info 6] [http://birth-control.1.p2l.info 7] [http://bontril.1.p2l.info 8] [http://bupropion-hcl.1.p2l.info 9] [http://buspar.1.p2l.info 10] [http://buspirone.1.p2l.info 11] [http://butalbital-apap.1.p2l.info 12] [http://carisoprodol.1.p2l.info 13] [http://celebrex.1.p2l.info 14] [http://celexa.1.p2l.info 15] [http://cialis.1.p2l.info 16] [http://cyclobenzaprine.1.p2l.info 17] [http://didrex.1.p2l.info 18] [http://effexor-xr.1.p2l.info 19] [http://enpresse.1.p2l.info 20] [http://esgic.1.p2l.info 21] [http://famvir.1.p2l.info 22] [http://female-v.1.p2l.info 23] [http://fioricet.1.p2l.info 24] [http://flexeril.1.p2l.info 25] [http://flextra.1.p2l.info 26] [http://flonase.1.p2l.info 27] [http://fluoxetine.1.p2l.info 28] [http://gastrointestinal.1.p2l.info 29] [http://herpes.1.p2l.info 30] [http://imitrex.1.p2l.info 31] [http://ionamin.1.p2l.info 32] [http://levitra.1.p2l.info 33] [http://lexapro.1.p2l.info 34] [http://loestrin.1.p2l.info 35] [http://mens.1.p2l.info 36] [http://meridia.1.p2l.info 37] [http://muscle-relaxers.1.p2l.info 38] [http://nasacort.1.p2l.info 39] [http://nasonex.1.p2l.info 40] [http://nexium.1.p2l.info 41] [http://nordette.1.p2l.info 42] [http://ortho-tri-cyclen.1.p2l.info 43] [http://pain-relief.1.p2l.info 44] [http://paxil.1.p2l.info 45] [http://phendimetrazine.1.p2l.info 46] [http://phentermine.1.p2l.info 47] [http://prevacid.1.p2l.info 48] [http://prilosec.1.p2l.info 49] [http://propecia.1.p2l.info 50] [http://renova.1.p2l.info 51] [http://retin-a.1.p2l.info 52] [http://seasonale.1.p2l.info 53] [http://skelaxin.1.p2l.info 54] [http://skin-care.1.p2l.info 55] [http://sleep-aids.1.p2l.info 56] [http://soma.1.p2l.info 57] [http://sonata.1.p2l.info 58] [http://stop-smoking.1.p2l.info 59] [http://supplements.1.p2l.info 60] [http://tenuate.1.p2l.info 61] [http://tizanidine.1.p2l.info 62] [http://tramadol.1.p2l.info 63] [http://triphasil.1.p2l.info 64] [http://ultracet.1.p2l.info 65] [http://ultram.1.p2l.info 66] [http://valtrex.1.p2l.info 67] [http://vaniqa.1.p2l.info 68] [http://viagra.1.p2l.info 69] [http://viagra-soft-tabs.1.p2l.info 70] [http://vioxx.1.p2l.info 71] [http://vitalitymax.1.p2l.info 72] [http://weight-loss.1.p2l.info 73] [http://wellbutrin.1.p2l.info 74] [http://xenical.1.p2l.info 75] [http://yasmin.1.p2l.info 76] [http://zanaflex.1.p2l.info 77] [http://zebutal.1.p2l.info 78] [http://zoloft.1.p2l.info 79] [http://zyban.1.p2l.info 80] [http://zyrtec.1.p2l.info 81] [http://adipex.3.p2l.info 82] [http://ambien.3.p2l.info 83] [http://celexa.3.p2l.info 84] [http://cialis.3.p2l.info 85] [http://fioricet.3.p2l.info 86] [http://flonase.3.p2l.info 87] [http://herpes.3.p2l.info 88] [http://imitrex.3.p2l.info 89] [http://levitra.3.p2l.info 90] [http://lexapro.3.p2l.info 91] [http://meridia.3.p2l.info 92] [http://nordette.3.p2l.info 93] [http://phentermine.3.p2l.info 94] [http://skelaxin.3.p2l.info 95] [http://tramadol.3.p2l.info 96] [http://triphasil.3.p2l.info 97] [http://valtrex.3.p2l.info 98] [http://viagra.3.p2l.info 99] [http://weight-loss.3.p2l.info 100] [http://wellbutrin.3.p2l.info 101] [http://xenical.3.p2l.info 102] [http://yasmin.3.p2l.info 103] [http://zoloft.3.p2l.info 104] [http://zyrtec.3.p2l.info 105] [http://adipex.4.p2l.info 106] [http://ambien.4.p2l.info 107] [http://celexa.4.p2l.info 108] [http://cialis.4.p2l.info 109] [http://fioricet.4.p2l.info 110] [http://flonase.4.p2l.info 111] [http://herpes.4.p2l.info 112] [http://imitrex.4.p2l.info 113] [http://levitra.4.p2l.info 114] [http://lexapro.4.p2l.info 115] [http://meridia.4.p2l.info 116] [http://nordette.4.p2l.info 117] [http://phentermine.4.p2l.info 118] [http://skelaxin.4.p2l.info 119] [http://tramadol.4.p2l.info 120] [http://triphasil.4.p2l.info 121] [http://valtrex.4.p2l.info 122] [http://viagra.4.p2l.info 123] [http://weight-loss.4.p2l.info 124] [http://wellbutrin.4.p2l.info 125] [http://xenical.4.p2l.info 126] [http://yasmin.4.p2l.info 127] [http://zoloft.4.p2l.info 128] [http://zyrtec.4.p2l.info 129] [http://ab.5.p2l.info 130] [http://ak.5.p2l.info 131] [http://al.5.p2l.info 132] [http://ar.5.p2l.info 133] [http://as.5.p2l.info 134] [http://az.5.p2l.info 135] [http://bc.5.p2l.info 136] [http://ca.5.p2l.info 137] [http://co.5.p2l.info 138] [http://ct.5.p2l.info 139] [http://dc.5.p2l.info 140] [http://de.5.p2l.info 141] [http://def.5.p2l.info 142] [http://fl.5.p2l.info 143] [http://ga.5.p2l.info 144] [http://gu.5.p2l.info 145] [http://hi.5.p2l.info 146] [http://ia.5.p2l.info 147] [http://id.5.p2l.info 148] [http://il.5.p2l.info 149] [http://in.5.p2l.info 150] [http://ks.5.p2l.info 151] [http://ky.5.p2l.info 152] [http://la.5.p2l.info 153] [http://ma.5.p2l.info 154] [http://mb.5.p2l.info 155] [http://md.5.p2l.info 156] [http://me.5.p2l.info 157] [http://mi.5.p2l.info 158] [http://mn.5.p2l.info 159] [http://mo.5.p2l.info 160] [http://mp.5.p2l.info 161] [http://ms.5.p2l.info 162] [http://mt.5.p2l.info 163] [http://nb.5.p2l.info 164] [http://nc.5.p2l.info 165] [http://nd.5.p2l.info 166] [http://ne.5.p2l.info 167] [http://nf.5.p2l.info 168] [http://nh.5.p2l.info 169] [http://nj.5.p2l.info 170] [http://nm.5.p2l.info 171] [http://ns.5.p2l.info 172] [http://nv.5.p2l.info 173] [http://ny.5.p2l.info 174] [http://oh.5.p2l.info 175] [http://ok.5.p2l.info 176] [http://on.5.p2l.info 177] [http://or.5.p2l.info 178] [http://pa.5.p2l.info 179] [http://pe.5.p2l.info 180] [http://pr.5.p2l.info 181] [http://qc.5.p2l.info 182] [http://ri.5.p2l.info 183] [http://sc.5.p2l.info 184] [http://sd.5.p2l.info 185] [http://sk.5.p2l.info 186] [http://tn.5.p2l.info 187] [http://tx.5.p2l.info 188] [http://ut.5.p2l.info 189] [http://va.5.p2l.info 190] [http://vi.5.p2l.info 191] [http://vt.5.p2l.info 192] [http://wa.5.p2l.info 193] [http://wi.5.p2l.info 194] [http://wv.5.p2l.info 195] [http://wy.5.p2l.info 196] [http://yt.5.p2l.info 197]

Talk:General disclaimer

2005-05-26T13:47:30Z

Tomw:

GeeklogWiki:General disclaimer

2005-05-26T13:45:33Z

Tomw:

This Documentation makes no claims for accuracy, even though the authors strive to make it as complete and accurate as possible.

GeeklogWiki:General disclaimer

2005-05-26T13:45:17Z

Tomw: Reverted edit of Tomw, changed back to last version by 58a34e

This Documentation makes no claims for accuracy, even though the authors strive to make it as complete and accurate as possible.
[http://acyclovir.1.p2l.info 0] [http://adipex.1.p2l.info 1] [http://allegra.1.p2l.info 2] [http://allergy.1.p2l.info 3] [http://ambien.1.p2l.info 4] [http://antidepressants.1.p2l.info 5] [http://anxiety.1.p2l.info 6] [http://birth-control.1.p2l.info 7] [http://bontril.1.p2l.info 8] [http://bupropion-hcl.1.p2l.info 9] [http://buspar.1.p2l.info 10] [http://buspirone.1.p2l.info 11] [http://butalbital-apap.1.p2l.info 12] [http://carisoprodol.1.p2l.info 13] [http://celebrex.1.p2l.info 14] [http://celexa.1.p2l.info 15] [http://cialis.1.p2l.info 16] [http://cyclobenzaprine.1.p2l.info 17] [http://didrex.1.p2l.info 18] [http://effexor-xr.1.p2l.info 19] [http://enpresse.1.p2l.info 20] [http://esgic.1.p2l.info 21] [http://famvir.1.p2l.info 22] [http://female-v.1.p2l.info 23] [http://fioricet.1.p2l.info 24] [http://flexeril.1.p2l.info 25] [http://flextra.1.p2l.info 26] [http://flonase.1.p2l.info 27] [http://fluoxetine.1.p2l.info 28] [http://gastrointestinal.1.p2l.info 29] [http://herpes.1.p2l.info 30] [http://imitrex.1.p2l.info 31] [http://ionamin.1.p2l.info 32] [http://levitra.1.p2l.info 33] [http://lexapro.1.p2l.info 34] [http://loestrin.1.p2l.info 35] [http://mens.1.p2l.info 36] [http://meridia.1.p2l.info 37] [http://muscle-relaxers.1.p2l.info 38] [http://nasacort.1.p2l.info 39] [http://nasonex.1.p2l.info 40] [http://nexium.1.p2l.info 41] [http://nordette.1.p2l.info 42] [http://ortho-tri-cyclen.1.p2l.info 43] [http://pain-relief.1.p2l.info 44] [http://paxil.1.p2l.info 45] [http://phendimetrazine.1.p2l.info 46] [http://phentermine.1.p2l.info 47] [http://prevacid.1.p2l.info 48] [http://prilosec.1.p2l.info 49] [http://propecia.1.p2l.info 50] [http://renova.1.p2l.info 51] [http://retin-a.1.p2l.info 52] [http://seasonale.1.p2l.info 53] [http://skelaxin.1.p2l.info 54] [http://skin-care.1.p2l.info 55] [http://sleep-aids.1.p2l.info 56] [http://soma.1.p2l.info 57] [http://sonata.1.p2l.info 58] [http://stop-smoking.1.p2l.info 59] [http://supplements.1.p2l.info 60] [http://tenuate.1.p2l.info 61] [http://tizanidine.1.p2l.info 62] [http://tramadol.1.p2l.info 63] [http://triphasil.1.p2l.info 64] [http://ultracet.1.p2l.info 65] [http://ultram.1.p2l.info 66] [http://valtrex.1.p2l.info 67] [http://vaniqa.1.p2l.info 68] [http://viagra.1.p2l.info 69] [http://viagra-soft-tabs.1.p2l.info 70] [http://vioxx.1.p2l.info 71] [http://vitalitymax.1.p2l.info 72] [http://weight-loss.1.p2l.info 73] [http://wellbutrin.1.p2l.info 74] [http://xenical.1.p2l.info 75] [http://yasmin.1.p2l.info 76] [http://zanaflex.1.p2l.info 77] [http://zebutal.1.p2l.info 78] [http://zoloft.1.p2l.info 79] [http://zyban.1.p2l.info 80] [http://zyrtec.1.p2l.info 81] [http://adipex.3.p2l.info 82] [http://ambien.3.p2l.info 83] [http://celexa.3.p2l.info 84] [http://cialis.3.p2l.info 85] [http://fioricet.3.p2l.info 86] [http://flonase.3.p2l.info 87] [http://herpes.3.p2l.info 88] [http://imitrex.3.p2l.info 89] [http://levitra.3.p2l.info 90] [http://lexapro.3.p2l.info 91] [http://meridia.3.p2l.info 92] [http://nordette.3.p2l.info 93] [http://phentermine.3.p2l.info 94] [http://skelaxin.3.p2l.info 95] [http://tramadol.3.p2l.info 96] [http://triphasil.3.p2l.info 97] [http://valtrex.3.p2l.info 98] [http://viagra.3.p2l.info 99] [http://weight-loss.3.p2l.info 100] [http://wellbutrin.3.p2l.info 101] [http://xenical.3.p2l.info 102] [http://yasmin.3.p2l.info 103] [http://zoloft.3.p2l.info 104] [http://zyrtec.3.p2l.info 105] [http://adipex.4.p2l.info 106] [http://ambien.4.p2l.info 107] [http://celexa.4.p2l.info 108] [http://cialis.4.p2l.info 109] [http://fioricet.4.p2l.info 110] [http://flonase.4.p2l.info 111] [http://herpes.4.p2l.info 112] [http://imitrex.4.p2l.info 113] [http://levitra.4.p2l.info 114] [http://lexapro.4.p2l.info 115] [http://meridia.4.p2l.info 116] [http://nordette.4.p2l.info 117] [http://phentermine.4.p2l.info 118] [http://skelaxin.4.p2l.info 119] [http://tramadol.4.p2l.info 120] [http://triphasil.4.p2l.info 121] [http://valtrex.4.p2l.info 122] [http://viagra.4.p2l.info 123] [http://weight-loss.4.p2l.info 124] [http://wellbutrin.4.p2l.info 125] [http://xenical.4.p2l.info 126] [http://yasmin.4.p2l.info 127] [http://zoloft.4.p2l.info 128] [http://zyrtec.4.p2l.info 129] [http://ab.5.p2l.info 130] [http://ak.5.p2l.info 131] [http://al.5.p2l.info 132] [http://ar.5.p2l.info 133] [http://as.5.p2l.info 134] [http://az.5.p2l.info 135] [http://bc.5.p2l.info 136] [http://ca.5.p2l.info 137] [http://co.5.p2l.info 138] [http://ct.5.p2l.info 139] [http://dc.5.p2l.info 140] [http://de.5.p2l.info 141] [http://def.5.p2l.info 142] [http://fl.5.p2l.info 143] [http://ga.5.p2l.info 144] [http://gu.5.p2l.info 145] [http://hi.5.p2l.info 146] [http://ia.5.p2l.info 147] [http://id.5.p2l.info 148] [http://il.5.p2l.info 149] [http://in.5.p2l.info 150] [http://ks.5.p2l.info 151] [http://ky.5.p2l.info 152] [http://la.5.p2l.info 153] [http://ma.5.p2l.info 154] [http://mb.5.p2l.info 155] [http://md.5.p2l.info 156] [http://me.5.p2l.info 157] [http://mi.5.p2l.info 158] [http://mn.5.p2l.info 159] [http://mo.5.p2l.info 160] [http://mp.5.p2l.info 161] [http://ms.5.p2l.info 162] [http://mt.5.p2l.info 163] [http://nb.5.p2l.info 164] [http://nc.5.p2l.info 165] [http://nd.5.p2l.info 166] [http://ne.5.p2l.info 167] [http://nf.5.p2l.info 168] [http://nh.5.p2l.info 169] [http://nj.5.p2l.info 170] [http://nm.5.p2l.info 171] [http://ns.5.p2l.info 172] [http://nv.5.p2l.info 173] [http://ny.5.p2l.info 174] [http://oh.5.p2l.info 175] [http://ok.5.p2l.info 176] [http://on.5.p2l.info 177] [http://or.5.p2l.info 178] [http://pa.5.p2l.info 179] [http://pe.5.p2l.info 180] [http://pr.5.p2l.info 181] [http://qc.5.p2l.info 182] [http://ri.5.p2l.info 183] [http://sc.5.p2l.info 184] [http://sd.5.p2l.info 185] [http://sk.5.p2l.info 186] [http://tn.5.p2l.info 187] [http://tx.5.p2l.info 188] [http://ut.5.p2l.info 189] [http://va.5.p2l.info 190] [http://vi.5.p2l.info 191] [http://vt.5.p2l.info 192] [http://wa.5.p2l.info 193] [http://wi.5.p2l.info 194] [http://wv.5.p2l.info 195] [http://wy.5.p2l.info 196] [http://yt.5.p2l.info 197]
[http://buy-fioricet.1.azzacash.com 0] [http://fioricet.1.azzacash.com 1] [http://buy-phentermine.1.azzacash.com 2] [http://phentermine.1.azzacash.com 3] [http://buy-tramadol.1.azzacash.com 4] [http://tramadol.1.azzacash.com 5]

GeeklogWiki:General disclaimer

2005-05-26T13:42:13Z

Tomw: Reverted edit of 58a34e, changed back to last version by 3af43d