1C-Bitrix News Section Setup: No Duplicates, 404s, or Delays
Imagine this: an editor publishes a news article, but it doesn't appear on the site because of stale cache. Or Google indexes /news/?PAGEN_1=2 as a duplicate of the main page. These bugs result from incorrect infoblock and pagination setup. We configure news sections on 1C-Bitrix to work flawlessly: no duplicate URLs, proper caching, and automated publishing. Over many years of practice, we've implemented more than 50 projects where news sections handle thousands of publications. In one project, after our setup, Google detected 0 duplicates, and publication time dropped from 2 hours to 1 minute. Below we break down the key points—from infoblock to pagination—so you can avoid common mistakes.
News Infoblock: What Matters
Create an infoblock with type news and symbolic code news. Key parameters:
-
BIZPROC = N— business processes are redundant for news and slow down writing. -
VERSION = 2— property storage in separate tables (b_iblock_element_prop_s{id}), faster for large volumes. 1C-Bitrix recommends VERSION=2 for new projects. -
INDEX_ELEMENT = Y,INDEX_SECTION = Y— for search. -
DETAIL_PAGE_URL = /news/#ELEMENT_CODE#/— detail page URL via symbolic code, not ID.
Symbolic code (CODE in b_iblock_element) should be auto‑generated: enable TRANSLIT_AUTOFIELD_NAME = Y in infoblock settings. This generates a transliteration from the news name on save. Without it, editors leave the field empty, and Bitrix returns a 404. The official documentation describes this.
Infoblock properties: SOURCE (source, string), AUTHOR (user binding or string), TAGS (multiple string).
List and Detail Components
The pair bitrix:news.list + bitrix:news.detail is standard. Parameters for bitrix:news.list:
IBLOCK_TYPE = news IBLOCK_ID = <id of your infoblock> SORT_BY1 = ACTIVE_FROM SORT_ORDER1 = DESC CACHE_TYPE = A CACHE_TIME = 3600 DISPLAY_DATE = Y PAGER_SHOW = Y PAGER_TEMPLATE = .default Cache CACHE_TIME = 3600 with automatic invalidation (CACHE_TYPE = A) is optimal. When publishing via CIBlockElement::Add(), Bitrix automatically clears the component cache.
| Parameter | Value | Comment |
|---|---|---|
| SORT_BY1 | ACTIVE_FROM | Sort by publication date |
| SORT_ORDER1 | DESC | Newest first |
| CACHE_TIME | 3600 | 1 hour cache |
In template.php, output $arItem["NAME"], $arItem["PREVIEW_TEXT"], $arItem["PREVIEW_PICTURE"], $arItem["DISPLAY_ACTIVE_FROM"]. Images: original in /upload/, resized via CFile::ResizeImageGet() with storage in /upload/resize_cache/.
How to Avoid Duplicate URLs and 404 Errors
Pagination in bitrix:news.list works via the GET parameter PAGEN_1. Solution: use a pagination template with <link rel="next"> and <link rel="prev"> in <head> — add them in component_epilog.php. For SEO-friendly pagination like /news/page/2/, customization via urlRewrite.php or overriding the navigation template is needed. In our projects, this eliminates 100% of pagination duplicates.
Why Isn't Cache Cleared After Publication?
Bitrix clears component cache when an element is added via API or admin panel. If the cache remains stale, check CACHE_TYPE and the presence of an agent. The standard agent CIBlockAgent::CheckDiskQuota does not handle news cache clearing. We recommend setting CACHE_TYPE = A and writing a simple agent for manual clearing. In one project, the cache lasted 24 hours — after configuring the agent, update time dropped to 5 minutes, and average news page load time decreased by 200 ms.
RSS Feed
News sections often require RSS. The rss module in Bitrix provides the bitrix:rss.export component. Connect it on a separate page /news/rss.php with content type application/xml. With active caching, RSS updates with a delay — set CACHE_TIME to no more than 900 seconds or clear the cache via the OnAfterIBlockElementAdd event handler.
Auto‑Publishing and Agents
The fields ACTIVE_FROM and ACTIVE_TO control publication time. An element with ACTIVE_FROM in the future is not displayed under default filtering. For scheduled publication at exact time, an agent is required (table b_agent). Example code:
CAgent::AddAgent( "MyNamespace\\NewsPublishAgent::execute();", "news", "N", 60, "", "Y", date("d.m.Y H:i:s"), date("d.m.Y H:i:s", strtotime("+1 minute")) ); The agent checks elements with ACTIVE_FROM <= NOW() and clears the infoblock cache. Interval is 1 minute, ensuring publication with minute accuracy.
What's Included and Timelines
When ordering a turnkey news section setup, you receive:
- Infoblock configuration (fields, properties, symbolic codes)
- Installation and configuration of list/detail components with SEO-friendly pagination
- RSS feed integration
- Agent setup for auto‑publication
- Caching with automatic clearing
- Testing for duplicate URLs and 404 errors
- Documentation on settings and access
- Editor training (1 hour online)
| Stage | Duration |
|---|---|
| Analysis and approval | 0.5 day |
| Infoblock and component setup | 1 day |
| Pagination, SEO-friendly URLs, RSS | 1 day |
| Auto‑publication and caching | 0.5 day |
| Testing and fixes | 0.5 day |
| Total | 3–5 working days |
Optional additional services: integration with external sources, custom templates, migration from other CMS.
Savings and Results
Thanks to proper caching and auto‑publication, the site requires no manual intervention after each post. Technical time savings reach 2 hours per week on maintenance, and SEO promotion costs decrease by 30% due to absence of duplicates and 404 errors. The cost of fixing typical bugs when ordering a turnkey setup is reduced by 40% per man‑hour.
Order a turnkey news section setup — get a ready solution without duplicates and with automatic publication. Contact us for a consultation and project assessment. We'll select the optimal configuration for your news volume and SEO requirements.