Jump to content
Search In
  • More options...
Find results that contain...
Find results in...

Jon Erickson

  • Posts

  • Joined

  • Last visited

  • Days Won


Jon Erickson last won the day on July 3

Jon Erickson had the most liked content!


Recent Profile Visitors

2932 profile views

Jon Erickson's Achievements


Proficient (10/14)

  • Very Popular Rare
  • Dedicated Rare
  • First Post
  • Conversation Starter
  • Collaborator

Recent Badges




Community Answers

  1. Yes, the email is still posted to the application forum. We can add some settings to disable this functionality but for the time being, you should set the forum to private to protect the data.
  2. You can turn off the email block in the personnel settings!
  3. @Midnight667, each roster has its own sort settings. You can adjust the sort settings by editing the individual roster you are looking at.
  4. We are hoping real soon. We are working to support PHP 8 in this release as well so there is a lot of tedious working going on!
  5. Hey @Midnight667, our next release will make the enlistment application fully customizable. Thanks!
  6. @iTzHoLT, all templates are accessible in the themes section of your ACP. The template you are looking for is soldierRow.
  7. Okay great - I’ll update the application to make sure the from name is in quotes. Do you mind sharing your community name so I can use it as a test to make sure the update is working correctly? Thanks.
  8. Hi @Timothy Kiselev, can you confirm if you temporarily remove the comma, the emails will send?
  9. Yes, exactly. The dev folder is the “source” for the compiled application and that’s why it’s kept out of the finished build process. Unfortunately I don’t see an easier way as well. But your case is extremely rare and not everybody is trying to develop an application to work with another. Haha. As long as you are not developing the front end, you can keep the application out of IN_DEV when you’re developing - which is where most of the work happens.
  10. Yes, I am referring to the REST API. As far as the source files, unfortunately, those are kept in-house and are not public, including the dev folder. It would give a user complete access to rip of PERSCOM and copy the application. Obviously, this probably would not be an issue but we have to draw the line somewhere. Yes, PERSCOM is 4.6 compatible. IPS Dev Toolbox is not even 4.5 compatible. Are you developing a custom IPB application or completely separate from IPB? As for the licensing error, no, you will not get an error if you are just using the development license. You will just be restricted in the amount of data that can be added to the application.
  11. You will receive a licensing error once the cache expires (30 days) due to the installation path and URL not matching your license. I would highly suggest using the PERSCOM API that is built into IPB to consume the data you have stored on your live site.
  12. We are excited to announce the release of our Single Sign On (SSO) application for WHMCS. Powered with Okta, Single Sign On with Okta allows your clients a seamless and secure login experience using only one set of login credentials.… https://www.deschutesdesigngroup.com/single-sign-on-with-okta-released-for-whmcs/
  13. Great - we’ll add this to our development roadmap. Thanks!
  14. PERSCOM has been officically updated and ready to support Invision Power Board 4.6. Head on over to the marketpalce to download and update your version. Invision Power Board is currently only in Beta so downloand and install at your own risk. Please make sure to make backups. https://invisioncommunity.com/files/file/9776-perscom-soldier-management-system/
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.