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.
What Professional 1C-Bitrix Installation Includes
We start by checking innodb_buffer_pool_size. The default MySQL value (128 MB) is a death sentence for an online store with a catalog of 10,000+ items. We set 70–80% of available RAM on a dedicated server, 50% on VPS. This single setting speeds up the site by 2–3 times compared to the default. We'll assess your project in one day — get a consultation. Contact us to order turnkey installation with performance guarantee.
How to Choose Hosting and Edition for 1C-Bitrix Installation?
BitrixVM is a virtual machine with a pre-installed stack: nginx + Apache, PHP-FPM, MySQL/MariaDB, Sphinx, Push server. For VPS — the best start. Everything is already configured for Bitrix, including OPcache, log rotation, and firewall. Management via web panel on port 8890. Bitrix documentation recommends starting with BitrixVM for predictable performance.
VPS/VDS is the sweet spot. Minimum configuration for a medium online store: 2 vCPU, 4 GB RAM, SSD. Optimal: 4 vCPU, 8 GB RAM. OS: Ubuntu 22.04 or Debian 12. If not BitrixVM, we configure the stack manually for the task. Virtual hosting — only for business cards and landing pages. Requirements: PHP 8.0+, MySQL 5.7+ / MariaDB 10.0+, 512 MB RAM, .htaccess. 1C-Bitrix hosting partners guarantee compatibility. Dedicated server — for highload. Typical architecture: web server separate, database separate, Redis/Memcached separate. For Enterprise edition — web cluster with load balancer. Cloud (Yandex Cloud, VK Cloud, Selectel) — when load spikes: sales, seasonal peaks. Autoscaling via Managed Kubernetes or simple VM vertical scaling.
Choosing the edition is equally important. A common mistake: choosing "Small Business" for a store that grows to B2B with wholesale prices and three warehouses in six months. Upgrading to "Business" — pay the difference, data is not lost, but it's better to plan ahead. Our specialists select the edition for current tasks and with room for growth. For example, the "Business" license (about 35,000 RUB) pays off through multi-warehouse and 1C exchange, while the wrong choice can lead to a loss of up to 30,000 RUB monthly on excess resources.
| Edition |
For Whom |
Key Limitation |
| Start |
Business cards, landing pages |
No infoblocks 2.0, no trade catalog |
| Standard |
Corporate sites |
No e-commerce module |
| Small Business |
Small stores |
1 price type, 1 warehouse, no 1C exchange |
| Business |
Medium stores, B2B |
Multi-warehouse, multicurrency, CommerceML |
| Enterprise |
Highload, cluster |
Web cluster, CDN, multisite |
What Server Settings Are Critical for 1C-Bitrix?
Web Server and PHP
nginx as reverse proxy + Apache (mod_php) or nginx + PHP-FPM directly. The second option saves memory — Apache is not needed. But some Bitrix modules use .htaccess, so for compatibility we sometimes keep Apache. nginx configuration: fastcgi_read_timeout 300 — for long operations (1C import), client_max_body_size 1024m — large file uploads. Block access to .settings.php, .settings_extra.php, bitrix/.settings.php — they contain database passwords. Rewrite rules from urlrewrite.php — Bitrix generates them, but with nginx + PHP-FPM they need to be duplicated. PHP 8.0–8.2 with extensions: mbstring, curl, gd, xml, json, opcache, redis/memcached. Key php.ini settings: opcache.memory_consumption=256, opcache.max_accelerated_files=20000, max_execution_time=300, memory_limit=512M, upload_max_filesize=100M, post_max_size=128M.
Database and Caching
MySQL/MariaDB. Key my.cnf parameters: innodb_buffer_pool_size — 70–80% RAM, innodb_log_file_size=256M, tmp_table_size=256M, max_heap_table_size=256M, thread_pool_size — number of CPU cores. Encoding utf8mb4 mandatory, otherwise emoji and special characters break. Redis is preferable to Memcached for Bitrix — supports persistent connections and is more reliable. In production, Redis handles concurrent writes three times faster than Memcached under typical load. Configure in .settings_extra.php:
'cache' => ['value' => ['type' => ['class_name' => '\\Bitrix\\Main\\Data\\CacheEngineRedis']]]
'session' => ['value' => ['mode' => 'default', 'handlers' => ['general' => ['type' => 'redis']]]]
Example Redis configuration for Bitrix
sudo apt install redis-server
sudo systemctl enable redis
Add to .settings_extra.php as above.
SSL, Email, and Cron
SSL — Let's Encrypt via certbot in 90% of cases. Redirect HTTP → HTTPS (301), HSTS, TLS 1.2/1.3, OCSP Stapling. In Bitrix, switch to HTTPS in the main module settings. Email: abandon mail() — connect SMTP (Yandex.Mail for domain, Mail.ru for Business). Be sure to configure SPF, DKIM, DMARC. Without SPF, emails go to spam. Test deliverability via mail-tester.com — score 9+/10. Cron: Bitrix agents switch to system cron — * * * * * /usr/bin/php /var/www/bitrix/modules/main/tools/cron_events.php. Schedule 1C exchange (15–60 min), search reindex, backups (mysqldump + rsync, rotation 7+4), temporary file cleanup.
Security and Administration
File system: owner www-data, directories 755, files 644, upload 775. nginx blocks access to configuration files. Enable Bitrix Proactive Protection — WAF, activity control (block after 5 failed attempts), kernel integrity check. For admin panel: two-factor authentication via Google Authenticator or OTP, restrict access by IP via nginx for paranoid.
How Long Does 1C-Bitrix Installation and Configuration Take?
| Task |
Timeline |
| Installation on virtual hosting |
2–4 hours |
| Installation on VPS with stack configuration |
1–2 days |
| Installation on dedicated with architecture design |
2–5 days |
| SSL + email + cron + security |
1–2 days |
| Backup and monitoring setup |
0.5–1 day |
Post-Installation Checklist
-
Performance Monitor (
/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
- System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
- Security Scanner — check for typical vulnerabilities.
- PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
- Test 1C exchange — if integration is planned, verify CommerceML exchange before launch.
Additionally, check software versions, caching settings, cron operation, SSL certificate, SPF/DKIM/DMARC, access rights, delete default users and pages. For projects with 54-FZ, ensure fiscalization is configured via OFD provider.
Deliverables
- Fully configured server for 1C-Bitrix with MySQL, PHP, nginx optimization.
- Installed and activated license of the required edition.
- SSL certificate, email settings, cron and backups.
- Documentation: all configuration parameters, access credentials, cron tasks.
- Content manager training: how to log into admin panel, add products, upload images.
- Post-installation support for 30 days — consultations on settings.
Why Trust Professionals with Installation?
Incorrect installation means lost time and money. We've seen projects where a store on "Start" couldn't handle 50 visitors because innodb_buffer_pool_size wasn't configured. After migrating to VPS with correct configuration, the site "flew". Incorrect configuration can cost 30,000 RUB monthly due to excessive resource consumption. You get a ready-made architecture that scales. Order turnkey 1C-Bitrix installation — get a reliable platform for business growth. Contact us for a free consultation: we'll calculate the cost and time for your project. Over 7 years of experience, 120+ Bitrix projects implemented, including highload stores with million-item catalogs. Get in touch — we'll help configure Bitrix for your project.
