PostNuke

Site search

Search results

Number of hits: 4

Logging you in. hang tight!   (News)

last few months, there have been lots of rumors about the future of PostNuke, and also the failings of PostNuke as it is today.

We at Team PostNuke think that on this occasion of hitting 10,000 members, that we should point this out to the world, let you all know that PostNuke is alive and doing great, the numbers speak for themselves.

If you wanted to have a peek at our pnForums Stats page, you'd be surprised to find the numbers speak quite clear as to the success of the forums, and our support structure we have in place. You could also, if interested enough, have a look at our pnForums Memberlist on those forums, to see in more detail, how many people actually even had to post. Many hundreds have not. Are they lurking? Maybe. Did they find what they needed while they were here, went back to their own sites with the information they were seeking and continued to work on their sites? We would like to think so.

There are many other Content Management Systems out there, good ones, one's that are new and up and coming, others that have been around for many years and have spawned forks from them going in new directions, as is the history of PostNuke. But our numbers continue to grow by leaps and bounds. This says something, this says that PostNuke is "the" choice of users worldwide.

Many of you that have been around a long time, know that there have been slow times and fast times alike around the world of PostNuke, this is the way of open source I believe. Just when you think everythings going great, something gets in the way to slow things down. We have had a few of these kinds of set backs in past months. One thing is sure though, as people come and go, there remains one constant thru it all, that is, the PostNuke project itself.

This project has brought people together from all points of this small world we all live in, many new friendships have been born, some have been lost, but the idea that the project itself should live on has always been there at one point in time for all of us.

In eight months over 10,000 people have logged in for the first time on those forums to see what PostNuke was all about, many more new "pnUsers" do each day.

There are some CMS projects out there that have no forums at all, either they don't have the time to be bothered with their users, wanting to help them succeed and use the software, or, they just don't have the support infrastructure that we do here at PostNuke. This is just one of the many great things about this software, that is the support you get with it.

PostNuke is not a finished product, but you'd really find that hard to believe by looking at how many use it worldwide in many, many different countries and languages. We are all here because we like the software, we like the tools that have been created by the wonderful teams of the past, present, and future developers of PostNuke. I for one, want to thank them all for their contributions.

In the coming weeks as has been promised, PostNuke .726 will hit the streets running. This will be our last release until .80 which has not yet been announced as to when it will be ready, but I can assure you all that it is being developed by some great developers, and you may have even visited the test site by now, which is running on the new code. The improvements are great, the new tools being developed right now for that .80 release promise to be exciting for us all. You can expect to be supported when it gets here.

PostNuke is alive and doing great, the software is constantly being developed, and there's room for you to get involved. We are always looking for new pnUsers that have an interest in working with the team.

Our forums shine above the rest of those other Content Management Systems because of the pnCommunity and the way we support each other on a daily basis. Yes, there have been times when there's been bad press posted, nay sayers if you will, that have spoken up to say they are unhappy with how things are going, well, we're sure sorry that some feel this way. Look around, we're trying, we are succeeding, PostNuke is still growing, it's growing every day.

As always, you'll find the support you seek on these forums if you are a new user. If your a seasoned veteran, come join us, get involved and help out on the pnForums, help someone else get going with their very own PostNuke site. Together we will take PostNuke places it's never gone before. The interaction of developers with users here on these forums IMHO, is second to none. We take pride in the support we give those that come to ask for help.

As with everything else branded with the name PostNuke around here, the forums are constantly being reworked to provide a better place to come to and get help fast. Changes will be made there as often as necessary to insure this continues. If you'd like to get involved, and you know your way around the PostNuke software well, we invite you to pitch in, if you don't have time to drop by the forums every day, maybe you have the time to put together tutorials of things you know about. The Tutorials and Solutions area is a great place to publish your work, and it will surely help others coming in behind you, new to all of this.

