None of the comp links in my staging website are getting resolved. I have checked that Tridion tag has been registered in web.config. Also the deployer output is given below.
<tridion:ComponentLink runat="server" ComponentURI="tcm:1-23" LinkText="something"
LinkAttributes=""
PageURI="tcm:1-34-64" TemplateURI="tcm:0-0-0"
AddAnchor="false" TextOnFail="false" />
I have checked the cd_core log in debug mode and here are it's stamp. Please suggest.
2013-10-25 09:41:27,718 DEBUG ComponentLink - ComponentLink.getLinkInfo(): is not null
2013-10-25 09:41:27,718 DEBUG ComponentLink - ComponentLink.getLinkInfo(): read all published components for component 748
2013-10-25 09:41:27,718 DEBUG ComponentLink - ComponentLink Could not find metadata for page: 1666
2013-10-25 09:41:27,718 DEBUG ComponentLink - ComponentLink.getLink(): start retrieving pathinfo for this page: 1666
2013-10-25 09:41:27,718 DEBUG ComponentLink - Found component with score 2147483647
2013-10-25 09:41:27,718 INFO ComponentLink - ComponentLink.getLink(): couldn't create a link to any other instance of component presentation 748:0 from page 1666
Update 1 - I am using Tridion 2011 SP1 and the same links works in dev and test.
Update 2
- Hi Bart, yes the TridionDB in deployer's storage config is different from the website's storage config. Is this the cause?
cd_storage_conf.xml
from the Deployer and the website and make sure they are pointing to the same locations (and database).cd_storage_conf.xml
can only be copied if you are not using a database, else I would expect that the database server and/or database names would at least differ between environments. So still worth showing your Deployercd_storage_conf.xml
.