PostNuke

Footnote: 1

Footnote: 1

Postnuke as I see it now is pretty function-centered. That means, if I have e.g. articles, pictures, and links belonging to the same topic, they are in totally different areas of the site.

More practical would be a content-centered approach: group the items by logical connections instead of functions. This reflects the thinking of an average non-programmer much better.

Here's the idea: why not introduce a hierarchical system where every item has a globally valid "parent" id that places it in the hierarchy. At the same time, finally realize the idea of center blocks, so that different kinds of contents (links, articles, etc) could be displayed on the same page.

Modules would probably need to provide a kind of "hook", which instead of displaying all (say) web links, would only return a formatted block for all items under a given parent id. The front page naturally would only contain items with parent id=0.

Footnote: 1

Footnote: 1

It seems to me that these are things that can be brought up in the forums, or can be resolved by RTFM. The result of making these requests in articles and the like are actually not as much to the poster's advantage as they think, for the following reasons:

A. If you post in the appropriate forum, people that have specific expertise in that area will respond if they know, whereas if you post it to the community at large a lot of time you might not get a response, or you might get bad advice from someone who is not an expert. Not a bad thing to contribute, but you'll get stronger support in specific forums than you will on the main page.

B. Many post these articles thinking that it will give them the quickest response, which is sometimes true. On the other hand, you may be inviting flames, or your question may not be addressed at all. If you post to the forums you may not get an answer as quick, but it'll probably be more complete and detailed.

C. Posting individual requests on these main pages unnecessarily takes attention away from community-wide development. It is more laborious for people looking for new modules, themes or bug fixes, when they're having to sift between feature requests, download locations and the real programming content.

I'm not an authority here on what should or shouldn't be done, I'm just giving people some suggestions on proper development etiquette. I'm not against people asking questions, but I think they should be routed to the proper location with a bit more care. This isn't meant as an attack on anyone, just a plea to make it a bit easier on all of us that visit...

-DietCoke
Techfocus

I heard this could be done. There could be a script that would go through each news stories and check each link within an a href tag to see if it is still active. If it isn't, it could either flag that news piece for deletion, or just delete it by itself.

What does everybody think?

A while ago I was looking for a decent classified system, and found none. The only script (open) that I liked was an auction system (http://www.phpauction.org). Probably the reason is that since classifieds are supposed to make money nobody wants to release one for free... who knows.

Therefore, I kinda forked phpauction, (in reality just modified it a bit here and there), and made it my classified system. Still is pretty rough around the edges, but it works, and I think that if enough bodies work on it, it can be made a nice piece of software.

It could even be made a PostNuke Plugin! However, I must admit my first priority will be to make it a good piece of software, and only then make it a plugin if anyone desires.

So hop in!. Development will follow the PostNuke way: Open to serious developers who want to help. I know my limitations, so if anyone out there wants to be a leader mysql guy, fine!, same for html, css, etc. The objective is to create a fine (open) classified system written in PHP.

Code is in CVS at sourceforge. I hope enough people are interested in making it a great piece of software, if not I'll have to stumble alone ;-(