In this post I would like to tell about a brief insight of benefits what Docker can provide to you as a .NET stack developer working with SQL Server. Maybe the main focus and excitement this time will be about the new opportunities in local development on Mac OS, nevertheless the good things what Docker can bring to you are more than just that.
Have you ever wanted to index a content item in Find without having to publish a meaningless change to it? Or index an entire content tree from a specific starting point? Maybe you want to force an item into the index even though it's excluded by conventions? Just install Geta.Epi.IndexContentInFind package and it will be easy to do just that.
Recently one of our customers experienced an issue with Episerver Forms and the PlaceHolderService (I know it is still in beta, but anyway). The placeholder service is used by the built in Email Actor and is responsible for replacing tokens in the subject, to address and the body of the email that is configured to be sent by the editor.
For quite a long time I've been wondering if Episerver is going to do anything about the built-in category functionality. I feel it's pretty outdated and it's not so convenient to edit and localize categories. I guess the teams at Episerver are busy with other, more important stuff, so I decided to create a module. Say hello to Geta.EpiCategories.
When you are working on several inRiver PIM projects simultaneously, you find yourself in need of switching between them from time to time. One option is to change the configuration files and restart inRiver services and website. A better option is have multiple instances of inRiver PIM running on the same system. This way you can easily access the desired instance for configurations, developing and demos. This is a walk-through on how to set up multiple instances of inRiver PIM on the same system.
Let's say you have developed a site framework that you use on many different sites that contains some content types spread over various assemblies. Sooner or later, on at least one of the sites, you will want to add, hide or modify a property on a specific content type. You could create a new content type that inherits the original and then hide the original. No thanks. Let's do it better than that.
It is time to start a new and exciting e-commerce year, and hopefully break some records. After a hectic holiday season, why not start the year by doing some technical tiding up? Here are three technical new years resolutions for your e-commerce site to make it more secure, slimmer and more visible.
Sometimes when developing Episerver solutions you find the need to extend the behaviour of already existing property editors. In this blog post I will briefly describe how I extended the built-in content selector with direct upload functionality using drag and drop. This way you don’t have to create your "Media"-items before being able to select them. You can just upload them directly to the property editor and they will be added to the assets folder of the content you are working on and selected automatically.
The other day I had to deal with a mysterious error with the Episerver Shell search function. You know the little search icon to the right in the dashboard drop-down menu. When I clicked it nothing happened. I looked at the request in developer toolbar, discovered the exception and this is how I fixed it.
From time to time I get asked; 'How can I retrieve all parent catalog nodes for a product in Episerver Commerce?' Achieving this using the current version of Episerver commerce API is a bit cumbersome. Luckily Episerver is working on a relation overhaul for the next major version of Commerce, but until then I'll provide some sample code that does the trick.
Is it time to take your first Episerver CMS certification exam or retake an expired ECD exam? I took my first Episerver ECD exam 8 years ago on CMS 5, and have taken it several times again since then for different versions. Recently I did the new Episerver CMS 9 MVC exam online. Here are my tips for how you can prepare to take your Episerver certification exam.
Førstkommende fredag er det «Black Friday» og med det store muligheter for å gjøre virkelige kupp i nettbutikkene. Fenomenet som startet i USA kom til Norge for 4-5 år siden. Prognoser fra Posten viser at omsetningen i årets «Black Friday» vil bli omtrent det dobbelte av i fjor og har innkallt ekstramannskaper.
Shipping and return policies affect the conversion rate of you online store more than you think. Research show that 3 of the top 5 reasons people abandon their shopping cart is related to shipping, and it is not all about cost. 40% of customers say they abandoned the cart because the shipping and handling costs were listed to late. In this blog post I will share some best practices from our experience working with our international e-commerce clients.
I was developing a new feature in EPiServer 8.8 for one of our customers which involved creation of multiple new page types and page instances that needed to be arranged in complex hierarchy. The plan was to create content in testing environment first and later transfer it to the production environment using Export data / Import data feature. Unfortunately, it didn't go as smooth as planned.
A thing that has bothered me for a long time with EPiServer is that you, out of the box, can't have different display options for different blocks. Based on the design for your site you might want to force one block to full width and another to half width etc. You can do this with CSS but what's bothering me is that the editor is presented with an option that doesn't make any sense. So, I decided to fix it. :)
Sometimes you may want to translate the EPiServer user interface to a currently unsupported language or just want to change the text of some button or whatever. If you have been working with EPiServer for a while you probably know that one way you can do this is by putting XML files in the ~/lang folder. But where the hell are the language files being used by EPiServer so you can lookup all the XPaths? I'll tell you. And because I'm so friendly I'll let you download the XML files for free.
This is a quick tip filed under the "Enhance the user experience for web editors" category. In an enterprise EPiServer solution with multiple sites it's a common scenario to have separate category structures for each site. This simple editor descriptor makes sure the web editor for a specific site only sees and can select the relevant categories.
Lately I was visiting and revisiting content area, code and functionality around this feature in EPiServer and decided to revisit it once again and take a closer look at what’s really inside. So the blog post is not about what content area is, but how it works, how responsible party for rendering and templating is selected when EPiServer needs to render this one of the most powerful content editing feature.
Yesterday we discovered an issue with our block preview implementation in a project we are currently working on, running EPiServer Commerce version 8.2.1. The problem was that all blocks got previewed in the master language (english in our case). When we clicked a property the correct translation was loaded, but it was very confusing for the editors so we had to fix it.
More than one time I have found myself in the need of a filtered category tree in EPiServer. In large sites there can be a lot of categories and sometimes you just want to force the web editors to choose from a predefined root category. What to do? Create a editor descriptor that replaces the built-in one!
For the last couple of days I have been working with a custom dojo component that plugs into the assets panel. I needed a way to select a page from the content tree and had no idea how to do it so I started to dig around in the large and deep structure of ClientResources in the EPiServer.CMS.UI package and voilà, I found the epi-cms/widget/ContentSelector. Let's use it!
I get a lot of questions from new and experienced developers alike asking how it is working with Episerver these days. They have maybe heard some rumors from people working with Episerver before or they have stumbled across an Episerver project in the past. The main thing is that there´s a lot of confusion out there about what we as Episerver developers do everyday.
I går meldte nyhetsbyrået Bloomberg News at amerikanske myndigheter setter store begrensninger i blant annet Amazons planer om å levere varer ut ved bruk av droner. U.S. Federal Aviation Administration (FAA) har nemlig satt som krav at små droner av sikkerhetshensyn kun kan flys i synlig avstand fra operatøren, og ikke i nærheten av menneskeansamlinger.
Synes du det er forvirrende å sette deg inn i offentlige anskaffelser og spillereglene her? Vel, du er nok ikke alene. Regelverket kan virke rigid og vanskelig, men i virkeligheten er det disse reglene som sikrer oss leverandører de gode rettighetene. Ofte er det ikke selve regelverket som er problemet, men personene som tyder disse og lager konkurransedokumentene.
Loggly is a great cloud-based logging tool. It enables developers to centralise their logging to one convenient location, which helps reduce the time it usually takes to log into the server where the project is located, find the relevant log files, and scroll through the countless number of lines to find that one specific log entry. Needless to say, it's a useful tool indeed, and this plugin enables you to effortlessly implement this feature into your EPiServer CMS project.
…og tips om et verktøy som kan hjelpe deg i gang! <BR><BR> Det er mye vi ikke vet om den menneskelige hjernen og de beslutningene vi tar. Men samtidig er det mange som vet veldig mye om det, og tar i bruk virkemidlene på nett også. Du trodde kanskje det var du som bestemte deg for å kjøpe det du sist handlet på nett helt selv…?
De fleste som driver med varehandel har nok opplevd det: Du har en excelfil med litt produktinfo her, en bildebank der, noe tekst på en epost, og ikke minst pris, lagerbeholdning og litt til samlet i et ERP-system (Enterprise Resource Planning) og POS-system (Point-of-Sale / checkout) med mer. Så ganger vi alt dette opp med antall produkter du har, og at du skal sende deler av infoen til forskjellige kanaler; avisannonser, nettsider, kataloger med mer. Kort fortalt; du ender opp med det vi på godt norsk kan kalle innholds-spaghetti.
Video ble mye diskutert på IRCE. Visste du at man i USA daglig bruker mer tid på smarttelefonen sin alene enn på TV ifølge Millward Brown Digital? Med PC blir TV "liten" i forhold. Og visste du at i gjennomsnitt brukes 33 minutter per dag å se på video på mobil og 22 minutter på PC (kilde: eMarketer)? Nå vet jeg ikke tallene for Norge, men ting tyder på at video på nett er populært også blant nordmenn. Men er vi flinke nok til å utnytte det? Joyus baserer seg nesten utelukkende på video. Her er deres tips.
IRCE er verdens største konferanse om e-handel, og feiret i år sitt 10års jubileum. Over 200 foredragsholdere på fire dager og nærmere 700 utstillere gjorde turen til Chicago og de 10 000 øvrige deltakere på konferansen vel verdt turen. Men det er mye å tygge på i etterkant. Her er noen av mine hovedinntrykk fra konferansen. Så langt.
Today I fixed an issue in our open source plugin for EPiServer 7.5, Geta.SEO.Sitemaps, a tool to generate Google XML sitemaps. The issue occurred when you had one site mapped to multiple hosts with different language branches. Only the sitemap for the main SiteUrl worked (although displaying links to all language branches which is not desired) and the other hosts resulted in a 404.
Forskjellen mellom en god nettside og en god nettbutikk er enorm. Det er ikke bare å legge til en "legg i handlekurv" knapp og tro at du har gått fra en produktpresentasjon til en fullverdig nettbutikk. Det ligger mye mer arbeid bak enn som så. Men hva gjør så de som lykkes? Jeg tok en prat med Sportmann for å høre hva de gjør.
Over the last 4-5 projects my team has been working with EPiServer 7 and 7.5 using ASP.NET MVC. We've ended up creating some useful methods and helpers that we used in all those projects, that we've found to be very valueable and time saving. This library is now in a stable version that we're excited to open source and let everyone use.
For å stikke hull på ballongen med en gang – ja, jeg jobber i Geta og Geta er EPiServer Premuim Solution Partner. Så da burde kanskje innlegget hete «hvorfor velge EPiServer»? Feil. Jeg lover etter beste evne å være så objektiv som mulig, og jeg lover å kun gi deg noen generelle tips og ideer som du må tenke på når du velger CMS, eller publiseringsløsning om du vil. Jeg skal til og med gi eksempler på andre CMS som kan være riktige for deg. Å velge feil, kan nemlig koste deg dyrt.
Velkommen til Getas nye blogg! I mitt første innlegg vil jeg gjerne ta for meg et tema som kanskje ikke vil bli så hyppig diskutert her, men siden det tross alt er nyttår, tar jeg sjansen. Godt Nytt, forresten! Hvis du ser et år tilbake, har du nå nådd de målene du satte på denne tiden i fjor? Og har du tenkt igjennom hvorfor du (ikke) har gjort det..?