A customer watched their referral numbers climb steadily for months—until it suddenly slowed down.

By the time we spoke, the frustration was clear. The team had invested real effort into building momentum, so the hiccup felt personal. Their first order of business was to regain control by making a few adjustments to the program.

As we walked through what had changed, the issue came into sharp focus. The program itself hadn’t failed, no. But the attitude around it had shifted.

In many domains, critical information is deliberately written down twice in two different places. While this might appear redundant, the practice is a safeguard against errors, loss, and failure. The underlying principle is simple: no single point of failure should be able to compromise the system.

Lost my laptop, possibly due to a virus, and now I have to rebuild it. Yeah, losing a laptop is hard. On the one hand, I have to be ready for such unfortunate events. And I actually am ready - I have a recent backup. I have non-recent backups, as well. Most important things are also duplicated in the cloud. Some heavy files like videos aren't backed up, but I'm actually not losing much there. And I managed to back up text files and important small files of the most recent days, via a tether. So I'm good, overall. 

Fixing this took me years... I can't believe how long it took. The answers on stack overflow did not help.

The error was due to a mismatching php configuration for running in the shell ( /etc/php/8.1/cli/php.ini ) and in apache (/etc/php/8.1/apache2/php.ini ).

Specifically, I had to enable short tags for the shell: 

short_open_tag = On

With that, this particular error was fixed, and I was off to fixing the next error!

npx pnpm i -g pnpm@latest

.

.^.

...then, the current idea, from completely lacking motivation to work, is as follows. Instead of reading news, etc, and being generally unuseful, I will spend time *writing* news, or scrum updates, or 2d sketches, or whatever else that can be generated, rather than consumed.

In HTML, classes should be lower-case with dashes:

<div class="class-name-1 another-class-name"> </div>

There are exceptions:

<div class="BookChapter" ></div>

However, ids should be camelCase or PascalCase (capitalized first letter):

<div id="thisDiv"></div><div id="anotherArray"></div>

Or the same question can be asked as: what's a better name: tag1 or tag-1? Depending on if underscores are disallowed, or dashes are disallowed.

While we are on the topic of dashes vs underscores, check out when to capitalize HTML classes, and when to keep ids in Pascal Case.

It appears that you can just re-run the setup in order to do that:

bundle exec rails ffcrm:setup

.

You can download the Selenium remote grid jar here:

Based on this excellent stackoverflow answer.

$bid = ??? // Get the block id through config, SQL or some other means
$block = \Drupal\block_content\Entity\BlockContent::load($bid);
$render = \Drupal::entityTypeManager()->
  getViewBuilder('block_content')->view($block);
return $render;

.