- Error
-
- The RokSprocket Module needs the RokSprocket Component enabled.
- Got error 28 from storage engine SQL=SELECT a.id, a.title, a.alias, a.title_alias, a.introtext, a.checked_out, a.checked_out_time, a.catid, a.created, a.created_by, a.created_by_alias, CASE WHEN a.modified = 0 THEN a.created ELSE a.modified END as modified, a.modified_by, uam.name as modified_by_name,CASE WHEN a.publish_up = 0 THEN a.created ELSE a.publish_up END as publish_up,a.publish_down, a.images, a.urls, a.attribs, a.metadata, a.metakey, a.metadesc, a.access, a.hits, a.xreference, a.featured, LENGTH(a.fulltext) AS readmore,CASE WHEN badcats.id is not null THEN 0 ELSE a.state END AS state,c.title AS category_title, c.path AS category_route, c.access AS category_access, c.alias AS category_alias,CASE WHEN a.created_by_alias > ' ' THEN a.created_by_alias ELSE ua.name END AS author,ua.email AS author_email,contact.id as contactid,parent.title as parent_title, parent.id as parent_id, parent.path as parent_route, parent.alias as parent_alias,ROUND(v.rating_sum / v.rating_count, 0) AS rating, v.rating_count as rating_count,c.published, CASE WHEN badcats.id is null THEN c.published ELSE 0 END AS parents_published FROM u75v6_content AS a LEFT JOIN u75v6_categories AS c ON c.id = a.catid LEFT JOIN u75v6_users AS ua ON ua.id = a.created_by LEFT JOIN u75v6_users AS uam ON uam.id = a.modified_by LEFT JOIN ( SELECT contact.user_id, MAX(contact.id) AS id, contact.language FROM u75v6_contact_details AS contact WHERE contact.published = 1 GROUP BY contact.user_id, contact.language) AS contact ON contact.user_id = a.created_by LEFT JOIN u75v6_categories as parent ON parent.id = c.parent_id LEFT JOIN u75v6_content_rating AS v ON a.id = v.content_id LEFT OUTER JOIN (SELECT cat.id as id FROM u75v6_categories AS cat JOIN u75v6_categories AS parent ON cat.lft BETWEEN parent.lft AND parent.rgt WHERE parent.extension = 'com_content' AND parent.published != 1 GROUP BY cat.id ) AS badcats ON badcats.id = c.id INNER JOIN u75v6_content_frontpage AS fp ON fp.content_id = a.id WHERE a.access IN (1,1) AND CASE WHEN badcats.id is null THEN a.state ELSE 0 END = 1 AND (a.publish_up = '0000-00-00 00:00:00' OR a.publish_up <= '2026-05-21 15:03:18') AND (a.publish_down = '0000-00-00 00:00:00' OR a.publish_down >= '2026-05-21 15:03:18') GROUP BY a.id, a.title, a.alias, a.title_alias, a.introtext, a.checked_out, a.checked_out_time, a.catid, a.created, a.created_by, a.created_by_alias, a.created, a.modified, a.modified_by, uam.name, a.publish_up, a.attribs, a.metadata, a.metakey, a.metadesc, a.access, a.hits, a.xreference, a.featured, a.fulltext, a.state, a.publish_down, badcats.id, c.title, c.path, c.access, c.alias, uam.id, ua.name, ua.email, contact.id, parent.title, parent.id, parent.path, parent.alias, v.rating_sum, v.rating_count, c.published, c.lft, a.ordering, parent.lft, fp.ordering, c.id, a.images, a.urls ORDER BY c.lft, fp.ordering, a.created DESC LIMIT 0, 2 Got error 28 from storage engine SQL=SELECT a.id, a.title, a.alias, a.title_alias, a.introtext, a.checked_out, a.checked_out_time, a.catid, a.created, a.created_by, a.created_by_alias, CASE WHEN a.modified = 0 THEN a.created ELSE a.modified END as modified, a.modified_by, uam.name as modified_by_name,CASE WHEN a.publish_up = 0 THEN a.created ELSE a.publish_up END as publish_up,a.publish_down, a.images, a.urls, a.attribs, a.metadata, a.metakey, a.metadesc, a.access, a.hits, a.xreference, a.featured, LENGTH(a.fulltext) AS readmore,CASE WHEN badcats.id is not null THEN 0 ELSE a.state END AS state,c.title AS category_title, c.path AS category_route, c.access AS category_access, c.alias AS category_alias,CASE WHEN a.created_by_alias > ' ' THEN a.created_by_alias ELSE ua.name END AS author,ua.email AS author_email,contact.id as contactid,parent.title as parent_title, parent.id as parent_id, parent.path as parent_route, parent.alias as parent_alias,ROUND(v.rating_sum / v.rating_count, 0) AS rating, v.rating_count as rating_count,c.published, CASE WHEN badcats.id is null THEN c.published ELSE 0 END AS parents_published FROM u75v6_content AS a LEFT JOIN u75v6_categories AS c ON c.id = a.catid LEFT JOIN u75v6_users AS ua ON ua.id = a.created_by LEFT JOIN u75v6_users AS uam ON uam.id = a.modified_by LEFT JOIN ( SELECT contact.user_id, MAX(contact.id) AS id, contact.language FROM u75v6_contact_details AS contact WHERE contact.published = 1 GROUP BY contact.user_id, contact.language) AS contact ON contact.user_id = a.created_by LEFT JOIN u75v6_categories as parent ON parent.id = c.parent_id LEFT JOIN u75v6_content_rating AS v ON a.id = v.content_id LEFT OUTER JOIN (SELECT cat.id as id FROM u75v6_categories AS cat JOIN u75v6_categories AS parent ON cat.lft BETWEEN parent.lft AND parent.rgt WHERE parent.extension = 'com_content' AND parent.published != 1 GROUP BY cat.id ) AS badcats ON badcats.id = c.id INNER JOIN u75v6_content_frontpage AS fp ON fp.content_id = a.id WHERE a.access IN (1,1) AND CASE WHEN badcats.id is null THEN a.state ELSE 0 END = 1 AND (a.publish_up = '0000-00-00 00:00:00' OR a.publish_up <= '2026-05-21 15:03:18') AND (a.publish_down = '0000-00-00 00:00:00' OR a.publish_down >= '2026-05-21 15:03:18') GROUP BY a.id, a.title, a.alias, a.title_alias, a.introtext, a.checked_out, a.checked_out_time, a.catid, a.created, a.created_by, a.created_by_alias, a.created, a.modified, a.modified_by, uam.name, a.publish_up, a.attribs, a.metadata, a.metakey, a.metadesc, a.access, a.hits, a.xreference, a.featured, a.fulltext, a.state, a.publish_down, badcats.id, c.title, c.path, c.access, c.alias, uam.id, ua.name, ua.email, contact.id, parent.title, parent.id, parent.path, parent.alias, v.rating_sum, v.rating_count, c.published, c.lft, a.ordering, parent.lft, fp.ordering, c.id, a.images, a.urls ORDER BY c.lft, fp.ordering, a.created DESC
White Papers
The Three States of Emergency Public Alerting
Communications related to disaster events are important to save lives. This Paper considers the three types of communication that contribute to an effective strategy to ensure that when disaster strikes, there is minimisation of damage to life and property.
A Comparison Between Broadcast Radio and Cellular Technologies for Emergency Public Alerting
TSUNADO New Zealand Limited (aka DIWA) has developed a system for nationwide Public Alerting based on Broadcast Radio technologies. The decision to use Broadcast Radio and Satellite systems as the primary communication channel, as opposed to cellular and internet based technologies, is outlined in this White paper.
Waking a Sleeper
TSUNADOAlert Radios are provided with an internal alert device similar to smoke alarms. This White paper outlines how different and effective the TSUNADO alert is in waking a deep sleeper.
ALERT Get Attention
The prime function for Tsunado alarms is to get the owner's attention, anytime day or night.
Read MoreINFORM Provide Information
The secondary feature, but by no less important, is to inform the owner of what to do.
Read MoreSave Keep you Safe
By delivering alerts quickly and informing owners of what to do, Tsunado saves lives.
Read More