8

This is a known issue : https://kb.sitecore.net/articles/583017 As a workaround for the issue, please consider deleting the {Express Migration Root folder}/Migration.db file before running the migration for another source instance of the same version.


7

This message is a dictionary entry in the core database in Sitecore. Go to Sitecore Desktop, switch to core database and find the item: Path: /sitecore/system/Dictionary/F/Failed to set the password Possible reasons are 1 The old password is incorrect 2 The new p_1 ID: {098CF1DA-CF18-412A-9EE9-A82E14BA3731} Enter any Phrase value you want: I ...


6

What Mark has outlined will work. The only downside is that you'll have to compose the XML yourself, and its structure could potentially change in future versions of Sitecore (however unlikely that is). I've been trying to come up with a way of getting the XML string via Sitecore API. It seems that there is no straightforward way of doing that, but here's ...


6

First things first. The fact that you get YSOD on a malformed value is actually a bug. It is registered with Sitecore under public reference 96011. That said; internally; General Link is an XML element. For your scenario to work, you need to store your value as such. The element looks like this: <link text="Text" linktype="internal/external" ...


6

The problem could be is that you are using the following: virtualUser.Profile.SetCustomProperty("Wallpaper", "/sitecore/shell/themes/backgrounds/Field.jpg") Try to use the following: virtualUser.Profile["Wallpaper"] = "/sitecore/shell/themes/backgrounds/Field.jpg" Explanation The SetCustomProperty does not check if the user is virtual user or not, but ...


5

Here is the correct code: var user = Sitecore.Security.Accounts.User.FromName("sitecore\\test", true); RemoveRoles(user); protected void RemoveRoles(Sitecore.Security.Accounts.User user) { Sitecore.Security.Accounts.UserRoles.FromUser(user).RemoveAll(); Sitecore.Security.UserProfile profile = user.Profile; profile.IsAdministrator = false; ...


5

Yes, basically. SELECT UserID, UserName into #temp FROM aspnet_Users WHERE UserName in ('MEMBER10001','MEMBER10002','MEMBER10003','MEMBER10004','MEMBER10005') You should adjust this WHERE clause to catch the users you want, presumably on something like Created Date or so. Then DELETE FROM dbo.aspnet_Membership WHERE UserId IN (Select UserId from #temp) ...


4

I think your solution to create a new collection in mongodb is a very viable solution. Then you can just query the collection to get the top 5 pages. I would not recommend to put it in xDB as a custom facet because it would be "difficult" to get top 5 pages, as you would have to query every single contact to find the pages. Even Sitecore does not do it ...


4

I recently came across with the same situation where we have created Virtual user and also created some custom property. At the early stage it was working properly as Sitecore user works but one day suddenly it stopped working. In my solution still Sitecore.Context.User.IsAuthenticated this was always true but all the profile properties was empty at this ...


4

You can create custom profile properties for the profile in the core database. There you can even use Image field. From your code you can reach it and show on the page. How to create custom property - Link Go to core database and create your custom profile template like /sitecore/templates/System/Security/MyCustomProfile Create your custom profile from ...


4

The best practice is to have everything in Sitecore. User profile fields are stored in Core db. You can define "database" in your field source. You will define source of your field like : databasename=master&datasource=/sitecore/content/cars See also: https://sitecorecontextitem.wordpress.com/2014/02/10/working-with-custom-user-profile-fields-in-...


3

There is, but none of the ways I know of will go via the standard API. The "problem" is; while the standard API will allow you to paginate through the user base, it will not allow you to filter based on profile properties. Which, from your code, is what you need here. This leaves you with a few options. Option 1, the SQL route Turns out, even this ...


3

Additional notes for Mark Cassidy's answer that, if you change the name of the user profile field in Sitecore you can migrate these values for the changed name. So you need something like this: foreach (var user in UserManager.GetUsers()) { var oldvalue = user.Profile.GetCustomProperty("Old Fields Name"); user.Profile.SetCustomProperty("New Fields ...


3

Another way to do this would be from User Manager, by leveraging the serialization feature. For this to work, you need direct access to the server. Click on "Serialize All Users". Go to your security serialization folder (by default: data/serialization/security). Users will be organized by domain. If all offending users are part of the same domain, it ...


3

Sitecore jobs is the best option in such case, but you can use them in different ways. Best approach for using them may vary by business requirements, like frequency of user logins and the time frame in which you want to update profiles. Below are some approaches - Once the user is logged in, create a job to update that user's profile data. In case ...


3

To make this work you need to follow these 5 steps: Create your own GeneratePassword() method.It should do exactly the same as System.Web.Security.SqlMembershipProvider.GeneratePassword(), but instead of using modulo 87, it should use your custom logic to generate valid passwords. Create your own SqlMembershipProvider and let it inherit from System.Web....


2

Can you try bellow solution : 1)Copy the attached Sitecore.Support.350672 file to the bin folder 2)Open the Website\sitecore\shell\Applications\Security\EditUser\EditUser.xaml.xml file and implement the below change: Comment <Sitecore.Shell.Applications.Security.EditUser Application="Security/Edit User" x:inherits="Sitecore.Shell.Applications....


