phpBB Weekly #047 Postponed to 1/19

[webmacster87]

Due to unforeseen circumstances, we are going to have to cancel phpBB Weekly for this Saturday, January 12th. David's move to Spokane, which has been the cause of his absence for the past few episodes, has unfortunately had some issues which have slowed it down. Therefore, he will not be able to be here this Saturday for phpBB Weekly. At the same time, I will be out of town for a meeting, and will not be here for phpBB Weekly. Therefore, we are not going to be recording an episode this week.

phpBB Weekly #047, which was intended to be the episode where David will be revealing for the first time what's new in phpBB 3.2, will be postponed to next Saturday, January 19th. David promises that he'll be there, and I'll also be there, so it will be great for both of us to be on the show at the same time for the momentous occasion. Even better, David will be joined by MOD Team member Josh W. (A_Jelly_Doughnut) and Development Team member David M. (DavidMJ)*, who will be joining David in revealing what's new in the up-and-coming 3.2. And, of course, I will be there, serving as the curmudgeon offering my opinions and judgments on the revealed features, and asking as many more-in-depth type questions as I can, while also making sure that the episode doesn't trump two hours. And, based on past experiences, with something this big going on, you can expect that there will be some more team members lurking about on TalkShoe, especially now that TalkShoe is more accessible now.

Oh, and of course, we invite you to not only come live and be among the first to learn about the new stuff coming in the next major release of phpBB, but also join in with your own questions and comments! Come in live to the chat room and share your opinions on the new features as they're introduced, or call in live on the show and talk with our guest team members! Or, if you have questions and comments that you'd like to share here, in this topic, feel free.

Finally, the last thing that I am going to pitch is to ask you all to mention what some of the features you'd like to see in phpBB 3.2. After all, this podcast isn't just for hearing what the team members have to say, it's for hearing what you, the community, has to say. Who knows (David does) whether or not your most-wanted feature will actually be showing up in 3.2, but sound off in this topic about what you want the teams to deliver in 3.2, and we'll be sure that they hear what you want them to hear.

We do apologize for the inconvenience of suddenly canceling this weekend's episode, but we're really looking forward to the exciting episode that we have planned for the 19th, and hope to see you then!
--Douglas Bell

* Guests are subject to change without notice.

[EXreaction]

I am looking forward too it.

One thing I'd like is for them to start using SVN for the repository instead of CVS so I don't have to install TortoiseCVS just for phpBB!

Oh, I would like to hear how the Soft Delete system is going (or if it is planned anymore) for 3.2. I've built a Soft Delete mod for 3.0, and I'd have to say, I don't really like it, it is way too complicated to be a mod IMO, at least with the style of coding I prefer to write (there are a bunch of places you need to alter the outputs, or rewrite entire parts to work correctly, at least to keep the post/topic counts looking right and not breaking the move/copy/etc for posts/topics).

[webmacster87]

Hey everyone! Just a reminder that the big episode is tomorrow, less than 15 hours after the time of this post! Hope to see you there.

[EXreaction]

Oh, one other thing.

If anyone gets a chance, please ask if they plan on doing anything with the hard codded BBCodes. Other than the Quote BBCode, none of the BBCodes need to be hard codded, I really think that the hard codded BBCodes should all be added as custom BBCodes so users can edit them if they want to.

Perhaps you could add the Quote to Custom BBCodes as well to allow users to edit it, if you set it up so that it couldn't be deleted and they could not change the input code.