New answers tagged

1

I finally did it a little bit the ugly way by still publishing the ascx to file system like on the Tridion 2011 install. I have replaced the ComponentPresentationAssembler code that was trying to load the componentpressentation with my own code. This code is now checking if the published ascx file exist and if that's the case then it loads the controller ...


0

I faced similar issue in the past. Answer to your original problem DCPs published as REL in the database, and your DCP template output has a component link tag. which is not getting resolved in the web app. Your case: Pages – stored in the filesystem DCPs – stored in DB Web app dotnet uses CIL. you should be able to get it working a Component Presentation ...


1

Yes, in Tridion 9.1 we can still publish items to the file system. In the cd_storage_conf.xml where the Discovery Service is installed, add the <Storage> element to publish files to the file system inside the <Storages> element like this: <Storage Class="com.tridion.storage.filesystem.FSDAOFactory" Id="ascx" Type="...


2

I recently ran into this same issue on a web 9.1 install. Our issue was that our cd_storage_conf.xml for our deployer and our content service was out of sync. In the deployer we had our config publishing some items to the file system and others to the broker. However, in our content service, we did not have any item types pointing to the file system. ...


Top 50 recent answers are included