2

You can use MongoDB to achieve what you need. Just create a custom facet (Sitecore documentation: Create a custom contact facet) and store the information whether user chose to never show the message again inside the facet. That will make sure you can access this information every time user logs in again, even if they use different browser. And yes, you ...


2

You can use Sitecore PowerShell Extensions to extract the custom properties. The data is stored in the Core database. $user = Get-User -Id "sitecore\michael" $data = @{} foreach($name in $user.Profile.GetCustomPropertyNames()) { $data[$name] = $user.Profile.GetCustomProperty($name) } $data | ConvertTo-Json


2

As you have specified in your comment, clearing the cache from the cache.aspx page, fixed the issue. The reason why even clearing the cache from the code is not working is because the Context.Site is not the correct one. The Context.Site at this point is equal to login. You should clear the cache for the shell. namespace CustomLogin { public class ...


2

Because a Security Profile Item in "core" is not a Schema And you're going about it wrong. To reach the "schema" for a user If you want to read all available fields defined for your user, you will have to refer to the definition you have defined for your user, which would be the Sitecore Security Profile. And essentially it would involve ...


2

User profile fields are not Sitecore.Data.Field. What you define in the custom profile is merely a mapping so that Sitecore can provide a basic UI for the user, such as this. Behind the scenes, these profile fields are used with the standard ASP.NET ProfileProvider - and this uses the profile name as key. Which means you cannot rename these, and expect to ...


2

Since membership data is stored in the core database and you have separate core databases between CM and CD, it's likely that the CDs' core does not contain the role memberships you expect. You will need to either: Share a core database between CM and CD or Configure replication of the core database between CM and CD For more information, consult the ...


2

Context.User.Profile Custom properties from Context.User.Profile are stored together with user profiles. It may vary between Sitecore versions where this data is stored and how it's accessed but in general they sit together with other aspnet membership provider data in core database in aspnet_Profile table. So whenever you call `Context.User.Profile....


2

From core database are indexed just items. Sitecore users are stored in the memberhip table which doesn't appear like items on Core db. You need to create your own crawler and your own index to index the users. On this blogpost is explained how to do it : https://nourestani.wordpress.com/2013/11/11/sitecore-lucene-net-how-to-index-users-and-profiles-from-...


1

Hi @Marek thank you it works fine, I don't know why the first time I didn't seen my changes. Just notice that for me it's not the same GUID {5BB66CB4-F2BC-E08E-9563-28194D5C9779} For adding a new user with User Manger if you want to change the password error message located here "/sitecore/system/Dictionary/T/The password is invalid"


1

Code that you posted is for setting custom property on default user object in Sitecore not for Sitecore CommerceUser / profile object. There is not much documentation on how to extend Sitecore CommerceUser in 8.2.1. You need to do it in Commerce Server Manager. You need to extend UserObject under Profile node and also make some SQL changes. This walk-...


1

This requires you to debug through the whole Sitecore--> xDB --> Aggregation pipeline--> reporting databases --> Sitecore_Analytics_Index. Please ensure the below: CD is recording the interactions correctly in xDB- MongoDB. CM / Processing server is picking up the interactions to be processed/aggregated Your Aggregation processors are not throwing any ...


1

To answer your related question, if a person visits the same page multiple times during a visit, each time should count as a separate hit to that page and be included in the calculation in that manner.


1

So I found that this was connected to a new config file that came with my upgrade to this version. /App_Config/Include/Sitecore.DefaultLanguage.config. I thought this was related to the AD since it worked in the past. I already had changes done to the sitecore.config for ContentLanguage Language ClientLanguage This was overwritten by the Sitecore....


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