Further reading

This is our blog. It contains the latest news and announcements about our open-source projects, services, and products; not least, there are gripping case studies, customer projects, and much more.

Featured tags

USA
CMS
NGO
Git
WTW
EU
CRM
n8n
API
All tags >

Helping out the builders of Ontario - RESCON case study

The Residential Construction Council of Ontario (RESCON) represents professionals in Ontario’s residential building industry and leads initiatives to foster innovation across the sector. Their public website runs on Orchard Core: it's a headless Orchard Core backend powering a separate Vue-based frontend application. But an issue had started to undermine one of the site’s most important functions: publishing up-to-date content. The problem: Homepage widgets showing outdated content The news, press releases, and blog post widgets on the homepage weren’t consistently showing the latest items. Immediately after publishing, everything looked fine. But over time, older items would start appearing again. For an organization communicating important industry updates, this was more than a minor inconvenience. It affected publishing reliability and trust. Understanding the architecture Since a different developer built the system originally, our first task was to understand and reproduce the environment. The application consists of: Orchard Core running as a headless backend. A separate Vue-based frontend. Lucene search indexing powering the homepage content widgets. Getting the frontend running locally required recreating an older Node.js environment. Node Version Manager for Windows made this possible by allowing us to install and switch between Node versions easily. The root cause The homepage widgets relied on data fetched from a Lucene index. Over time, the index became inconsistent with the database, resulting in outdated content appearing on the homepage. While fixing the indexing would have been possible, we stepped back and asked a simpler question: does this feature even require Lucene? It turned out it didn’t. The fix: Simplify, don’t patch Instead of investing in a lengthy Lucene investigation, we removed the unnecessary dependency and modified the widgets to fetch content directly via SQL queries. This: Eliminated a moving part, Reduced architectural complexity, and Resolved the inconsistency issue at its root. Sometimes the best fix is not making a system more robust, but making it simpler. Leaving the system healthier While working on the issue, we also enabled Orchard Core’s Audit Trail feature, allowing precise tracking of content changes. This improves governance and operational safety, particularly important for organizations publishing public information. We also performed smaller cleanups to ensure the application was in a better state than when we first examined it. That’s a principle we follow in every project. Collaboration We worked closely with Chris Ohan, IT Lead, and Grant Cameron, Senior Director of Public Affairs at RESCON. Since Grant manages much of the website’s content, his rapid feedback helped validate improvements quickly and ensure the publishing experience was restored. This is what Grant told about working with us: Lombiq stepped in to fix a problem with several widgets on our homepage. We met virtually, explained the problem and their experts went to work quickly and identified the issue. They explained the problem to us and corrected the issue. The team at Lombiq was efficient and professional. They got our site up and running and tweaked the Orchard Core setup to improve functionality. We were more than pleased with the result. Need help with an Orchard Core issue? If your Orchard Core application behaves unpredictably, whether it’s publishing inconsistencies, performance issues, or architectural drift over time, we can help diagnose and stabilize it. Get in touch and let’s take a look.

When you visit a concert, you visit Orchard: Troubleshooting Live Nation's Orchard platform

Did you ever go to a concert? Well, then most possibly you've been a guest of Live Nation Clubs and Theaters: A subsidiary of the Fortune 500 entertainment company Live Nation, Live Nation Clubs and Theaters manages a wide array of venues within the United States. But this is not what they're famous for, they also use Orchard :). Specifically all of Live Nation Clubs and Theater venues and brands, including e.g. House of Blues, The Aztec Theatre, and the Coca Cola Roxy are part of a 50-site multi tenant Orchard application. And we helped to iron out a few issues. Running 50 sites in a multi tenant Orchard app is not an extreme number (we have 3600 sites on DotNest) but if you have such high-profile websites it's still a challenge, especially operations-wise, to keep it all working smoothly. Live Nation Club and Theaters's development team got in touch with us to help troubleshoot some evasive bugs that hogged the whole application randomly when modules were enabled or disabled. We drilled into the issue and came up with a solution for the application's hosting environment, so the whole platform is much more stable now. We also helped the Live Nation Clubs and Theaters team with a few other issues and questions, and still continue to work together so Orchard serves them well. This is what Bryan Pritchard, Sr. Director Digital Development & Content Production told about us working together: There was this pesky problem that surfaced randomly when we enabled a feature on one of our sites and caused recurring (though short) downtimes. Since there was enough work on our plate already we reached out to the Lombiq team to help us fix the issue, which they soon did! We'll continue to be in touch with Lombiq as our Orchard experts. Do you also have a big multi tenant Orchard app that needs some maintenance? You found just the right team, get in touch with us!

Solving a huge site's downtime - Parapolitika.gr case study

Recently the maintainers of the big Greek news site Parapolitika, the guys from the Greek subsidiary of Tatchit contacted us asking for our help: the site was going down routinely for some reason after going live (it was rewritten on Orchard from the legacy engine). The Orchard application was sometimes using up all of the server's CPU (despite it being a 24-core beast) and crashing the IIS worker process in the end. This needed some urgent fix because websites tend to be only worthy if they're alive... We immediately jumped into the task of getting the site stable! Neither the Orchard logs, neither the Windows Event Log revealed anything interesting. However soon we could experience the phenomena live: the worker process was eating up memory until at around 3,8GB while the CPU started spinning like mad and finally the process died. The Event Log told that ImageResizer.NET was running out of memory. Seriously? There are 32GBs of it, damn it! The culprit was the worker process running on 32b, thus not able to use the whole huge memory. While such big memory usage is not something Orchard does everyday (a vanilla Orchard instance in a 32b worker process uses about 80MB) this solved the immediate issue quickly. Together with some other tweaks to the server config the site was now running stable, quickly reaching new uptime records (although the previous uptimes weren't too hard to beat). In the newly gained peace we finally upgraded the site to Orchard 1.7.1 from 1.6 (the new version doesn't only give many features but also performs a way better). Meanwhile we also fixed an issue that could cause OutputCache to serve expired content. To quote Sotirios Roussos, CEO of urbanIT whom we worked with closely on this emergency: "After making some not demanding sites using Orchard, we decided to use it as CMS for creating the new parapolitika.gr, a really huge news site with more than 100.000 visitors daily and over 20 editors and a lot of content. It was a challenge for us and Orchard as well. Unfortunately, the first days were tough. Sudden breakdowns of site were appeared and the pressure was high. Orchard seemed to have limits, or maybe not? That's why we asked help for Lombiq, due to their experience into Orchard infrastructure. Fortunately, they did respond quick and spent hours and nights with us. Until we reach our goal. A stable and quick site. And, we did it. Thanx Lombiq! Keep up the good work!" It was a rush but we're really glad that we see a happy ending to this story!

Helping GI Joe Search & Rescue get back on track with their website

On Friday we completed a short but important emergency assignment: getting the GI Joe Search & Rescue team's website back online. The website was moved to a new hosting company but wasn't feeling all right (the standard IIS 404 page greeted the visitors). This was especially problematic given that the team needed the website for their communication on the weekend. That's when we got contacted on behalf of the team and started investigating. After checking the logs and verifying the integrity of the deployment we recognized the source of the error: although the site's database was seemingly restored all the tables were empty! Running the restore again fixed the database and thus solved the issue altogether. Naturally we didn't charge the team for this emergency fix: they don't charge you when you need their help either!