In SDL Tridion 2009 SP1, I am using Page Metadata with Component Links to set some featured media, SEO data, etc for Pages. The problem is when the editor clicks the "open" button to edit this from the Page, the Shared Item is opened at the current Publication in read only mode. What we need is for the Shared Item dialog to be displayed as per opening a Component Presentation so that we can edit the parent item.
Is there a way to enable this functionality?
I believe there is a hot fix for this. I will try to find the number.
UPDATE
It seems I was wrong - The issue I am thinking of was for SDL Tridion 2011 and solved with hotfix CM_2011.0.1.73971 at https://www.sdltridionworld.com/downloads/hotfixes/SDL_Tridion_2011/index.aspx - I guess it is possible the issue came from 2009 SP1.
SDL have now produced a Hotfix for this issue:
https://www.sdltridionworld.com/images/CM_2009.1.81021_tcm89-20623.zip (log in required)
Related
I've recently encountered an issue in Sitecore 8.2
After deleting the component in content editor. I tried navigating in page editor and clicked the DELETED component.
Now this is where the issue occurs. The options that are usually displayed in page editor are now gone, and after clicking the other components, they all behave the same way.
If I don't click the component that was deleted, then the other components behave normally. This didn't happen to me when I was using Sitecire 7.1 but now that I've upgraded to 8.2 I've recently encountered this issue.
What are the areas I can check? Is this issue known in Sitecore 8?
My recommendations to authors, regardless of version, is to always remove a component from presentation details before deleting any datasource in the Content Editor.
In fact, unless you made a drastic layout mistake, in most cases you should probably not delete the datasource at all.
As of Sitecore 8 editing now has versioned presentation details (Final Renderings). When removing a component from a page in Sitecore 8, you are editing a new version of the page. That new version will no longer have the component displayed. However, all previous versions will still have the component referenced. If you happened to roll back to a previous version, you would need that component. Unless you are removing from ALL versions (or from the shared layout) you probably shouldn't be removing the datasource.
We are using Tridion 2011 SP1. Is there any way to enable styles in Design tabs of RTF field? We have preview tab but editors are finding it as an extra activity to click on preview tab and see the look and feel. In Tridion 5.3 in design tab as well style were applying. We have 2 paragraphs in RTF field but when we check it in design tab we can't see paragraph formattin rather <p> tag is treated as </br> tag.
Now Tridion has their own stack exchange site.It have answer of this question here
Since you are also from Tridion community so I would like to request you to join it. See you there :-)
Thanks
I'm looking for help to add a Button on the Outlook 2007 Message Ribbon to, when its clicked, add the text in a HTML file.
My first questions is:
Is this possible?
What are the possible language you can do this is?
What languague is the the best for this?
EDIT:
I now know how to create the button and so on. But what I need help with now is the coding.
What's the code for when clicking the button it will add the HTML file (the main signature) to the bottom of the mail?
I don't know about all languages support, but C#.NET has a lot of support because both product are from same vendors.
You can use visual studio IDE 2010 which already has templates of outlook add-in for MS-Office with ribbon support also.
http://www.codeproject.com/Articles/194126/Creating-an-Outlook-2010-Add-In
I have a problem with my development VM with SDL Tridion 2011 SP1 installed on it.
When I add a new publication, I cannot add an existing Publication as a parent and so I am unable to create a BluePrint hierarchy.
The add Publication button flashes up the dialog but then it disappears.
Each Publication seems to be created in its own BluePrint hierarchy..
Am I missing something really obvious?
You need to create a root structure group before you can use a publication as a parent publication.
I have faced this scenario, but that was happened cause of Chrome browser only, Have you tried this in IE?
I have a SP 2010 Publishing Site (14.0.4762.1000). It has a contenttype containing a Publishing Hyperlink (SPFieldLink). Inserting a link with the Link Tools (part of the ribbon) works fine, but I can't delete the link once I set it.
For quick reproduction:
Create a Publishing Portal site
Create a column of type Publishing Hyperlink
Add the column to de Welcome Page contenttype
Navigate to the Press Releases page
View information -> Edit
Add a link to the newly created column and save the page
Open it again, remove the link (the link is visually removed, it even says: Click here to add a new Hyperlink)
Save the page again
Now open the page again.
In our situation, the message 'Click here...' is gone, and if you view the source our original link is still there, but there is no text inside it.
I did some testing on it and these are the results:
It occurs on dev and prod server with a custom solution installed
It occurs on a server with no custom solution installed (clean install)
It also occurs on the 'Adventure Works' site (both on a clean install and on a server with custom solution)
It occurs both when creating a sitecolumn of type Publishing Hyperlink through API and UI
When viewed with firebug the 'deleted' link is still in the href property, but the text property is empty
Tested on IE/FF
When viewing with Sharepoint Manager 2010, the link is still in de DB (with no text property as stated above)
It happens on Dutch and English sites
Anyone familiar with this behaviour? Is there a solution for this problem?
I currently have exactly the same issue in a publishing site. I'm looking into it. Let you know if I find anything.
Found your topic on social MSDN. Apperently this is a bug in SP2010.
http://social.msdn.microsoft.com/Forums/en-AU/sharepoint2010general/thread/8ce468ec-096b-4ad2-a1e9-0bfb93cecf95
Currently there is a powershell fix (not really an option for me)
http://vasya10.wordpress.com/2011/06/07/inconspicuous-sharepoint-quirks-2/
Hope this helps.