Help:Caching - Revision history

imported>Ryangibsonstewart: this already indents enough...there's no need to indent more

2009-01-10T05:46:36Z

this already indents enough...there's no need to indent more

← Older revision	Revision as of 05:46, 10 January 2009
(No difference)

imported>Ryangibsonstewart: this already indents enough...there's no need to indent more

2009-01-10T05:46:36Z

this already indents enough...there's no need to indent more

← Older revision		Revision as of 05:46, 10 January 2009
Line 21:		Line 21:

	From any Heroes Wiki page:		From any Heroes Wiki page:
	:# At the end of the [[Wikipedia:URL\|URL]] in the address bar of your browser, append the text <tt>?action=purge</tt>.		# At the end of the [[Wikipedia:URL\|URL]] in the address bar of your browser, append the text <tt>?action=purge</tt>.
	:# Press [Enter] or click "Go" to tell the browser to go to that revised URL.		# Press [Enter] or click "Go" to tell the browser to go to that revised URL.
	:# The page should be refreshed in a short time.		# The page should be refreshed in a short time.

	or:		or:
	:# Click the "edit this page" tab.		# Click the "edit this page" tab.
	:# In the address bar in your browser, at the end of the URL, where you see <tt>&action=edit</tt>, replace "edit" with "purge," so it now reads <tt>&action=purge</tt>.		# In the address bar in your browser, at the end of the URL, where you see <tt>&action=edit</tt>, replace "edit" with "purge," so it now reads <tt>&action=purge</tt>.
	:# Press [Enter] or click "Go" to tell the browser to go to that revised URL.		# Press [Enter] or click "Go" to tell the browser to go to that revised URL.
	:# The page should be refreshed in a short time.		# The page should be refreshed in a short time.

	From editable pages:		From editable pages:
	:# Click the "edit this page" tab and preview the page.		# Click the "edit this page" tab and preview the page.
	:# Then click save without making any changes. No changes will be saved, but the cache will have been cleared.		# Then click save without making any changes. No changes will be saved, but the cache will have been cleared.

	==External Links==		==External Links==

imported>MiamiVolts: remove extra brackets

2008-12-18T22:20:17Z

remove extra brackets

