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

Search Results :

Business

Hydraulic Concrete Pump 400 PSI: RD6536 Skid Steer Pump . . . . .

Introduction to Hydraulic Concrete Pump 400 PSI Systems A hydraulic concrete pump 400 PSI is designed for controlled and efficient concrete placeme . . . . .

Read More ↠
Business

Hydraulic Concrete Pump and Squeeze Concrete Pump: Disc . . . . .

Construction professionals need equipment that delivers dependable performance, straightforward maintenance, and the flexibility to handle a variety o . . . . .

Read More ↠
Business

Hydraulic Concrete Pump for Construction: RMX-5000 Comm . . . . .

High-Performance Hydraulic Concrete Pump for Demanding Construction Applications The RMX-5000 Mixer / Pump is a powerful commercial mixer pump mach . . . . .

Read More ↠
Business

Hydraulic Concrete Pump for Sale: 2-Inch Concrete Pump . . . . .

Finding the right hydraulic concrete pump for sale can make a significant difference for contractors working on concrete repair, block fill, epoxy, pl . . . . .

Read More ↠
Business

Hydraulic Concrete Pump: Improve Construction Efficienc . . . . .

RD6536 Hydraulic Concrete Pump for Reliable Concrete Placement A Hydraulic Concrete Pump is an essential piece of equipment for modern construction . . . . .

Read More ↠
Business

Hydraulic Control Concrete Pump RD6536 Squeeze Hose Pu . . . . .

Hydraulic Control Concrete Pump Overview The hydraulic control concrete pump RD6536 is a high-performance squeeze hose pump designed for precise an . . . . .

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.