I'm using Sitecore 7.0 and there is an publishing ribbon.
If I select item on the left panel and click big ribbon on the top of tool box, it shows two options, Publish site and Publish Item.
I'd like to make sure the difference between "Republish" in Publish Site and "Republish" in Publish Item.
Also, I know that if site publishes, it clears all caches.
Does the cache clear when I use "Republish" in Publish Item option as well??
Both you do the same thing, the difference is only as the name says, Republish Site will republish all items while republish item will only republish the selected item.
The difference between smart, incremental and republish you can see here:
http://www.sitecoreinsight.com/sitecore-publish-site-tool-publishing-modes/
And about the cache, yes, it always clear the cache :)
You can check that in a event handler on your web.config file. That is the proccess responsible for it and it is fired when any type of publish ends.
<event name="publish:end">
<handler type="Sitecore.Publishing.HtmlCacheClearer, Sitecore.Kernel" method="ClearCache">
<sites hint="list">
<site>website</site>
</sites>
</handler>
</event>
UPDATE:
It clears all HTML cache for the list of sites you see in the configuration above. Publishing does not affect the items cache, I actually don't know what Sitecore does to renew such cache.
There is a tool where you can check the cache status:
http:// your domain /sitecore/admin/cache.aspx
Also take a look at this post, it has a good overview about Sitecore caching
http://sitecorebasics.wordpress.com/2011/03/05/sitecore-caching/
There is another tool that is also incredibly helpful for investigating what's being cached. It's on the Marketplace and is called "Cache Admin":
https://marketplace.sitecore.net/Modules/Sitecore_Cache_Admin.aspx?sc_lang=en
Related
My PingFed has a connection to a SSO page. That page doesn't have the verbiage I want even though I changed and replaced the properties files. How can I rebuild so that it works?
I agree with Andrew K's comment above, but my guess here is that your updated messages are not being used because you either need to restart PingFederate or disable caching of the message properties files.
For more details, see the tip at the bottom of this page (cache-language-pack-messages setting in <pf_install>/pingfederate/server/default/data/config-store/locale-options.xml): https://docs.pingidentity.com/bundle/pingfederate-101/page/ujv1564002982909.html
I am deploying my site to Azure from VS 2017. After each deployment, I am supposed to clean the cache of my browser to get the latest version of the website (or use ctrl+f5 to ignore the cached content when refreshing). But, this is a problem for the end users.
This is a asp.net + react website. So, the client-side code is cached in the browser. I have WEBSITE_DYNAMIC_CACHE set to 0, but did not help. Any suggestions? Is there a solution to this?
In VS 2017 right-click on the project and choose Publish. Click on Configure, then make sure the box is ticked for "remove additional files at destination"
I don't have enough votes to post screenshots yet, sorry!
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 made some changes to the existing asp page. When I access it I don't see the changes yet and I still see the old content. Do I need to recompile .asp files?
The pages are likely cached in your browser. There are a number of ways to get around this. You can:
force a page refresh on the browser ([Ctrl]+[F5])
Recycle the application pool (if this is an application)
(or the dirty way) make a tiny change (like adding a space) to the global.asa which will in turn recycle the app pool
Edit (2017)
If you're debugging using IE then you can also set your cache to refresh every time you visit the page:
Bring up the internet options. Click the Settings button on the Browsing history section of the dialog and change the Check for newer versions of the stored pages: setting to Every time I visit the webpage...
ASP pages are scripting , you do not need to compile , just check if you have page cached on the browser .
Request.RawUrl always returns the /default.aspx variant. I did not find any way at all to differentiate between these urls. Does anybody know how to do that?
Environment is .NET 3.5SP1 on IIS 7.
I actually had to combat this same problem when designing my URL Rewriter. It has to do with the processes that occur before you can even access the URL's. To get around this you have to make sure that in IIS 7 the default page handling is turned off. Because if there is no default page handling it is not going to go through the extra step of trying to map it to the drive, so you will be the exact URL requested. But this may or may not be an option depending on if you are using System.Web.Routing or not.
To turn off the default page handling you need to do the following:
Go to your site in IIS
Go to Default Document
Click Disable in the top right corner.
Or you can add the following to your web.config:
<system.webServer>
<!-- ... other tags here ... -->
<defaultDocument enabled="false" />
</system.webServer>
After you do this the default document will be no longer added to your URL. However be warned that since this is no longer active you cannot rely on default.aspx actually mapping to your directories, you will have to handle this manually or use something like System.Web.Routing to handle this functionality.
To accomplish the same in IIS 6 you need to turn on wildcards:
The following instructions apply for IIS 6.
Open IIS and right-click on the website and select 'properties'.
Click the 'Configuration' button under Application Settings section
Click the 'Insert...' button to create a new wildcard mapping
Set the executable textbox to aspnet_isapi.dll file location.
for .net 2.0, 3.0, 3.5: C:\Windows\Microsoft.NET\Framework\v2.0.50727\aspnet_isapi.dll
Make sure the checkbox 'Verify that file exists' is not checked.
Press 'OK' to confirm and close all the windows.
NOTE: by the way all the source is available on the site I linked above incase you were curious how I was doing things.