You can tweak elements of most Portal pages by using queries. You can add a query at the end of your URLs to configure how the page and content will be displayed.
Usually, this is accomplished in your Portal Skin or using a Message Snippet when communicating via email.
https://my.example.com/portal/online_giving.aspx?template=special_event
You can find the values for all of the filter options by looking in MinistryPlatform. For example, you can copy the desired Congregation ID# found in MinistryPlatform > Church Structure > Congregation.
The whole query string starts with "?" and follows aspx in the page's file-name. All following settings are separated with "&" symbols. A common mistake is to introduce an extra "?" symbol after the initial one.
https://my.example.com/portal/online_giving.aspx?template=special_event&remembertemplate=true&filter=campus:1
In the example above, there are three queries (only the first one starts with "?" and the others start with "&"):
Some pages support a special query for filtering the values or selecting defaults that are present on that page. The available options are specific to the page and determine how the content is displayed. This type of query looks like this (filter=):
https://my.example.com/portal/online_giving.aspx?template=giving&filter=campus:1
You can use multiple queries together. Each query name/value pair needs to be separated with the “|” pipe character. For example, you can use a campus and purpose to create links directly to a specific online giving item:
https://my.example.com/portal/online_giving.aspx?template=giving&filter=campus:1|purpose:289|amount:100
In the above example, there are three queries. The first one is introduced with "filter=" and has no pipe. Additional filters start with a pipe. Each filter includes a label and value separated by a colon:
There are other items that can also be used to filter, depending on the page you are on:
Various Filters are available for the following pages. Note that Filters are specific to each page, and only include the values or defaults that are present on that page:
It is possible to use multiple skins at the same time. Some multi-site churches like to brand each campus with different colors or websites. The Portal can be tuned to allow these different websites to each have access to the same Portal, but with different skins. Another example is having a specific Portal page (e.g., Opportunity Details page for a specific Opportunity) skinned differently than the rest of the Portal.
To accomplish this, you would create multiple skins with customized URLs in your menus. This can be combined with filters (above). You could also create a stripped-down skin and have it in either an iframe or a popup window.
This process works on any page ending in aspx. It does not work on the Portal root.
To use a skin other than the default (set in the Portal Admin page) add the following after aspx:
?template=[your skin name here]
To make this stick temporarily, you can add the following query. The non-default skin will be remembered for the duration of your browser session, but not affect anyone else.
&remembertemplate=true
After a user visits a URL with this switch, they will no longer see the default skin unless they are directed to a URL which resets the skin settings to the default (unless you have a skin named "default." In this case, it just sets the skin temporarily to the skin named "default").
?template=default
For example, this url uses the "NewWine" skin to display Event 9999. The change will stay in effect until the user closes the browser or session times out on the server (due to user inactivity).
https://my.example.com/portal/event_detail.aspx?id=9999&template=NewWine&remebertemplate=true&filter=month:2|year:2017|campus:0|ministry:0|listview:0|featuredevents:0
Notice that the skin settings can be incorporated into the url with other settings (query strings).
The whole query string starts with "?" and follows aspx in the page's file-name. All following settings are separated with "&" symbols. A common mistake is to introduce an extra "?" symbol after the initial one.
The example above can be broken down into 4 parts (only the first one starts with "?" and the others start with "&"):
When you have issues with the default skin, you can always override this in the URL and reset the session to use a working skin (such as "Responsive").
Use the following URL to reset your default:
/portal/site_index.aspx?template=Responsive&remembertemplate=true
