I've been having a terrible time with the page that
contains a weblog in the monthly view. This page has a
weblog module that use using the source of another
weblog module and is displaying the information using
the stock "Monthly" view. Whenever I access the page,
it churns and churns for minutes until the page comes
back half-rendered.
I've checked this on several different installations of
0.96.3 and on different servers. I was able to
manipulate the location_data values in the SQL to get
the old blog posts to show up in a newlycreated weblog
module. They display fine. So, it's not anything in the
web log posts.
So, the new web lgo module works fine. I try to
duplicate my old layout by having another weblog module
share this NEW blog module's source and display the
information using the "Monthly" view - just like I had
it before 0.96.3. Lo and behold, the problem shows back
up again.
I even found a very old EQL file and imported the data
from it jus to double-check that the data in the web
log posts is not the problem. Nope, the half-rendering
problem persists.
So, it seems that the problem exists when "Monthly"
view is added to the stable 0.96 release. I say that
because I also tried 0.96.2 and the problem showed up
there too. I'm not sure how far back this bug goes. I
upgraded my server from 0.96-beta5.
I'd like to look into this further, but I wouldn't even
know where to start. Any logs to look at? Any error
messages that I can capture? Any ideas?
Logged In: YES
user_id=972839
Can you edit the pathos_version.php file and set the DEVELOPMENT
constant to 1 (this will turn on PHP debugging), and then try it
again, and reply back to this bug report with the PHP error
messages you get.
That should help to clear stuff up.
Logged In: YES
user_id=1190502
I made some progress with this problem a while ago. Sorry
for not updating this earlier.
My weblog contains 103 posts. It seems that the "Monthly
View" simply takes too long to make its count calculations
with that many posts. If I create another weblog module
instance, then change it to Monthly View, it works just fine.
I thought that perhaps the instance might have something to
do with it. So, I started editing the SQL data to copy posts
from the old source to the new source. Once my old source
gets to around 85 posts, the Monthly View works. Meanwhile,
the new source works as well. Therefore, there is no problem
with the data in any of the posts.
The web server simply causes the operation to time out
before the Monthly View can finish its calculations for that
many posts. I've tested this on a local test Apache server.
I can change the time limit in php.ini all I want. The
problem still exists.