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

Search Results :

Business

Predampener for Refractory Gunning Materials: Controlle . . . . .

Proper preparation of refractory gunning materials is an important part of achieving consistent application performance. A Predampener for refractory . . . . .

Read More ↠
Business

Predampener: High Capacity Refractory Predampener With . . . . .

Consistent moisture management is essential for efficient refractory gunning applications. Adding the right amount of moisture to gunning materials ca . . . . .

Read More ↠
Business

Predampener: Low Rebound Refractory Equipment for Prope . . . . .

Efficient refractory installation depends on proper material preparation, controlled moisture, and consistent application. The right low rebound refra . . . . .

Read More ↠
Business

Predampener: Refractory Moisture Control System for Pre . . . . .

Consistent moisture control is an important part of efficient refractory gunning. When dry gunning materials are properly predampened before reaching . . . . .

Read More ↠
Business

Predampening System and Dry Process Shotcrete Machine: . . . . .

Modern construction, mining, and industrial repair projects require reliable equipment that can deliver accurate material placement, reduce downtime, . . . . .

Read More ↠
Business

Predampening System for Industrial Refractory Applicati . . . . .

Consistent preparation of refractory gunning materials is important for demanding industrial applications. A predampening system for industrial refrac . . . . .

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.