phpwcms Support Forum

OK - I do not will answer on the feature requests at the moment - because this is to hard to read because of rare time. Most of the feature requests are discussed multiple times. I have a lot of ideas and want to inform you a bit about what I have in mind and maybe is realized very soon.

One word first: Thanks to all of you - supporting phpwcms and using phpwcms. At the moment it's no good idea to share development. There are some things not finished and documentation is more important than adding new features.

OK. Here are my thoughts and plans for sooner realization:

• finishing newsletter development
• finishing search development including highlighting
• conf.template_default.inc.php transferred into db and usage per pagelayout
• style snippets for article / content parts
• text to image headline functionality
• dhtml menu
• additional menus
• sitemap content part
• multiple content blocks
• possibility to duplicate articles and content parts
• possibility to paste content part or article at special place
• optimized sorting
• languages stored in db and can be edited in backend
• integration of formmailer into phpwcms
• more W3C styled code
• ecard content part
• basic forum content part
• guestbook content part
• final deletion of trashed/deleted content/files

This are the most important things at the moment.

How can you help?
Translate! Create documentation!!! Build sample templates and layouts!!!

regards
Oliver

Ok Oliver ..

i see this as the answer to the email i wrote you. I sitting in front of the thread and don't know what i really should think. The only thing i could do was to offer my knowledge supporting you and your great work.

The other thing, yes, i'm technical writer much that i'm webdeveloper, so i could write documentations much that i can develop code. But in either case, your part is to manage the work. Coz nobody is afraid doing work for basket. Especially not me, coz i also have to work to pay my flat, car, food and girlfriend

I also read in your posting, that you are generally not interested sharing the development. I'm sure, thats depend on the thing phpWCMS is your baby. That's allright at any rate. But TYPO is also Kaspers baby in face of the worldwide shared development.

If you like you can explain me your thoughts in a personal mail (in german) maybe i can understand you then better then i do at the moment.

best wishes
christian

hmm, I thing not sharing the development at the moment is more a thing of structure, logistic and calculation of time to finish parts..?

Not of the own babe, i think.

wheater the "i" is so big, no one would make an open source project, i'am right?

kind regards

i also see sharing the development is a logistic problem - but as i explained to Oliver in my personal mail - i life next to him, just 20 - 30 mins away (also JM does) and so logistic is also handable.

Especially coz of available knowledge of projectmanagement, teamwork e.g. the only thing i could do was to offer my knowledge. I did that in a personal mail to Oliver, but now i have to defend myself in the forum.

The next thing is, that i only can express my oppinion. I hope i could do that - as well in english as in german - so that nobody will feel pissed by my postings.

kisses

Thanks for your thoughts on the developement Oliver, this helps me a lot in where to focus my attentions with phpwcms.
your TODO list is very full and comprehensive and I'm sure I speak for everyone who uses phpwcms that any and all that you do is very welcome, and in your time not ours.
at times we seem to bow down to you with gratitude and stealing your shoes while we are down there if you understand me.

on hearing you thoughts on outside developement I understand completely, as quality WILL suffer through bugs, code styles, and content management. 'more haste less speed'.

finally ( I bet you thought I am never going to end)
I would ask if you would give consideration to the desires an needs of many users (myself included of course) who have been posting requests for a more powerfull permissions functionallity. I know you have read many posts on the subject and even replied to some indication that you undestand the need yourself.
There you see, I'm bowing and looking at your shoes with a greedy eye myself now, I'm sorry.

cguenther wrote:i also see sharing the development is a logistic problem - but as i explained to Oliver in my personal mail - i life next to him, just 20 - 30 mins away (also JM does) and so logistic is also handable.

Especially coz of available knowledge of projectmanagement, teamwork e.g. the only thing i could do was to offer my knowledge. I did that in a personal mail to Oliver, but now i have to defend myself in the forum.

The next thing is, that i only can express my oppinion. I hope i could do that - as well in english as in german - so that nobody will feel pissed by my postings.

kisses

Don´t take it personal - Oliver just want the final release to be finish before he spend time making standards for the coding, coordinating, etc (a time killer I guess). He want the "template" to be done first

Yes it's true: phpwcms is my baby. But that's not the fact why I don't like to share development at the moment. The project is not well documented and not good structured - so it's like Cyrano said: more logistical problem. It will (maybe) costs me much more time to tell where and why I made this and so on. I really do not have additional time for this right now.

