11

The admin page in the latest Sitecore version has what you are looking for. Go to /sitecore/admin for the admin overview or directly to /sitecore/admin/Jobs.aspx It will display like this: Not sure if it does exactly the same as Rocks but it's a start.


11

I was unable to find the culprit using Vlad's method, so I went down another path. I installed the Sitecore PowerShell Extensions Module and modified one of the built-in scripts - the "Broken Links Report" under /Content Reports/Reports/Content Audit. I added a Try { } Catch { } as follows: Try { $brokenLinks = $item.Links.GetBrokenLinks($...


9

An often overlooked benefit of it, is it's capability to browse any Sitecore Item structure. While obvious, many people don't consider that an Item needs to inherit a lot of fields/base templates for the Content Editor to be able to navigate them properly. Security, Workflow, Item Statistics and so on. The DBBrowser tool needs none of that. It just allows ...


9

In Sitecore 8.2.1 the GeneralLink field allows to contain links with empty "id" attribute like : <link text="Description" linktype="internal" class="" title="HomeAlt" target="" querystring="" id="" /> But in Sitecore 8.2.6 it does not allow you to have such links. Based on this the check for null or empty value is not needed because this situation ...


8

There is no general rule that tells Sitecore to force user to login when they access /sitecore/admin/* url. However most of the pages there (or maybe all) inherits from the Sitecore.sitecore.admin.AdminPage class and they check if user is administrator (Context.User.IsAdministrator). Here is part of the AdminPage class code: protected void CheckSecurity() ...


6

Quick note for anyone who may stumble upon this like I did. After experiencing this issue myself on 8.2.6 (and not having any luck with the other solutions listed here), I submitted a ticket with Sitecore Support and they informed me that this is a known bug: For your latest exception when rebuild link database, it was identified this issue as a bug. To ...


6

I wasnt extending the adminpage base class. My script tag should have read like this: <%@ Page Language="c#" Inherits="Sitecore.sitecore.admin.AdminPage" %> There a good writeup and example page in this post on BrainJocks.


6

A quick way to browse through the separate Sitecore databases. It is pretty lightweight and supports previewing of item’s fields, versions, languages etc. The DB Browser also allows preview of the file system.


5

It is also usefull in situations when Content Editor does not work because of broken item. You can use dbbrowser.aspx to navigate to that item and


5

In Sitecore all admin pages are aspx pages. You need to create your own aspx page to create your custom admin page. To add to the list of admin pages you need to override : c:\inetpub\wwwroot\yourlocalfolder\sitecore\admin\default.aspx page Codebehind for this page is in class: Sitecore.ExperienceContentManagement.Administration.Default You have to ...


5

Here is a complete script to detect all those errors: Add-Type -AssemblyName Sitecore.Kernel function Resolve-Error ($ErrorRecord=$Error[0]) { $ErrorRecord | Format-List * -Force $ErrorRecord.InvocationInfo |Format-List * $Exception = $ErrorRecord.Exception for ($i = 0; $Exception; $i++, ($Exception = $Exception.InnerException)) { "$i" * ...


5

This issue is related to the 'Caching.DisableCacheSizeLimits' setting in the web.config file. When set to true, Sitecore ignores any maximum cache sizes specified in the web.config file. Please change the value to "false" like bellow : <setting name="Caching.DisableCacheSizeLimits" value="false"/>


4

The boolean for the CheckSecurity method will specify whether or not to allow users of the Developer role access (or not). If 'false' (as shown) only admin users can get through. I also recommend that you place this physically inside the /sitecore/admin folder to take advantage of any hardening you might have configured on your servers to prevent access to ...


4

If Sitecore is telling you ItemNotFound, then it's trying to resolve your request to a content item. Being your admin page is a physical file, the issue is most likely that you've not included the file extension in the request. For example, to access the ShowConfig admin page I must include the aspx extension of the file when I request it: http://mysite/...


4

You can use from code: ItemLink[] itemLinks = Globals.LinkDatabase.GetReferrers(item); Or from Content Editor you can use Link ribbon button from Navigate tab:


3

Is it possible with the use of Identity Server at the /sitecore/ path is not included in one that is authenticated with IS? Consider this file Sitecore.Owin.Authentication.IdentityServer.config at the very end there is a section indicating which paths are authenticated. <sites> <site name="shell" set:loginPage="$(loginPath)shell/...


3

Maybe I am not reading into this right. But you can set denial permissions on the items on the menu items under the path /sitecore/content/Applications/Control Panel/ in the core database. I would prefer you create a user role and set the denial access to that role. Then adding users to the new role will be easier and cleaner to maintain.


2

Here you go, sample code snippet for that: <%@ Page Language="c#" EnableEventValidation="false" AutoEventWireup="true" %> <script runat="server"> void Page_Load(object sender, System.EventArgs e) { repValues.DataBind(); } public IEnumerable<string> Names { get { return new[] { "1", "...


2

This should be pretty much all you need, less the ASPX that inherits that class, and with the added caveat that this solution will only work for users that are either administrators or have the 'Developer' role. Note that you will likely still want to follow the Security Hardening best practices and move your "admin page" into the <webroot>/sitecore/...


2

Usually, you can create an item (or a whole structure) in your content tree for admin pages as well. You get: Item permissions to manage access to various admin pages You can store settings/configurations on these items Get versioning/workflow for these data Utilize the rendering pipeline of Sitecore Unless you have very unique requirements, I don't think ...


2

I believe your redirect is incorrect. From what I can tell, your rewrite rule above is just forcing HTTPS if somebody accesses the sitecore url, it isn't actually blocking it. My memory is fuzzy on the regex stuff for rewrites, but it looks like this is looking for an HTTP call only (HTTPS pattern is OFF). Since your first rule matches against all URLs with ...


2

You should use Sitecore.StringUtil.EscapeJavascriptString on the parameter values, which (besides escaping) adds surrounding quotes. Without the quotes, the parsing goes wrong and you end up with this error. args.UiResponseHandlerEx.FileCannotBeUploaded( StringUtil.EscapeJavascriptString(fileName), StringUtil.EscapeJavascriptString(reason));


2

The Package Item tools can be used to generate packages of items with their dependencies. Unlike the Package Designer wizard accessible from through the Desktop though, the UI here is much more limited but the tool will package the dependencies of an item as well: all item references, presentation items if you’re using Webforms, custom assemblies, workflow ...


1

If you have the pageItem which is an instance of Sitecore.Data.Items.Item class, you can wrap your code into a DatabaseSwitcher and DeviceSwitcher using (new DatabaseSwitcher(pageItem.Database)) { using (new DeviceSwitcher(pageItem.Database.Resources.Devices.GetAll().Where(t=>t.Name.Equals("default",System....


1

Based on my investigation, the statistics of the rendering is added during the execution of the <mvc.renderRendering> pipeline. The method RecordStatistic is called at the end. So, for every rendering being rendered on the page, Sitecore is adding the statistics so duplicate should not be present. However, what may happened is that if you have 2 ...


1

You can use Link Database via GetReferrers method. e.g. var links = Globals.LinkDatabase.GetReferrers(item); if (links == null) return new Item[0]; var linkedItems = links.Select(i => i.GetSourceItem()).Where(i => i != null);


1

To bypass this annoying redirect, instead of typing /sitecore I just type /sitecore/login and keep moving. The last time this happened I decided to investigate a little bit more the cookies involved in the issue and realized that by deleting the cookie sitecore_userticket the bug stop happening. Using those two strategies I can get rid of the weird issue ...


1

Sitecore does not offer a Spanish language pack for the Sitecore client. Only the following are available:


1

By some experiments (comparing assemblies on PRC and CM roles, disabling different commands, ...) I have realized that the issue is caused by marketingtaxonomy:deploy command from the Sitecore.Marketing.Client.config file. Simply, if I disable it, the UI is working properly. Unfortunately, the root cause is not understandable still. Hopefully, I'll have ...


1

I doubt this has anything to do with your admin user. You say the host name has been changed. Likely you have a <site> definition for your site that sits in a wrong place in the order of sites that serve up Sitecore. <sites> <site name="shell" virtualFolder="/sitecore/shell" physicalFolder="/sitecore/shell" rootPath="/sitecore/content" ...


Only top voted, non community-wiki answers of a minimum length are eligible