We want to thank all that have helped out these past 8 months on our new pnForums to make them the success that they are, and we invite you all to look forward to the future of PostNuke.
Still growing, ever changing, filled with drama and ups and downs, this is PostNuke.

Welcome to PostNuke we're glad to have you with us.
Logging you in, hang tight! :)

Generated on June 5, 2003.

Mutant Dot Sixty-Four Released   (News)

asked to assemble a change log since the last release. That change log can be viewed here. As you can see it is pretty extensive.

What we have done is added quite a bit behind the scenes that will probably be transparent to you. However, the performance should be something that you will find at least a little better. I am going to list just a small portion of the changes (mainly because my memory is going, and I can't remember everything we have done in the past month).

New Language System -- Credit to nexia, adam_baum, and Sam Luxford-Watts. I've already left out a message on the new system last week, but this is pretty impressive to announce again. There is now a very small global file, with several files that are only used on specific page views. What this means to you is that on a normal pageview instead of your server parsing a 100k file, it is only parsing a 10-20k file and then the specific translations for that page.

Remember, there are some negatives, mainly that all the previous translations have to now be re-done. Work has already began on that and there is now 2 language files on SF (German and Thai) by Jan Hübener and Prateep Kulapalanont. It's a start, and as folks send me translations I will add them to our SourceForge page.

New Admin System -- Credit to Patrick and adam_baum (hope I'm not forgetting anyone here!) Goes hand in hand with the language system. We had to have a solid way of using file specific translations and this is what we came up with. This also goes a very long way to making the modules system a true plugin system, where all you have to do is drop the modules that you want to install in a single folder.

New Install File -- Credit to dacia and Micheal. Michael cleaned the mess that we had made with the install file and made it a modular system. It is very fast now, as well as a little nicer to look at, with a little easier directions to follow.

Text Santitizer -- Credit to Michael again -- This is a system that myPHPNuke has been using for quite some time. We have integrated it into PostNuke, because quite frankly, it works better than what we were using. With that system, we are also close to having a myPHPNuke upgrade file to being released.

Include_Once problem -- Credit to Patrick -- There were some problems with the previous release because we were using include_once commands for our mainfile.php. Patrick solved the problem with a custom function so the script should now work with all builds of PHP4.

AutoLink enhancements -- credit to Jens -- Jens made quite a few enhancements to his already great system of autolinking. This system is now a bit more user friendly, but also takes the place of the article.php key word linking.

Ability of choosing custom start page -- credit to Sascha -- A very popular request that we listen to. You can now choose the page that you want to be displayed on your index page. Very cool feature.

image consolodation -- nexia -- nexia trimmed the images that were no longer used out of the system to make the download of the package a little more reasonable

Sebastien has also done quite a bit towards running multiple sites off of one codebase. There are still some problems to iron out with that. Jun, besfred and Sascha also deserve some mentioning here for some of the wonderful work behind the scenes. They have all been working very hard on securing the script as well as some very nice performance enhancements. Let's also not forget Isaac and his work in the chat room with the support. Real nice job there, along with everyone else that is helping out!

I apologize to all the people that I didn't mention on this post. Everyone has done a woderful job, but my fingers are about t

Generated on October 8, 2001.

Lot of things to say.   (News)

e and powerful links manager. I have work hard to make it as I wanted and to feed it. You can see it in action on my site at links.
Ok, that just an example about tools that we want keep alive in our own site. But of course we try to integrate our tools as much as we can. So, as my site is multilingual, I would like to implement the multilingual feature from Postnuke. The problem is that I don’t know very well how this feature works. I mean I know how to use tags and how to implement vocabulary files but unfortunately I don’t know how to detect the language currently in service. I suppose we need to play with cookies but how to decode it, especially when my files are not in the root of Postnuke. But I think is not a problem cause a cookie can be read from an other folder ?? well that my first question. Is someone have some tutorials about how Postnuke works or is it to early to ask cause is in beta ? But I think it’s the same problem to develop modules. How to adapt which are existing if we don’t know what we must change ?

I think you will find that quite a few perl scripts like Gossamer Threads, would require quite a lot of work to work with PostNuke. I would perfer to look at functionality that is similar, than trying to port something that would take much longer

2. Also, the second issue is about modules and addons. As I like to have Gadgets ;) like child, I like to implement new tools on my site for the happiness of my visitors. I have found lots of interesting thinks from time to time. As everybody, we know how is frustrating to see feature working in other site but not on our, cause these modules have been primarily developed for PHPnuke. Everyone have notice that we are poor (Postnuke users) about working modules ;-( It’s cool to have a stable and well written “OS” but without applications to use with, who cares) That was the case of Linux against Windows. So I think it’s important to create a “real and clean” approach to increase the number of “Certified Postnuke modules”. As someone said it’s cool to offer this kind of guaranty which mean that a module have been correctly tested and written for Postnuke. I don’t want to blame anyone ;) but to be honest the “mutant_plugins pakage” was not a success at all. Only 2 modules had worked. And the forum…. Héhé I will come back later to speak about that. Well, concerning this issue, what I suggest is to create a board where everyone who found a module, will put information about it in a same place. So everyone will know what kind of module we can find among the php community. I say PHP community because sometime we found great tools that could me easily (or not so easily) transform in a module. We don’t have to reinvent the wheel all the time. I have already spoke with one module developer and he is ready to port his php module to Postnuke. I think that most of time, developer will be nice enough to make it available for Postnuke as long as it still compatible with PHP Nuke of course. Ok, I continue with my idea… The board will be viewable by everyone, and will offer this options:

