Search the Community
Showing results for tags 'methods'.
Hi Forum, I recently had a chat with a friend who was introduced to PW by me. He said: "brilliant cms, poor documentation." His comment makes me think about the cheatsheet: While we see new API methods introduced at a very fast pace, the cheatsheet doesn't seem to keep up. That's sad, because it's such a good resource. So, how can I (as a user with very limited PHP skills) help to update the cheatsheet? Is somebody skilled willing to team up with me - as kind of a supervisor - for the update tasks? Or are there any plans on behalf of the team to update the cheatsheet? Thanks!
Hi, I'm developing mailbox and I wanna rather use single class then making pages. Here is the plan (or I think that its a good plan): - I have mailbox.php template and mailbox page - when user click on mailbox, on sidebar he have options to write/read massages to and from ppl Instead of making these pages, and to prevent "ugly URLs" I wanna offer user to call write msg like: http://www.domain.com/mailbox/?actionType=newMail. Also, I think that this will be useful for some other stuff which I wanna add to my project. I'm not skilful but wanna learn stuff. Cheers
Hello everyone, my oop knowledge is pretty limited so please don't stone me for the forthcoming question: I have a rather large project which I'm moving from symfony 1.4 to PW (finally). I'm rebuilding most of the functions in modules with Page hooks, which at one point (now) leads to a naming problem. LIke a countMedia() method can be neccessary for many different contextes. - Is there a way to give a module it's own class name? So I can use $channel->countMedia(), $tag->countMedia(), both referring to different modules? - how do YOU deal with a large set of user functions that are needed in many different templates? Thanks, thomas