Jump to content
  • Announcements

    • terry

      Invision Theme Demo Site   06/17/2016

      TPP Themes provides this forum for a demo of my themes create for Invision Power Software.

terry

Administrators
  • Content count

    6,318
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by terry

  1. President Donald Trump is promoting a conservative argument that he's been "victimized" by the Obama administration through its allegedly flawed application for a surveillance warrant on a former campaign foreign policy adviser. View the full article
  2. Two Ohio police officers, who were referred to as "true American heroes," died while responding to a call in Westerville on Saturday, police said. View the full article
  3. Valentine’s Day will be here in a heartbeat, and the freshest flowers will be gone from store shelves even sooner. View the full article
  4. A Northern California school district is investigating the display of a controversial science fair project that some students, parents and staff say is racially insensitive. View the full article
  5. Westerville police have confirmed that two officers have been fatally shot Saturday at a home in this Columbus suburb. View the full article
  6. The immediate result of President Donald Trump's decision to block the release of a Democratic memo on the Russia investigation is to expose him to charges of hypocrisy. View the full article
  7. As police tried to serve an arrest warrant at a home outside of Atlanta, the criminal suspect became combative and both sides started shooting, resulting in the death of an officer and the suspect, authorities said. View the full article
  8. Suzy Cairns, at sentencing, insisted that a video session with her dog has been “exaggerated," said a report in The Sun. View the full article
  9. President Donald Trump sounded his campaign battle cry of "drain the swamp" again Saturday morning in response to an article about US spies attempting to recover stolen US cyberweapons. View the full article
  10. A 19-year-old Washington state man, who police say raped a high school student as she died from a drug overdose and texted semi-nude photos of her, has been charged with manslaughter. View the full article
  11. Matthew Rosenberg of The New York Times reports that US spies, in an effort to retrieve cyberweapons stolen by Russia, were scammed out of $100,000 by a Russian who promised to deliver cyberweapons and damaging information on President Donald Trump. View the full article
  12. If there's been one consistent thing about Donald Trump since he emerged as a presidential candidate in June 2015, it's this: When women accuse men of sexual assault or domestic abuse, Trump sides with the men. View the full article
  13. President Donald Trump took to Twitter Saturday to lament "lives are being shattered" by a mere allegation in the wake of the resignations of former White House staff secretary Rob Porter and speechwriter David Sorensen following allegations of domestic abuse. View the full article
  14. Rep. Adam Schiff, D-Calif., the top Democrat on the House Intelligence Committee, has been leading the charge against the GOP memo, calling it a "political hit job" on the FBI. View the full article
  15. A judge has ordered a father to arrange a funeral for his 14-year-old daughter, whose body has languished in the Milwaukee County morgue for two months amid a dispute between her parents. View the full article
  16. The case against Big Tech seems to be building by the week. And interestingly, some of the most powerful evidence is being provided by those who really know what they’re talking about: tech insiders. View the full article
  17. David Sorensen, a member of the Trump administration's speechwriting team, has resigned after being accused of domestic abuse, a White House official says. View the full article
  18. Amid continuing fallout from the Rob Porter scandal, Donald Trump has come to the defense of longtime confidante and White House communications director Hope Hicks, despite reports that the President was growing frustrated with her role in the situation. View the full article
  19. The White House is gripped with internal tumult over the handling of domestic abuse allegations against a top aide, with furor centered on two top officials, according to people familiar with the matter. View the full article
  20. Former Vice President Joe Biden spoke out against President Trump's response to Rob Porter's resignation. Porter was accused by two ex-wives of physical and emotional abuse. He has denied the accusations. View the full article
  21. "No man is an island" wrote John Donne. He wrote that a good 200 years before computers were invented, but it rings true for any well written framework like Invision Community. The included REST API allows developers to fetch data from Invision Community and also allows data to be added. This data can be used to power widgets on your website, or to be used within other applications you are already using in a very simple way. Several enhancements have been made to the REST API for Invision Community 4.3 that we wanted to let you know about. These changes are developer-oriented, so if you do not use the REST API with your community please feel free to skip this update. If you would like to learn more about the REST API available with Invision Community, please see our REST documentation. Search capabilities As previously noted, you can now perform searches through the REST API. You can perform searches based on keywords, tags, or both, and you can limit and filter results with parameters similar to when you perform a regular search on the site (e.g. to specific containers, returning only results over a set number of comments, or searching within clubs). Permission awareness Several REST API endpoints are now permission-aware when combined with Oauth functionality built into Invision Community 4.3. This means that many REST API endpoints can be called using a specific user's access token, and only results that the specific user would normally be able to see will be returned (and/or they will only be able to submit to areas they normally have permission to). Ability to search members While an endpoint has always been available to retrieve (and add/edit/delete) members, the ability to search for members has now been implemented. You can search by name, email address, and (one or more) group(s), and a paginated response will be returned. Private conversations You can now start a new private conversation, reply to an existing private conversation, and delete a private conversation through the REST API. Other REST API changes You can now specify member's secondary groups when adding or updating a member through the REST API. You can specify the member's registration IP address through the REST API when adding or updating a member. You can now specify other member properties not directly exposed through the REST API when adding or updating a member by setting the rawProperties input field. You can now specify other member properties to retrieve through the REST API through the otherFields request parameter. The REST API now better logs changes to member accounts (so you will be able to more easily identify how a user's name, email address, password, etc. has changed when looking at the member history). You can now retrieve all content a member is following through the REST API, as well as follow a new container/content item, and delete an existing follow. You can now validate an account through the REST API You can now specify a 'perPage' parameter for paginated responses to control how many items are returned per page. Most of these changes were directly culled from client feedback and implemented per specific requests. If there are other REST API changes you would like to see implemented please don't hesitate to leave your feedback! View the full article
  22. "No man is an island" wrote John Donne. He wrote that a good 200 years before computers were invented, but it rings true for any well written framework like Invision Community. The included REST API allows developers to fetch data from Invision Community and also allows data to be added. This data can be used to power widgets on your website, or to be used within other applications you are already using in a very simple way. Several enhancements have been made to the REST API for Invision Community 4.3 that we wanted to let you know about. These changes are developer-oriented, so if you do not use the REST API with your community please feel free to skip this update. If you would like to learn more about the REST API available with Invision Community, please see our REST documentation. Search capabilities As previously noted, you can now perform searches through the REST API. You can perform searches based on keywords, tags, or both, and you can limit and filter results with parameters similar to when you perform a regular search on the site (e.g. to specific containers, returning only results over a set number of comments, or searching within clubs). Permission awareness Several REST API endpoints are now permission-aware when combined with Oauth functionality built into Invision Community 4.3. This means that many REST API endpoints can be called using a specific user's access token, and only results that the specific user would normally be able to see will be returned (and/or they will only be able to submit to areas they normally have permission to). Ability to search members While an endpoint has always been available to retrieve (and add/edit/delete) members, the ability to search for members has now been implemented. You can search by name, email address, and (one or more) group(s), and a paginated response will be returned. Private conversations You can now start a new private conversation, reply to an existing private conversation, and delete a private conversation through the REST API. Other REST API changes You can now specify member's secondary groups when adding or updating a member through the REST API. You can specify the member's registration IP address through the REST API when adding or updating a member. You can now specify other member properties not directly exposed through the REST API when adding or updating a member by setting the rawProperties input field. You can now specify other member properties to retrieve through the REST API through the otherFields request parameter. The REST API now better logs changes to member accounts (so you will be able to more easily identify how a user's name, email address, password, etc. has changed when looking at the member history). You can now retrieve all content a member is following through the REST API, as well as follow a new container/content item, and delete an existing follow. You can now validate an account through the REST API You can now specify a 'perPage' parameter for paginated responses to control how many items are returned per page. Most of these changes were directly culled from client feedback and implemented per specific requests. If there are other REST API changes you would like to see implemented please don't hesitate to leave your feedback! View the full article
  23. "No man is an island" wrote John Donne. He wrote that a good 200 years before computers were invented, but it rings true for any well written framework like Invision Community. The included REST API allows developers to fetch data from Invision Community and also allows data to be added. This data can be used to power widgets on your website, or to be used within other applications you are already using in a very simple way. Several enhancements have been made to the REST API for Invision Community 4.3 that we wanted to let you know about. These changes are developer-oriented, so if you do not use the REST API with your community please feel free to skip this update. If you would like to learn more about the REST API available with Invision Community, please see our REST documentation. Search capabilities As previously noted, you can now perform searches through the REST API. You can perform searches based on keywords, tags, or both, and you can limit and filter results with parameters similar to when you perform a regular search on the site (e.g. to specific containers, returning only results over a set number of comments, or searching within clubs). Permission awareness Several REST API endpoints are now permission-aware when combined with Oauth functionality built into Invision Community 4.3. This means that many REST API endpoints can be called using a specific user's access token, and only results that the specific user would normally be able to see will be returned (and/or they will only be able to submit to areas they normally have permission to). Ability to search members While an endpoint has always been available to retrieve (and add/edit/delete) members, the ability to search for members has now been implemented. You can search by name, email address, and (one or more) group(s), and a paginated response will be returned. Private conversations You can now start a new private conversation, reply to an existing private conversation, and delete a private conversation through the REST API. Other REST API changes You can now specify member's secondary groups when adding or updating a member through the REST API. You can specify the member's registration IP address through the REST API when adding or updating a member. You can now specify other member properties not directly exposed through the REST API when adding or updating a member by setting the rawProperties input field. You can now specify other member properties to retrieve through the REST API through the otherFields request parameter. The REST API now better logs changes to member accounts (so you will be able to more easily identify how a user's name, email address, password, etc. has changed when looking at the member history). You can now retrieve all content a member is following through the REST API, as well as follow a new container/content item, and delete an existing follow. You can now validate an account through the REST API You can now specify a 'perPage' parameter for paginated responses to control how many items are returned per page. Most of these changes were directly culled from client feedback and implemented per specific requests. If there are other REST API changes you would like to see implemented please don't hesitate to leave your feedback! View the full article
  24. "No man is an island" wrote John Donne. He wrote that a good 200 years before computers were invented, but it rings true for any well written framework like Invision Community. The included REST API allows developers to fetch data from Invision Community and also allows data to be added. This data can be used to power widgets on your website, or to be used within other applications you are already using in a very simple way. Several enhancements have been made to the REST API for Invision Community 4.3 that we wanted to let you know about. These changes are developer-oriented, so if you do not use the REST API with your community please feel free to skip this update. If you would like to learn more about the REST API available with Invision Community, please see our REST documentation. Search capabilities As previously noted, you can now perform searches through the REST API. You can perform searches based on keywords, tags, or both, and you can limit and filter results with parameters similar to when you perform a regular search on the site (e.g. to specific containers, returning only results over a set number of comments, or searching within clubs). Permission awareness Several REST API endpoints are now permission-aware when combined with Oauth functionality built into Invision Community 4.3. This means that many REST API endpoints can be called using a specific user's access token, and only results that the specific user would normally be able to see will be returned (and/or they will only be able to submit to areas they normally have permission to). Ability to search members While an endpoint has always been available to retrieve (and add/edit/delete) members, the ability to search for members has now been implemented. You can search by name, email address, and (one or more) group(s), and a paginated response will be returned. Private conversations You can now start a new private conversation, reply to an existing private conversation, and delete a private conversation through the REST API. Other REST API changes You can now specify member's secondary groups when adding or updating a member through the REST API. You can specify the member's registration IP address through the REST API when adding or updating a member. You can now specify other member properties not directly exposed through the REST API when adding or updating a member by setting the rawProperties input field. You can now specify other member properties to retrieve through the REST API through the otherFields request parameter. The REST API now better logs changes to member accounts (so you will be able to more easily identify how a user's name, email address, password, etc. has changed when looking at the member history). You can now retrieve all content a member is following through the REST API, as well as follow a new container/content item, and delete an existing follow. You can now validate an account through the REST API You can now specify a 'perPage' parameter for paginated responses to control how many items are returned per page. Most of these changes were directly culled from client feedback and implemented per specific requests. If there are other REST API changes you would like to see implemented please don't hesitate to leave your feedback! View the full article
  25. "No man is an island" wrote John Donne. He wrote that a good 200 years before computers were invented, but it rings true for any well written framework like Invision Community. The included REST API allows developers to fetch data from Invision Community and also allows data to be added. This data can be used to power widgets on your website, or to be used within other applications you are already using in a very simple way. Several enhancements have been made to the REST API for Invision Community 4.3 that we wanted to let you know about. These changes are developer-oriented, so if you do not use the REST API with your community please feel free to skip this update. If you would like to learn more about the REST API available with Invision Community, please see our REST documentation. Search capabilities As previously noted, you can now perform searches through the REST API. You can perform searches based on keywords, tags, or both, and you can limit and filter results with parameters similar to when you perform a regular search on the site (e.g. to specific containers, returning only results over a set number of comments, or searching within clubs). Permission awareness Several REST API endpoints are now permission-aware when combined with Oauth functionality built into Invision Community 4.3. This means that many REST API endpoints can be called using a specific user's access token, and only results that the specific user would normally be able to see will be returned (and/or they will only be able to submit to areas they normally have permission to). Ability to search members While an endpoint has always been available to retrieve (and add/edit/delete) members, the ability to search for members has now been implemented. You can search by name, email address, and (one or more) group(s), and a paginated response will be returned. Private conversations You can now start a new private conversation, reply to an existing private conversation, and delete a private conversation through the REST API. Other REST API changes You can now specify member's secondary groups when adding or updating a member through the REST API. You can specify the member's registration IP address through the REST API when adding or updating a member. You can now specify other member properties not directly exposed through the REST API when adding or updating a member by setting the rawProperties input field. You can now specify other member properties to retrieve through the REST API through the otherFields request parameter. The REST API now better logs changes to member accounts (so you will be able to more easily identify how a user's name, email address, password, etc. has changed when looking at the member history). You can now retrieve all content a member is following through the REST API, as well as follow a new container/content item, and delete an existing follow. You can now validate an account through the REST API You can now specify a 'perPage' parameter for paginated responses to control how many items are returned per page. Most of these changes were directly culled from client feedback and implemented per specific requests. If there are other REST API changes you would like to see implemented please don't hesitate to leave your feedback! View the full article
×