a. Everyone put his ideas about a module he found or he would like to found.

i. This module exist and works for Postnuke (need to be certified),

ii. This module exist and but I’m not sure if it’s work for postnuke,

iii. This module was made for php nuke and don’t work for postnuke,

iv. This module doesn’t exist but can be built as modules,

v. I found a nice soft and would like that someone port as a module,

vi. I have an idea of a module,…



b. We offer the possibility to everyone to vote for the modules they want first. So we can develop modules, in priority, those which are the most needed. But of course everyone is free to develop which he wants in priority.
c. Then the next board will show:

i. the name of the module,

ii. the definition of it,

iii. the functionalities,

iv. which developers take care of this module,

v. the new functionalities that people would like to see implemented,

vi. the stages of the module development,

vii. ….

This, in order to know who do something to avoid people doing the same thing twice. We know how is frustrating to find 2 great modules which do the same things but both have one functionality that the other one don’t have. So, if we want both of this feature in our site we must choice one or install both modules ;-( . The better example to give is the module memberlist. Héhé I can’t tell you how much people have the both version in their site (like me, ok).



Well, this is how I see the things to perform and to go, all, in the same direction ;-)


Your ideas are valid, but right now, we are concentrating more on the core of the script to make the use of plugins even easier. If the core of the script is small, versital, and fast, then the plugins become even more viable.

This might however help those of you that are working on plugins to meet your site specific needs. Most plugins that I have found spring from necessity, rather than luxery.



Oh yes, 3rd issue. Concerning existing modules. As I saw in the forum, when we have problem installing a module, users explain their problem with it, and “niceguyeddy” (really nice guy) try to check where is the problem to solved it. But don’t blame it, if after one week the discussion fall in the dungeon and the problem still there. That’s normal cause he have to much thinks to do. As example here I will speak about Submit DHTML module ;) We still want it. Or IM-Buddy which still not a module at all. So, to solve this problem we need again a board where we will find :

1. the name of the module,

2. the problems encounter,

3. the causes and the error message,

4. the stages to solve problems (with colors green for problem solved, yellow for problem take in consideration by a developer, red for a problem not yet take into consideration). When I say problem solved, I want to say really solved and certified solved by the “Postnuke team” cause I see often someone says : “I’ve solved the problem but he haven’t test it widely before to say that, and the problem still be present.

