Like many who worked for years in the world of K2 4.x, I had to adjust to multiple changes when clients adopted K2 Five. Experience made some problems in K2 4.x a snap to fix, but we maybe needed to grow a little to accomplish the same in the new version.
I’m going through the rules in a SmartForm and associated views to squash a bug, when I came upon an Execute a Form method action in the When the Form is Initializing rule.
Trouble is, the method to call is the Initialized method.
Would that even work?
Last August I wrote a post about how a column in a list view was excluded from SmartForms’ Quick Search because the column wasn’t displaying the field directly — it was displaying a data label via an expression.
I ran into a similar-but-not-really-similar situation today.
File this under “Learning the Hard Way” and “Stop Messing With Your Browser Settings.”
I’m working for a client new to the world of software development and unencumbered by familiarity with development lifecycles and environments. (Not their fault; it just places the onus on us to teach them.) I’m not sure how long my company has been working with them; I just joined the project a couple of months ago.
Somewhere in the past, some percentage of the developers on the project acquiesced to doing development work in their production environment, probably because they were asked to do so to help them with some tight deadlines or urgent requirements. The short term effect was that it helped the client meet whatever deadlines or requirements they had; the long term effect is… disastrous.
The upgrade evolution across four environments and two months is finally complete. And I learned something about the process I want to share: Thanos doesn’t come to visit.