WPIntell

Source evidence

Messed up database

cbnet Different Posts Per Page · review · 2013-03-05T02:00:00+00:00

cbnet Different Posts Per Page plugin evidence original source source API
complaintsentiment
mediumseverity
0.88relevance
1replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

6 / 35 rows with source links

17.1% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

29 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

review · 1 stars
BHGdesigns unresolved
at first I thought this plugin was great, would do exactly what i wanted. But it messed up my database and all my pages were gone. None of the links worked. After a big scare, uninstalling this plugin restored my site. Use at you own risk! This Plugin doesn’t interact with the database, other than to store/retrieve its own wp_options entry. It does not, and cannot, do anything to your static Pages. It merely filters the posts query via pre_get_posts , for certain contexts (blog posts index, archive index, category index, etc.) Could you describe your problem in more detail, so I can help you resolve it? What Theme are you using, and what Plugins do you have active? I suspect that either your Theme or an active Plugin is improperly using query_posts() , which resulted in what you observed.

Comments

1 shown
Chip Bennett 2013-03-05T13:01:00+00:00

This Plugin doesn’t interact with the database, other than to store/retrieve its own wp_options entry. It does not, and cannot, do anything to your static Pages. It merely filters the posts query via pre_get_posts , for certain contexts (blog posts index, archive index, category index, etc.) Could you describe your problem in more detail, so I can help you resolve it? What Theme are you using, and what Plugins do you have active? I suspect that either your Theme or an active Plugin is improperly using query_posts() , which resulted in what you observed.