Collapsing Recent Forums Block v2.3.4 Release?

Posted: Sat Jan 24, 2009 8:00 am

I was wondering if you guys are going to put the v2.3.4 for download. It seems to be XHTML 1.0 Transitional compliant while v2.3.3 has a few errors showing up. If not no big deal, just figured I'd ask. Thanks.

Posted: Sun Jan 25, 2009 12:02 am

That is for Raven to answer Smile

Site Admin/Owner Joined: Aug 27, 2002 Posts: 17088

Absolutely! speedtype

We are working and extremely focused on the v2.30.01 Maintenance release and trying to get it released by mid February. I have this on my (BIG) list of things to do when hell freezes over, er, I mean when/after v2.30.01 is released. However, since you asked so nicely I'll see what I can do Wink

Posted: Sun Jan 25, 2009 7:21 am

Thank you. I have been trying to get all of my site compliant and I really like the forums block you use.

Posted: Fri Jan 30, 2009 3:39 am

I have this up and running at http://www.ravennuke.com/ . However, I have only tested it under fisubice and RavenIce themes. Afaict there are no issues with fisubice. But, RavenIce has a couple of issues that I see. The font is too large, imo, in the header block of the table and the mouse over on the show/hide button isn't changing to the hand/pointer. Small issues but the theme need to be tweaked. Please test it with the other themes and if all seems well then I will release it.

Posted: Fri Jan 30, 2009 6:51 am

Thank you Raven. I know you are very busy. The work y'all have done with Raven Nuke is so very much appreciated by me and many others. The high standards set by this community have taken phpnuke to a new level of usability. Keep up the great work.

Posted: Fri Jan 30, 2009 10:23 am

Raven, just an FYI "View/Edit Your Watched Posts" is not an option in RN Smile

. So I don't know if you want to remove that option for RN or what.

Worker Joined: May 26, 2006 Posts: 153

Raven, I have just realised that I'm still using your Collapsing Forums Block v2.3.3 with RN2.30.01 and the RavenIce theme. Is it possible that this could be messing up the output in IE6 but be ok in IE7 and Firefox 3 ?