A common use case you hear from content editors is to add the ability to ‘auto-publish’ content so that they can schedule the introduction of new content to the cms. On some of these occasions, this can be achieved by applying a window to content rather than attempting to publish it in a given window.
It is worth noting – to make this a more complete solution, additional work may be required to ensure links etc do not show, this has to be treated more specifically.
It’s been a long time.., and… as some of the inner circle already know.. I have defected …
Well.. by defected, I mean I am no longer a developer by day (still helping on Glass and some project work by night.) I decided that I would try and make an active change in my working in life to start working in the arena I feel plagues most projects I have worked on… Delivery (DevOps)..
I thought I would start looking at a series focused more on delivery of systems and solutions on the platform including commmon scenarios, potential solutions, etc.
I know this may well be one of my controversial views, but… One of my pet hates of the modern era of Sitecore development is the insistence that front end developers work in the same place / same way as back end developers. I have been involved in many projects (100s for sure), small and large and on differing technologies. Whilst this approach can work ok on a simple MVC application, I think it is pretty poor on the Sitecore platform and here is why: Continue reading
Today I have released a minor update following community feedback, this should hopefully address a few issues seen on Content Management instances. This release disables the cache usage except when the page is running in normal mode.
Sitecore Boost received a small but important bug fix to relax the caching of Rendering Items for renderings added on standard values.
Being a sell sword, I can comment on a lot of different stacks (along with providing my preferred). Following on from a discussion Sitecore Community – CI / CD I thought I would share my thoughts a little on this subject:
Fundamentally most Continuous Integration / Delivery environments involve the following elements (in a very rough ordering): Source Control > Build Tool > Automated Testing Tools > Code Metrics Tool(s) > Deployment Tool(s) > Sitecore Content Deployment Tools > Environment Scaffolding > Monitoring
Before I go any further, I think I should state what I believe to be the MOST important goals of your CI build environment.
- The simplest to manage / manipulate. The tooling should get out of you way and soak close to zero time.
- Should be maintainable by the majority of the development team, not ‘key holders’.
- Deployments should be done by non-developers.
- It just works – once set up, you shouldn’t have to tinker with it.
My biggest bug bear of any system is where only the Solution Architects / Team Leads can manage the build process. QA’s testers / product owners should be responsible for sending stuff to QA / Production (if there is to be ANY human involvement at all).
So hear it is split down by element:
A while ago I started the process to soft release a little module I have been working on. It is called the ‘Advanced Content Security’ module (ACS). It’s primary purposes are the following:
- To provide alternative layouts to pages that are ‘restricted’ but not unreadable by users – think the average newspaper site that allows you 10 views before you have to sign up.
- To provide rules based read and restriction security
- To provide a rules engine based solution to the initialisation of users
Today, the latest version was approved and added to the market place.
For a more detailed overview, you can find more information about it here:
The source code resides here:
The module itself can be downloaded here
In a recent Glass release I was working on an issue that led to Mike making a comment on how I work as a programmer. The particular issue in question was actually quite straight forward to solve – I wrote unit tests that showed the issue, wrote some sandbox tests that showed how code behaved in the underlying Sitecore library, then fixed the tests approriately. All typical of TDD. The normal thing for me though is then to write a unit test that performs this simple fix 1,000,000 times emitting the result of stopwatch timings at various points. Mike jokingly commented at the time that this was ‘typical Nat’ which, to be fair, he was right on.
In this post I will look at the effect on work done in the constructor and how it has affects your development life in the context of modern DI practice – in particular – the DI principle.
This post is one that there is less of a right or wrong answer on, but it is my approach on how and when I look to use Glass Mapper in my solutions.