News Module custom fields Appearing and Disappearing when using them in RSS Feed Imports into the News Module
At some point when you go back to the news feed and click on Mapping Settings, the custom field has disappeared.
Running the following script:SELECT
*
FROM
sf_meta_fields
WHERE
[column_name]
LIKE
'%ThomsonsLink%'
;
Hello Jacques,
Thank you for sharing this workaround with the community.
In Sitefinity 6.3 this issue cannot be reproduce as there are lot of improvements made regarding custom fields, so we strongly recommend you to consider an upgrade at some point.
Best regards,
Vassil Vassilev
Telerik
Hi Vassil,
Upgrading every few months is not an option for most companies. Would have been nice to see Telerik focus on some fixes instead of new releases all the time.
Regards,
Jacques
Vassil,
We've upgraded the site to 6.3.
I went to the news content items and both our custom fields are there.
I went to the RSS feed that we'd setup and low and behold there's no custom fields!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
So what's your next suggestion? Wait for version 7 I'm sure it will be fixed there!
I've just deleted the feed and the custom fields, recreated the fields then recreated the feed. When I click Actions > Run I get the message attached
"For security reasons DTD is prohibited in this XML document. To enable DTD processing set the DtdProcessing property on XmlReaderSettings to Parse and pass the settings into XmlReader.Create method."
What?
Looking at the console:
PUT xpo.nedoweb.com/.../ 500 (For security reasons DTD is prohibited in this XML document. To enable DTD processing set the DtdProcessing property on XmlReaderSettings to Parse and pass the settings into XmlReader.Create method.) ScriptResource.axd?d=soT65IVsRF6JSefna9Rl2ZUxf-RAntuOTQKvQanbX8z6c_Efii1lSr3BptVHxIFUmjL2xvaf7QR1XX…:1Sys.Net.XMLHttpExecutor.executeRequestScriptResource.axd?d=soT65IVsRF6JSefna9Rl2ZUxf-RAntuOTQKvQanbX8z6c_Efii1lSr3BptVHxIFUmjL2xvaf7QR1XX…:1Sys.Net._WebRequestManager.executeRequestScriptResource.axd?d=soT65IVsRF6JSefna9Rl2ZUxf-RAntuOTQKvQanbX8z6c_Efii1lSr3BptVHxIFUmjL2xvaf7QR1XX…:1Sys.Net.WebRequest.invokeScriptResource.axd?d=soT65IVsRF6JSefna9Rl2ZUxf-RAntuOTQKvQanbX8z6c_Efii1lSr3BptVHxIFUmjL2xvaf7QR1XX…:1Telerik.Sitefinity.Data.RequestQueue.executeTelerik.Web.UI.WebResource.axd?_TSM_HiddenField_=ctl06_TSM&compress=0&_TSM_CombinedScripts_=%3b%3bT…:7761Telerik.Sitefinity.Data.RequestQueue.addAndExecuteTelerik.Web.UI.WebResource.axd?_TSM_HiddenField_=ctl06_TSM&compress=0&_TSM_CombinedScripts_=%3b%3bT…:7765Telerik.Sitefinity.Data.ClientManager.InvokePutTelerik.Web.UI.WebResource.axd?_TSM_HiddenField_=ctl06_TSM&compress=0&_TSM_CombinedScripts_=%3b%3bT…:7510handleBinderItemCommandTelerik.Web.UI.WebResource.axd?_TSM_HiddenField_=ctl06_TSM&compress=0&_TSM_CombinedScripts_=%3b%3bT…:5009(anonymous function)ScriptResource.axd?d=soT65IVsRF6JSefna9Rl2ZUxf-RAntuOTQKvQanbX8z6c_Efii1lSr3BptVHxIFUmjL2xvaf7QR1XX…:1Telerik.Sitefinity.Web.UI.ClientBinder._itemCommandHandlerTelerik.Web.UI.WebResource.axd?_TSM_HiddenField_=ctl06_TSM&compress=0&_TSM_CombinedScripts_=%3b%3bT…:20730(anonymous function)Telerik.Web.UI.WebResource.axd?_TSM_HiddenField_=ctl06_TSM&compress=0&_TSM_CombinedScripts_=%3b%3bT…:21034v.event.dispatchScriptResource.axd?d=OqpfTXW4x1V2q-8jqor-WXAKsZVPXWy8aHGm1ssoupa3lF8JGDKEo-JpZIZc6qmhwwEIc8GyMD_7IR…:2o.handle.uScriptResource.axd?d=OqpfTXW4x1V2q-8jqor-WXAKsZVPXWy8aHGm1ssoupa3lF8JGDKEo-JpZIZc6qmhwwEIc8GyMD_7IR…:2
Nice work Vassil... Yes upgrade we can't replicate the problem in 6.3
Another issue after the upgrade (this is when I try to delete news items):
0 item(s) are successfully deleted. 10 item(s) cannot be deleted (see below).Content Block XPO Logistics to Acquire Pacer International, the Third Largest Provider of Intermodal Transportation Services in North America: Failed to create a 'Settings' from the text 'Assembly references and imported namespaces serialized as XML namespaces'.Content Block XPO Logistics Releases Preliminary Results for Fourth Quarter 2013: Failed to create a 'Settings' from the text 'Assembly references and imported namespaces serialized as XML namespaces'.Content Block XPO Logistics Announces Common Stock Offering: Failed to create a 'Settings' from the text 'Assembly references and imported namespaces serialized as XML namespaces'.Content Block XPO Logistics Announces Pricing of $375 Million Public Offering of Common Stock: Failed to create a 'Settings' from the text 'Assembly references and imported namespaces serialized as XML namespaces'.Content Block XPO Logistics Schedules Fourth Quarter 2013 Conference Call for Tuesday, February 25, 2014: Failed to create a 'Settings' from the text 'Assembly references and imported namespaces serialized as XML namespaces'.Content Block XPO Logistics Announces Closing of $375 Million Public Offering of Common Stock : Failed to create a 'Settings' from the text 'Assembly references and imported namespaces serialized as XML namespaces'.Content Block XPO Logistics Announces Exercise of Underwriters' Option for 2,250,000 Shares of Common Stock: Failed to create a 'Settings' from the text 'Assembly references and imported namespaces serialized as XML namespaces'.Content Block XPO Logistics Announces Fourth Quarter and Full Year 2013 Results: Failed to create a 'Settings' from the text 'Assembly references and imported namespaces serialized as XML namespaces'.Content Block XPO Logistics Agrees to Acquire NLM, the Largest Web-based Expediter in North America: Failed to create a 'Settings' from the text 'Assembly references and imported namespaces serialized as XML namespaces'.Content Block XPO Logistics Completes Acquisition of NLM: Failed to create a 'Settings' from the text 'Assembly references and imported namespaces serialized as XML namespaces'.
Hello,
Can you check your upgrade log file? Can you find information about failed upgrade scripts? If yes, I would strongly recommend you to try the upgrade sequence again as described in our documentation:
http://www.sitefinity.com/documentation/documentationarticles/installation-and-administration-guide/upgrade
Please, make sure you strictly follow it, because omitting some of the steps may cause unexpected behavior of your project and always after upgrading to some Sitefinity version, check the upgrade log to be sure all upgrade scripts has passed.
I hope this information helps.
Regards,
Vassil Vassilev
Telerik