Skip to content

Commit

Permalink
Grammar check updates for blogpost 2024-01-15-Sitecore-10-problems-an…
Browse files Browse the repository at this point in the history 
…d-solutions
  • Loading branch information
Tutku Can Yalcin committed Jan 10, 2024
1 parent b37b06c commit d0037f2
Showing 1 changed file with 29 additions and 28 deletions.
57 changes: 29 additions & 28 deletions docs/_posts/2024-01-15-sitecore-10-upgrade-problems-and-solutions.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -14,18 +14,18 @@ author: tcanyalcin
![alt text](../files/2024/01/15/sitecore-10.png "Sitecore 10")


After upgrading from Sitecore 9.1 to Sitecore 10.3 like many people, we faced with bugs and some features stopped working for us. In this post I will try to list some of them and explain how we fixed them.
After upgrading from Sitecore 9.1 to Sitecore 10.3 like many people, we faced bugs and some features stopped working for us. In this post, I will try to list some of them and explain how we fixed them.

## Problem: Sitecore forms list fields stopped showing values of list items on local languages
## Problem: Sitecore forms list fields stopped showing values of list items in local languages

We use local languages and they have fallback to main languages. Such as; en-gb to en, de-de to de.
We use local languages and they have a fallback to the main languages. Such as; en-gb to en, de-de to de.

We realized after the upgrade, any field that is based on list fields started showing item names on these local languages instead of translated ones for them. So we opened a ticket to Sitecore Support and ask for a solution. Sitecore Support registered this behavior as a bug in their bug tracking system and gave us a reference number 602361 for tracking.
We realized after the upgrade, that any field that is based on list fields started showing item names on these local languages instead of translated ones for them. So we opened a ticket to Sitecore Support and asked for a solution. Sitecore Support registered this behavior as a bug in their bug-tracking system and gave us a reference number 602361 for tracking.

## Solution
As a workaround they suggested either not use fallback mechanism on form fields and create versions on local languages or use ListDataSourceProvider from Sitecore 9.
As a workaround, they suggested either not using a fallback mechanism on form fields and creating versions on local languages or using ListDataSourceProvider from Sitecore 9.

We went with second option as we had many forms on many languages. So we patched Sitecore 9 ListDataSourceProvider over Sitecore 10:
We went with the second option as we had many forms in many languages. So we patched Sitecore 9 ListDataSourceProvider over Sitecore 10:

{% highlight csharp %}
public class ListDataSourceProvider : IListDataSourceProvider
Expand Down Expand Up @@ -90,91 +90,92 @@ public class ListDataSourceProvider : IListDataSourceProvider

{% endhighlight %}

## Similar Problem: Form submissions not working on local languages
On our website, we use custom submit actions to make API requests. These API requests rely on datasource items selected on Sitecore. After some testing, we realized that some fields on these datasource items have empty values sent to API even though they were filled on main languages on Sitecore. So Sitecore was not able to fill these values that are supposed to come from fallback language.
## Similar Problem: Form submissions not working in local languages
On our website, we use custom submit actions to make API requests. These API requests rely on data source items selected on Sitecore. After testing, we realized that some fields on these data source items have empty values sent to API even though they were filled on the main languages on Sitecore. So Sitecore could not fill these values that are supposed to come from fallback language.

## Solution

