PostNuke

Site search

Search results

Number of hits: 25

PostNuke .8 MS2 Release Estimate   (News)

the news module include an Ajax editing interface, but I will leave it to our new team member Arjen to go into more detail here.

So, to the title of the article. We estimate that 0.800 MS2 will be released sometime during the week beginning 4th September. At this point, the core database structure will be finalized and we can begin to finish work on cross database compatibility. That, and the completion of all modules, will be the aim of 0.800 MS3, with the first RC soon after.

Please feel free to test MS2 in development environments once it is released, but we must stress again that 0.800 code should

Generated on August 22, 2006.

Ready For Your Testing: Phoenix 0.726rc2   (News)

Generated on June 29, 2003.

PostNuke Is Alive and Well   (News)

launch of demo.postnuke.com, it should be up sometime this week. But if you are the adventurous type you can always download the
latest/greatest from CVS (http://developers.postnuke.com) but remember this is only for review purposes and shouldn't be used on
"live" sites. If you're unfamiliar with CVS you can get more information here:http://noc.postnuke.com/docman/view.php/5/2/CVS%20Access%20Guide.htm
And we encourage those interested in discussing the upcoming release we have setup a forum
on the NOC and you can access it here: http://noc.postnuke.com/forum/forum.php?forum_id=227
There has also been
some concern regarding the templating engine, it is true we lost work on the
PTE (Phoenix Template Engine) but the XTE (Xanthia Template Engine) will be as
powerful as the proposed PTE. Both
are based
on SMARTY which
brings a wealth of features to the table. We've created a compare/contrast
chart for you to review so you can see that the templating
engine will deliver on the promises made in the past and we're confident you won't be disappointed
with the new engine's features and stability. (Note:
XTE
is currently in CVS for review.)

In
the past promises have been with the fullest intentions of keeping
them -- but as we all know life happens and plans change.
But as said before we've picked up and are marching (coding) forward.
And just so you know the progress is exciting, and that sense of
excitement is back in the project. We are having fun and in my
opinion this is the most important part of the project because in the end that's what everyone gets in return, that sense of accomplishment and the joy of doing it. So as a team we are working
towards, a 1.0 release.
Other changes have been made behind the scenes too. For example, Harry has passed the day-to-day activities of managing the project to me. He is still actively involved in the project in the background and in an advisory role. Moving forward things aren't going to change from the original vision of the project but we are looking toward the future as technology and developments change. Keeping up-to-date on new technologies will allow us to integrate any new developments into the project when it makes sense.
Finally, the community of PostNuke is what makes it unique, and therefore I consider keeping you informed about all aspects of development an important part of being a member of this community. So announcements will be made on a monthly basis under the category pnUpdates. We're all working toward the same goals, so let's all have fun in helping to create software that provides each of us with the kind of solution that meets our needs.

Development Information Links
PostNuke
Task Tracker
http://noc.postnuke.com/pm/?group_id=5
Reporting
Bugs
http://noc.postnuke.com/tracker/?atid=101&group_id=5&func=browse
Feature
Requests
http://noc.postnuke.com/tracker/?atid=104&group_id=5func=browse
Interesting
Statistics:
May 2003 PostNuke Downloads: 14,884
 
Informational
Links
What
is CVS (Concurrent Versions System)?

Generated on June 9, 2003.

Installing PostNuke for Absolute Beginners   (News)

the Installing PostNuke for the Absolute Beginner is now back and has been updated to tie in with the Phoenix release of PostNuke.

It can be found in the same place it used to be at http://postnuke.bloodymongrel.com. I hope people find it a useful guide to help them get started in the world of PostNuke. There is also a demo site online where people can just play around and see if PostNuke is what they need.

I hope you enjoy reading my tutorial as much as I enjoyed writing it and may it allow PostNuke to be available to users of all skill levels.

Cheer

Generated on March 19, 2003.

PostNuke Security Fix (SQL injection and directory traversal)   (News)

SOLUTION
It is recommended that all admins upgrade their sites to v7.2.3 and applythe latest security fix package available right now from the locations listed below.

