We are having problems with unpublishing the content of any Tridion publication. When we try to unpublish any content, these unpublished elements do not disappear from the application of the front and remain in the file system. After unpublishing the content, we have verified the following actions:
In the Tridion publishing queue, the content has been successfully unpublished, giving Success in the queue.
It is verified that the icon next to the element that indicates if an element is published, also disappears.
In the "Where used" tab, it does not appear that the item is published in any target.
Finally, check that in the Broker the unpublished content has also disappeared.
As we have commented previously, the problem of unpublication occurs with any publication of Tridion, therefore, we discard the problem of advertising or the application in particular. The permissions have also been revised in the front applications are correct.
On the other hand, when we publish any content, it works correctly, updating this published element with the content and the correct date of the publication in the front of the application.
Thanks a lot for you help!!
Andres.
Related
Running AEM 6.5.8.0 and we've a range of content in grid containers that no longer render visibly despite the code being present when viewing source.
For instance, on https://www.redfcu.org content below "featured rates" can be seen, edited in author, and the source is present when published, but does not render in the browser. Our implementation partner has not responded to the issue in several days, and Adobe's only solution is restore from back-up, but without knowing the root cause, I'm hesitant to just restore for the sake of it.
content in author
content when published
I see the content now, and I guess the issue has been solved. What was the root cause. In the future, if you have access to the logs, there should be errors or warnings printed in error.log (or in the default project log project-name-project.log) when you try to access that page. Missing content in publish is a common issue. In this case, it could be that this component is reading the child pages below a given path and these pages or experience fragments are not present in the publish instance. Similar scenarios happen when the content is tagged but the tags are not published, or there is a failure in a logic validating if you are on author/publish mode.
So I've been having issues with a large website trying to build itself over and over during publishing, being lazy I wanted to take it offline and back on again with publishing.
I followed these instructions:
http://blogs.msdn.com/b/webdev/archive/2013/10/30/web-publishing-updates-for-app-offline-and-usechecksum.aspx
<EnableMSDeployAppOffline>true</EnableMSDeployAppOffline>
Trouble is the page it creates is empty. The title says Site under Construction. but nothing on page, the body has mention of being IE friendly:
additional hidden content so that IE Friendly Errors don't prevent this message from displaying (note: it will show a 'friendly' 404 error if the content isn't of a certain size).
but thats in a comment, the page is just white blank.
I found this article: Custom app_offline.htm file during publish
Suggesting that C:\Users[user]\AppData\Roaming\Microsoft\VisualStudio\11.0\app_offline.htm has the content for MSDeploy, I'm using VS2013 and went to the 12 folder accordingly, found the file edited it and MSDeploy just laughs in the face of my hopes and smashes my dreams of any sort of on-screen message.
I don't care if all my websites get the same screen, it's an intranet and all my websites look similar anyway, but I just need to get an onscreen message and a meta tag to refresh the page in 1 minute.
Does anyone know where or what to edit?
Problem: Within the Content Editor, our web editors with the privileges to edit content as well as publish that content are often forgetting to go to Edit>Approve and Publish, instead they are just saving and trying to press the publish button which publishes to master, but not the live production server. I understand that approve and publish puts the page into the final workflow step, and (atleast on our servers) the publish button does not. I'm wondering if the Publish button can be changed to function as 'Approve and Publish' and whether that will cause any issues for people who have editor privileges but not publishing privileges.
Along those same lines, our admins can save and publish with the publish button without approving by using Edit>Approve and Publish, but they cannot do this with new pages. New pages have to be approved and published once and from that point on they can simply save and then publish with publish button and the content goes live. Is there any way to bypass that initial 'Approve and Publish' step for admins?
I have some experience working in the core as well as editing the workflow, but I apologize if this is a really simple problem, or if I'm missing the point of the way our workflow is setup. I also considered creating an Approve button and putting it next to edit, so that our editors were more likely to remember that step, but I couldn't find an approve command to associate with the new button. I would love some feedback from Sitecore veterans.
Changing the behavior of the publish button is not recommeded and will just end up confusing everyone. Also adding a new button will just lead to more confusion about which button your editors should be using.
Since your editors have to use workflow, they probably don't need access to the standard publish button. Simply removing them from the Sitecore Client Publishing role will make it so they can't see the publish button and therefore have to use the workflow command.
If workflow is turned on, a new version of an item will always be put into the first step of that workflow. You could change that behavior with a handler for the version:added event. If you are only concerned about new items, a processor for the uiAddFromTemplate pipeline could also be used. However, I don't recommend changing this behavior at all. For that matter, I don't recommend using full admin users for content editing at all since you will lose the versioning of your content items. Admin users should be used for administration, not content editing.
I am checking the following documentation and looking for little bit more information on How archive manager checks for content changes.
http://sdllivecontent.sdl.com/LiveContent/content/en-US/SDL_ArchiveManager_10SP2/concept_756FB4CA97E94AE9836229E605A06CAD
Scenario:
I have Component A with related Components field links to Component
B,C,D.
On my page A, we add the Component A with Template A and
publish the page A.
On Publish Archive Manager is processing this
and storing the a version in Archive Manager DB.
Subsequent updates to the content is done on any of Component B, C , D.
When we re-publish Page A, does Archive Manager process it as a new copy ? Right now, we see it for some updates and we do not see it for some updates.
We want to get some clarification on the below documented.
Republication (content unchanged) — When the page is republished, the
Archive Manager checks to see whether the content of the page and/or
its artifacts has actually changed. If neither the contents of the
page nor its artifacts have changed, a new version of the record is
created to indicate the resource has been republished, but the
content itself is not rearchived.
Republication (content changed) — when the page is republished, and
its content has changed, a new version of the record is created and a
new entry for its content created.
How does Archive Manager checks whether its artifacts changed or not? Does it check Componet A, B, C , D and Page A ?
Any clarification will be helpful.
Archive Manager's archiving happens in Tridion's content deployment phase and it doesn't reach back to the Content Manager.
The archiver determines which Component Presentations are being deployed by looking at the instructions that the Publisher put into the transport package. But as far as I remember (it's been a while) it only uses the actual web page to determine whether the Components have been changed.
So I have an umbraco setup with a 'content' root node and then a 'home' node under that. Under the 'home' node is the content and the URLs are the name of those nodes for example I have a 'about u's node under home and it's URL is '/about-us/'
In the case of the 'news' node, below 'about us', its children some times get '/home/about-us/news/title' of the story as the URL, which throws a 404. I can see that this is the URL of the node on the properties tab, but if I republish it it returns to '/about-us/news/title' for a period before returning to the broken link.
I have only seen this behavior on this node, which contains new-item document types. I basically watched the umbraco tv video and created it following along.
It seems to be to be a umbraco bug, but I would really appreciate any help with the issue
In the web.config, there is a setting called umbracoHideTopLevelNodeFromPath. This causes the behavior you are describing when it is set to false. Do you perhaps have multiple people working on the site and publishing different versions of the web.config that have this setting changed?
When publishing a node with the setting set to false, it would add the /home part to the URL. Otherwise, it would leave off the /home.
Once the Umbraco application has started, there are several processes that run on a regular basis (e.g. to check for expired content). It is possible to piggy-back on these by creating a custom class that inherits from umbraco.cms.businesslogic.ApplicationBase. If you have created one that uses the Document.AfterPublish eventhandler then I would check that it is not causing the issue.
I'm assuming that you haven't written one of these though, so the only other thing I can suggest is checking whether it is an installed package that is causing the issue. Have you installed any Umbraco packages? If so, do they have any automated behaviours, like creating folders etc. If so, this may be causing the issue. The author of a package will usually have a website, codeplex project etc. and they will usually have a issue list or blog.
Edit
I've just quickly checked and uBlogsy, one of the plugins you mention exactly this. It has auto moving and sorting of posts. This is described in the release notes. If you are using this tool for creating news pages, then this will be your issue.
I followed obsidian's link in his answer and read about someone else having the same issue. It seems to be traces back to a umbraco.library:NiceUrlFullPath call in the RSS creator that was feeding news items. I replaced the umbraco.library:NiceUrlFullPath calls with umbraco.library:NiceUrl calls and the issue has disappeared.