I saw other projects dying based on sharing. I think we can talk about that when v1.2 is released - maybe in 3 months. But I also think it would be enough when only 3-5 people are developing together.

Typo3 is based on 5 years development!!! phpwcms is public since 4 months. And it is not shared in the way some people are thinking. You have the chance to create own modules in Typo3 (but how many really good modules - have a look again - every useful Typo3 module is made by same people). That's all! As I know there are not more than 3-4 developers including Kasper enhancing Typo3.

I want to make phpwcms more professional - but it should stay leaner than Typo3. It does not make any sense to try to become better than Typo3. This is no fight. phpwcms should be the cms that you can install and use within minutes - without reading tons of documentation. Have a try with Typo3 and you will understand!

So stop posting feature requests right now. I have so many ideas too. Lets focus on documentation, bug finding and optimization. That's my request to you.

regards
Oliver

I never said that there should be a fight between TYPO and phpWCMS. Both CMS are not in the same league. And i already did more with TYPO then playing around, and that's y i know about the tons of TYPO-Documentation and also the tons of errors in the documentations.

To your request: how you thing that documentating should work without telling y u made something like u did? And how should that work without managing around a bit? Technical documentation is nothing that is been done overnight same with developing.

Plz don't feel pissed of me, but plz understand that i feel pissed a bit at mom. I would be glad if you had found the time to answer my mail, coz i found the time to write you one.

More i don't want to post in that thread to give your nerves a brake of me.

I answerd your email

phpwcms is fun and should bring fun.
And I don't wish to be set under pressure.

Every other user: No flaming please.

Regards
Oliver

Oliver, would you BCC everyone your email to cguenther....please?
I'm making up the content of it myself, I hope it is every bit I as I would hoped it would be.

sorry, I'm not helping the 'no flaming rule' here am i

as a very beginner but nevertheless happy user I see that the code is at the moment not made for sharing some work. I think it could be very useful to make the essential part of the code more modulare and define some plugin structure. than the core of phpwcms can be as lean as useful but every user has the possibility to enhance the cms by adding some plugins.

this can be made by changing the code to enable this or to make an installer for plug ins and give the user a sample plugin where they can see what is needed for doing this.

the cms has not the function of a "eierlegendewollmilchsau" which fits everybodys needs. but everybody should have an easy way to enhance the cms.

I know - and this is what I want to make (a bit later).

But first I want to say - that's it. Then: now lets start with next thing.

If I would begin doing such work another construction site is born.

Oliver

Since Oliver wants to keep the development for himself at the moment it might be a good idea to start a site dedicated to "third party" or non-standard add ons to phpwcms. We can take Oliver's stable branch and add our modules/features that we need. This would be like separating the core development and the feature development. This way maybe Oliver can have a little fun and the people who make features can have a place to put them for other to use.

@Oliver - I want to say that this is not some sort of a plan to fork your project or anything. It is merely an idea to help create a library of phpwcms functionality for users to fill the gap they may have with phpwcms.

If this sounds like a good idea leave me a message on the message board and I can have a site up by the weekend I do want to say that if Oliver does not wish this to happen then we should respect that wish and do whatever possible to help any way we can.

One more note - This idea could include things like tuturials, FAQs, and themes for how to do things. This could help fill the void of documentation while Oliver and others work on the official docs. I hope this seems like a good idea to folks and I would be happy to head it up and make something happen.

Thanks to all and thanks to Oliver. I hope this can help him and phpwcms.

I do not really like to see a split from main developent at the moment or something like experimental enhancement for phpwcms. This has to do that every new feature that's introduced is forcing me to enhance or thinking about enhancement.

What I think can make sense is to include a new function in the frontend renderer that checks for custom include files in a special subdir. There you can add extra functionality without the need to change main code once and once again if I release a new version of phpwcms. This might be especially for custom replacment tags I've seen discussed here in the forum.

What I really like to see is documentation, tutorial or something like that.

Is there somebody who can help me preparing the CVS for phpwcms on SourceForge.net? This would also be a good place for shared documentation and tutorials (by using web hosting on SourceForge.net). If there would be CVS for phpwcms more people can have access to the code base.

Regards
Oliver

At the first look, it seems that the CVS-System at Sourceforge is completly running and ready to check in & out files. Should be enough to get a CVS-Client e.g. WinCVS and configure it like it's explained at SF http://sourceforge.net/cvs/?group_id=94396.

I already worked with CVS, but it was some years ago, so i have to read some documentations to back on top with that.