Sitecore Interview Questions PDF
Sitecore Interview Questions PDF
Contents
1) What is Sitecore? ............................................................................................................................. 7
2) Why should you use Sitecore? ......................................................................................................... 7
3) How can you setup Sitecore?........................................................................................................... 7
4) Which are different versions of Sitecore? ....................................................................................... 7
5) First look at Sitecore? ...................................................................................................................... 8
6) What is Desktop? ........................................................................................................................... 10
7) What is Content Editor? ................................................................................................................. 10
8) What is Page Editor? ...................................................................................................................... 10
9) How many databases are associated with Sitecore? ..................................................................... 11
10) What is core database?.................................................................................................................. 11
11) What is master database? ............................................................................................................. 11
12) What is web database? .................................................................................................................. 12
13) What is content author? ................................................................................................................ 12
14) What is Item in Sitecore? ............................................................................................................... 12
15) What is Template in Sitecore? ....................................................................................................... 12
16) What is publishing? ........................................................................................................................ 12
17) Which are different types of publishing? ...................................................................................... 12
18) What is Staging Environment? ....................................................................................................... 13
19) What is Production Environment? ................................................................................................. 13
20) What is versioning in Sitecore? ...................................................................................................... 14
21) Which are different types of view modes in Sitecore? .................................................................. 14
22) What is standard values in Sitecore? ............................................................................................. 14
23) What is standard fields? ................................................................................................................ 14
24) What is raw values? ....................................................................................................................... 14
25) Which field contains item sort value? ........................................................................................... 17
26) What is Layout in Sitecore? ........................................................................................................... 17
27) Which are different types of rendering in Sitecore? ..................................................................... 17
28) What is difference between droplist and droplink field type? ...................................................... 18
29) What is pipeline? ........................................................................................................................... 19
30) What is processor?......................................................................................................................... 19
31) Under which pipeline Sitecore context gets defined? ................................................................... 19
32) How many processors are there under <httpRequestBegin> pipeline? ........................................ 20
Disclaimer
This book is presented solely for educational purposes. This book is designed to provide
information on Sitecore CMS only. This information is provided with the knowledge that
the author do not offer any legal or other professional advice. In the case of a need for
any such expertise consult with the appropriate professional. This book does not contain
all information available on the subject. This book has not been created to be specific to
any individual’s or organizations’ situation or needs. Every effort has been made to make
this book as accurate as possible. However, there may be typographical and or content
errors. Therefore, this book should serve only as a general guide and not as the ultimate
source of subject information. This book contains information that might be dated and is
intended only to educate and entertain. The book may include information by third party
blogs or websites. Third Party materials comprise of the products and opinions expressed
by their owners. As such, the authors of this book do not assume responsibility or liability
for any Third Party Material or opinions. The author shall have no liability or responsibility
to any person or entity regarding any loss or damage incurred, or alleged to have incurred,
directly or indirectly, by the information contained in this book. You hereby agree to be
bound by this disclaimer.
Thanks To,
Sitecore Community
What is Sitecore?
Sitecore is very flexible Content Management System (CMS). It is one of the leading enterprise-
level content management systems (CMS) using which you can create enterprise website and
intranet portal website.
Sitecore was found in 2001 and it is built on Microsoft .NET platform. Sitecore also allows
deployment via Microsoft Azure.
There are three ways you can login to Sitecore – Desktop, Content Editor and Page Editor.
What is Desktop?
When you are login using Sitecore Desktop you will find rich set of features using which you can
Create and Install packages
View files using File Explorer
Clean up database using Control Panel
Change the desktop background
Change the application options
Many more
Sitecore Desktop user interface has many feature options compare to Content Editor user
interface.
Content Editor Interface has less feature options compare to Desktop interface but have more
feature options compare to Page Editor Interface.
authors prefer to work in such interface that is designed to meet their needs and not those of
the developers and designers who create the Web sites.
With this mind, Sitecore CMS allows content authors to edit and create items directly on the
Web page with the Page Editor.
The Page Editor is the simplest of the editing tools that Sitecore contains. It is designed for
inexperienced content editors who edit and write content items directly on the page. It is a
WYSIWYG editor (what you see is what you get) and limits the amount of functionality that is
presented to the user.
When you log in to the Content Editor, the items that make up your Web site are presented to
you in a very different way than they are in the Page Editor. In the Page Editor, you see the
items as they are presented on the Web site.
What is publishing?
By this time you are now aware with the fact that whenever you add, edit and delete any item
in Sitecore, it will be stored in master database. Now in order to move this change to live
website, you need to use publishing. Publishing is a process which will help you to copy updated
items from master database to web database.
As name implies, it will publish every item no matter whether it is changed or not. It is
intended to be used when you are publishing a new site first time. This is most time
consuming publishing method as it blindly publish all items.
2) Smart Publish
This method works smartly by comparing each item in the master database with the
item in web database. Sitecore maintains revision number for each item which gets
changed whenever the item gets updated. By comparing this revision number with web
database, it will create a list of updated items changes and will publish only those items
changes. Even though this method is comparing each item, it is much faster than
republish method.
3) Incremental Publish
Every time an item is changed, it is added to the publishing queue. This applies both to
changes made through the Sitecore user interface and changes made programmatically.
Doing an incremental publish will only publish the items in the publishing queue.
Therefore only items that has been changed will be published and Sitecore does not
have to do any comparisons to figure out which items has been changed. This way of
publishing is therefore by far the fastest. Republish and smart publish do not use the
publishing queue.
Once user is happy with changes on staging environment, deployment is then roll-out to
production environment.
Standard values are a way of having default or fallback values for fields in Sitecore, meaning that when
items are created, you can specify a field value that should be used by default. This does not only
account for custom fields you build, but also standard fields in Sitecore such as presentations and insert
options. This means that you can specify a value on the standard values, and when you create a new
item which inherits from this template, it will by default use the values specified on the standard values.
In Sitecore, there are two ways of getting data out of a field – the raw value or the rendered
value.
A field’s raw value is how the data is stored in the underlying database – for simple fields such
as Single Line Text, there is no difference between the rendered and raw values; it’s just plain
text.
This is not the case for more complex field types, such as General Link, Image, or Rich Text.
Take the raw value of a General Link field, for instance – if you enable raw values in the Content Editor
(by clicking the View tab and ticking Raw values) and look at an item with a General Link field, you will
see that the value stored in the database is custom XML:
The following table provides an example of each field type, as the value is stored in the Sitecore
database.
Field Type Example
checkbox 1
checklist {E00D9E00-2582-4022-88AE-151CE3CD7C41}|{858D25B3-B8A6-4ED1-B6F8-
B52C4CC0EFDF}
date 20051003T120000
datetime 20051003T163256
file /images/extimages/outh gif
html This is some <strong>example</strong> HTML content.
icon /sitecore/shell/Themes/standard/carousel.png
image <image alt="Alternate text" width="150" height="150" hspace="4"
vspace="4" mediaid="{539587C7-1F36-4D94-A10D-FFFAF079B746}"
mediapath="/images/hist_gunung100px jpg" showineditor="1"
usethumbnail="1" src="/upload/images/hist_gunung100px.jpg"/>
internal link /sitecore/content/Home/Sample Forms
layout <r ><d id="{FE5D7FDF-89C0-4D99-9AA3-B5FBD009C9F3}" l="{14030E9F-CE92-
49C6-AD87-7D49B50E42EA}"><r id="{493B3A83-0FA7-4484-8FC9-
4680991CF743}" ph="content" ds="" par="Param1=Value1" cac="1" vbd="1"
vbu="1" /></d><d id="{46D2F427-4CE5-4E1F-BA10-EF3636F43534}"
l="{14030E9F-CE92-49C6-AD87-7D49B50E42EA}"><r id="{5D104030-657E-
48DA-B032-0F9BB1A3C671}" ph="content" ds="" par="" /><r id="{E0E16B09-
0176-4756-978C-63459B19F8ED}" ph="content"
ds="/sitecore/content/Home/Other selectable document"
Technically speaking, your .ASPX page is layout and .ASCX, .CS or .XSLT file is component (user control).
a. ASP.NET web controls are created to use this rendering. Create .CS file for this
rendering.
3) XSL Rendering (rarely used)
a. Very few programmers are using this rendering as writing XSLT program is bit difficult
and it has limited features. Create .XSLT file to use XSL rendering.
Sitecore has two different types of drop-down lookup fields that are available: Droplist and Droplink.
Both of them function essentially the same way: they point to a Sitecore data item and list its children in
a drop-down list for a content editor. This is a great tool because it allows you (as a data designer) to
build a nice set of lookup values and not worry that editors will fat-finger these values.
But why are there the two, and what’s the difference between them?
Droplist data type only stores the string value of the item that was chosen by the content editor, while
Droplink stores the GUID of the item that was chosen by content editor.
This will cause a problem when you want to read selected item’s field value. If you use droplist,
you are not going to get selected item and will get only selected item’s string value. But if you
use droplink, you can easily get selected item and then can read any field value of that selected
item.
What is pipeline?
A lot of things happens when you request a page in Sitecore which is handled by pipelines.
Pipelines define a sequence of processor that implement different functions such as handling
page requests, to uploading files and saving items through the UI. If you have a series of tasks,
which need to be performed to accomplish a task, then a pipeline may be the way to go.
Each processor in a pipeline contains a method named Process() that accepts a single argument
and returns void. This method should return immediately if the processing context is not
relevant to the processor. A processor can abort the pipeline, preventing Sitecore from invoking
subsequent processors.
Sitecore separates the pipelines into two groups: those defined within the
/configuration/sitecore/pipelines and /configuration/sitecore/processors elements in the
web.config file. In general, those defined within the /configuration/sitecore/processors define
pipelines that operate for UI requests and can interact with the user. Those defined with the
/configuration/sitecore/pipelines tend to define system processes.
What is processor?
Each step in pipeline is called a ‘processor’. The sequence of processors within a pipeline is
defined in web.config file. Each Processor contains a unique operation and all these steps
together create a pipeline.
<pipelines /> define system process such as initialize Sitecore application, load content editor
warning. <processors /> define UI process such as copy item, delete item, drag item and so on.
What is command?
When you click any button within the Sitecore interface, the respective command gets called. Typically
Sitecore commands are used to map actions to c# code. This mapping is defined in
/App_Config/Commands.config file.
If you want to add your own commands you can either edit /App_Config/Commands.config file or setup
a patch file in /App_Config/Include.
2) Serialization
If you are not seeing “Developer” option in menu bar, then configure it as shown in
below screen capture.
If you have question which is the good choice – Package or Serialization? Keep reading this book, it will
be covered in next set of questions.
There is size limit of 2 GB for package creation in sitecore, so you need to create
multiple packages instead of creating one package if your deployment exceeds 2 GB
size.
After installing package, if you have changed few items and now you want to revert
these items back to original version then there is no way to achieve it.
For example: If your package contains 50 new items, then you will have 50 new items in
your sitecore instance after installing this package. Now let say you have changed 10 of
these 50 items and you want to revert these 10 items back to previous version (same
version when you installed package), then there is no such mechanism in package
installation which will help you to revert these specific 10 items.
2) Sitecore Serialization:
Note: Always use firefox browser while installing items from "package" or "serialization"
because Internet Explorer gets time-out issue while installing a big package.
In order to move Sitecore items from staging environment (master database) to live
environment (web database), there are two options available in Sitecore:
1) Publish (recommended) – you should always use publish option if you want to move
item(s) from staging environment (master database) to production environment (web
database).
2) Transfer (rarely used in specific scenarios) – you should refrain from transfer
option if you want to move item(s) from staging environment (master database) to
production environment (web database).
Then in which circumstances you should use transfer option? What’s the difference between
publish and transfer? Why it is recommended to use publish option?
On the opposite side, there is no cache clear job performed while using transfer option. That
means when you transfer any item(s), it will simply move item(s) from master database to web
database. So it’s your responsibility to clear the cache manually by using cache clear tool.
Now let’s talk about circumstances in which you can use transfer option. If you have published
tons of items which will take hours of time to get complete and suddenly you come across a
situation where you want publish single/few item(s) instantly. You cannot publish this item until
publishing queue completes current running publishing items (tons of item). Even if you publish
that urgently required item, it will be queued and will be published last. In such situation, you
can take advantage of transfer option to move instantly required item from stage environment
(master database) to live environment (web database). This will push your item to live
environment instantly although you need to clear the cache manually by using cache clear tool.
If you don’t know what is cache clear tool, then don’t worry we will discuss about Sitecore
cache and cache clear tool in upcoming questions.
So from where these checkbox values are coming? They are coming from publishing target
configuration.
As per the above screens “Internet” publishing target is pointing to “web” database. And the
“web” database definition is configured in web.config file.
You can configure more than one publishing target database as per your need. It is worth to
note that master database contains all versions items while publishing target database (e.g.
web) contains only single latest version of each language item.
If you have multiple publishing targets then you will see all of them in publishing window as
checkbox items. In case you want to set any of these publishing target database as your default
target database then you can configure it via DefaultPublishingTargets setting in web.config
file.
<setting name="DefaultPublishingTargets" value="Pre-Production" />
Workflow is controllable way by which you can define series of tasks to add, review and publish
content.
In order to achieve above series of task, you can take advantage of Sitecore Workflow feature.
You can find workflow at /sitecore/system/Workflows in Sitecore content tree. Below figure
shows an example of sample workflow.
Draft State: The draft state is initial state and it will be assigned to item whenever user creates
or edit the content. Sitecore item cannot be published if it is in draft state.
Awaiting Approval State: Once content editing is completed and item is ready to review, user
can submit that item to reviewer. This submission action will move item from draft state to
awaiting approval state. Sitecore item cannot be published if it is in awaiting approval state.
At any point of item if you want to know current state of item you can either check workflow
section fields of item or by looking into workbox.
For example: if you have specified $name token at “Title” field in standard value, then Sitecore will
replace “Title” field with item name that you provided while creating item.
For example you are working on template item and you want to know that how many items are created
using this template or how many items are using this template?
Below screen shot will guide you how to get referrers list.
If want to check this for multiple items then it will be time consuming job to select every item
and check links for all those items. For that you can download “Sitecore Informatics” module
from Sitecore Market place which will show you all your site templates and items created using
those templates.
How can you add help text for particular field in Sitecore?
Many times you want to provide some help text to user to understand the purpose of particular
field. You want to convey message to user what should be value of that field. This can be
accomplished by configuring help text for that field.
Below screen-shots will help you how to configure help text for any field.
For example – if you want to create an item “What we do?” Sitecore will not allow it as it contains
special character “?”
Display name (e.g. “Who we are?”) will be shown in CMS user interface such content tree in
place of item name (e.g. “Who we are”).
It is worth to note that Sitecore constructs the default URL of an item based on its name not based on
display name.
How can you configure log folder path of your Sitecore site?
Sitecore uses log4net API to log all the events and information. By default Sitecore create date
wise logs in log folder.
You will find this logs folder under dataFolder variable path. dataFolder is the variable that
defines exact path of your logs folder.
Where does Sitecore store all packages? How can you configure
this package folder path?
As we have seen earlier, Sitecore stores all the packages under dataFolder variable path. . dataFolder is
the variable that defines exact path of your logs folder.
Each website can be configured to enable or disable HTML cache along with allowed HTML
cache size in web.config file under <sites> section.
<site name = "website" virtualFolder="/" physicalFolder="/"
rootPath="/sitecore/content " startItem="/Home" database="web"
domain="extranet" cacheHtml="true" htmlCacheSize="10MB"
enablePreview="true" enableWebEdit="true" enableDebugger="true"
disableClientData="false" />
2) Item Cache
Sitecore items are cached under this cache layer. This cache contains objects of the Sitecore
class Sitecore.Data.Items.Item, which are the one you use in your code most of the time.
Whenever any sitecore item is requested, it will be served from item cache and if it is not there
then it will be served from data cache (next layer of cache) and will populate cache in item
cache layer. So that whenever next request for same item is made, it will be directly served from
item cache.
3) Data Cache
Data cache contains items of the Sitecore class ItemInformation. Whenever any request is
made, data is pulled from data cache. But if it is not present there it will be pulled from prefetch
cache and then will be put into data cache. So that whenever next request for same item is
made, it will be directly served from data cache.
4) Prefetch Cache
There is prefetch cache for each database. The cache contains items of Sitecore class
PrefetchData which is same like data pulled from database. Prefetch cache load the cache at
Sitecore start up as per specified in App_Config/Prefetch folder.
Step-1:
Configure your site hostname in Sitecore Instance. There are two ways to add new site in your
Sitecore instance.
Now you may be wondering which one is good option. Well, let me help you on this. It is good
to add new site in SiteDefinition.config file because it’s always advisable not to touch default
web.config file and override your custom settings in config files situated under App_Config
folder provided by Sitecore.
After adding new site in config file, there are two more steps need to be performed out of
Sitecore to access newly added site.
Step-2:
Add your site hostname in IIS binding
Step-3:
Add your site hostname in hosts file (under WINDOWS\System32\drivers\etc\ folder)
After completing these three steps your newly added Sitecore website is ready to access.
2) Data Browser
The /Sitecore/admin/dbbrowser.aspx page displays Sitecore database view. It is similar
to content tree but it is lightweight interface.
3) Serialization
The /Sitecore/admin/serialization.aspx page allows to serialize sitecore databases (e.g.
core, master and web) into XML file system. This page can be very useful when you want
to backup database content.
This is how the page actually looks like:
4) Show Config
The /Sitecore/admin/showconfig.aspx page shows final version of the sitecore configuration
including all external configurations from App_Config folder. This page is very useful for
debugging purpose to find if your web.config setting is overridden by any other external
config settings from App_Config/Include folder.
5) Stats
The /Sitecore/admin/stats.aspx page provides rendering statistics for presentation
components of each site, it shows how much time components take to load. It also defines
how many times components have been loaded from cache. This page is very useful for fine
tuning caching settings.
6) Unlock Admin
As the name implies /Sitecore/admin/unlock_admin.aspx page is used to unlock a locked
admin account. After certain number of invalid login attempts, a user may be locked out. If this
happens with admin user then this page will be very helpful to unlock admin account.
2) Coveo: It offers a rich search interface for faceted search. It allows to customize all the
search result fields without writing code or css. It provides highly advance search for
personalized online experience in Sitecore websites.
Coveo recently (at Sitecore Symposium 2014) announced a free version for Sitecore –
“Coveo for Sitecore – Free Edition” with some lmited features compare to paid
Enterprise edition.
Rich Text Default provides few editor options as shown in below figure.
While Rich Text Full provides wide range of editor options as highlighted in below figure.
By default, Sitecore is configured to use Rich Text Default profile. That means if no Html Editor path is
specified in source for Rich Text data type field, then it will use Rich Text Default profile.
Each rendering control contains Caching section which can be used to set caching
parameters. These caching parameters will be applied to all the pages though out the
site wherever that rending control is used.
I found and recommend second approach to get string value because it will not through any
exception even though there is no “Title” field found in pageItem. While second approach will
throw exception if “Title” field not found.
How can you get all child items of item which has particular
template?
Item currentItem = Sitecore.Context.Item;
If you have image field in item and you want to get that image
field URL in order to set on your image control, how can you
achieve it using Sitecore API?
Sitecore.Data.Fields.ImageField careerAreaImageFieldItem = randCareerArea.Fields["Image"];
version of sitecore item same as you see in stage environment (e.g. master database) for
troubleshooting.
To see live copy of any item (e.g. web database), you need to login desktop mode and can
switch database by clicking bottom right corner icon as suggested in below figure.
You can switch among any of Sitecore databases by clicking database selector icon.
Sitecore.Layouts.DeviceDefinition device =
layout.GetDevice(Sitecore.Context.Device.ID.ToString());
Sitecore.MainUtil.Out((device.ID.ToString()));
}
Moreover there is also option to open Rich Text Editor to update page data. Sitecore is using
third party tool (i.e. Telerik control) to provide this Rich Text Editor (RTE).
case "external":
default:
//Set link to external URL
string pageURL = link.Url;
break;
}
Sitecore.MainUtil.Out(productItem.Name);
}
}
item.Fields["Title"].Value will simply check whether title field contains any value or not.
Event queue as introduced in Sitecore 6.3 version to communicate between CM and CD servers.
It helps to trigger events from CM server to CD server.
For example:
When you publish an item in Sitecore, Sitecore will add a record in the EventQueue table of the
corresponding database. There is a timer in Sitecore instance which will check EventQueue
table periodically and will trigger any event if found.
Content authors works on CM server to add/edit content. Whenever content author publishes one or
more items from the CM servers, it gets published on CD server.
CD Server stands for Content Delivery server which usually have core and web databases. It is
live/production server.
Luckily Sitecore has tool like Digital Marketing System (DMS) which provides all of these features under
one umbrella.
First of all, how can you check whether DMS is installed in your Sitecore instance or
not?
If you are not sure whether Sitecore DMS is configured/setup in your local Sitecore instance or not and
want to confirm it, then you can do it by visiting your ConnectionStrings.config file. If you find any entry
of Sitecore_analytics database then it means that DMS is configured in your environment.
The downloaded ZIP file will contain Sitecore.Analytics.config file and Sitecore.Analytics database.
Step-2#:
Copy downloaded Sitecore.Analytics.config file to your App_Config/Include folder.
In order to check it, visit/preview couple of pages of your Sitecore instance where you have configured
DMS and then go to Sitecore Analytics database. Check Visits table under Sitecore Analytics database,
you should found records of your visits there.
But how can you start using Sitecore DMS as you are noob?
So far, you have only configured Sitecore DMS and confirmed whether it is up and running in your local
enviroment.
Now Let's use it to get real advantage of DMS - for which it is made.
There is dedicated menu option given for DMS under Sitecore menu - Marketing Center
To work with DMS, you need to go to Marketing Center. Here you will find many options like setting
Goals, Campaigns, Engagement Plans, Personalization and many more.
Hey, someone of you may have question - what is goal? why should you create goal? So let's see why
are we going to create goal?
Suppose that you want to track visits of all people who have downloaded ProductManual PDF from your
website. This is called Goal in Sitecore DMS terminology, hence you need to create Goal under
marketing center and assign it to respective PDF (ProductManual).
Create goal
Assign goal
Track goal
Hope you are now comfortable with terminology - goal. So let's proceed further and create goal, I have
created goal named - BrochureDownload.
Please note that you must have to deploy goal in order to assign it.
If you forget to deploy goal then you will not be able to see your goal in goal list as mentioned in below
screen capture. You need to now assign this goal to ProductManual PDF, use below mentioned steps to
assign the goal.
That's it - your ProductManual PDF has goal now. So let's link this PDF to your product page and rest of
all things will be managed by Sitecore DMS.
It's time to track the goal now. Preview your page where you have linked ProductManual PDF and click
on link to download it.
This will of-course download PDF and trigger the your BrochureDownload goal that you have set and
assign to this PDF.
Again you may have question - how can you check whether my goal is triggered and achieved or not?
Yes, you have valid question. In order to confirm that, go to Analyze menu - select Reports option and
then select Page-Goals and Events report type.
You can also check all such analytics report at Executive Insight Dashboard under Sitecore menu.
If you are not able to see Goal records in reports (as shown in above figure), please make sure that you
have published that goal. Publishing goal will start showing data in Goals and Event report.
In case you are not able to view any visit data under Dashboard, that means you don't have enough visit
data. To bypass this rule, you can change default sitecore configuration to pull whatever data you have.
This can be achieved by changing MinimumVisitsFilter value from 50 to small value like 5 at:
\Website\sitecore\shell\Applications\Reports\Dashboard\Configuration.config
So we have seen one way of triggering goal, fine? Actually there are three ways of triggering goal in
Sitecore DMS. In this post, we are going to uncover remaining two ways to trigger goal.
The next thing in your mind may come - how can I check whether this query-string triggered your goal or
not? You can check it at below section: How to check whether goal is triggered or not?
Suppose you want to trigger a goal on button click, and you cannot assign goal to button from Sitecore
content editor. In such case, you can go with third option - trigger goal programmatically.
Scenario:
Your site has feature to subscribe for product newsletter, and you need to trigger goal whenever any
user subscribed for this newsletter.
Implementation:
Sitecore.Analytics API provides built-in methods to trigger your goal. Here is code that you can hook into
button_click event.
That's it!
Click on "Subscribe" button and it will trigger your "Newsletter Signup" goal. The next question in your
mind may come - how can I check whether goal is triggered or not?
Select the page on which you have added "Newsletter Subscribe" button -> go to "Analyze" menu ->
click on "Reports" -> select "Page - Goals and Events" report. You will see report having "Newsletter
Signup" goal there.
Shared: When this checkbox is selected, the field has same value for every version of item for all created
languages.
Unversioned: When this checkbox is selected, the field has the same value for every version of item
within single language. But it may have different values between languages.
Content faceting
Flexible search results
Solr search
Introduces item bucket to remove restriction of 100 child items
An item bucket is repository in the content tree that can store other content items. The difference
between an item bucket and regular container in the content tree is that an item bucket can store a
theoretically unlimited amount of items without displaying them in content tree.
If the items in bucket are hidden, a small notification tells you that there are hidden items in the
container as shown in below figure.
bc = The background color of the fill when as=0. bc=000000 is black and bc=ffffff is white.
sc = scale image. Use decimal numbers. sc=1 is the original size. sc=1.5 is 150% above normal size.
1. Remove items those have parents, but the parents are not in the item tree.
2. Remove invalid language data.
3. Remove fields for non-existing items.
4. Remove orphaned items.
5. Remove unused blob records.
6. Rebuild the Descendants table (which stores parent/child relationships).
7. Clear all caches.
You can see newly added arrowlink css class in rich text editor dropdown.
2) Programmatically:
item.Appearance.Hidden = true;
Answer: 3
http://support.sitecore.net/
Please note that you must be Sitecore certified developer having necessary credentials in order to
access Sitecore support portal.
https://marketplace.sitecore.net/
http://sdn.sitecore.net/Forum.aspx
Besides that you can also check at Sitecore knowledgebase for known issues and how-to’s.
https://kb.sitecore.net/