← Older revision		Revision as of 22:20, 18 December 2008
Line 10:		Line 10:
	Heroes Wiki pages can use multiple templates and multiple categories meaning the server has to compile information from multiple sources in order to completely display a page. To lessen the load this would normally imply, the Heroes Wiki server uses caching such that whenever a page is saved on the wiki, a complete copy of the page is put into server cache. Subsequent viewings of the saved page then refer to the server's cache of that page until a portion of the page is re-edited or that page's cache is purged.		Heroes Wiki pages can use multiple templates and multiple categories meaning the server has to compile information from multiple sources in order to completely display a page. To lessen the load this would normally imply, the Heroes Wiki server uses caching such that whenever a page is saved on the wiki, a complete copy of the page is put into server cache. Subsequent viewings of the saved page then refer to the server's cache of that page until a portion of the page is re-edited or that page's cache is purged.

	There are a couple of exceptions to that description of server caching. The most common exception is in regards to categories. When a page is saved with a tag for a particular category, the server automatically adds an entry to the respective category page with the added page's name. However, when a page is removed from that category, the category page update does not always happen immediately and often requires a form of purging to remove the page from the category's list of articles. (See [[#How to Purge\|how to purge]] below]].) Also, when a category page is created after it has been used, it normally requires purging to force the server to search for and immediately include those pages that were categorized before it existed. The server's cache auto-updates itself eventually to include those pages, but the process that does so normally takes a few hours.		There are a couple of exceptions to that description of server caching. The most common exception is in regards to categories. When a page is saved with a tag for a particular category, the server automatically adds an entry to the respective category page with the added page's name. However, when a page is removed from that category, the category page update does not always happen immediately and often requires a form of purging to remove the page from the category's list of articles. (See [[#How to Purge\|how to purge]] below.) Also, when a category page is created after it has been used, it normally requires purging to force the server to search for and immediately include those pages that were categorized before it existed. The server's cache auto-updates itself eventually to include those pages, but the process that does so normally takes a few hours.

	Another exception is related to an extension Heroes Wiki uses called [http://semeb.com/dpldemo/index.php?title=DPL:Manual Dynamic Page List] (DPL). This extension uses it's own form of markup on a page to create a dynamic list using the content and names of other pages in a wiki's database. There is an option in DPL to access content from the server's cache, and that option has been set to be always on at Heroes Wiki. Thus, if a template uses DPL on a page, the server's cache of that page must be cleared for changes to be immediately viewable. If the DPL is adding pages based on whether a page has been added to a category, removing a page from the list may require not only purging the page containing the DPL markup, but also purging the category of the page that has been removed and/or the page that has been removed itself. Like with the previous situation, the server's cache will eventually auto-update the DPL listings. However, if that is not desired, purging can be applied.		Another exception is related to an extension Heroes Wiki uses called [http://semeb.com/dpldemo/index.php?title=DPL:Manual Dynamic Page List] (DPL). This extension uses it's own form of markup on a page to create a dynamic list using the content and names of other pages in a wiki's database. There is an option in DPL to access content from the server's cache, and that option has been set to be always on at Heroes Wiki. Thus, if a template uses DPL on a page, the server's cache of that page must be cleared for changes to be immediately viewable. If the DPL is adding pages based on whether a page has been added to a category, removing a page from the list may require not only purging the page containing the DPL markup, but also purging the category of the page that has been removed and/or the page that has been removed itself. Like with the previous situation, the server's cache will eventually auto-update the DPL listings. However, if that is not desired, purging can be applied.

imported>Ryangibsonstewart: User:MiamiVolts/Help:Caching moved to Help:Caching: move to help ns

2008-12-16T00:03:38Z

User:MiamiVolts/Help:Caching moved to Help:Caching: move to help ns

← Older revision	Revision as of 00:03, 16 December 2008
(No difference)

imported>Ryangibsonstewart: cap sections, clarify, add a section to make it a little more user friendly, add cache clearing

2008-12-16T00:03:16Z

cap sections, clarify, add a section to make it a little more user friendly, add cache clearing

← Older revision		Revision as of 00:03, 16 December 2008
Line 2:		Line 2:
	Heroes Wiki eases its bandwidth and server load requirements by using '''caching'''.		Heroes Wiki eases its bandwidth and server load requirements by using '''caching'''.

	==Browser ~~caching~~==		==Browser Caching==
	The main means by which Heroes Wiki uses caching is by allowing users' internet browsers to keep a cache of its articles and other pages on the users' local machines. Many browsers have an option to store pages in a local cache for later viewing and may also refer to that cache instead of the wiki itself on previous viewings depending on the browser's settings. Depending on a user's browser, clicking "refresh" or "reload" on the browser may normally bring up the latest version of a Heroes Wiki page. Browsers often include options for how page text content is stored, but do not always have options for images, audio files, and software scripts. For those browsers, bypassing or clearing the cache completely may be the only way to immediately access an updated image or audio file. Wikipedia has [[Wikipedia:Wikipedia:Bypass your cache\|instructions]] for doing so for the main types of browsers.		The main means by which Heroes Wiki uses caching is by allowing users' internet browsers to keep a cache of its articles and other pages on the users' local machines. Many browsers have an option to store pages in a local cache for later viewing and may also refer to that cache instead of the wiki itself on previous viewings depending on the browser's settings. Depending on a user's browser, clicking "refresh" or "reload" on the browser may normally bring up the latest version of a Heroes Wiki page. Browsers often include options for how page text content is stored, but do not always have options for images, audio files, and software scripts. For those browsers, bypassing or clearing the cache completely may be the only way to immediately access an updated image or audio file. (See [[#How to Clear the Cache\|how to clear the cache]] below.) Wikipedia has [[Wikipedia:Wikipedia:Bypass your cache\|instructions]] for doing so for the main types of browsers.

	Changes to software scripts on Heroes Wiki pages also often require clearing the browser cache, and sometimes a restart of the browser itself as the code may still be running in the browser even after the cache is cleared. Heroes Wiki uses a scripting called [[Wikipedia:Cascading Style Sheets\|cascading style sheets]] (CSS) to add default style formatting to Heroes Wiki pages. In addition, Heroes Wiki uses JavaScript to add other features such as [[Help:Collapsible tables\|collapsible tables]].		Changes to software scripts on Heroes Wiki pages also often require clearing the browser cache, and sometimes a restart of the browser itself as the code may still be running in the browser even after the cache is cleared. Heroes Wiki uses a scripting called [[Wikipedia:Cascading Style Sheets\|cascading style sheets]] (CSS) to add default style formatting to Heroes Wiki pages. In addition, Heroes Wiki uses JavaScript to add other features such as [[Help:Collapsible tables\|collapsible tables]].

	==Server ~~caching~~==		==Server Caching==
	Heroes Wiki pages can use multiple templates and multiple categories meaning the server has to compile information from multiple sources in order to completely display a page. To lessen the load this would normally imply, the Heroes Wiki server uses caching such that whenever a page is saved on the wiki, a complete copy of the page is put into server cache. Subsequent viewings of the saved page then refer to the server's cache of that page until a portion of the page is re-edited or that page's cache is purged.		Heroes Wiki pages can use multiple templates and multiple categories meaning the server has to compile information from multiple sources in order to completely display a page. To lessen the load this would normally imply, the Heroes Wiki server uses caching such that whenever a page is saved on the wiki, a complete copy of the page is put into server cache. Subsequent viewings of the saved page then refer to the server's cache of that page until a portion of the page is re-edited or that page's cache is purged.

	There are a couple of exceptions to that description of server caching. The most common exception is as regards to categories. When a page is saved with a tag for a particular category, the server automatically adds an entry to the respective category page with the added page's name. However, when a page is removed from ~~the same~~ category, the category page update does not always happen immediately and often requires a form of purging to remove the page from the category's list of articles. Also, when a category page created after it has been used, it normally requires purging to force the server to search for and immediately include those pages that were categorized before it existed. The server's cache auto-updates itself eventually to include those pages, but the process that does so normally takes a few hours.		There are a couple of exceptions to that description of server caching. The most common exception is in regards to categories. When a page is saved with a tag for a particular category, the server automatically adds an entry to the respective category page with the added page's name. However, when a page is removed from that category, the category page update does not always happen immediately and often requires a form of purging to remove the page from the category's list of articles. (See [[#How to Purge\|how to purge]] below]].) Also, when a category page is created after it has been used, it normally requires purging to force the server to search for and immediately include those pages that were categorized before it existed. The server's cache auto-updates itself eventually to include those pages, but the process that does so normally takes a few hours.

	Another exception is related to an extension Heroes Wiki uses called [http://semeb.com/dpldemo/index.php?title=DPL:Manual Dynamic Page List] (DPL). This extension uses it's own form of markup on a page to create a dynamic list using the content and names of other pages in a wiki's database. There is an option in DPL to access content from the server's cache, and that option has been set to be always on at Heroes Wiki. Thus, if a template uses DPL on a page, the server's cache of that page must be cleared for changes to be immediately viewable. If the DPL is adding pages based on whether a page has been added to a category, removing a page from the list may require not only purging the page containing the DPL markup, but also purging the category of the page that has been removed and/or the page that has been removed itself. Like with the previous situation, the server's cache will eventually auto-update the DPL listings; ~~but~~ if that is not desired, purging can be applied.		Another exception is related to an extension Heroes Wiki uses called [http://semeb.com/dpldemo/index.php?title=DPL:Manual Dynamic Page List] (DPL). This extension uses it's own form of markup on a page to create a dynamic list using the content and names of other pages in a wiki's database. There is an option in DPL to access content from the server's cache, and that option has been set to be always on at Heroes Wiki. Thus, if a template uses DPL on a page, the server's cache of that page must be cleared for changes to be immediately viewable. If the DPL is adding pages based on whether a page has been added to a category, removing a page from the list may require not only purging the page containing the DPL markup, but also purging the category of the page that has been removed and/or the page that has been removed itself. Like with the previous situation, the server's cache will eventually auto-update the DPL listings. However, if that is not desired, purging can be applied.

			===How to Clear the Cache===
⚫	There are a few ways ~~on Heroes Wiki~~ for ordinary users or unregistered visitors to purge the server's cache.
			To clear the cache on most browsers, press the refresh button which is usually at the top of your browser's page. You can also press F5 or CTRL + F5 to accomplish the same thing.

			===How to Purge===
		⚫	There are a few ways for ordinary users or unregistered visitors to purge the Heroes Wiki server's cache.

	From any Heroes Wiki page:		From any Heroes Wiki page:
	:# At the end of the [[Wikipedia:URL\|URL]] in the address bar of your browser, append the text <tt>?action=purge</tt>		:# At the end of the [[Wikipedia:URL\|URL]] in the address bar of your browser, append the text <tt>?action=purge</tt>.
	:# Press [Enter] or click "Go" to tell the browser to go to that revised URL		:# Press [Enter] or click "Go" to tell the browser to go to that revised URL.
	:# The page should be refreshed in a short time		:# The page should be refreshed in a short time.

	or:		or:
	:# Click the "edit this page" tab		:# Click the "edit this page" tab.
	:# In the address bar in your browser, at the end of the URL, where you see <tt>&action=edit</tt>, replace "edit" with "purge," so it now reads <tt>&action=purge</tt>		:# In the address bar in your browser, at the end of the URL, where you see <tt>&action=edit</tt>, replace "edit" with "purge," so it now reads <tt>&action=purge</tt>.
	:# Press [Enter] or click "Go" to tell the browser to go to that revised URL		:# Press [Enter] or click "Go" to tell the browser to go to that revised URL.
	:# The page should be refreshed in a short time		:# The page should be refreshed in a short time.

	From editable pages:		From editable pages:
	:# Click the "edit this page" tab and preview the page		:# Click the "edit this page" tab and preview the page.
	:# Then click save without making any changes. No changes will be saved, but the cache will have been cleared.		:# Then click save without making any changes. No changes will be saved, but the cache will have been cleared.

	==~~See~~ ~~Also~~==		==External Links==
	* [[Wikipedia:Wikipedia:Purge\|Wikipedia's help on purging]]		* [[Wikipedia:Wikipedia:Purge\|Wikipedia's help on purging]]
	* [[Wikipedia:Wikipedia:Bypass your cache\|Wikipedia's help on bypassing cache]]		* [[Wikipedia:Wikipedia:Bypass your cache\|Wikipedia's help on bypassing cache]]

imported>MiamiVolts at 04:51, 15 December 2008

2008-12-15T04:51:43Z

← Older revision		Revision as of 04:51, 15 December 2008
Line 17:		Line 17:

	From any Heroes Wiki page:		From any Heroes Wiki page:
	:# At the end of the [[URL]] in the address bar of your browser, append the text <tt>?action=purge</tt>		:# At the end of the [[Wikipedia:URL\|URL]] in the address bar of your browser, append the text <tt>?action=purge</tt>
	:# Press [Enter] or click "Go" to tell the browser to go to that revised URL		:# Press [Enter] or click "Go" to tell the browser to go to that revised URL
	:# The page should be refreshed in a short time		:# The page should be refreshed in a short time

imported>MiamiVolts: finish article

2008-12-15T04:46:25Z

finish article

← Older revision		Revision as of 04:46, 15 December 2008
Line 10:		Line 10:
	Heroes Wiki pages can use multiple templates and multiple categories meaning the server has to compile information from multiple sources in order to completely display a page. To lessen the load this would normally imply, the Heroes Wiki server uses caching such that whenever a page is saved on the wiki, a complete copy of the page is put into server cache. Subsequent viewings of the saved page then refer to the server's cache of that page until a portion of the page is re-edited or that page's cache is purged.		Heroes Wiki pages can use multiple templates and multiple categories meaning the server has to compile information from multiple sources in order to completely display a page. To lessen the load this would normally imply, the Heroes Wiki server uses caching such that whenever a page is saved on the wiki, a complete copy of the page is put into server cache. Subsequent viewings of the saved page then refer to the server's cache of that page until a portion of the page is re-edited or that page's cache is purged.

			There are a couple of exceptions to that description of server caching. The most common exception is as regards to categories. When a page is saved with a tag for a particular category, the server automatically adds an entry to the respective category page with the added page's name. However, when a page is removed from the same category, the category page update does not always happen immediately and often requires a form of purging to remove the page from the category's list of articles. Also, when a category page created after it has been used, it normally requires purging to force the server to search for and immediately include those pages that were categorized before it existed. The server's cache auto-updates itself eventually to include those pages, but the process that does so normally takes a few hours.
	There are a couple of exceptions to that description of server caching. One of the extensions Heroes Wiki uses is [http://semeb.com/dpldemo/index.php?title=DPL:Manual Dynamic Page List] (DPL). This extension uses it's own form of markup on a page to create a dynamic list using the content and names of other pages in a wiki's database. There is an option in DPL to access content from the server's cache, and that option has been set to be always on at Heroes Wiki.

	{{sectstub}}
			Another exception is related to an extension Heroes Wiki uses called [http://semeb.com/dpldemo/index.php?title=DPL:Manual Dynamic Page List] (DPL). This extension uses it's own form of markup on a page to create a dynamic list using the content and names of other pages in a wiki's database. There is an option in DPL to access content from the server's cache, and that option has been set to be always on at Heroes Wiki. Thus, if a template uses DPL on a page, the server's cache of that page must be cleared for changes to be immediately viewable. If the DPL is adding pages based on whether a page has been added to a category, removing a page from the list may require not only purging the page containing the DPL markup, but also purging the category of the page that has been removed and/or the page that has been removed itself. Like with the previous situation, the server's cache will eventually auto-update the DPL listings; but if that is not desired, purging can be applied.

			There are a few ways on Heroes Wiki for ordinary users or unregistered visitors to purge the server's cache.

			From any Heroes Wiki page:
			:# At the end of the [[URL]] in the address bar of your browser, append the text <tt>?action=purge</tt>
			:# Press [Enter] or click "Go" to tell the browser to go to that revised URL
			:# The page should be refreshed in a short time

			or:
			:# Click the "edit this page" tab
			:# In the address bar in your browser, at the end of the URL, where you see <tt>&action=edit</tt>, replace "edit" with "purge," so it now reads <tt>&action=purge</tt>
			:# Press [Enter] or click "Go" to tell the browser to go to that revised URL
			:# The page should be refreshed in a short time

			From editable pages:
			:# Click the "edit this page" tab and preview the page
			:# Then click save without making any changes. No changes will be saved, but the cache will have been cleared.

	==See Also==		==See Also==

imported>MiamiVolts: add some more; almost done

2008-12-15T01:26:35Z

add some more; almost done

← Older revision		Revision as of 01:26, 15 December 2008
Line 8:		Line 8:

	==Server caching==		==Server caching==
			Heroes Wiki pages can use multiple templates and multiple categories meaning the server has to compile information from multiple sources in order to completely display a page. To lessen the load this would normally imply, the Heroes Wiki server uses caching such that whenever a page is saved on the wiki, a complete copy of the page is put into server cache. Subsequent viewings of the saved page then refer to the server's cache of that page until a portion of the page is re-edited or that page's cache is purged.
	Heroes Wiki's server also has its own cache to minimize server load. Many Heroes Wiki pages use multiple templates.

			There are a couple of exceptions to that description of server caching. One of the extensions Heroes Wiki uses is [http://semeb.com/dpldemo/index.php?title=DPL:Manual Dynamic Page List] (DPL). This extension uses it's own form of markup on a page to create a dynamic list using the content and names of other pages in a wiki's database. There is an option in DPL to access content from the server's cache, and that option has been set to be always on at Heroes Wiki.
	{{sectstub}}		{{sectstub}}

imported>MiamiVolts: begin work on a new help

2008-12-15T00:49:32Z

begin work on a new help

New page

__NOEDITSECTION__{{helpbox}}
Heroes Wiki eases its bandwidth and server load requirements by using '''caching'''.

==Browser caching==
The main means by which Heroes Wiki uses caching is by allowing users' internet browsers to keep a cache of its articles and other pages on the users' local machines. Many browsers have an option to store pages in a local cache for later viewing and may also refer to that cache instead of the wiki itself on previous viewings depending on the browser's settings. Depending on a user's browser, clicking "refresh" or "reload" on the browser may normally bring up the latest version of a Heroes Wiki page. Browsers often include options for how page text content is stored, but do not always have options for images, audio files, and software scripts. For those browsers, bypassing or clearing the cache completely may be the only way to immediately access an updated image or audio file. Wikipedia has [[Wikipedia:Wikipedia:Bypass your cache|instructions]] for doing so for the main types of browsers.

Changes to software scripts on Heroes Wiki pages also often require clearing the browser cache, and sometimes a restart of the browser itself as the code may still be running in the browser even after the cache is cleared. Heroes Wiki uses a scripting called [[Wikipedia:Cascading Style Sheets|cascading style sheets]] (CSS) to add default style formatting to Heroes Wiki pages. In addition, Heroes Wiki uses JavaScript to add other features such as [[Help:Collapsible tables|collapsible tables]].

==Server caching==
Heroes Wiki's server also has its own cache to minimize server load. Many Heroes Wiki pages use multiple templates.
{{sectstub}}

==See Also==
* [[Wikipedia:Wikipedia:Purge|Wikipedia's help on purging]]
* [[Wikipedia:Wikipedia:Bypass your cache|Wikipedia's help on bypassing cache]]
{{nousercat|Help}}