Home/ Questions/Q 7172289
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-28T15:35:11+00:00

80765 | localhost | Query | 135 | Locked | UPDATE pligg_links set link_summary=”,

  • 0
80765 | localhost | Query | 135 | Locked | UPDATE pligg_links set link_summary='', link_title_url='-165999', link_url='OMIT' |

| 80781 | localhost | Query | 143 | Sending data | SELECT * FROM pligg_links

| 80861 | localhost | Query | 135 | Locked | SELECT link_id, link_category, link_title, link_title_url, COUNT(tag_link_id) AS relevance, tag_link |

| 80872 | localhost | Query | 134 | Locked | SELECT count(*) from pligg_links where link_status = "queued" |

This last one goes on & on… same process it seems. Pligg’s support is pretty sparse and I’ve been trying to solve these issues for days.

Would anyone know an edit I can make either within PHPMyAdmin, a php file or inside Pligg to cut this out?

Secret ninja password: SHOW CREATE TABLE pligg_links\G

Thank you!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Change the table engine to InnoDB (phpMyAdmin can help you do this), as this lets you use row-level locking.

    On top of that, run this immediately after mysql_connect():

    mysql_query( "SET SESSION TRANSACTION ISOLATION LEVEL READ UNCOMMITTED");

    That mouthful will allow SELECT queries to run even if an UPDATE is running, by reading the rows before they get updated if they have to. In most cases, this is fine – it’s only if you’re dealing with majorly important issues like ones that involve money that you need to be careful.

    • 0