#22 Removed the All About Tracking guide

matomo-org · Feb 15, 2015 · 60b521d · 60b521d
1 parent bf7a1fe
commit 60b521d
Show file tree

Hide file tree

Showing 5 changed files with 4 additions and 158 deletions.
diff --git a/app/helpers/Redirects.php b/app/helpers/Redirects.php
@@ -25,6 +25,7 @@ public static function getRedirects()
             '/guides/mvc-views'                => '/guides/views',
             '/guides/mvc-controllers'          => '/guides/controllers',
             '/guides/all-about-analytics-data' => '/guides/data-model',
+            '/guides/all-about-tracking'       => '/guides/tracking-introduction',
         ];
     }
 }
diff --git a/docs/all-about-tracking.md b/docs/all-about-tracking.md
diff --git a/docs/getting-started-part-1.md b/docs/getting-started-part-1.md
@@ -169,7 +169,7 @@ If you'd like to learn the basics of Piwik plugin development all at once, conti
 - If you're interested in **creating new analytics reports**, you may want to read about [Reports](/guides/reports) and [Visualizing Report Data](/guides/visualizing-report-data) guides.
 - If you're interested in **changing the look and feel of Piwik**, read our [Theming](/guides/theming) guide.
 - If you're interested in **taking part in core development**, read our [Contributing to Piwik Core](/guides/contributing-to-piwik-core) guide.
-- If you're interested in **integrating Piwik with another technology**, you might want to read our [All About Tracking](/guides/all-about-tracking) guide to learn how to use our Tracking API. You might also want to read our [Piwik's HTTP API](/api-reference/tracking-api) guide to learn about Piwik's Reporting API.
+- If you're interested in **integrating Piwik with another technology**, you might want to read our [Tracking guides](/guides/tracking-introduction) to learn how to use our Tracking API.
 - If you'd like to **add new console commands**, read our [Piwik on the command line](/guides/piwik-on-the-command-line) guide.
 - If you want to **use automated testing to ensure your plugin works**, read your [Automated Tests](/guides/tests) guide.
 

diff --git a/docs/persistence-and-the-mysql-backend.md b/docs/persistence-and-the-mysql-backend.md
@@ -274,7 +274,7 @@ In `archive_blob` tables:
 
 **Site** entities contain information regarding a website whose visits are tracked. There won't be nearly as many of these as there are visits and archive data entries, but they will be queried often.
 
-Every reporting request (either through the [Reporting API](/guides/piwiks-reporting-api) or through Piwik's UI) will query one or more site entities. The tracker will only query site data if the [tracker cache](/guides/all-about-tracking#the-tracker-cache) needs to be updated. For most tracking requests, site data will not be queried (thus resulting in greater performance for the tracker).
+Every reporting request (either through the [Reporting API](/guides/piwiks-reporting-api) or through Piwik's UI) will query one or more site entities. The tracker will only query site data if the tracker cache needs to be updated. For most tracking requests, site data will not be queried (thus resulting in greater performance for the tracker).
 
 Site entities are stored in the `site` table and contain the following information:
 
@@ -360,13 +360,12 @@ This association and the persistence logic is implemented by the [LanguagesManag
 
 ### Options
 
-[Options](/api-reference/Piwik/Option) are key-value pairs where the key is a string and the value is a another string (possibly bigger and possibly binary). They are queried on every UI and [Reporting API](/guides/piwiks-reporting-api) request. The tracker will [cache](/guides/all-about-tracking#the-tracker-cache) relevant option values and so will only query options when the cache needs updating.
+[Options](/api-reference/Piwik/Option) are key-value pairs where the key is a string and the value is a another string (possibly bigger and possibly binary). They are queried on every UI and [Reporting API](/guides/piwiks-reporting-api) request. The tracker will cache relevant option values and so will only query options when the cache needs updating.
 
 Some options should be loaded on every non-tracking request. These options have a special **autoload** property set to `1`.
 
 ## Learn more
 
-* To learn **how the tracker inserts log data** see our [All About Tracking](/guides/all-about-tracking) guide.
 * To learn **how log data is aggregated** see our [Archiving](/guides/archiving) guide and take a look at the [LogAggregator](/api-reference/Piwik/DataAccess/LogAggregator) class.
 * To learn **how archive data is cached** see our [Archive Data](/guides/archive-data) guide.
 * To learn **about Piwik's logging utility** see this section in our [Getting started extending Piwik](/guides/getting-started-part-1) guide.

diff --git a/docs/tracking-introduction.md b/docs/tracking-introduction.md
@@ -3,7 +3,6 @@ category: Integrate
 subGuides:
   - tracking-javascript-guide
   - tracking-api-clients
-  - all-about-tracking
   - content-tracking
 ---
 # Tracking your application