Each item has publish info. You can use:
PublishInfoData publishInfoData = CoreServiceConnector.Client.GetListPublishInfo(item);
PublishInfoData class has the property PublishedAt, so you can filter there all for the last 24 hours.
So you can list every item in Tridion, get its published info, and then see if it was published somewhere in the last 24 ...
After Investigating the elastic search logs (path: c:\elasticsearch-7.7.0\logs\elasticsearch-service-x64-stderr.YYYY-MM-dd)
Error "the system property [es.path.conf] must be set" when starting the service registered
Refer to the link for the fix
The fix provided here [#57769] doesn't help since the culprit is not the same variable, I ...
It is in Tridion.ExternalContentLibrary.V2 dll.
public static class SessionFactory
public static IEclSession CreateEclSession(Session tcmSession);
public static IEclSession CreateEclSession(string username);
No. Minor version translation deals with source item being in workflow.
Review functionality works with workflow on target item.
All you need for Review functionality is workflow on target items, that supports Translation Manager Review. And appropriate workflow steps on TMS or WS.
Indeed only one metadata schema allowed per BluePrint hierarchy.
BluePrint hierarchy in this case means standalone tree.
You can change metadata using event system
By subscribing to "Item Send" event:
EventSystem.Subscribe<ITranslationJob, IItemSendEventArgs>(OnItemSend, EventPhases.Initiated, EventSubscriptionOrder.Normal)...
When I've set Translation Review up in the past the AllowTranslateDynamicContent setting was not enabled (so left commented out in the TranslationManager.xml file as per default) and Translation Review worked as expected.
<!-- Enable translation of minor versions. -->
<!-- <AllowTranslateDynamicContent>true</AllowTranslateDynamicContent> ...
Customer should use Event System approach.
Old Translation Manager Plugin system is deprecated for many years.
I think the documentation needs updating. Looking in the Installation Media, theres now an EventHandlers folder with a ErrorEmailNotifications.cs file which using the Event System and not the old plug-in approach.
public class ErrorEmailNotifications : TcmExtension
Complimenting Marko's answer on the Event System, you could also look at extending Tridion CM search to store such information within the SOLR index as well. This way you can leverage existing infra and benefit from SOLR's powerful querying which can be executed via Core Service.
See Arjen's post: http://80000ft.blogspot.com/2012/08/search-indexing-handlers....
Another option, which might be a better one regarding performance would be to create Event System that would for each successful transaction send Transaction data to some custom storage (to some DB, or service). Then you can query that service periodically.
It would give you flexibility where you would not check all items in Tridion for their publish info, ...