AFAIK: It's not possible to extend Keyword description field size it's tied with Database ITEM table Description field size, currently, it's designed to allow 255 characters only.
If you're looking to keep bigger description content on a keyword level. you could create a metadata schema with a custom description field as a text field or RTF field depends on ...
it does get stored on DB from SDL 8.6. you can find the details [APP_DATA] table CM Database.
You can use the following code to read the value using core service:
var client = CMSession.GetInstance().CoreServiceClient;
var appData = client.ReadApplicationData(null, APPDATA_CUSTOMPAGES_ID);
if (appData != null)
var ada = new ApplicationDataAdapter(...
After playing with install scripts, I was finally able to install services with domain URL containing context path. To help others with similar requirement, I am writing the steps to install service with a custom URL:
When services are installed as a window service:
Following changes required in installService.ps1
-Add spring boot variables to pass as a ...
It's true - you can't extend it as per Velmurugan states.
I can't suggest an alternative for your web app purposes as it's not clear what you're using the description for but I would add:
If you translate keywords the translation will not be imported if the translated value is over 255 characters; so 'fixing' this with a GUI extension may not suffice.
Besides everything Dylan and Velu stated which is all true, I would like to ask why are you trying to store more than 256 characters in keyword description? Taxonomies are meant to be used to tag/classify content, not to be content themselves. Just like tags on social networks :) they should describe your content, not be content. If you have keywords that ...
To clarify to understand correctly.
For content service caching invalidation, you need to use Amazon ActiveMQ, not AmazonSQS.
To setup a scaled-out Content Deployer worker, you could use Apache ActiveMQ or AmazonSQS.
Answer to your question.
For Amazon MQ Setup- Step 1 Configure Basic Broker Settings refer to amazon documentation.
For example, when ...
Welcome to Tridion stack exchange, Error message Indeed!, When you get this kind of errors, it's due to that the DD4T version you are trying to install or use is built against a different version of the Tridion.ContentDelivery DLL.
You need to ensure that your DD4T solution rebuild with the right Tridion DLLs version since you updated your web.config to ...
AFAIK - Yes, you can increase your database connection pool size since you have a high load. You will need to make sure your database can support the number of connections and allowed by your database.
Try with this below settings on your cd_storage.config
<Pool Type="jdbc" Size="30" MonitorInterval="60" IdleTimeout="120" CheckoutTimeout="120" ...
Try the following steps to fix your issue.
Go to SDL Tridion Sites 8.5 Installation Media folder
Navigate to this path: \Content Delivery\roles\deployer\deployer-combined\standalone\services\deployer-common\ and copy the file cd_datalayer-8.5.0-1014.jar to your local path folder for example c:\temp
Open cmd as administrator and go to c:\temp and run the ...
Indeed. Anand already answered how to see the custom pages details using Coreservice API.
As @Anand/Peter already mentioned in his comment to clarify how to get the custom page XML using API, because in database it's store as Encoded XML Fragment.
It looks like you are still looking at the database level to see that data not using Coreservice API.
We were actually able to resolve the issues by creating custom indexes on the broker database. We ran query tests to see what queries were taking longer and added the recommended indexes. That improved the performance from 50sec to 3sec.