From e970fa1b5387f729330c782c396ed97cf5df0ebd Mon Sep 17 00:00:00 2001 From: Tom Fox Date: Wed, 5 Jun 2019 18:07:32 +0100 Subject: [PATCH] Remove unneeded parse.com references (#620) * change email * removing a bunch of references * removed more references --- _config.yml | 2 +- _includes/android/push-notifications.md | 8 ++++---- _includes/android/queries.md | 4 ---- _includes/cloudcode/cloud-code-advanced.md | 4 ++-- _includes/common/errors.md | 3 --- _includes/common/sessions.md | 4 ++-- _includes/dotnet/push-notifications.md | 10 +++++----- _includes/dotnet/queries.md | 4 ---- _includes/header.html | 2 +- _includes/ios/push-notifications.md | 2 +- _includes/ios/queries.md | 4 ---- _includes/js/push-notifications.md | 6 +++--- _includes/js/queries.md | 4 ---- _includes/menu.html | 9 ++------- _includes/parse-server/push-notifications.md | 4 ++-- _includes/php/push-notifications.md | 18 +++++++++--------- _includes/php/queries.md | 4 ---- _includes/rest/push-notifications.md | 8 ++++---- _includes/rest/queries.md | 4 ---- _includes/rest/quick-reference.md | 2 +- _includes/rest/sessions.md | 4 ++-- _includes/unity/push-notifications.md | 8 ++++---- _includes/unity/queries.md | 4 ---- css/docs.scss | 2 +- css/guide.scss | 2 +- 25 files changed, 45 insertions(+), 81 deletions(-) diff --git a/_config.yml b/_config.yml index 25e3f4dc0..ab9e91241 100644 --- a/_config.yml +++ b/_config.yml @@ -8,7 +8,7 @@ # Site settings name: Parse Platform Docs title: Parse Docs -email: community@parse.com +email: community@parseplatform.org description: The open source docs for the Parse platform SDKs & other guides. url: "http://docs.parseplatform.org" # the base hostname & protocol for your site repository: parse-community/docs diff --git a/_includes/android/push-notifications.md b/_includes/android/push-notifications.md index ad2867f06..eadf19e7b 100644 --- a/_includes/android/push-notifications.md +++ b/_includes/android/push-notifications.md @@ -43,13 +43,13 @@ The Parse Android SDK will avoid making unnecessary requests. If a `ParseInstall There are two ways to send push notifications using Parse: [channels](#using-channels) and [advanced targeting](#using-advanced-targeting). Channels offer a simple and easy to use model for sending pushes, while advanced targeting offers a more powerful and flexible model. Both are fully compatible with each other and will be covered in this section. -Sending notifications is often done from the Parse.com push console, the [REST API]({{ site.baseUrl }}/rest/guide/#sending-pushes) or from [Cloud Code]({{ site.baseUrl }}/js/guide/#sending-pushes). However, push notifications can also be triggered by the existing client SDKs. If you decide to send notifications from the client SDKs, you will need to set **Client Push Enabled** in the Push Notifications settings of your Parse app. +Sending notifications is often done from the Parse Dashboard push console, the [REST API]({{ site.baseUrl }}/rest/guide/#sending-pushes) or from [Cloud Code]({{ site.baseUrl }}/js/guide/#sending-pushes). However, push notifications can also be triggered by the existing client SDKs. If you decide to send notifications from the client SDKs, you will need to set **Client Push Enabled** in the Push Notifications settings of your Parse app. -However, be sure you understand that enabling Client Push can lead to a security vulnerability in your app, as outlined [on our blog](http://blog.parse.com/2014/09/03/the-dangerous-world-of-client-push/). We recommend that you enable Client Push for testing purposes only, and move your push notification logic into Cloud Code when your app is ready to go into production. +However, be sure you understand that enabling Client Push can lead to a security vulnerability in your app. We recommend that you enable Client Push for testing purposes only, and move your push notification logic into Cloud Code when your app is ready to go into production. -You can view your past push notifications on the Parse.com push console for up to 30 days after creating your push. For pushes scheduled in the future, you can delete the push on the push console as long as no sends have happened yet. After you send the push, the push console shows push analytics graphs. +You can view your past push notifications on the Parse Dashboard push console for up to 30 days after creating your push. For pushes scheduled in the future, you can delete the push on the push console as long as no sends have happened yet. After you send the push, the push console shows push analytics graphs. ### Using Channels @@ -366,7 +366,7 @@ To track push opens, you should always pass the `Intent` to `trackAppOpened`. Pa Please be sure to set up your application to [save the Installation object](#installations). Push open tracking only works when your application's devices are associated with saved `Installation` objects. -You can view the open rate for a specific push notification on your Parse.com push console. You can also view your application's overall app open and push open graphs on the Parse analytics console. Our push open analytics graphs are rendered in real time, so you can easily verify that your application is sending the correct analytics events before your next release. +You can view the open rate for a specific push notification on your Parse Dashboard push console. You can also view your application's overall app open and push open graphs on the Parse analytics console. Our push open analytics graphs are rendered in real time, so you can easily verify that your application is sending the correct analytics events before your next release. ## Push Experiments diff --git a/_includes/android/queries.md b/_includes/android/queries.md index d4f93bb4b..a023d28a4 100644 --- a/_includes/android/queries.md +++ b/_includes/android/queries.md @@ -207,10 +207,6 @@ query.whereContainsAll("arrayKey", numbers); ## Queries on String Values -
- If you're trying to implement a generic search feature, we recommend taking a look at this blog post: Implementing Scalable Search on a NoSQL Backend. -
- Use `whereStartsWith` to restrict to string values that start with a particular string. Similar to a MySQL LIKE operator, this is indexed so it is efficient for large datasets: ```java diff --git a/_includes/cloudcode/cloud-code-advanced.md b/_includes/cloudcode/cloud-code-advanced.md index beb6dca70..9204c5f49 100644 --- a/_includes/cloudcode/cloud-code-advanced.md +++ b/_includes/cloudcode/cloud-code-advanced.md @@ -8,7 +8,7 @@ A simple GET request would look like: ```javascript Parse.Cloud.httpRequest({ - url: 'http://www.parse.com/' + url: 'http://www.awesomewebsite.com/' }).then(function(httpResponse) { // success console.log(httpResponse.text); @@ -24,7 +24,7 @@ A GET request that specifies the port number would look like: ```javascript Parse.Cloud.httpRequest({ - url: 'http://www.parse.com:8080/' + url: 'http://www.awesomewebsite.com:8080/' }).then(function(httpResponse) { console.log(httpResponse.text); }, function(httpResponse) { diff --git a/_includes/common/errors.md b/_includes/common/errors.md index 3693c6c5d..1e427a764 100644 --- a/_includes/common/errors.md +++ b/_includes/common/errors.md @@ -162,9 +162,6 @@ The following is a list of all the error codes that can be returned by the Parse |----------------------------------|------|---------------------------------------------------------------| | `RequestTimeout` | 124 | The request was slow and timed out. Typically this indicates that the request is too expensive to run. You may see this when a Cloud function did not finish before timing out, or when a `Parse.Cloud.httpRequest` connection times out. | | `InefficientQueryError` | 154 | An inefficient query was rejected by the server. Refer to the Performance Guide and slow query log. | -| `RequestLimitExceeded` | 155 | This application has exceeded its request limit (legacy Parse.com apps only). | -| `TemporaryRejectionError` | 159 | An application's requests are temporary rejected by the server (legacy Parse.com apps only). | -| `DatabaseNotMigratedError` | 428 | You should migrate your database as soon as possible (legacy Parse.com apps only). | {: .docs_table} ## Other issues diff --git a/_includes/common/sessions.md b/_includes/common/sessions.md index 5ce149d3b..5c2429743 100644 --- a/_includes/common/sessions.md +++ b/_includes/common/sessions.md @@ -1,6 +1,6 @@ # Sessions -Sessions represent an instance of a user logged into a device. Sessions are automatically created when users log in or sign up. They are automatically deleted when users log out. There is one distinct `Session` object for each user-installation pair; if a user issues a login request from a device they're already logged into, that user's previous `Session` object for that Installation is automatically deleted. `Session` objects are stored on Parse in the Session class, and you can view them on the Parse.com Data Browser. We provide a set of APIs to manage `Session` objects in your app. +Sessions represent an instance of a user logged into a device. Sessions are automatically created when users log in or sign up. They are automatically deleted when users log out. There is one distinct `Session` object for each user-installation pair; if a user issues a login request from a device they're already logged into, that user's previous `Session` object for that Installation is automatically deleted. `Session` objects are stored on Parse in the Session class, and you can view them on the Parse Dashboard Data Browser. We provide a set of APIs to manage `Session` objects in your app. `Session` is a subclass of a Parse `Object`, so you can query, update, and delete sessions in the same way that you manipulate normal objects on Parse. Because the Parse Cloud automatically creates sessions when you log in or sign up users, you should not manually create `Session` objects unless you are building a "Parse for IoT" app (e.g. Arduino or Embedded C). Deleting a `Session` will log the user out of the device that is currently using this session's token. @@ -18,7 +18,7 @@ The `Session` object has these special fields: * `restricted` (readonly): Boolean for whether this session is restricted. * Restricted sessions do not have write permissions on `User`, `Session`, and `Role` classes on Parse. Restricted sessions also cannot read unrestricted sessions. * All sessions that the Parse Cloud automatically creates during user login/signup will be unrestricted. All sessions that the developer manually creates by saving a new `Session` object from the client (only needed for "Parse for IoT" apps) will be restricted. -* `expiresAt` (readonly): Approximate UTC date when this `Session` object will be automatically deleted. You can configure session expiration settings (either 1-year inactivity expiration or no expiration) in your app's Parse.com dashboard settings page. +* `expiresAt` (readonly): Approximate UTC date when this `Session` object will be automatically deleted. You can configure session expiration settings (either 1-year inactivity expiration or no expiration) in your app's Parse Dashboard settings page. * `installationId` (can be set only once): String referring to the `Installation` where the session is logged in from. For Parse SDKs, this field will be automatically set when users log in or sign up. All special fields except `installationId` can only be set automatically by the Parse Cloud. You can add custom fields onto `Session` objects, but please keep in mind that any logged-in device (with session token) can read other sessions that belong to the same user (unless you disable Class-Level Permissions, see below). diff --git a/_includes/dotnet/push-notifications.md b/_includes/dotnet/push-notifications.md index 77b29434e..a23ba8e43 100644 --- a/_includes/dotnet/push-notifications.md +++ b/_includes/dotnet/push-notifications.md @@ -57,13 +57,13 @@ While it is possible to modify a `ParseInstallation` just like you would a `Pars There are two ways to send push notifications using Parse: [channels](#using-channels) and [advanced targeting](#using-advanced-targeting). Channels offer a simple and easy to use model for sending pushes, while advanced targeting offers a more powerful and flexible model. Both are fully compatible with each other and will be covered in this section. -Sending notifications is often done from the Parse.com push console, the [REST API]({{ site.baseUrl }}/rest/guide/#sending-pushes) or from [Cloud Code]({{ site.baseUrl }}/js/guide/#sending-pushes). However, push notifications can also be triggered by the existing client SDKs. If you decide to send notifications from the client SDKs, you will need to set **Client Push Enabled** in the Push Notifications settings of your Parse app. +Sending notifications is often done from the Parse Dashboard push console, the [REST API]({{ site.baseUrl }}/rest/guide/#sending-pushes) or from [Cloud Code]({{ site.baseUrl }}/js/guide/#sending-pushes). However, push notifications can also be triggered by the existing client SDKs. If you decide to send notifications from the client SDKs, you will need to set **Client Push Enabled** in the Push Notifications settings of your Parse app. -However, be sure you understand that enabling Client Push can lead to a security vulnerability in your app, as outlined [on our blog](http://blog.parse.com/2014/09/03/the-dangerous-world-of-client-push/). We recommend that you enable Client Push for testing purposes only, and move your push notification logic into Cloud Code when your app is ready to go into production. +However, be sure you understand that enabling Client Push can lead to a security vulnerability in your app. We recommend that you enable Client Push for testing purposes only, and move your push notification logic into Cloud Code when your app is ready to go into production. Settings for the Push client -You can view your past push notifications on the Parse.com push console for up to 30 days after creating your push. For pushes scheduled in the future, you can delete the push on the push console as long as no sends have happened yet. After you send the push, the push console shows push analytics graphs. +You can view your past push notifications on the Parse Dashboard push console for up to 30 days after creating your push. For pushes scheduled in the future, you can delete the push on the push console as long as no sends have happened yet. After you send the push, the push console shows push analytics graphs. ### Using Channels @@ -314,7 +314,7 @@ await wpPush.SendAsync(); ## Scheduling Pushes -Sending scheduled push notifications is not currently supported by the .NET SDK. Take a look at the [REST API]({{ site.baseUrl }}/rest/guide/#scheduling-pushes), [JavaScript SDK]({{ site.baseUrl }}/js/guide/#scheduling-pushes) or the Parse.com push console. +Sending scheduled push notifications is not currently supported by the .NET SDK. Take a look at the [REST API]({{ site.baseUrl }}/rest/guide/#scheduling-pushes), [JavaScript SDK]({{ site.baseUrl }}/js/guide/#scheduling-pushes) or the Parse Dashboard push console. ## Receiving Pushes @@ -379,7 +379,7 @@ To track push opens, you should always pass your event handler's input args to ` Please be sure to set up your application to [save the Installation object](#installations) Push open tracking only works when your application's devices are associated with saved `Installation` objects. -You can view the open rate for a specific push notification on your Parse.com push console. You can also view your application's overall app open and push open graphs on the Parse analytics console. Our push open analytics graphs are rendered in real time, so you can easily verify that your application is sending the correct analytics events before your next release. +You can view the open rate for a specific push notification on your Parse Dashboard push console. You can also view your application's overall app open and push open graphs on the Parse analytics console. Our push open analytics graphs are rendered in real time, so you can easily verify that your application is sending the correct analytics events before your next release. #### Tracking on WinRT Applications diff --git a/_includes/dotnet/queries.md b/_includes/dotnet/queries.md index c64e64d9b..496114072 100644 --- a/_includes/dotnet/queries.md +++ b/_includes/dotnet/queries.md @@ -228,10 +228,6 @@ var query = ParseObject.GetQuery("MyClass") ## Queries on String Values -
- If you're trying to implement a generic search feature, we recommend taking a look at this blog post: Implementing Scalable Search on a NoSQL Backend. -
- Use `WhereStartsWith` or a `StartsWith` LINQ query to restrict to string values that start with a particular string. Similar to a MySQL LIKE operator, this is indexed so it is efficient for large datasets: ```cs diff --git a/_includes/header.html b/_includes/header.html index 97f61a8e7..bda6a4b53 100644 --- a/_includes/header.html +++ b/_includes/header.html @@ -57,7 +57,7 @@ diff --git a/_includes/ios/push-notifications.md b/_includes/ios/push-notifications.md index 6aeb1b306..ac028faa3 100644 --- a/_includes/ios/push-notifications.md +++ b/_includes/ios/push-notifications.md @@ -291,7 +291,7 @@ You can read more about handling push notifications in Apple's [Local and Push N ### Tracking Pushes and App Opens -To track your users' engagement over time and the effect of push notifications, we provide some hooks in the `PFAnalytics` class. You can view the open rate for a specific push notification on the Parse.com push console. You can also view overall app open and push open graphs are on the Parse analytics console. Our analytics graphs are rendered in real time, so you can easily verify that your application is sending the correct analytics events before your next release. +To track your users' engagement over time and the effect of push notifications, we provide some hooks in the `PFAnalytics` class. You can view the open rate for a specific push notification on the Parse Dashboard push console. You can also view overall app open and push open graphs are on the Parse analytics console. Our analytics graphs are rendered in real time, so you can easily verify that your application is sending the correct analytics events before your next release. This section assumes that you've already set up your application to [save the Installation object](#installations). Push open tracking only works when your application's devices are associated with saved `Installation` objects. diff --git a/_includes/ios/queries.md b/_includes/ios/queries.md index 449921b18..8454ef44b 100644 --- a/_includes/ios/queries.md +++ b/_includes/ios/queries.md @@ -530,10 +530,6 @@ query.whereKey("arrayKey", containsAllObjectsIn:[2, 3, 4]) ## Queries on String Values -
- If you're trying to implement a generic search feature, we recommend taking a look at this blog post: Implementing Scalable Search on a NoSQL Backend. -
- Use `whereKey:hasPrefix:` to restrict to string values that start with a particular string. Similar to a MySQL LIKE operator, this is indexed so it is efficient for large datasets:
diff --git a/_includes/js/push-notifications.md b/_includes/js/push-notifications.md index fd993626c..1ea7a2c32 100644 --- a/_includes/js/push-notifications.md +++ b/_includes/js/push-notifications.md @@ -39,13 +39,13 @@ This class has several special fields that help you manage and target devices. There are two ways to send push notifications using Parse: [channels](#using-channels) and [advanced targeting](#using-advanced-targeting). Channels offer a simple and easy to use model for sending pushes, while advanced targeting offers a more powerful and flexible model. Both are fully compatible with each other and will be covered in this section. -Sending notifications is often done from the Parse.com push console, the [REST API](#sending-pushes) or from [Cloud Code](#sending-pushes). Since the JavaScript SDK is used in Cloud Code, this is the place to start if you want to send pushes from your Cloud Functions. However, if you decide to send notifications from the JavaScript SDK outside of Cloud Code or any of the other client SDKs, you will need to set **Client Push Enabled** in the Push Notifications settings of your Parse app. +Sending notifications is often done from the Parse Dashboard push console, the [REST API](#sending-pushes) or from [Cloud Code](#sending-pushes). Since the JavaScript SDK is used in Cloud Code, this is the place to start if you want to send pushes from your Cloud Functions. However, if you decide to send notifications from the JavaScript SDK outside of Cloud Code or any of the other client SDKs, you will need to set **Client Push Enabled** in the Push Notifications settings of your Parse app. -However, be sure you understand that enabling Client Push can lead to a security vulnerability in your app, as outlined [on our blog](http://blog.parse.com/2014/09/03/the-dangerous-world-of-client-push/). We recommend that you enable Client Push for testing purposes only, and move your push notification logic into Cloud Code when your app is ready to go into production. +However, be sure you understand that enabling Client Push can lead to a security vulnerability in your app. We recommend that you enable Client Push for testing purposes only, and move your push notification logic into Cloud Code when your app is ready to go into production. -You can view your past push notifications on the Parse.com push console for up to 30 days after creating your push. For pushes scheduled in the future, you can delete the push on the push console as long as no sends have happened yet. +You can view your past push notifications on the Parse Dashboard push console for up to 30 days after creating your push. For pushes scheduled in the future, you can delete the push on the push console as long as no sends have happened yet. After you send the push, the push console shows push analytics graphs. diff --git a/_includes/js/queries.md b/_includes/js/queries.md index d1d515fae..28f571aa6 100644 --- a/_includes/js/queries.md +++ b/_includes/js/queries.md @@ -183,10 +183,6 @@ query.containsAll("arrayKey", [2, 3, 4]); ## Queries on String Values -
- If you're trying to implement a generic search feature, we recommend taking a look at this blog post: Implementing Scalable Search on a NoSQL Backend. -
- Use `startsWith` to restrict to string values that start with a particular string. Similar to a MySQL LIKE operator, this is indexed so it is efficient for large datasets: ```javascript diff --git a/_includes/menu.html b/_includes/menu.html index a701acbad..8d1a497ae 100644 --- a/_includes/menu.html +++ b/_includes/menu.html @@ -11,12 +11,7 @@

Stay Connected

-If you also specify an `expiration_interval`, it will be calculated from the scheduled push time, not from the time the push is submitted. +If you also specify an `expiration_interval`, it will be calculated from the scheduled push time, not from the time the push is submitted. This means a push scheduled to be sent in a week with an expiration interval of a day will expire 8 days after the request is sent. -The scheduled time cannot be in the past, and can be up to two weeks in the future. -It can be an ISO 8601 date with a date, time, and timezone, as in the example above, or it can be a numeric value representing a UNIX epoch time in seconds (UTC). +The scheduled time cannot be in the past, and can be up to two weeks in the future. +It can be an ISO 8601 date with a date, time, and timezone, as in the example above, or it can be a numeric value representing a UNIX epoch time in seconds (UTC). To schedule an alert for 08/22/2015 at noon UTC time, you can set the `push_time` to either `2015-08-022T12:00:00.000Z` or `1440226800000`. diff --git a/_includes/rest/queries.md b/_includes/rest/queries.md index 329937e66..7f8dda4b1 100644 --- a/_includes/rest/queries.md +++ b/_includes/rest/queries.md @@ -551,10 +551,6 @@ print result ## Queries on String Values -
- If you're trying to implement a generic search feature, we recommend taking a look at this blog post: Implementing Scalable Search on a NoSQL Backend. -
- Use the `$regex` operator to restrict to string values that match a regular expression. Most regular expression queries in Parse are heavily throttled due to performance considerations. Use case sensitive, anchored queries where possible. Similar to a MySQL LIKE operator, anchored queries are indexed so they are efficient for large datasets. For example:
diff --git a/_includes/rest/quick-reference.md b/_includes/rest/quick-reference.md index 92b0dae8e..84ab29f83 100644 --- a/_includes/rest/quick-reference.md +++ b/_includes/rest/quick-reference.md @@ -163,6 +163,6 @@ Whether a request succeeded is indicated by the HTTP status code. A 2xx status c You should not use the REST API Key in client apps (i.e. code you distribute to your customers). If the Parse SDK is available for your client platform, we recommend using our SDK instead of the REST API. If you must call the REST API directly from the client, you should use the corresponding client-side Parse key for that plaform (e.g. Client Key for iOS/Android, or .NET Key for Windows/Xamarin/Unity). -If there is no Parse SDK for your client platform, please use your app's Client Key to call the REST API. Requests made with the Client Key, JavaScript Key, or Windows Key are restricted by client-side app settings that you configure in your Parse.com app dashboard. These settings make your app more secure. For example, we recommend that all production apps turn off the "Client Push Enabled" setting to prevent push notifications from being sent from any device using the Client Key, JavaScript Key, or .NET Key, but not the REST API Key. Therefore, if you plan on registering installations to enable Push Notifications for your app, you should not distribute any app code with the REST API key embedded in it. +If there is no Parse SDK for your client platform, please use your app's Client Key to call the REST API. Requests made with the Client Key, JavaScript Key, or Windows Key are restricted by client-side app settings that you configure in your Parse Dashboard app dashboard. These settings make your app more secure. For example, we recommend that all production apps turn off the "Client Push Enabled" setting to prevent push notifications from being sent from any device using the Client Key, JavaScript Key, or .NET Key, but not the REST API Key. Therefore, if you plan on registering installations to enable Push Notifications for your app, you should not distribute any app code with the REST API key embedded in it. The JavaScript Key cannot be used to make requests directly against the REST API from JavaScript. The JavaScript Key is meant to be used with the Parse JavaScript SDK, which makes its posts through a Cross Origin-friendly format without HTTP headers. diff --git a/_includes/rest/sessions.md b/_includes/rest/sessions.md index 3644662b4..4ffbb2001 100644 --- a/_includes/rest/sessions.md +++ b/_includes/rest/sessions.md @@ -1,6 +1,6 @@ # Sessions -Sessions represent an instance of a user logged into a device. Sessions are automatically created when users log in or sign up. They are automatically deleted when users log out. There is one distinct `Session` object for each user-installation pair; if a user issues a login request from a device they're already logged into, that user's previous `Session` object for that Installation is automatically deleted. `Session` objects are stored on Parse in the Session class, and you can view them on the Parse.com Data Browser. We provide a set of APIs to manage `Session` objects in your app. +Sessions represent an instance of a user logged into a device. Sessions are automatically created when users log in or sign up. They are automatically deleted when users log out. There is one distinct `Session` object for each user-installation pair; if a user issues a login request from a device they're already logged into, that user's previous `Session` object for that Installation is automatically deleted. `Session` objects are stored on Parse in the Session class, and you can view them on the Parse Dashboard Data Browser. We provide a set of APIs to manage `Session` objects in your app. A `Session` is a subclass of a Parse `Object`, so you can query, update, and delete sessions in the same way that you manipulate normal objects on Parse. Because the Parse Cloud automatically creates sessions when you log in or sign up users, you should not manually create `Session` objects unless you are building a "Parse for IoT" app (e.g. Arduino or Embedded C). Deleting a `Session` will log the user out of the device that is currently using this session's token. @@ -18,7 +18,7 @@ The `Session` object has these special fields: * `restricted` (readonly): Boolean for whether this session is restricted. * Restricted sessions do not have write permissions on `User`, `Session`, and `Role` classes on Parse. Restricted sessions also cannot read unrestricted sessions. * All sessions that the Parse Cloud automatically creates during user login/signup will be unrestricted. All sessions that the developer manually creates by saving a new `Session` object from the client (only needed for "Parse for IoT" apps) will be restricted. -* `expiresAt` (readonly): Approximate UTC date when this `Session` object will be automatically deleted. You can configure session expiration settings (either 1-year inactivity expiration or no expiration) in your app's Parse.com dashboard settings page. +* `expiresAt` (readonly): Approximate UTC date when this `Session` object will be automatically deleted. You can configure session expiration settings (either 1-year inactivity expiration or no expiration) in your app's Parse Dashboard settings page. * `installationId` (can be set only once): String referring to the `Installation` where the session is logged in from. For the REST API, you can set this by passing the `X-Parse-Installation-Id` header on login and signup requests. All special fields except `installationId` can only be set automatically by the Parse Cloud. You can add custom fields onto `Session` objects, but please keep in mind that any logged-in device (with session token) can read other sessions that belong to the same user (unless you disable Class-Level Permissions, see below). diff --git a/_includes/unity/push-notifications.md b/_includes/unity/push-notifications.md index 5aae1a58a..5ede4e6dd 100644 --- a/_includes/unity/push-notifications.md +++ b/_includes/unity/push-notifications.md @@ -41,13 +41,13 @@ While it is possible to modify a `ParseInstallation` just like you would a `Pars There are two ways to send push notifications using Parse: [channels](#using-channels) and [advanced targeting](#using-advanced-targeting). Channels offer a simple and easy to use model for sending pushes, while advanced targeting offers a more powerful and flexible model. Both are fully compatible with each other and will be covered in this section. -Sending notifications is often done from the Parse.com push console, the [REST API]({{ site.baseUrl }}/rest/guide/#sending-pushes) or from [Cloud Code]({{ site.baseUrl }}/js/guide/#sending-pushes). However, push notifications can also be triggered by the existing client SDKs. If you decide to send notifications from the client SDKs, you will need to set **Client Push Enabled** in the Push Notifications settings of your Parse app. +Sending notifications is often done from the Parse Dashboard push console, the [REST API]({{ site.baseUrl }}/rest/guide/#sending-pushes) or from [Cloud Code]({{ site.baseUrl }}/js/guide/#sending-pushes). However, push notifications can also be triggered by the existing client SDKs. If you decide to send notifications from the client SDKs, you will need to set **Client Push Enabled** in the Push Notifications settings of your Parse app. -However, be sure you understand that enabling Client Push can lead to a security vulnerability in your app, as outlined [on our blog](http://blog.parse.com/2014/09/03/the-dangerous-world-of-client-push/). We recommend that you enable Client Push for testing purposes only, and move your push notification logic into Cloud Code when your app is ready to go into production. +However, be sure you understand that enabling Client Push can lead to a security vulnerability in your app. We recommend that you enable Client Push for testing purposes only, and move your push notification logic into Cloud Code when your app is ready to go into production. -You can view your past push notifications on the Parse.com push console for up to 30 days after creating your push. For pushes scheduled in the future, you can delete the push on the push console as long as no sends have happened yet. After you send the push, the push console shows push analytics graphs. +You can view your past push notifications on the Parse Dashboard push console for up to 30 days after creating your push. For pushes scheduled in the future, you can delete the push on the push console as long as no sends have happened yet. After you send the push, the push console shows push analytics graphs. ### Using Channels @@ -289,7 +289,7 @@ wpPush.SendAsync(); ## Scheduling Pushes -Sending scheduled push notifications is not currently supported by the .NET SDK. Take a look at the [REST API]({{ site.baseUrl }}/rest/guide/#scheduling-pushes), [JavaScript SDK]({{ site.baseUrl }}/js/guide/#scheduling-pushes) or the Parse.com push console. +Sending scheduled push notifications is not currently supported by the .NET SDK. Take a look at the [REST API]({{ site.baseUrl }}/rest/guide/#scheduling-pushes), [JavaScript SDK]({{ site.baseUrl }}/js/guide/#scheduling-pushes) or the Parse Dashboard push console. ## Receiving Pushes diff --git a/_includes/unity/queries.md b/_includes/unity/queries.md index 35b1f5199..020b3eeab 100644 --- a/_includes/unity/queries.md +++ b/_includes/unity/queries.md @@ -140,10 +140,6 @@ var query = ParseObject.GetQuery("MyClass") ## Queries on String Values -
- If you're trying to implement a generic search feature, we recommend taking a look at this blog post: Implementing Scalable Search on a NoSQL Backend. -
- Use `WhereStartsWith` to restrict to string values that start with a particular string. Similar to a MySQL LIKE operator, this is indexed so it is efficient for large datasets: ```cs diff --git a/css/docs.scss b/css/docs.scss index f399ed2e0..805ec0084 100644 --- a/css/docs.scss +++ b/css/docs.scss @@ -13,7 +13,7 @@ * _\/\\\\\\\\\\\\/____/\\\/___\///\\\_\/\\\_____________\/\\\_ * _\////////////_____\///_______\///__\///______________\///__ * - * Parse.com (Docs) Sass Library + * Parse Docs Sass Library * ============================================================================ */ // ============================================================================ diff --git a/css/guide.scss b/css/guide.scss index 6ae0c7d46..d8f57d792 100644 --- a/css/guide.scss +++ b/css/guide.scss @@ -13,7 +13,7 @@ * _\/\\\\\\\\\\\\/____/\\\/___\///\\\_\/\\\_____________\/\\\_ * _\////////////_____\///_______\///__\///______________\///__ * - * Parse.com (Docs) Sass Library + * Parse Docs Sass Library * ============================================================================ */ // ============================================================================