The devlog-ist/landing project recently underwent a significant enhancement to its subscription and pricing infrastructure. Traditionally, managing different pricing tiers can become a bottleneck when hardcoded, leading to slow updates and lack of flexibility. Our goal was to create a robust, easily manageable system for defining and presenting various subscription plans.

The Challenge:

Introduction

The landing project encountered a performance bottleneck related to how it was handling JSON data within PostgreSQL. Specifically, the issue arose when using SELECT DISTINCT queries on columns containing JSON data.

The Challenge

PostgreSQL's inability to directly compare JSON columns for equality posed a problem. The Filament admin panel, when preloading the attach-user

This post discusses how we addressed a rendering issue in the Breniapp project related to dynamically updating canvas aspect ratios. The problem stemmed from using Alpine.js to manage the aspect ratio of a canvas element within a Blade template that conditionally rendered based on Livewire state.

The Problem

Initially, Alpine.js was used to dynamically update the aspect ratio of a canvas

The Problem

In the landing project, we encountered a subtle but significant security issue related to how data was being passed from PHP to JavaScript within our Blade templates. Specifically, when using Livewire and Alpine.js, values containing special characters (like apostrophes in names such as "O'Brien") could break the JavaScript context, leading to unexpected behavior or, worse,

The Reimpact/platform project is focused on [description]. Recent work has concentrated on improving the reliability and accuracy of PostgreSQL dashboard functions. A key area of focus was addressing data type mismatches and sequence issues that could lead to errors and inconsistencies in the displayed data.

The Problem

One specific issue involved the product_ranking function, where a

The landing project provides customizable landing pages. Recently, we addressed an issue with the theme selection process that was causing cross-origin errors on tenant subdomains.

The Problem

Previously, the theme selector used the route() function to generate URLs. This resulted in the main domain URL being generated, which caused cross-origin failures when the landing page was accessed

Introduction

The Reimpact platform leverages PostgreSQL for its data storage needs. Ensuring data integrity and accurate comparisons within dashboard functions is crucial for reliable reporting and analysis. Recent work focuses on addressing data type inconsistencies that can lead to unexpected errors and inaccurate results.

The Problem

In the PostgreSQL database, the `products.

Ever faced a baffling error message that seemed to defy logic? In the Reimpact platform, we encountered a particularly frustrating issue in our PostgreSQL dashboard functions. The symptom? A cryptic 42883 error cropping up across all Packaging dashboard widgets.

The culprit turned out to be PostgreSQL's strictness regarding implicit type casting. Specifically, it doesn't automatically convert

Introduction

This post explores how the Reimpact/platform project enhanced its Filament-based dashboard by leveraging PostgreSQL functions to improve data visualization. The focus was on creating a more insightful and efficient packaging dashboard.

From MySQL to PostgreSQL: A Performance Shift

The initial implementation relied on MySQL stored procedures. To optimize performance and

When working with Laravel Filament on the Reimpact platform, small UI refinements can have a significant impact on user experience. Recently, we addressed an issue concerning the module selector's icon sizing and positioning, particularly its integration with the platform's logo.

The Problem

The original implementation relied on Tailwind CSS classes for styling the module selector icon.