After opening another Sitecore support ticket, we realized that Enable item language fallback and Enable field language fallback checkboxes were not checked on site items. In Sitecore 9 version, there was no checkbox and we were using Other Properties field. That's why the problem occurred. You can check the following documentation from Sitecore here
After opening another Sitecore support ticket, we realized that Enable item language fallback and Enable field language fallback checkboxes were not checked on site items. In the Sitecore 9 version, there was no checkbox and we were using the Other Properties field. That’s why the problem occurred. You can check the following documentation from Sitecore here
[link](https://doc.sitecore.com/xp/en/developers/sxa/103/sitecore-experience-accelerator/enable-language-fallback-for-sxa-sites.html)


For these 2 problems thank you for your support Arun Tiwari..
For these 2 problems thank you for your support, Arun Tiwari...

## Problem: Form field classes not rendered

After the upgrade, all of our forms were not showing css classes. Since they are added to the project for custom implementations, they were not changed by upgrade automatically.
After the upgrade, all of our forms were not showing CSS classes. Since they are added to the project for custom implementations, they were not changed by upgrade automatically.

## Solution
In Sitecore 9, Model.CssClass for fields and Model.LabelCssClass for labels were used. These properties become obsolete in Sitecore, so we needed to use Model.CssClassSettings.CssClass and Model.LabelCssClassSettings.CssClass respectively. After these changes, forms were rendering css classes again.

In Sitecore 9, *Model.CssClass* for fields and *Model.LabelCssClass* for labels was used. These properties become obsolete in Sitecore, so we needed to use *Model.CssClassSettings.CssClass* and *Model.LabelCssClassSettings.CssClass* respectively. After these changes, forms were rendering CSS classes again.

## Similar Problem: Forms Editor not showing Styling section on custom form fields

In Sitecore 10, there was another change for each form field on core database. Sitecore started using new CssClass and LabelCssClass items on Styling item:
In Sitecore 10, there was another change for each form field on the core database. Sitecore started using new CssClass and LabelCssClass items on Styling item:

![alt text](../files/2024/01/15/sitecore-10-styling-item-image.png "Sitecore 10 styling item")

## Solution

Even though item names are same, there are different items selected in Sitecore 10. You can put the following ids on ControlDefinitions field on Sitecore for each of these custom fields, then we will be able to see css classes on Sitecore Forms Editor:
Even though item names are the same, there are different items selected in Sitecore 10. You can put the following IDs on the ControlDefinitions field on Sitecore for each of these custom fields, then we will be able to see CSS classes on Sitecore Forms Editor:

{% highlight ruby %}
{98FB361E-3A7F-49F9–8789–8C169FB95B61}|{121B9875–2F7D-4D62-BD0F-35A7B909ECE8}
{% endhighlight %}


## Problem: Missing field values after Glass mapper upgrade
## Problem: Missing field values after Glass Mapper upgrade

After the upgrade, we realized there were many field values not showing on website. All of these fields had one thing in common. Their properties did not have setters on class entities. But all of them were working fine before the upgrade.
After the upgrade, we realized there were many field values not showing on the website. All of these fields had one thing in common. Their properties did not have setters on class entities. But all of them were working fine before the upgrade.

## Solution

We searched on glass mapper release documentation and found this one:
We searched on Glass Mapper release documentation and found this one:
[glass mapper](http://www.glass.lu/Mapper/Releases.html) on version 5.3.17 which mentions:

>ISSUE 370 The lazy object inceptor will now ignore class properties that don't have a setter or have the SitecoreIgnore attribute.
So, after upgrading glass mapper, checking if every property mapped with glass mapper has a setter is crucial. Especially, if you use them for API calls or search functionality.
So, after upgrading the Glass Mapper, checking if every property mapped with the Glass Mapper has a setter is crucial. Especially, if you use them for API calls or search functionality.

## Problem: Custom Powershell scripts on Toolbar not working

In our project, we used powershell scripts to bulk edit workflow state, copy item version, reset field value and many more. We created these scripts and added them to Toolbar so our customer can use it too. But after the upgrade to Sitecore 10, we have seen that all of them were not clickable, showing just script names and blank icons.
In our project, we used Powershell scripts to bulk edit workflow state, copy item version, reset field value, and many more. We created these scripts and added them to the Toolbar so our customers can use them too. But after upgrading to Sitecore 10, we saw that all of them were not clickable, showing just script names and blank icons.

## Solution

After some investigation, we decided to rebuild all scripts on Powershell ISE. This rebuild created some changes on items. But mainly on items that represent each script on core database had a different type now:
After some investigation, we rebuilt all Powershell ISE scripts. This rebuild created some changes on items. But mainly on items that represent each script on the core database had a different type now:

>Spe.Client.Controls.ContentEditorRibbonPanel,Spe
*Before* they had the following value on type field:
*Before* they had the following value on the type field:

>Cognifide.PowerShell.Client.Controls.ContentEditorRibbonPanel,Cognifide.PowerShell
So after we start using the updated type, scripts become clickable and icons are showing again.

## Problem: Fast Queries Not Supported

Fast queries are depricated in Sitecore 10. It's suggested to use search index. In our case, we were using fast query to reach a setting item.
Fast queries are deprecated in Sitecore 10. It's suggested to use a search index. In our case, we used a fast query to reach a setting item.

## Solution

We developed a custom SettingProvider and started using it instead of queries or search indexes.

## Problem: System.OutOfMemory Exception

After we switched to Sitecore 10 and started using the databases from production system, many developers in team experienced this exception.
After we switched to Sitecore 10 and started using the databases from the production system, many developers in the team experienced this exception.

Either cm was unhealty or after some time it was becoming unhealty. When we check logs on docker or inspect container, we would always see this error popping up. Also, Sitecore system was too slow to work on.
Either cm was unhealthy, or after some time it was becoming unhealthy. When we check logs on the docker or inspect container, we would always see this error popping up. Also, the Sitecore system needed to be faster to work on.

## Solution

We first checked how much which container consumes when docker is started with following command:
We first checked how much each container consumes when docker is started with the following command:

>docker stats
Thanks to this command, we were able to see SQL server is using way more than usual. We have seen values like 10–20 GB. We tried changing mem-limit for each container to find the combination that works but that was barely enough. Sitecore was again too slow to work. We also tried deleting the whole data on preview database, since it was not needed on our locals, but that was also not enough.
Thanks to this command, we could see that the SQL server is using way more than usual. We have seen values like 10–20 GB. We tried changing the mem-limit for each container to find the combination that works but that was barely enough. Sitecore was again too slow. We also tried deleting the whole data on the preview database, since it was not needed on our locals, but that was also not enough.

Then we realized something golden. EventQueue and PublishQueue tables in master, web db had over 405k entries on them. So we started a cleanup using the following sql:
Then we realized something golden. EventQueue and PublishQueue tables in the master, web db had over 405k entries on them. So we started a cleanup using the following SQL:

{% highlight sql %}
USE [Sitecore.Core]
Expand All @@ -188,6 +189,6 @@ DELETE FROM dbo.EventQueue
DELETE FROM dbo.PublishQueue
{% endhighlight %}

After this cleanup docker become really fast, we got rid of the exception.
After this cleanup docker became fast, and we got rid of the exception.

Thanks to Fabian Geiger and Ramazan Yilmaz for their support..

0 comments on commit d0037f2

Please sign in to comment.