As a general rule of thumb we also recommend to never use the 'root' user to connect to MySQL server be it the PostNuke installation or any other application running on the web.

UPDATED PACKAGES
1. PostNuke Phoenix 0.723 (tar.gz format) http://download.hostnuke.com/pafiledb.php?action=file&id=15
Size/MD5 checksum: 1844005 606a6f45dcd232c48e2bfb37004339a6

2. PostNuke Phoenix 0.723 (zip format)
http://download.hostnuke.com/pafiledb.php?action=file&id=16
Size/MD5 checksum: 2620869 0d54b12224746bacc5258b1b9562525a

3. Security Fix for PostNuke Phoenix 0.723 (zip format) http://download.hostnuke.com/pafiledb.php?action=file&id=17
Size/MD5 checksum: 14495 a6ea89e6669c35f80a7167ecf1aafa47

4. Security Fix for PostNuke Phoenix 0.723 (tar.gz format) http://download.hostnuke.com/pafiledb.php?action=file&id=18
Size/MD5 checksum: 11785 1e5c2a2c938aba4103af1e217a37d9c7

ADDITIONAL INSTRUCTIONS
Place the files contained in this patch into the appropriate PostNuke directory that replaces the current files because by doing this you are applying the security fix to the system fix and this is what is meant by "patching" your system.


