If the pages that are not displayed are the ones with the most comments it could mean you web host kills you PHP script because it's too long. In that case you need to go to a better web host.

No, that's not the case. And it occured just after the upgrade. I'm going to investigate further...

I just tried to increase the posts which are displayed on a page. The page works, but still posts are skipped displaying on page two.

When setting $c=1, then the "next" link is

http://www.realfragment.de/blog/index.php?blog=1&show_statuses%5B%5D=published&order=ASC&c=1&type%5B%5D=comment&paged=2

but the dafault behaviour without $c=1 is

http://www.realfragment.de/blog/index.php?blog=1&paged=2

...seen that but can't classify if this is an issue.

I just tried to get comments displayed not via $c=1 but with a modified _item_feedback_inc.php, which works but the mistake that many posts are skipped is still there.
Now I'm thinking to make a downgrade back to where everything worked.

I wouldn't be surprised if you use the original skin. Comare yours with a prestine Asevo skin you find in the B2evo download.

Sorry I didn't mention that: I also tried using the unmodified Asevo skin that came with the latest b2evo. But even then the error occured.
BTW: My modifications are just plain html+css, no php, and all based on the Asevo skin that came with the latest b2evo.

Thanks and regards, pgs

I didn't find the

$c=1

trick in the current version of Asevo. I thought that was very old code.

...and now I uploaded - once again - a b2evo out of the box. But the error still occurs.

Something new: I transplanted the page navigation from the pluralism skin in my asevo, and now one can see following:

With $c=1, the content normally displayed on page 2 is displayed on the last page-1 (e.g. on page 64 when having totally 65 pages).
The content normally displayed on page 3 is displayed on the last page-2.
The content normally displayed on page 4 is displayed on the last page-3. And so on.
And on the last page, the first post (not page) is being repeated.
It's like the pages are getting "rotated".

Good night, pgs

Afwas wrote:

I didn't find the

$c=1

trick in the current version of Asevo. I thought that was very old code.

Hmm. Well, I just tried that in the pluralism skin. And in that skin it does not work. There are no errors occurring, but it does not do the job, either.
So maybe the $c=1 thing does not work anymore in the current b2evo.
Hmmmmmm.

regards, pgs

Another thing i discovered: Neither Asevo nor Basic nor Pluralism or any other pristine skin does display the "comment awaiting moderation" message anymore.

Should I open a new post for that?

Regards, pgs

Hello again. I discovered that in my other blogs (http://heidelberg-im-bild.de, http://www.mensch-maschine.net, http://www.stopp-seite.de) after an upgrade, the same error occured. So I really think that it is not possible to use the $c=1 thing anymore.
And it's not just the $c=1 thing. If I let the feedback be displayed via another method (dirty: just commented out the check if feedbacks do not have to be displayed), the same error occures.
The error occures independent of skins and any settings, and also on a pristine blog with no plugins at all. I tried that.

It is a pity for me that there is appearently no possibility to display the feedback under the posts. I am really thinking to change to another software although I appreciate b2evo very much, and that since 2007 (this is not meant as threat, just in case someone thinks so).

Regards, pgs

Hi pgs,

I did find $c.
Copy /skins/_item_feedback.inc.php to the Asevo folder (or whatever folder your skin resides.)
In it is this code:

if( empty($c) )
{	// Comments not requested
	$params['disp_comments'] = false;					// DO NOT Display the comments if not requested
	$params['disp_comment_form'] = false;			// DO NOT Display the comments form if not requested
}

You could set:

$params['disp_comments'] = true;

to show comments on a normal page.

Good luck

Afwas, that does nor change anything. Problem still exists. As mentioned, it seems that no matter /how/ one displays feedback directly under posts. May it be with c$ or "dirty" or with your method: Whenever a feedback is displayed "inline", the error occurs.