Dizkus

After lots of troubleshooting, I have narrowed down the cause of my problems with PNphpBB to the real culprit: the PostCalendar block. When I deactivate this block, everything works perfectly.

Anyone else have this problem as well? I'm running PN .750 Gold release (new install) with the latest PostCalendar version and of course, a fresh install of PNphpBB2 1.2g RC1.

--
www.indybay.org - San Francisco Bay Area Independent Media Center

So far, without figuring out what it is about PostCalendar block that breaks PNphpBB 1.2g RC1 (namely Search and New Topic), the only way to get them to both exist is to set PNphpBB 1.2g RC1 in the admin to default to full page view.

--
www.indybay.org - San Francisco Bay Area Independent Media Center

As I mentioned before, if I deactivate the PostCalendar block, PNphpBB will work fine without any of the mentioned problems.

But this time I left PostCalendar block activated and tried deleting modules/PostCalendar/pnblocks/calendar.php. The PostCalendar block said something like "This block does not seem to exist." But doing this made PNphpBB work perfectly without having to put it to full page view by default.

So I guess this means it has to do with modules/PostCalendar/pnblocks/calendar.php itself or something that calendar.php is calling. I've tried replacing calendar.php from the CVS but the problems still remained.

What's interesting (although I'm not sure if this has to do with much) is that I've tried replacing calendar.php with all the past versions and while they reproduced the same type of problem, the results varied slightly depending on the version. For example, whenever I clicked on Search in the forum, using calendar.php v 1.100 (2002/12/16) showed only the Main Menu block and the Categories block (which are both on the left). Using calendar.php v.1.1 (Feb 11 17:33:24 2004) showed only the Photoshare Random block (which is on the right). Version 1.2 again showed only the Photoshare Random block and Version 1.3 showed only the Main Menu block and the Categories block.

What's weird is that I actually have PNphpBB2 1.2g (pre-RC1 version) and PostCalendar block (same version) working perfectly together on another site on a different server. This makes me think that this problem might have to do with the RC1 version of PNphpBB2 1.2g.

The PostCalendar version I'm running is the latest stable version of 4.0.1. I did just try upgrading to the 4.0.2 from the CVS but that version seemed to act a lot worse than 4.0.1 so I got rid of that did a clean install of 4.0.1 again, which brought it back to just as how it was with the same exact problems.

I'm almost at my wit's end at this point. I'm not a coder so I really don't know where to go from here to troubleshoot. Any help would be greatly appreciated.

--
www.indybay.org - San Francisco Bay Area Independent Media Center

Do you have it configured to display the postcalendar block in a column that 'disappears' when PNphpBB2 is displayed? That's what I have - the postcalendar block is in the third col, which isn't displayed in modules, just the home page. So, I haven't noticed the problem.

I do have a module template for PNphpBB2 so that the PostCalendar block (which is on the right column) "disappears" when accessing PNphpBB2. The problem I'm having apprently doesn't have to do with the PostCalendar block displaying or not. It has to do with whether the PostCalendar block is activated or not. More accurately, it has to do with modules/PostCalendar/pnBlocks/calendar.php itself, since deleting this file even while PostCalendar block is activated, makes PNphpBB work again.

Are you also running the latest PNphpBB2 1.2g RC1 on PN .750 Gold release and PostCalendar 4.0.1?

--
www.indybay.org - San Francisco Bay Area Independent Media Center

Hmmm. I'm running the latest PNphpBB2 1.2g RC1 on PN .750 Gold release and PostCalendar 4.0.2 from larsneo with no problems like those.

noboarders : Then maybe try upgrading to PostCalendar 4.0.2? Since someone says he has no problems with it

Kenshino, as i've said, "I did just try upgrading to the 4.0.2 from the CVS but that version seemed to act a lot worse than 4.0.1 so I got rid of that did a clean install of 4.0.1 again, which brought it back to just as how it was with the same exact problems."

The problem was still there for me with 4.0.2.

--
www.indybay.org - San Francisco Bay Area Independent Media Center

I could never get 4.0.1 working in PN .750 but 4.0.2 works fine and has no issues that I can find with PNphpBB2.

The version of /modules/PostCalendar/pnblocks/calendar.php that I'm currently using is can be viewed here. The presence of this file is what breaks PNphpBB2 for me.

Does anyone have any idea what about this file may be causing this?

--
www.indybay.org - San Francisco Bay Area Independent Media Center

Ok. This is too weird and it's driving me crazy now. I just completely removed PostCalendar from the Administration > Modules AND the database tables and did a fresh install of PostCalendar 4.0.2 (from the CVS). Installation went smoothly but when I tried to access the calendar:
http://new.spaz.org/index.php?module=PostCalendar
I was now getting the same Blank Page with just the Main Menu block and the Categories block, but this time with PostCalendar.

So I just tried deactivating PNphpBB2's multi-block, and what do you know, PostCalendar can be accessed again!

This is driving me insane!

--
www.indybay.org - San Francisco Bay Area Independent Media Center

Sampson, CliffT or anyone else that have both PostCalendar 4.0.2 and PNphpBB2 1.2g RC1: Are you also using PNphpBB2's multi-block?

--
www.indybay.org - San Francisco Bay Area Independent Media Center

I was not using it but I just turned it on and saw no issues with it and the postcalendar block on the same page.

Something must be wrong with the way blocks are working on my site...

Not knowing how to solve this problem, I thought I'd work on something else and installed the latest version of PagEd 0.931. As soon as I installed it, I could no longer add new blocks. Whenever I click on New Blocks in the Blocks admin, it would go to a Blank Page with no error messages.

And interestingly enough, I'm finding posts by others who've had similar problems and the 2 modules that keep getting mentioned are PostCalendar and PNphpBB2:
http://forums.postnuke.com/index.php?name=PNphpBB2&file=viewtopic&t=12517

--
www.indybay.org - San Francisco Bay Area Independent Media Center

PROBLEM SOLVED!

I had my host check the error log and found this

As soon as they increased the PHP memory limit to 16MB, EVERY problem I've had so far was solved.
I think the lesson learned here is that having 16MB for PHP memory limit should be a requirement for PostNuke considering how memory-intensive so many modules are, especially PostCalendar and Content Express.

--
www.indybay.org - San Francisco Bay Area Independent Media Center