We’ll start off in Content Hub where we’ll create a new taxonomy and add that to our assets. We’ll then make sure that if that taxonomy has a value set, we’ll trigger some automated actions to create a public link.
We will then go into Personalize and update our whole setup. We’re going to no longer be using Offers, instead we’ll use a Data System that queries Content Hub using GraphQL. Continue reading
This title might seem strange at first sight. As a Sitecorian I’ve obviously been using the individual components of Sitecore’s offering, however I’ve not tried to use them together in anger so I thought I’d write up a blog post … Continue reading
I’ve really been enjoying working with SXA and its CLI, which is pretty cool when you need a new Theme. For a while it was working perfectly but all of a sudden I didn’t see my changes show up on the site anymore.
I ruled out the actual building of the scss fairly quickly (as I could see the changes in the minified css file), but weirdly it wasn’t being uploaded. The SPE log files showed the following:
[…]
20048 15:58:34 INFO ‘POST/media’ called by user: ‘sitecore\admin’
39844 15:58:34 INFO ‘POST/media’ called by user: ‘sitecore\admin’
24384 15:58:34 INFO ‘POST/media’ called by user: ‘sitecore\admin’
23548 16:04:57 ERROR Attempt to call the mediaUpload service failed as – user not logged in, authentication failed, or no credentials provided.
25584 16:04:57 ERROR Attempt to call the mediaUpload service failed as – user not logged in, authentication failed, or no credentials provided.
18252 16:04:57 ERROR Attempt to call the mediaUpload service failed as – user not logged in, authentication failed, or no credentials provided.
33192 16:04:57 ERROR Attempt to call the mediaUpload service failed as – user not logged in, authentication failed, or no credentials provided.
29864 16:04:57 ERROR Attempt to call the mediaUpload service failed as – user not logged in, authentication failed, or no credentials provided.
For whatever reason, the username wasn’t pulling in anymore even though I didn’t change anything.
Running the rebuild command with the debug flag didn’t really give me anything useful either
sxa rebuild -l sitecore\admin -p b -d
After some more digging, I found that somehow in those couple minutes my admin user got locked…
All that I had to do to resolve the issue was unlock the account and voila, my changes started appearing again.
I’ll start this post with a little caveat: While a lot of my posts are reasonably technical, this one is not – this is aimed at end users of Sitecore.
Having said that, I wanted to dig in to what the various facets that Sitecore’s Media Library comes with (at least, the out-of-the-box ones) Continue reading
As we all probably are aware of by now, Sitecore 9.x requires on SOLR OOTB (of course, you can change this). There’s a load of blog posts on installing SOLR, but I ran into a couple of additional issues which no-one else seemed to have run into, and weren’t as easy to debug. I figured I’d share 🙂 Continue reading
Before I start: Sitecore’s licensing model changes occasionally, so it is always recommended to check in with your Sitecore sales representatives or your Sitecore contact. As a partner, you can find who your Sitecore contact is (and get their details) by logging in to Sitecore’s Partner Network. As a customer, you can talk to your Sitecore account manager. Continue reading
We all know that with Sitecore we have extensive functionalities we can use when it comes to dictionaries. They can be used to make form labels, button texts, watermarks and other pieces more dynamic rather than hardcoded. They can even support functionality similar to the string.Format() method in .NET. Continue reading
Before letting you go on to the contents of the blog post, I’ve had this one in my draft for quite a while but figured I should finish it. Yes, we can use Sitecore on PaaS these days as well (which is great), but I feel like the info in here is still useful as IaaS is still alive and kicking! Anyway, without further ado:
Do you have a Sitecore Virtual Machine (preferably in Hyper-V), and do you want to get your website to Azure? In a rush to get there? Well, you might be in luck!
I’ve been trying to get our internal demo website running on Azure, and have it deployable in a very easy manner. Provisioning Sitecore onto Azure is really easy these days, and the code itself is also easily deployed to my environments (see these previous posts for more information).
The issue I was having was with Unicorn – or more specifically the locations of my data folder. On my local machine, I have Sitecore running in a specific location, and can simply point my Unicorn to a specific location on my machine (i.e. c:\development\demo\data\unicorn). Since all my colleagues working on the projects have the same file structure and we never have to deploy to an actual server that works perfectly.
However, I’m now adding a new deployment server to the mix, with a different file structure. I can’t simply use the same path as it might not exist there. Continue reading
Since Sitecore 8.2 update 1, we can simply scale our App Service plans up or out. You can find these options on the App Service Plan as well as the App Service themselves.
Scaling up means selecting a different tier for our subscriptions – more RAM and cores for instance.
As you can see, I’m currently running on the S1 tier – which I can’t recommend to anyone as it’s quite slow (of course, it is way below the minimum specs found in the installation guides)…
Our other option is to scale out. That means we can add (or remove) a number of instances based on… something. Let’s take a look.
Sitecore and such 