Tuesday, December 29, 2015

Umbraco Initial setup and sample website.. Part 1

Here are simple steps to set up the Umbraco development environment and set up for a sample website.
  1. Initial Setup for Umbraco
·         Download the Umbraco from: - https://our.umbraco.org/download/    


·         Extract the download package:-  


·         Open the VS and browser this website and run the project.


·         Create a new SQL database like Umbraco.


·         Run your application


·         Very nice UI will be appear...


·         For the initial setup, it’s required to provide below information, Provide the configuration details as below:-



·         Click on the customization to setup the SQL database that we recently created.



·         Landing Screen: - Provide the credentials for the login: -


·         Preview site option:-

·         Sample site will look like this:-


·         Changes in the content and publish to verify these changes :- 



·         After these changes, Need to publish these changes.




Second part will cover the new site setup and process for creating new sample pages.




Sunday, December 6, 2015

key ask for Sitecore Migration/Up-gradation.



1)      Current Version of Sitecore?
·         Helpful to identify the scope of migration.
2)      List of all components and their uses and dependencies?
·         Helpful to identify the dependencies and scope of migration.
3)      What is the approach for digital assets/Media library management?
·         To understand the type of content like audio, images, multimedia and how they are managing.
4)      What is the current search approach?
5)      Is the solution multilingual? If so, does the content on the multilingual versions differ?
·         To understand the scope and complexity of the migration.
6)      What is the current architecture and process flow of the CD and CM server?
·         To understand the current infrastructure and deployment process.
·         Help to decide the migration approach.
·         Scope for performance and process improvement.
7)      List of Sitecore customizations types and their details?
·         Pipeline customization?
·         Changes in the caching approaches and settings?
·         Changes in the web.config?
·         Url aliases or rewriting implemented?
8)      What is the design of current Information architecture, content models and data models?
·         For migration and performance prospective we should know what all our content are interdependent/linked or reusable.
·         To define the serialization approaches for the migration.
·         To understand the inputs, Outputs, and Designs.
·         To understand what types of content elements appear consistently on multiple pages or sites.
9)      Required Server configuration (Software and Hardware) latest version and load balancer details?
·         It’s required to check the compatibility with the Sitecore new version.
·         Help to decide the migration approach.
·         We can review and suggest the Scope for the performance improvement.
10)   Are all existing sites compatible on MVC framework?
·         There is a lot of architectural difference in MVC and web form like web form work with Page controller pattern and MVC work on the front Controller approach.
·          In case of migration from web form to MVC all the existing rendering and design components needs to be reviewed or rewritten.
11)   List of modules which implemented/added like WFFM, Email campaign connector or CRM connector etc. And their latest version details?
·         It’s required to check the compatibility with the new version.
·         To understand the scope like In case of WFFM, it will require more manual process.
·         Challenges like cannot add form from the new Experience Editor interface
·         Important aspect of Solution Upgrade.
·         Any custom modules is integrated like Advanced Database Crawler, blogging, SES, etc.)
12)   List of website instances and their features.
·         To understand the technical challenges and scope of migration.
·         Help to design and upgrade the components.
13)   Is there any mobile device detector module associated?
·         Help to decide the migration approach.
14)   What all are the custom roles defined?
·         Help to decide the scope of migration.
15)   A list of the system template changed/manipulated?
·         Help to decide the scope of migration.
16)   Are all website code are using Sitecore standard field rendering or not?
·         To understand the scope of migration.
17)   What all are databases used, required their version details.
·         Help to decide the scope and possibility as Oracle database is not yet supported in the latest version.
18)   How much dependencies of Analytics data?
·         It helps us to define the scope of migration.
19)   Any out of the box customization like HTTP handlers?
·         It helps us to define the scope of migration.
20)   What is the Content authoring approach and what all are the workflow implemented?
·         To understand the scope of migration.
·         To understand the scope of migration.
21)   Is there any global and template specific placeholder settings implemented?
·         To understand the scope and complexity of the migration.
22)   What all are the types of authorization role to access the content?
·         Very important to understand their security model that they have given/implemented for the users.

Tuesday, November 24, 2015

Browser - Cookies limits.

Typically, the following are allowed:
  • 300 cookies in total
  • 4096 bytes per cookie
  • 20 cookies per domain
  • 81920 bytes per domain*
* Given 20 cookies of max size 4096 = 81920 bytes.

IE (and Opera) introduces a new limit, max bytes per domain

Reference :- http://browsercookielimits.squawky.net/
 

Monday, November 23, 2015

Sitecore options for serialization and deserialization .

Serialization – Convert data/objects into stream of bytes.
Deserialization – Convert stream of bytes into data/objects

There are three options for serialization and deserialization in the Sitecore.

1)      The Sitecore serialization page provide the interface to transfer the database to the bytes/text files
Location is: - /Sitecore/admin/serialization.aspx
Helps to take backup of database, version control and to track the changes (in case of trouble shooting).

File created on the file system:- 


2)      Serializing Items through content editor option :-
Steps:-
To serialize an item:
1. In the Content Editor, select an item that you want to store in a text file on the disk.
2. On the Developer tab, in the Serialize group, click Serialize Item.

To show the developer options enable this from the ribbon bar:-



Click on serialize item:-


To serialize an item with all its sub items:
1. In the Content Editor, select a parent item that you want to store with all its sub items in text format on the disk.
2. On the Developer tab, in the Serialize group, click Serialize Tree.

3)      Sitecore event handlers :-
Need to enable the event handler by default it’s disabled

Add below configuration in the web.config file

             <configuration>
  <sitecore>
    <events>
      <event name="item:saved">
        <handler type="Sitecore.Data.Serialization.ItemHandler, Sitecore.Kernel" method="OnItemSaved"/>
      </event>
      <event name="item:deleted">
        <handler type="Sitecore.Data.Serialization.ItemHandler, Sitecore.Kernel" method="OnItemDeleted"/>
      </event>
      <event name="item:moved">
        <handler type="Sitecore.Data.Serialization.ItemHandler, Sitecore.Kernel" method="OnItemMoved"/>
      </event>
      <event name="item:versionRemoved">
        <handler type="Sitecore.Data.Serialization.ItemHandler, Sitecore.Kernel" method="OnItemVersionRemoved"/>
      </event>
    </events>
  </sitecore
</configuration> 





Other tools available on the Hedghog for the serialization and comparisons