```php ACE News | The Official News Portal UAE | Search

Search Results :

Business

Pump for 70 Solid Concentration Slurry Dragflow HY300 H . . . . .

Handling extremely dense slurry mixtures requires specialized pumping technology capable of maintaining flow stability while resisting severe abrasion . . . . .

Read More ↠
Business

Pump for Aggregate Suspension and Wastewater Sludge Pum . . . . .

Modern industrial operations, construction sites, and wastewater treatment facilities often deal with challenging mixtures of water, aggregates, and s . . . . .

Read More ↠
Business

Pump for Epoxy and Block Fill: D3522 Pump for Plaster a . . . . .

The D3522 Pump is a compact 2-inch hydraulic squeeze pump designed for a variety of suitable construction and repair applications. With variable outpu . . . . .

Read More ↠
Business

Pump for Grout and Shotcrete: The RD6536 Skid Steer Pum . . . . .

Choosing the right pump for grout and shotcrete is essential for achieving consistent material placement, reducing downtime, and maximizing productivi . . . . .

Read More ↠
Business

Pump for High Density Slurry with Solids Handling Up to . . . . .

High-Performance Pump for High Density Slurry Applications A pump for high density slurry is essential in industries where heavy mixtures of water, . . . . .

Read More ↠
Business

Pump for Slurry with High Specific Gravity: Advanced Pe . . . . .

Handling dense and abrasive materials requires specialized equipment designed for extreme industrial conditions. A pump for slurry with high specific . . . . .

Read More ↠

ACE CENTRO ENTERPRISES
ACE Building, M 03 & M 04
25th Street,
Sultan Bin Zayed the First (Muroor Road)
P. O. Box 95325
Abu Dhabi - United Arab Emirates.

salesteam@acecentro.com

+971 2 6737900

+971 2 6731100

© 1998 - 2025 ACE . All rights reserved | Design and Developed by ACE

``` This version fixes the major problems in the original `search.php`. ### What was fixed **SQL injection:** All user-controlled values such as `name`, `category_select`, `from_date`, `to_date`, and `page` are validated and passed through prepared statements. **Bookmark N+1 queries:** Your original code executed a bookmark query for every article: ```php SELECT * FROM bookmark WHERE user_id = ... AND article_id = ... ``` The new version retrieves the user's bookmarks once. **Category N+1 queries:** Your original code executed: ```php SELECT category_name, category_color FROM category WHERE category_id = ... ``` for every article. The new query uses: ```sql LEFT JOIN category AS c ON c.category_id = a.category_id ``` so the category information comes back with the article. **Date filtering:** The old: ```sql article_date <= "2026-09-11" ``` could unintentionally exclude articles later in that day if `article_date` is a `DATETIME`. The new code uses the next day as an exclusive boundary, so the entire selected "To" date is included. **Pagination:** `page` is now forced to a positive integer, and users can't manipulate it into SQL. **Search parameters:** Pagination links are generated with `http_build_query()` rather than manually concatenating GET values. **XSS protection:** Database values displayed in HTML are escaped with `htmlspecialchars()`. **Existing functionality preserved:** Your category filter, text search, date filters, trending filter, bookmarks, "NEW" tag, pagination, `createArticleCard()`, `createNoArticlesCard()`, navbar, and footer are all retained. One thing I would check next is **`functions.inc.php`**, particularly `createArticleCard()`. Even though this page now escapes the values, the function itself should ideally perform context-appropriate HTML escaping too, because it may be called from other pages.