My Contributions to the Sitecore Community in 2025

Contributions to Sitecore Community 2025

Content(Blogs)Around 10 blog posts
Code1 code contribution for Sitecore Hackathon
CommunityAround 10, acting as co-organizer of SUB-BR, the monthly edition
Social MediaMore than 10 posts, promoting our community event SUG-BR(Sitecore user group Brazil)
Sitecore Support Tickets3 tickets , 1 new bug registered

DateLinkSummary
15 Jan 2025“Sitecore 10.4 Search operation not supported with xConnect collection-only configuration” Error cotidianam+1Walkthrough of resolving the “Search operation not supported with xConnect collection-only” error when upgrading to Sitecore 10.4; includes config steps on CD servers.
2 February 2025https://errorcotidianam.wordpress.com/2025/02/02/the-ultimate-guide-for-sitecore-ssl-issues/A comprehensive guide to diagnosing IIS/Sitecore SSL issues, including certificate installation, bindings, permissions, and chain validation. Helps avoid xConnect failures, expired cert issues, and 403 errors.
3 April 2025https://errorcotidianam.wordpress.com/2025/04/03/sitecore-hackathon-2025/Participated in the 2025 Sitecore Hackathon, where our team built an AI-powered module that enhances brand consistency and streamlines content governance within Sitecore. The solution empowers marketing teams with smarter, automated brand-management capabilities. Grateful to collaborate with Rodrigo Peplau and Eduardo Tonon on this innovative project.
2 May 2025https://errorcotidianam.wordpress.com/2025/05/02/will-ai-take-sitecore-jobs/Thought-leadership article exploring how AI/LLMs may impact the Sitecore profession and how DXP maturity may evolve (Intelligent → Smart → Autonomous).
07 Junehttps://errorcotidianam.wordpress.com/2025/06/07/next-gen-search-how-ai-is-changing-our-interfaces/The article traces the shift from traditional keyword-based search to AI-driven semantic search and RAG, showing how tools like Coveo and LLMs deliver faster, smarter, context-aware answers. It highlights how combining Sitecore content with AI transforms websites into intelligent, chat-based experiences that outperform conventional search.
02 Julyhttps://errorcotidianam.wordpress.com/2025/07/02/sitecore-10-4-xdb-performance-tips-and-tricks/This article explains how to diagnose and fix xDB performance issues in Sitecore 10.4 by identifying fragmented indexes and optimizing data retention. It also highlights when to purge old contacts and interactions using the xConnect Purging Tool to keep analytics fast and databases healthy.
29 Augusthttps://errorcotidianam.wordpress.com/2025/08/29/fixing-the-sitecore-xconnect-purging-error-an-error-has-occurred-and-the-task-is-not-registered/This article explains why the xConnect Purging Tool in Sitecore 10.4 fails with “task is not registered,” pinpointing certificate misconfigurations as the root cause. It outlines how correcting permissions, removing duplicates, and fixing misplaced certificates resolves the issue and restores proper xDB purging.
04 Septemberhttps://errorcotidianam.wordpress.com/2025/09/04/sitecore-10-4-fixing-a-sneaky-coveo-error-after-restoring-a-sitecore-web-db/This article describes how restoring a Sitecore web database can break Coveo integration by reverting outdated WEB_ENCRYPTIONKEYS, causing Sitecore to fail decrypting the API key. Updating the encryption key to the correct environment value fixes the issue instantly and prevents future search failures.
14 Octoberhttps://errorcotidianam.wordpress.com/2025/10/14/views-this-year-a-global-thank-you/This article highlights the global reach of the blog, with readers from the US, Europe, India, Australia, Canada, and Brazil. It celebrates the growing international community and expresses gratitude for the continued support and engagement.
18 Novemberhttps://errorcotidianam.wordpress.com/2025/11/18/sitecore-10-4-security-domain-everyone-is-not-blocking-access/This article explains why “domain\Everyone” failed to block access in Sitecore 10.4, ultimately tracing the issue to a missing domain entry in the CD server’s Domains.config. Adding the correct domain configuration restored proper role resolution and fixed the security behavior.