Support - Revision history

4523550: /* Self-support */ Removing redundant information.

2024-04-11T17:56:39Z

Self-support: Removing redundant information.

@@ Line 7: / Line 7: @@
 The Self-support button allows the user to start background jobs that could potentially fix issues. Each self-support button can be used once per week per user.
-Before using the self-support buttons, the user should be aware that some issues might not be a issue but related to how Project-GC operates.
+More information can be found at [[Self-support]].
 ==Community support==

21934609: Edits for flow.

2023-05-31T00:43:49Z

Edits for flow.

← Older revision		Revision as of 00:43, 31 May 2023
Line 1:		Line 1:
	The orange ~~button labeled~~ '''Support''' is in the top right corner of most pages at [[Project-GC]]~~, it~~ offers several different support ~~options~~.		The orange '''Support''' button is available at the top right corner of most pages at [[Project-GC]]. It offers several different support functions.

	==FAQ==		==FAQ==
	~~This~~ button links to the [https://project-gc.com/Home/FAQ FAQ], ~~this page gives answers to the most~~ frequently asked questions.		The FAQ button links to the [https://project-gc.com/Home/FAQ FAQ], where frequently asked questions are answered.

	==Self-support==		==Self-support==
	~~This~~ button allows the user to start background jobs that could potentially fix ~~some~~ issues. Each ~~Self~~-support button can be used once per week per user.		The Self-support button allows the user to start background jobs that could potentially fix issues. Each self-support button can be used once per week per user.

	Before using the self-support buttons, the user should be aware that some 'issues' might not be a issue but related to how Project-GC ~~works~~.		Before using the self-support buttons, the user should be aware that some issues might not be a issue but related to how Project-GC operates.

	*~~A latency~~ of up to 36 hours is normal~~, for~~ more information see [[Data synchronization]].		*Latency of up to 36 hours is normal. For more information see [[Data synchronization]].
	*Editing of logs takes longer for Project-GC to detect. More information can be found in the [https://project-gc.com/Home/FAQ FAQ].		*Editing of logs takes longer for Project-GC to detect. More information can be found in the [https://project-gc.com/Home/FAQ FAQ].
	*FTFs are detected by log tagging and bookmark lists~~, for~~ more information see [[First to Find#Logging an FTF\|Logging an FTF]].		*FTFs are detected by log tagging and bookmark lists. For more information, see [[First to Find#Logging an FTF\|Logging an FTF]].
	*The [[Profile Stats]] are not generated live and might not be affected by these changed until the next time they render.		*The [[Profile Stats]] are not generated live and might not be affected by these changed until the next time they render.
	*Most pages at Project-GC ~~avoid refetching all information every time they are displayed (~~for performance reasons~~) and~~ may ~~therefore~~ be ~~10 minutes~~ to 1 hour ~~behind~~. These pages take some additional time to update after the background job has completed.		*Most pages on Project-GC use data caching for for performance reasons. Therefore, they may sometimes be up to an hour out-of-date. These pages take some additional time to update after the background job has completed.

	{\| class="wikitable"		{\| class="wikitable"
Line 19:		Line 19:
	\|-		\|-
	\|Refresh number of finds		\|Refresh number of finds
	\|Refreshes which geocaches the user has found~~, this~~ manual job runs a full fetch and will take around 1 minute per 1000 finds.		\|Refreshes which geocaches the user has found. This manual job runs a full fetch and will take around 1 minute per 1000 finds.
	\|-		\|-
	\|Refresh found geocaches		\|Refresh found geocaches
	\|Refreshes data about geocaches that the user has found, ~~this includes~~ logs. This job will correct missing FTFs if the FTFs have been tagged correctly. This will take around 1 hour per 1000 finds.		\|Refreshes data about geocaches that the user has found, including logs. This job will correct missing FTFs if the FTFs have been tagged correctly. This will take around 1 hour per 1000 finds.
	\|-		\|-
	\|Refresh hidden geocaches		\|Refresh hidden geocaches
	\|Refreshes data including logs about geocaches the user has hidden~~, this~~ requires that Project-GC already knows that the user is the hider of the cache. This will take around 1 hour per 1000 hides.		\|Refreshes data including logs about geocaches the user has hidden. This requires that Project-GC already knows that the user is the hider of the cache. This will take around 1 hour per 1000 hides.
	\|-		\|-
	\|Refresh cache notes		\|Refresh cache notes
Line 34:		Line 34:
	\|-		\|-
	\|Refresh		\|Refresh
	\|Refreshes specific geocaches by their ~~GCcode, multiple GCcodes~~ can be run as one job.		\|Refreshes specific geocaches by their reference code. (Multiple reference codes can be run in one job.)

	\|}		\|}

	==Community support==		==Community support==
	~~This~~ button links to the [https://project-gc.com/qa/ Q&A-system], ~~for more informations~~ see [[Community support]].		The Community Support button links to the [https://project-gc.com/qa/ Q&A system]. For more information, see [[Community support]].

	==Project-GC Support==		==Project-GC Support==
	~~For~~ questions ~~about payments~~ or other ~~things~~ that ~~can not~~ be answered by the community~~, this is the option to use~~.		The Project-GC Support button can be used for questions regarding payment, or other topics that cannot be answered by the community.

	~~The support page is a~~ e-mail form ~~where~~ the user should ~~make sure to~~ include as much ~~data~~ as possible to increase the ~~chance~~ that [[Project-GC]] can ~~find~~ and ~~solve~~ the ~~problem~~.		It provides an e-mail based form for the user. They should include as much information as possible to increase the likelihood that [[Project-GC]] can identify and effectively address the issue.

	The support ~~crew mainly speaks~~ '''English''' and '''Swedish''', with some understanding in German. It is preferred that support tickets are written in one of ~~those~~ languages or ~~at least that Google Translate or similar is not used. (i.e. That~~ the user ~~writes in their~~ native language ~~instead of using Google Translate~~.)		The support staff predominantly speak '''English''' and '''Swedish''', with some understanding of '''German'''. It is preferred that support tickets are written in one of the aforementioned languages, or, if impossible, in the user's native language.

	[[Category: Site Info]]		[[Category: Site Info]]

4523550: created page

2020-11-25T10:34:27Z

created page

New page

The orange button labeled '''Support''' is in the top right corner of most pages at [[Project-GC]], it offers several different support options.

==FAQ==
This button links to the [https://project-gc.com/Home/FAQ FAQ], this page gives answers to the most frequently asked questions.

==Self-support==
This button allows the user to start background jobs that could potentially fix some issues. Each Self-support button can be used once per week per user.

Before using the self-support buttons, the user should be aware that some 'issues' might not be a issue but related to how Project-GC works.

*A latency of up to 36 hours is normal, for more information see [[Data synchronization]].
*Editing of logs takes longer for Project-GC to detect. More information can be found in the [https://project-gc.com/Home/FAQ FAQ].
*FTFs are detected by log tagging and bookmark lists, for more information see [[First to Find#Logging an FTF|Logging an FTF]].
*The [[Profile Stats]] are not generated live and might not be affected by these changed until the next time they render.
*Most pages at Project-GC avoid refetching all information every time they are displayed (for performance reasons) and may therefore be 10 minutes to 1 hour behind. These pages take some additional time to update after the background job has completed.

{| class="wikitable"
!colspan="2"|Available self-support buttons
|-
|Refresh number of finds
|Refreshes which geocaches the user has found, this manual job runs a full fetch and will take around 1 minute per 1000 finds.
|-
|Refresh found geocaches
|Refreshes data about geocaches that the user has found, this includes logs. This job will correct missing FTFs if the FTFs have been tagged correctly. This will take around 1 hour per 1000 finds.
|-
|Refresh hidden geocaches
|Refreshes data including logs about geocaches the user has hidden, this requires that Project-GC already knows that the user is the hider of the cache. This will take around 1 hour per 1000 hides.
|-
|Refresh cache notes
|Refreshes information about the users [[personal cache note]]s.
|-
|Refresh corrected coordinates
|Fetches all [[corrected coordinates]] from Geocaching.com.
|-
|Refresh
|Refreshes specific geocaches by their GCcode, multiple GCcodes can be run as one job.

|}

==Community support==
This button links to the [https://project-gc.com/qa/ Q&A-system], for more informations see [[Community support]].

==Project-GC Support==
For questions about payments or other things that can not be answered by the community, this is the option to use.

The support page is a e-mail form where the user should make sure to include as much data as possible to increase the chance that [[Project-GC]] can find and solve the problem.

The support crew mainly speaks '''English''' and '''Swedish''', with some understanding in German. It is preferred that support tickets are written in one of those languages or at least that Google Translate or similar is not used. (i.e. That the user writes in their native language instead of using Google Translate.)

[[Category: Site Info]]