The thing is that you should have new component Xml set to the component before you can save it. Imagine you have a schema with default values associated with folder where this component (will)resides.
You should create component (UI side, just like you did) then load it (it will load xml of created item) and only then do save.
increment = 0;
In your screenshot, notice how the "Content" attribute is null. For each component, you need to call:
ComponentData component = (ComponentData)coreServiceClient.Read(
componentTcmId, new ReadOptions());
Now you can parse the component.Content to read the field values.
By the way, if you happen to have metadata fields as ...
Those characters are also used for the "Shellshock bug" (a Bash vulnerability discovered recently) that is currently all the rage.
It's possible that a security update outside of Tridion (firewall, Windows Update, anti-virus, etc.) is preventing the request from going through. Check all your logs!
The solution to this problem is to restart (or start) Tcm Batch Processor process. This process is in charge of executing batch jobs, like copying or deleting multiple items at once. If this error happens again, you should check logs and contact customer support to investigate the issue further.
There are a number of reasons why you can't delete a Component, for example: it could be used by some other items, it is published, checked-out, the deletion is not attempted from the owning publication etc.
But... the grayed out appearance leads me to believe that the Component has entered a Worflow. Did you attach a Workflow to the Schema?
For each component
From the component determine the publication
For each publication target
From the publication target determine the publication bindings
If publication in publication bindings component can be published to this target (if not the component cannot be published to this target)
You can get the ...
You don't have to use Search for this. A where used query will also work, and might be the better choice. Here's a powershell snippet to illustrate how you might do this:
$core = Get-TridionCoreServiceClient
$filter = new-object Tridion.ContentManager.CoreService.Client.UsingItemsFilterData
$filter.ItemTypes = "Component"
$components = $core.GetList("tcm:...
Lots of users including me facing issue with mentioned version of chrome.
Hot Fixes available now. Login to SDL Tridion World required before downloading.
SDL Tridion 2011 SP1 HR2: Hotfix CME_2011.1.2.1673
SDL Tridion 2013 SP1 HR1: Hotfix CME_2013.1.1.1673 (Updated version available now)
I've found a solution (without tridion).
I've added another scheme to the template which was rendered with the component I tried to delete, then I unpulbished the component again and this time it also unpublished to rendered with thing which let me delete the component.
Then I had to unpbulish the template with the extra scheme > remove the scheme and ...
SDL Tridion doesn't provide a method to bulk-load components. When loading items from an OrganizationalItem (like a folder) you can use .GetItems which will load all the objects, but under the hood it's still hitting the database for each individual items anyway.
In other words, that's the way it (currently) is.
You can set the default location in CME. It is an out of the box feature, please look at the screenshot below. Once you set a start location, the next time you open the CME, you will directly come to this location without any clicks! Also I want to suggest careful use of virtual folders since it executes a search query everytime you click on the folder and ...
In your deployer Role, try updating the value to dotnet in following property
<Property Name="tcdl.target.language" Value="dotnet" /> in the cd_deployer_conf.xml file
Restart the deployer services and unpublish the page once and publish it again to see whether it helps to generate the tags<tcdl:ComponentPresentation type="dynamic" ComponentURI="...
The issue was with how I was creating the new components. When selecting a schema for a new component I was opening the schema dropdown and typing the letter "i" to get to the schema I wanted (instead of scrolling). This was selecting a different schema first (since my desired schema was not the first "i" in the list) and loading the fields for it. Then I ...
Another option would be to use Event System on Page Save and interrupt the saving if the Page Template <-> Component Template combination is not allowed. You can throw an exception with a meaningful message informing the Editors that what they're trying to achieve is not permitted.
The advantage of this approach is that you handle your specific case ...
As your query uses the underlying Tridion search functionality, it is processed using the standard Solr request handler.
In the [Tridion Home]\solr-home\tridion\conf\solrconfig.xml file, this request handler is set to return a maximum of 1000 rows:
<requestHandler name="standard" class="solr.SearchHandler" default="true">
As Robert points out, there is a compare option.
To see this for the component view (where it's most useful) a simple path
Select History of the item
Select two versions from the displayed list
Click the 'compare' icon - hover over each until you see the title for compare
I just tried this in Tridion 2013 SP1 and cannot replicate the issue. So it sounds like a defect that has been addressed since your version.
Does the CM's event viewer log give you more details about this save error, e.g. stacktrace? If you share it, we may be able to help further. Otherwise, feel comforted that the issue is addressed in the next Tridion ...
Your note indeed states it all, the Component Presentations on a Page are not versioned. When a Page is rendered for preview, the latest available version for that user is used. When a Page is rendered for publishing, the latest checked in version is used. So even if you are rendering an earlier version of a Page, you don't have a guarantee that the Content ...
There's a bit Tridion does behind-the-scenes with versions, "ownership," and workflow. It's seamless without workflow, makes sense with workflow, but may seem complicated when you have both in an implementation.
When you first create a Component it will have a 0.1 version number and be greyed out until you save. There will be nothing in the ...
In SDL Tridion 2009, you need to use the TOM (Interop) API to create new items, this differs from the TOM.NET API (since the TOM.NET API in 2009 was read-only).
So you have to work from the TDSE like this:
using ItemType = ...
I see that you are concerned with the performance as well. You may think of using the GetListXml method of Core Service.
The code that is working and tested for me to retrieve even all the component of a publication or a folder with huge numbers of component with all the detail is as below -
public XElement GetItems(string tcmURI)
TcmUri tcm = new ...
It looks like your component is not in fact unpublished, which would prevent it from being deleted. In Tridion components can be added to a page and then that page published, or published directly themselves as a Dynamic Component Presentation. The images you're showing above are of the second option. To delete the component you've shown you'll have to go to ...
(Can't really answer you question, but I'm not allowed to comment on it.)
What I understand from your question you use the event system to create a page when a user saves a component.
I would look into the logic for how you set the name for the new page and where you store that page, do you have very many pages in the same structure group? (and inheritance ...
So now you got the metadata xml of the component, the Tridion core service role is over; it's all about compiling the xml and get the desired things out of it using .net.
So assuming you want to get the values of metadata fields, you can follow the below example code, I haven't run it though so you may need some adjustments as well.
doc = XDocument.Parse(...
I assume you are talking about the "Save & Comment" PowerTool?
In that case, the comments should be visible on the "Change History" tab that is also added by the same extension.
The data itself is stored in Application Data on the item with the Application ID 'ext:ItemCommenting'.
The PowerTools are open source and available on GitHub, so you can ...
Sadly there is no default folder location that you can set.
But, as a workaround what I do is create a "Shortcuts" folder at the root level (right under building blocks) and create virtual folders to the commonly used folders for the editors
That way when the hit browse to add a component link they can reduce the number of clicks needed to reach ...
Both versions of that URI are valid.
The item type part of a TCM URI is optional for Components. The default behavior is not to include it when the URI is for a Component (so tcm:163-193997 would be what you would normally get from the CM, CME, etc.). But again, it's equally valid with the -16 at the end.
In your case, since you want to compare it later, ...
Increase buffer size limit in TcmServiceHost.exe.config, you need to add a maxBufferSize parameter (it is set to 500KB here):
<binding name="StreamUpload_netTcpBinding" maxBufferSize="524288" maxReceivedMessageSize="2147483647" transferMode="StreamedRequest" receiveTimeout="00:30:00" />
There are 2 ways I can think of that you can tackle this issue:
Update Tidy to parse <iframe> tag as block tag. For this I suggest you check Nikoli's blog.
create HTML parser (some sort of C# code which can parse your HTML code and replace self closing tags with correct opening and closing tags) on publish time. Honestly, this is not the best approach,...
You should check the Schema RTF field, it usually has a XSLT fillter tab. This fillter uses <xsl:copy> which I have found leaves behind self closing tags.
The portion of the xslt that does this will look similar to
<xsl:template match="/ | node() | @*">
<xsl:apply-templates select="node() | @*"></xsl:apply-...