CREDITS
This exploit has been originally found by pokleyzz, pokleyzz@scan-associates.net from Scan Associates (http://scan-associates.net/)and has been reported on 2003-02-24.

Generated on March 7, 2003.

Updates from the Top !   (News)

it's worth, I have never seen a weirder 'campaign' angle than the 'Free PostNuke' buttons that were part of that 'open letter'.

In context to this original situation, I would like to take a line here to extend special thanks to those of other projects, who have posted common sense messages in support - Thanks, Zoom of Envolution, and thanks MikesPub of Xaraya.


I've also noticed that some issues have been raised about potential developments and moves towards a closed development model - this is simply not true, and I can assure you that this won't happen. To those that recall both the genesis of PostNuke, as well as the recent splits into two forks a while back, the openess of the development model was at the core of all of them. We split from php-nuke mainly because of the closed development that it's author advocated. Now, why would we want to replicate that same mistake on here? I believe someone aptly stated "Those who do not learn from the past are doomed to repeat it", and while this certainly holds true for many of life's situations, it is nowhere more true than in open source projects.

So, rest assured, PostNuke will always remain *free*, and development will always remain open. That's my pledge.

Now, this doesn't mean that just about ANYONE will and can receive CVS access, and that we can have a wild committ-fest of anyone with a 'net connection. In order to maintain a certain level of sanity, development, and particularly commits to the CVS *must* be done in a controlled, orderly fashion. This means that while I advocate keeping CVS always open for anonymous check-out, and welcome submissions of fixes and patches, we *must* keep the ability to commit to core developers to prevent insanity and chaos (we've had that at one point in the past). We're working out a system that should be able to accomodate most needs. Stay tuned.


We've also had a couple of changes in the management, the absence of both of which will be felt, as PostNuke owes both a tremendous deal. Effective immediately, both Neo and MagicX have left the project to hopefully pursue life outside of the stresses that this project brings with it. Neo and MagicX were responsible for much of the enhancements, infrastructure, and site redesigns that you've witnessed after the Xaraya split, and they masterfully carried the weight of the project on their shoulders during my hiatus. As you also may know, Neo was the mastermind behind the Phoenix Rendering Engine (based on SMARTY). I fully understand the reasons behind the departures (the words 'burned out' come to mind), and while I wish them well, I also want to assure them that any help will always be only an e-mail away, and that both will be welcome back here in a heartbeat.


One of the changes is also that the NOC will not be going away, but it will change servers, and this change is going to happen this weekend. In fact, I plan on doing a minor and major overhaul of the server and infrastructure, adding a bit here, a tweak there.


Lastly, we're also readying a new security fix release, and have several incremental updates to the 0.723/0.724 codebase planned, to tide existing installations over with asked-for enhancements and minor fixes until arrival of 0.8 (née 0.725). Stay tuned for more news on those.


Finally, there will be a couple of follow-up articles, including 'openings' for help with some of the stuff planned for the immediate future. Like I said - Stay Tuned!

-Harry

P.S. Oh yeah, and for those wondering "Where the hell have you been all his time???", let me just give the short of it being "

Generated on March 1, 2003.

Phoenix Template Rendering Engine Overview   (News)

What is a template
rendering engine?
A template rendering engine is the total separation (abstraction) of an
application business logic and rules from the content layer (output HTML, XHTML,
XML, PDF, etc.).
It includes dynamic variable substitutions
(replaces keywords or place holders with content), dynamic block substitutions
(for example the result of a record set from a query, for instance the number
of available news topics on the news index), amazing capabilities to process
unlimited nested loops among many others.
Conditional statements ( [if/elsif/else]
which allow you to make decisions based on user interaction in a easy to understand
way - optional).
The problem here is many template
solutions for PHP are based on regular expressions replacements, which highly
complicated the code and added an immense overhead into the application, this
regular expressions metaphor where hard to extend (and to adjust to taste),
and did not quite provided the complete separation of presentation and logic
(for example, to make rows of a table alternate colors, PHP code had to be adjusted).
Instead of following this route and
live with this and many other drawbacks, Phoenix takes advantage of a revolutionary
concept in template rendering engines, provided by the underlying architecture
of Smarty. The compilation of templates, which combines the speed of execution
of pure PHP code with the ease and simplicity of template syntax.

By using this approach template files
are first converted into PHP scripts before they are executed. This may sound
costly in terms of performance until you consider that this need only be done
when the template file is changed! Once a template file is compiled, they are
stored for later use (and re-use) using a caching mechanism, the end result
being a reduced overall server load. Which can be greatly enhanced (up to 500%)
by the use of PHP optimizing technologies like php-accelerator or the zend optimizer.
The second biggest advantage is extensibility,
this is what really makes it invaluable for programmers and designers a like.
How
does it work?
Basically templates work quite similar to
any ordinary HTML page, it uses template "tags" to distinguish dynamic content
(data provided from the DB for example), from the rest of the template which
is pure HTML. This tags are then automatically replaced with the result of the
requested data set. All template functions are loaded on demand this means that
even though the rendering engine is extensive in its core it will only load
the required code to perform each task.
While working with templates you have
access to a wealth of resources, among them are:
Variable modifiers (allows you to
transform on the fly the properties of your content, i.e. Caps, indentation,
upper, lower, etc)
Configurations files, this allow you
to define settings for colors, width and practically every aspect of the HTML
properties.
A wealth of Built-in functions which
you can extend, like free block/module positioning, forms, automatic clocking
and encoding of email addresses, and many more.
You can easily add and extend with
your own functions the engine by taking advantage of the plugin architecture.
Many new possibilities arise with
the capability of automatic inclusion of static content either local or remote
on the fly.
Caching Mechanisms designed with great
granularity allows you to specify how, when and how often cached content is
to be updated (turning your site as fast as static HTML) and under which conditions.
Advanced
Features:
Prefilters
Are
a set of functions that are run on the templates prior to them being compiled
with the engine. (i.e. removing unwanted comments form them)
PostFilters
This are functions that are executed after the templates have been compiled.
And
could help add valuable data to the whole of your templates if needed on the
fly.
Output Filters
This
feature allows you to apply settings to content while being executed as opposed
to the postfilters which are applied just before saving the compiled template.
Multiple Template sources
Templates
may come from a variety of sources, like file system or the database.
Debugging Tools
Intelligent
debugging console which allows one to trace all items related to any and all
templates used diring the course of a page rendering.
The pnTemplate API
This
(Template Application Programming Interface) provides a set of tools that allow
programmers to harness the full set of combined resources that PostNuke and
Smarty provide.
It follows the pnAPI naming conventions
and style and will become easy to understand and apply for module/block programming,
taking current modules and block to the next level of usability, flexibility
and power.
The Phoenix Administration (system)
Module
It’s the front end for all
this power and flexibility, it manages Themes, which are composed of templates,
that in turn have interesting properties like content type (html, xhtml, csv,
rss, pdf), they also belong to a layout, each template in a theme can belong
to a different layout, lets say you create a "dual column" layout and an "art
deco", layout for theme "Postnuke", then you can switch among this with the
click of a mouse, and then apply this system wide, templates also belonge to
specific zones (header, footer, module content, block etc.)
Templates install them self’s
similar to how modules do now, you just drop in the theme, initialize and activate
it and you are done. Same goes for upgrades or removal.
In the Phoenix administration module
you can manage all aspects of the rendering engine, including but not limiting
to all properties that control the behavior of smarty, as well as create, edit,
delete templates and its related itmes online, since you can choose to use file
system templates or db templates or a combination of both, you can directly
upload new sets of templates from your computer.
You have access to CSS and many more
properties and features, the best part of it all is, that you can have the old
themes right along with the next generation and also switch back and forth among
them with ease.

Templates Programming Language
and Active Zones
While working with templates
as mentioned before you can either use the basic template "tags" and normal
HTML or go beyond the choice is yours, the rendering engine provides enough
resources to make your templates intuitive and intelligent accomplishing quite
complex task with great ease, this is done by the use of what we call the "active
zones". Active zones are special place holder areas in your templates that allow
execution of commands from the template rendering language or invocation of
plugins, filters, variable substitution, etc.
This, active zones, are easy to use
and apply and will make your life very simple and productive while customizing
and designing the site of your dreams.
In conclusion the Phoenix Template
Rendering Engine can answer the needs and requirements of both novices and
seasoned developers or graphics designer. And it supports popular HTML editors
like DreamWeaver among others allowing you to use visual tools to enhance your
experience and over-all productivity harnessing all this power in one simple
place.


For reference if you happen to read this before the principal article of this series please read the first part which you will find here:
http://news.postnuke.com/modules.php?op=modload&name=News&file=article&sid=2357
Note: [ For clarification 1st quarter refers to the 1st four (4) months [Jan-Apr] of 2003, thus the goal is to have the 0.8

Generated on February 11, 2003.

The Future: Where is PN going?   (News)

Introduction
PN has grown both in core logic and in modules/blocks available, the lines
between the core logic and the modules and/or extensions have blurred at times,
forcing 3rd party developers to impose upon the core, creating incompatibilities,
delaying upgrades, and slowing response times from the system (pnCore).
So we'll get to the point in the
beginning, what can you look forward to in the next release of PN? A modularized
core, plug and play architecture, short URL's, admin redesign, a templating
engine (get
more info here), better security, caching, and a visual editor. Some
may be asking, "How is this going to be accomplished?" and "Who is going
to do it?" Read on and you'll discover who has volunteered their time, how
it is organized and how you can contribute.
Modularizing the core is key to separating
core logic and presentation layers. And the work on modularizing pnAPI, and
key core components is well under way and means you will see this change
in the next release 0.8 (code named: adam_baum). As a result of this modularization
future PN releases will include the following packages, (i.e. Core, Modules,
Languages, Docs, & Themes) and are reflected in the current CVS as main
categories which in turn hold the components belonging to it, (i.e. Modules:
Content, Legacy, Miscellaneous, ResourcePack and Utility).
Some of you may be asking yourself, "How
do these changes help me as a module dev, webmaster, or user?" First for
module devs, the categorization of data provides you with the ability to
group your module in a logical way within the current module structure already
available in PN. It will also provide a webmaster with the ability to better
use and manage their site, targeting their site to specific use or tastes.
For example, you can create and tailor your installations based on your personal
tastes, needs, or target audiences, i.e., site focusing on community, content,
e-commerce, or education. For users this won't make much difference to you
other than the site you are using will provide you with a richer user experience.
Also, webmaster/admin's can look
forward to new and enhanced core functionality. PN will now be able to categorize
modules, blocks, and content. Furthermore it will be able to resolve module
dependencies; for example, if you want to install the "News" module it would
require the installation of dependent modules that provide additional functionality.
The new installer will detect those dependencies and guide you in the set-up
process of customizing and installing PN. For example, a request for the "News" module,
requires the following additional modules: Submit_News, Topics and NS-AddStory,
so the installer will prompt the user to install these dependent modules
at the time of installation. Once all the demands are met the Wizard will
continue with the installation.
Of course in order to accomplish
the above successfully, another technology is needed that we will call the "Custom-Wizard".
The "Custom-Wizard" is a low level tool with the ability to handle the dreaded
Unix permissions, create, delete, set permissions and ownership among many
other things and will even work under "SAFE MODE" installations. So where
ever PHP runs the "Custom-Wizard" will work regardless of the ownership and
host system restrictions. This extended functionality will cut down almost
98% of the installation/customization issues present today in support requests.
The new and improved core will also
cater a solution for 3rd party developers who wish to hook directly into
the pnCore, to extend it in a safe and efficient way. This new plug & play
architecture will also be made available allowing module devs to tap into
the resources without the need of modifying core files. These changes alone
will provide certainty and unparalleled power and flexibility to all devs.
Also, new CMS importers will be available in order to convert from other
systems (i.e., PHPNuke, Xoops, Envolution) with as much accuracy as possible.
Also, another valuable tool, the
pnAntiCracker will become a module that will allow greater flexibility. By
doing this webmasters will be able to finer control its operation and general
properties.
The visual editor will also become
a module with cross browser/platform capabilities in the latest generation
browsers. Along with this last point PN will be able to automatically detect
browser type versions and current rendering capabilities aiding in the creation
of themes and templates, which will be possible to enable in a per module
setting.
Last but not least, this brings us
to templates. Yes, finally the 0.8 version of PN on top of the previous points
will bring you the Phoenix template-rendering engine. The work in the global
implementation of the Phoenix rendering engine will engage in parallel tasks
associated with it, as the complete compliance of all system and core modules
with the pnAPI. With the templating system short URL's are implemented and
all modules will be fully template based. The administration module will
have a new and improved design and new database back ends (i.e. postgreSQL)
with enhanced caching technologies for queries and content will be added
as well, a new logging mechanism will track trends and use of your site in
a friendly and powerful new ways.
This will be a next generation CMS
that includes a slim core, is extensible, modular and smart. And will support
several backend database servers taking full advantage of ADODB and will
finally provide a complete separation of core logic and presentation layers,
becoming an N-Tier application. (For those non-developers an N-Tier application
architecture is a model for developers to create a flexible and reusable
application. By breaking the application into tiers, developers only have
to modify or add to specific layers to change or scale up a tool.) http://www.webopedia.com/quick_ref/app.arch.asp




The benefits will be astounding. Developers can
focus on code; designers can work on layout and presentation; and writers
can focus on content.
This provides a solid foundation
to extend the users management area, abstraction of reusable code and much,
much more.
You may ask who will do this and
how?
It is with great pleasure that I introduce you to, the newly elected Task
Force Team Leaders and Members along with its responsibilities and Tasks definitions.


PostNuke Development
Task Force Teams
In order to streamline our efforts
and efficiently organize the work we are dividing the development into different
teams. Each team in addition to the responsibilities listed below will also
be responsible for keeping their specific tasks up to date in the NOC and
maintain any team related

PostNuke_Security
The security task team will primarily
be responsible for overall security of the PN core as well as responding
to the security mailing list. They will be the front line for all security
concern with PostNuke. They will also be responsible for the permissions
system found in PostNuke.
Team Leader: Tanis
Team Members: larsneo, markwest

PostNuke_Research
The research task team will primarily
be responsible exploring and testing new and fresh ideas and technologies
that could possibly be used in PostNuke. As new technologies are identified
they will be slated for inclusion in a future PostNuke release. Analyzing
the current needs of admins and conducting suability research to improve
the current state of PN
Team Leader: bharvey42
Team Members: Tanis, elgranazul, vworld, class007, spliffster, Neo, pnCorps

PostNuke_Modules
The module task team will primarily
be responsible for the non-core (with the exception of 3rd party modules)
modules and blocks found in a PostNuke release.
Team Leader: magicx
Team Members: skooter, nunizgb, class007, markwest, spliffster

PostNuke_Themes
The themes task team will primarily
be responsible for the core themes as well as the Phoenix rendering engine.
Team Leader: Neo
Team Members: magicx, vworld, bharvey42

PostNuke_Core
The core task team will primarily
be responsible for the PostNuke API, the Install/Upgrade scripts and other
core logic of the PostNuke.
Team Leader: larsneo
Team Members: Neo, magicx, nunizgb, skooter, lcabrera, spliffster, cybersliver

PostNuke_Languages
The language task team will primarily
be responsible for all things related to language within the structure of
PostNuke.
Team Leader: nunizgb
Team Members: elgranazul, class007

PostNuke_Database
The database task team will primarily
be responsible for the main database access found within PostNuke. Currently
that will be with the pnADODB logic, as well as moving the code forward to
be used with any database engine.
Team Leader: lcabrera
Team Members: skooter, Tanis, xaplo, cybersliver


PostNuke_Releases
The releases task team will primarily
be responsible for the versioning, packaging, and posting new releases to
the appropriate locations. They will be the packaging experts and will provide
many various packages, including but not limited to *.tar, *.zip, *.deb and
possibly others like *.rpm.
Team Leader: magicx
Team Members: larsneo, nunizgb, class007, bharvey42

PostNuke_Docs
The docs task team will primarily
be responsible for documentation found within the released PostNuke package.
That could be their own developed documentation or documentation from 3rd
parties.
Team Leader: infopro
Team Members: jim
hadfield, pnCorps, class007

All Task Force Team leaders where
elected among their peers in an open vote in the IRC meeting. After these
elections a final vote was taken for the following: Lead Developer and Communications
Officer.

The elected individuals where:
Lead Developer: Neo
Communications Officer: vworld
Last but not least, project manager
is HZink

Conclusion
This summarizes the results of the meeting, presents us with the goals and
objectives for this 1st quarter and allows us to see clearly into the future.
All of these new developments and implementations will, be performed in
such a way that existing modules, themes and blocks will work flawlessly
while new generations of them will be able to do as much and more. These
new developments will also allow you to leverage your current and future
faith in PostNuke to be safeguarded and extended exponentially.
We invite you all to help us, because
together go even farther than we could if we worked alone. And we'd like
to thank everyone involved in the community for your support you are the
reason this project is unique and different from every other CMS out there!
This is the road, this is the
vision, and future of PostNuke.

The PostNuke development team


Related
Links:
IRC meeting log
http://noc.postnuke.com/docman/?group_id=5
(Look under IRC Meeting logs document
category)

Organizational chart:
http://noc.postnuke.com/docman/view.php/5/31/pnOrgChart-2003b.png
pnDev
Profiles
http://developers.postnuke.com/modules.php?op=modload&name=phpWiki&file=index&pagename=bio
Phoenix
Rendering Engine Info
http://news.postnuke.com/modules.php?op=modload&name=News&file=article&sid=2358&mode=thread&order=0&thold=0

Generated on February 11, 2003.

Fellow PostNukers Cross Paths!!!   (News)

for about two years now. Before that I had briefly found phpnuke a month prior and quickly determined that PostNuke was for me.

While following links and looking around at all the neat stuff that was being created for both systems. I had run across a website that stuck in my mind because of the Topic icons and logos this webmaster used. It was a cartoon or characature of the webmaster. I didn't think much of it, it was just memorable.

This was at least a year or so ago. Shortly after I happened to be taken to his site again and realized that he had switched over to using the Postnuke system and recalled that topic icon again. Since then I stop by his site from time to time as I do alot of your postnuke websites looking for new and innovative things that you all are working on.

Recently I threw my hands up in the air and toyed around with the idea that I would just have to write my own programs and have to break down and learn php (like I am not busy enough already) so... I went to a local book store (Borders Books) close to home to see what kind of books I could find and see if I wanted to tackle such a project.

After seeing how thick the book was I decided quickly that it would be way to time consuming and I would have to again continue my search for a php programmer that was not busy and that was familiar with the PostNuke system and preferably local.

Its not real easy as you can't just open the yellow pages and find one. There isn't a section in the yellow pages for PostNuke PHP programmers (But I do invision one soon) And the searches I have done on the net have not been fruitful as I would prefer a local one that I could meet and share my great ideas and we could work and develop the ideas together. Of couse I would Pay them if I could only find one.

Well when I left the BIG FAT PHP BOOK behind on the shelf I had gone up to the information desk where they have all the intelegent workers there that know everything that is in the store and where to find it. I was now in search of another book of a different topic.

I was waiting as one guy was busy with a customer and the other was on the phone. It happened that the one on the phone was able to help me first. I asked this guy with long blonde hair in a ponytail and a goatee for help and he pointed me in the right direction for the type of book I was looking for and off I went.

My conclusions were right and I couldn't find any books about my subject and thought to myself that I may could write a book on such a thing ( basically a how to book on creating eBook).

I was about to leave that section when this guy came back up to me in the section he directed me to and asked me if I found what I was looking for.

I proceeded to tell him that I didn't and that was ok because of my idea to write such a how to book. Then I started to tell him the original reason I was there about the php book and that I gave up on the idea of programming my ideas myself and that I wish I could just find someone that knew php. He had this look on his face and so I asked him if he was into computers and if he knew anything about php and he said yes.

At that moment I was so excited that I was even in the same freaking state as a php programmer I right away said I need your number!

I then started to tell him that I use this software called Postnuke and was telling him how it works and he said he knew about it. I then got even more excited. You should've seen me I must have acted like the biggest nerd and kid because I was all giddy from excitement.

I said how cool that was that we met and I asked him if I could get his name and number so I could talk to him about the ideas I had.

He said sure and he pulled out a business card and handed it to me. As soon as I looked at his card I got excited allover again as I knew of him because I had been to his site many times. On his card he had that unforgettable icon/cartoon of himself and right away after looking at him again I saw the resemblence.

I told him that I had been to his site and I think he felt like a rock star because I was telling him how I stopped by his site and kept track of his developments and again I know the excitement was showing.

We chatted while he worked for another hour and before you know it he was getting off work. We went to the snack bar area and I gave him my number and emails and chatted more briefly and I had to leave to be somewhere else.

We have exchanged emails and are on track to a great new friendship based on our common postnuke interests.

I have been thinking back on that night and if certain things had not happened we would have never met.

One thing is that I never go to the book store anymore. I get all my info online anymore. the last time I was in a book store was a year ago. Let alone that one as that isn't the closest one to me.

Also that night I was heading to work and I had called them to tell them I would be in later because I knew it was going to be a slow night and I knew they wouldn't mind me coming in a little later than usual. I was on a quest. (little did I know what I would find)

If he was on the phone with the customer a little longer than the other guy then that other guy would've helped me and that would've been the end of that.

If He hadn't followed up to see if I had found what I was looking for I don't think we would've ever know about each other. I think it was great that his attention wasn't consumed by questions of another patron of the store

I think it was devine intervention that guided him back over to me.

It just goes to show you that you never really know if you are standing right next to a fellow PostNuker or not.

Im glad I found a new friend.

"Gordon aka Baohx here's to you!!! (b)(b) "

By the way I haven't told Gordon yet but I think we should start a local Postnuke Fan Club :)

Who knows maybe we will have more than two members. hehe.


Richard Wing
Phoenix AZ

Generated on February 10, 2003.

Polish translation for PN 0.722 Phoenix   (News)

Generated on December 13, 2002.

Page 1 / 3 (1 - 10 of 25 Total)