Ok don’t know if I lost all of my readers but I continue héhé ;-)



Of course all I said before is valid for Postnuke development. When we notice a problem or when we have some idea about improving Postnuke where do we put our requests ? on the forum or you submit an article of course, but after one week who remember what you said and what the postnuke team answer ? You need to do a wide search inside forum or articles to see if the topics was treated. We need here again to see what’s going on. To follow and above all to not forgot what has been asked:

1. Where are you in the development stage,

2. Is my idea took into consideration,

3. Is this idea will be implemented in the next release,

4. Is this idea important for all ? Here again users could vote for the features they think are the most important.

5. some color again to see :

a. green, the feature is now implemented for the next released,

b. yellow, the feature is in course of development,

c. red, the feature is not yet take in consideration,



An example again ? Yes of course ;) I have notice that in postnuke 0.61 we can’t modified the type of the block we create, so I have ask if we could next time change the type of block (simple include file, html, links block,….) as we can change block language or position at anytime. The answer was yes it will be done for the next released but it’s still not ;) Here again I don’t blame someone ;) Just try to explain what we can do, to improve things ;) I’m a strategic consultant, it’s why I like to improve the way to manage things and to make the life better. Perhaps it will be done for the next release, perhaps they forgot, and perhaps someone will asked the same question again and again cause he doesn’t know if someone else have asked the same question 2 or 3 weeks before.

Concerning block I take the advantage to tell you that I encounter problems.

If I use :

 simple file include: it doesn’t interpret the php code of the file and show it’s content (code lines). In the file window I see this : “$row[url]“ how do I use it ? if I put an url inside [] no block appeared. If I put url inside the window and erase the code showed before, I can see the content of an html file correctly but if I come back to change block configuration the link have disappeared and I must retype the file root.

 Php script : I got error, can’t interpret ….error line 1….

So I use html block as before with a hack in my theme which interpret the path root of a file put inside the block. So I got my php file interpret correctly inside a block. But, because is there a but ;-) if I switch to an other language, the content still be in English for all language) .

For any bug what so ever, if it doesn't end up on SourceForge, then there is always the possibility that it will be lost on the forums. There are links to the bug reporting all over this site. It just needs to be used, so we can track and assign the problems:)


Ok it’s time to stop my annoying letter. Now I still alone to read myself boooooooo.

I will finish by the forum issue as I told you before. I just want to inform you that I found a really great and also free forum which will soon work with sql database. But use cgi to run. After lots of comparison it the direct challenger of “Vbulletin” the reference. Take a look at www.ikonboard They’re official and multilingual version will be available in the next two weeks. Test it, it’s a very very powerful forum .



Ok I have finish for now and I will come back soon to know what everyone thinks.



Thanks again to everyone for their job.

Generated on August 25, 2001.

Creating your own database tool in Nuke   (News)

to allow all visitors to the intrnaet (only registered users) to query this database, say by name of town oder name of company.



Big deal! You might say. Just modify the user.php and memberlist.php and there you go.

Right. But can you imagine that there is anybody in the Nuke community who needs exactly THIS feature? Probalby one person wants to add addresses, another one wants to add company profiles and another one just wants to add some products with details.



All ideas require that you can decide via and admin tool:



- which fields you need,

- how many fields you need,

- which fields can be searchable

- which fields contain the primary key



Then this system would create the appropriate tables in the Nuke database.



Now special registered users (with the new user system the assigning of different groups promises to work) could enter their data in the appropriate fields.



The "normal" registered user could call the page and search for some criteria.



Just imagine companies putting their job ads online. O.k., classified ads system, you might say. But the idea I had was to create a totally dynamic classified ads system where each user can decide himself, how it is going to be used.



Does anybode have an idea where to obtain such a system or would anybody like to tackle it? I can give ideas, unfortunately I am not a programmer.



Cheers and thanks for your attention.



Titus.

Generated on July 26, 2001.