ver 9.8.1 : Pagination seems to be broken Revisited

[sefs]

It seems that this broken pagination is a re-occurring problem in the 9.8.x release. Today I posted some new stories, went into the admin and maked some articles published and volia, the pagination went off skew again. I had to again regenerate totals to bring it back in order.

Can someone say if this is a know problem that will be fixed?

Thanks.

[Adaman]

It seems that this broken pagination is a re-occurring problem in the 9.8.x release. Today I posted some new stories, went into the admin and maked some articles published and volia, the pagination went off skew again. I had to again regenerate totals to bring it back in order.

Can someone say if this is a know problem that will be fixed?

Thanks.

Damn i was hoping they would have fixed this with the v9.8.1 update, i will be stying with v9.7 for now then as i cant be bothered with the hassles of regenerate totals etc. Tried upgrading my site to v9.8 previously and had to revert back to v9.7 due to pagination headaches.

I am sure all the new users of pligg will be totally confused by this bug and will have beens since v9.8, this is somthing the pligg team really should concentrate on fixing instead of just putting a bandaid over the problem with a regenerate module.

The original release of v9.8 was made on the 9th August and well over a month later this bug that is annoying as hell still has not been fixed apparently. Pligg is a great project but this is very poor for once, get a move on guys. :P

[sefs]

Is there a way to set it to run as a cron job every few hours as a temporary fix until they get around to it?

[AshDigg]

Are you running 9.8 or 9.8.1.

9.8 had a bug where if you, as god, changed the status of a story it would afect pagination but that bug was fixed in 9.8.1.

thanks

Is there a way to set it to run as a cron job every few hours as a temporary fix until they get around to it?

[sefs]

I'm on 9.8.1, and am changing the status of stories via god. So the problem still seems to be there.

Are you running 9.8 or 9.8.1.

9.8 had a bug where if you, as god, changed the status of a story it would afect pagination but that bug was fixed in 9.8.1.

thanks

[AshDigg]

Can you please take a look at your linkadmin.php file. Check line 107. Make sure you have this

 totals_regenerate(); 
  

[sefs]

Yes, this is present at line 107.

Can you please take a look at your linkadmin.php file. Check line 107. Make sure you have this

 totals_regenerate(); 
  

[sefs]

AshDigg,

There is another file I see here as well called admin_links.php.

This seems to be the page that where you actually select publish/discard/cue on and click on the change status.

a code snippet from this page

	// if admin changes the link status
	if ($_GET['action'] == "bulkmod") {
		if(isset($_POST['submit'])) {
			$comment = array();
			foreach ($_POST["link"] as $k => $v) {
				$comment[intval($k)] = $v;
			}
			foreach($comment as $key => $value) {
				if ($value == "publish") {
					$db->query('UPDATE `' . table_links . '` SET `link_status` = "published", link_published_date = now() WHERE `link_id` = "'.$key.'"');
				}
				elseif ($value == "queued") {
					$db->query('UPDATE `' . table_links . '` SET `link_status` = "queued", link_published_date=0 WHERE `link_id` = "'.$key.'"');
				}
				elseif ($value == "discard") {
					$db->query('UPDATE `' . table_links . '` SET `link_status` = "discard" WHERE `link_id` = "'.$key.'"');
				}
			}

			header("Location: ".my_pligg_base."/admin_links.php");
		}
	}

as in linkadmin.php I see you are updating the table_links table but unlinke in linkadmin.php there is no total_regenerate() call. It's not needed in there as well?


PS: If it's the case that a totals_regenerate is needed there, where else in the app is the table_links updated (eg. it may auto update when a story has enough votes to go from upcoming to publish), that may also need a totals_regenerate.

[AshDigg]

Ah ha! I completely forgot about the bulk modify page for admins. Yes, total_regenerate(); should come before the "header" line.

Thanks for your help!