Encoding problems are almost always about telling lies, albeit sometimes lies of omission. What I mean by this is that when sending data, you do three things:
Transform your data into a stream of bytes using an encoding,
Transmit the stream of bytes.
Tell your client what encoding needs to be used to interpret the bytes.
Sometimes you don't actually ...
From your question it seems that you probably do not have the background of the application. The Content Hub is no term in the SDL Tridion and must be related to the project (I probably know which project is this). If it is told to you that the data is being fetched from the SOLR, it means it is not the Tridion's SOLR but must be a separate implementation - ...
tl;dr to Dominic Cronin's answer, encoding issues in SDL Tridion are always an issue of some system down the publishing/deployment line not being correctly configured.
Read Elena Serghie's blog post 7 Clues to Solve Character Encoding Issues for more details. My initial guess on what is wrong, will be the Deployer JVM settings (as these are by default not ...
The culprit was Sync-TcmSearchIndex. It was scheduled to run every evening.
This was resulting in a huge Search Queue (items or be indexed) and an ever churning search index
Sync-TcmSearchIndex is now disabled, and will only be ran as required e.g. out of date search index due to environment sync
To remove items from the queue, you can run Remove-...
My understanding of SI4T is that the index data is appended as comment in the rendering phase to the rendered (Page) output, and on the CD side, this is (from a storage extension):
Sent to indexing to Solr (or some other system)
Stripped from the received output and persisted without it into the Content Data Store (Broker or filesystem).
Having this in ...
When you say that you're planning to integrate Solr with Tridion, presumably you mean that you want to use the Solr functionality on your published website(s)?
If that's correct, then that is quite a common requirement and you should take a look at the SI4T (Search Integration 4 Tridion) project, where most of the hard work has already been done for you.
Please refer to the link on how to add a custom field on solr and implement Search Indexing Handler and add it to the content manager configuration.
In your case
<field name="Link_URL_dyn_s_str" type="text" indexed="true" stored="false"/>
Not sure what is your requirement to add the field Link_URL to solr, you ...
That is weird. The baseModelType is obtained from the View Model Registry (the MVC data of the CT is resolved to a View Model Type), but is not expected to ever be null; in case the View Model Type cannot be resolved, an exception should be thrown.
I notice that you seem to be using a custom build of Sdl.Web.Common. Have you made any changes?
Since you are ...
It turns out that the Deployer was the guilty party. Updating the JVM settings is what fixed it. More information on this can be found here:
Tridion 2013 SP1 DD4T SOLR index arabic character encoding issue
It seems like you have not given the command correctly. The command on slave needs master server with port (the port was missing in your command)
configure-search-host.ps1 slave masterserver:8983 domain\user password
This could be a probable reason. Also, for communication across servers on the port, FW should be open
Do you mean DXA 1.1 or DD4T 1.1? In either case, if the body field is not being searched, it sounds like your SOLR configuration is not correct. The body field should be the default search field I guess...
I am not sure what the suppress from search thing you are talking about is? In DXA/SI4T there is a metadata field to prevent the page being indexed - but ...
Since this is an implementation question, reaching out to Customer Support won't help you much.
You might want to take a look at http://si4t.github.io/ which contains a nice framework for integrating Tridion with Search engines and a ready-made Solr indexer that you can use.
For Razor and Dreamweaver Templating you might need to make some changes, SI4T was ...
Alternatively, you can create the "Search Indexing TBB Parameters" Schema instead of "Search Indexing Metadata" Schema and then Link it with "Generate Index Data" TBB as Parameters Schema.
Example TBB Parameters Schema
In the Page Template while Adding the Generate Index Data TBB select and provide the Including/Excluding individual component fields ...
we have implemented a search master which replicates the index to 2 slave servers. If you have multiple CME machines, you have to do something like this or you will have the inconsistencies for the search index. It's a single search queue. the first CME to pick up the record would index it and keep it in its local index, the others wouldn't have it. so you'd ...
You have two choices:
Get the XML data into Solr without passing it through the CMS. In this case SI4T no longer plays a role (even the indexer would not be particularly helpful as a code example as it is Java and not .NET) your question becomes something for a Solr forum and doesnt really belong here.
Read the XML data as part of the publishing process ...
if you want to query from the solr admin Tridion CME (e.g. http://my.tridion:8983) (or) http://my.tridion:8983/#/tridion You will get a prompt for a username and password. The “MTSUser” (Tridion’s system user) and select the collection and click on query to see the results refer link
All Results - Link
Only Title - Link
You can do the same for ...
From Tridion's perspective, the following points are relevant:
What "type" is your website application, the tag
says DXA, is this correct?
Are you using Solr for your website search?
If yes, how are you populating Solr?
But even then, this doesn't look like a Tridion specific question per se. I suggest you take a look at the following article on how to ...
SI4T based SOLR search integration framework already has the option to restrict indexing of binaries by file extension.
You can configure DocExtensions="pdf,docx,doc,xls,xlsx,pptx,ppt" in cd_storage.xml
<Indexer Class="org.si4t.solr.SolrIndexer" DefaultCoreUrl="http://localhost:8080/solr/staging" Mode="http"...
So far great answers already for SI4T Solr integrations references.
I understand based on your comments, you are looking for specific 8.5 Solr jars files for your deployer-combined service.
Download SI4T source Extract the source and modify pom.xml for Tridion version 8.5 and build against 8.5 dependencies and copy all the dependencies and si4t-se-1.2.jar ...
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 ...
You can approach Reindexing Search Queue in another manner. As following documentation states, you can execute reindex PER Publication.
That being said, you can schedule every publication separately at certain intervals to decrease total number of messages. The number of process items will still be the same, only difference is that it will be evenly spread ...
Adding some logging revealed ~1 in every 10 dates having strange values.
Removing static final from the DATE_FORMAT variable fixed the issue so it seems my diagnosis was correct.
Not strictly a Tridion problem rather a Java threading one.
As Warner suggested, the inconsistencies that you are seeing seems to be because of Search setup issues.
In case of multiple CM servers, you have setup master / slave search servers. You can refer to following link for that: Outscaled Search Setup
There is an automatic replication which happens from the master servers to the slave servers whenever an item ...
With 2013 SP1, CME search works for components when using name as the search criteria (irrespective of whether there is "/" in the component name or not). As long as solr implementation hasn't changed on the backend between Tridion versions (2011 and 2013) it should work the same way in 2011 as well. Like with the example that you have provided, you can ...