Jump to content
Deschutes Design Group LLC Open For Limited Support. All Other Services Closed Until August 2021. ×
Search In
  • More options...
Find results that contain...
Find results in...

All Activity

This stream auto-updates

  1. Last week
  2. I am glad to see this has been added. Please let me know if I can help with any other features.
  3. Earlier
  4. 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.
  5. Ok understandable. The dev folder shouldn't contain anything "secret", it's simply what builds up all the XMLs and JSONs that are then used to load the default theme files, emails and translations in the database when you install the module or revert to the default templates. So that's why I brought up that we can get them anyway, it's just be much simpler if it could be shared so 3rd party developers can run a development IPS environment with PERSCOM installed & enabled. Now we constantly need to switch IN_DEV on to do our changes, build our app, turn IN_DEV off and then see if it worked if we're working on PERSCOM hooks for example. It's a major pain to debug. And yes, it's an IPS application, same as core, forums, pages and PERSCOM. So we can interact with everything on a deeper level and have our own controllers, templates, hooks, database schema, sources, settings,.......
  6. 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.
  7. I assume you're talking about the REST API? Thus far we've always just edited the templates in our theme but we want to go way more in-depth, building an expansion of PERSCOM for our specific needs, working really closely with PERSCOM code. We already migrated a big chunk of our modifications to an application, but we've been holding off on those that require template modifications. So far, it's been smooth sailing with PERSCOM code and it's a lot more semantically correct, more maintainable and a lot more comfortable for a developer to work on. Our previous implementations used the REST API and hackish JavaScript implementations to achieve our goals, but as these modifications grew out of proportions we really needed a more solid foundation so we started developing our own application to fill the gaps. As far as my knowledge goes, the dev folder just holds all the files that you can find in the backend/theme area anyway. It could be extracted using something like the IPS Dev Toolbox but it seems like they're not entirely compatible with 4.6 yet as it's giving me some errors at the moment that I didn't have on 4.5 so I've had to disable that application. Getting it from the source, Deschutes, will probably be the most accurate anyway. So if you won't provide these files, we'll simply have to look at these alternative methods of extraction or manually convert what we can from the default theme. As for the licensing error. On the top of our development version (localhost) we have a banner notifying us we've got a limited PERSCOM development license and limits may apply. Which is fine, it's just for development, nobody but the developer will see that. We never entered any license and didn't copy the database. It's a completely fresh IPS install and fresh PERSCOM install. If it gives issues in 30 days, we can just repeat the process to refresh it I assume?
  8. 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.
  9. Seems like everything is fine in terms of installing without a license, I just exported the application from our production and imported into my localhost dev environment. There's just one thing... We can't enable dev mode without having the PERSCOM dev folder. Is there any way we could get these files so that we can create hooks and interact with PERSCOM code while running IN_DEV = true?
  10. We would love to interact with PERSCOM inside of our application. Our application is developed locally, but on local installs the marketplace is disabled. Is there any way we can run PERSCOM locally so that we can use PERSCOM sources and so on to build on top of it? I suppose licensing would be another issue we'd run into if I were to just copy the PERSCOM application files from our production environment. Has anyone attempted this before? How would I go about getting the marketplace version of PERSCOM on our dev machines? Thanks in advance.
  11. 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/
  12. Great - we’ll add this to our development roadmap. Thanks!
  13. It would be really nice to be able to control every aspect of the enlistment form (without having to edit the file). The first few options (Firstname, Lastname, Email, Location) I really don't have much use for.. I have most, if not all of that based on the member record for IPB. Now, if the enlistment application also handled IPB registrations, that would be pretty cool. But I think just making the enlistment application completely separate and 100% customizable is a better solution. Promotion Point Automation: Unless I am a missing something, promotion points have to be manually assigned to the soldier. This means I have to go create another "tracker" to keep track of points from awards, service records, quals etc. It would be nice to be able to assign a point value to those items so the promotion points are awarded accordingly. I know this opens a can of worms. Because some communities will also want the ability to add arbitrary points based on different things. Such as activity or participation in another event etc. But I feel that the things that I can manage in PERSCOM should be all talking to one another.
  14. Could you please look into a way for a user to create more than one application for when someone wants multiple personnel files.
  15. I have found this. But this still does not allow a member to fill out another application. So having two Personnel files still isn't possible for me. Am I missing something?
  16. 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/
  17. Should be found in the personnel settings if I can recall right. I am not currently in front of a PC.
  18. Where is this option located? Added setting to allow forum members to be assigned to multiple personnel files.
  19. Matthew, I believe we have this fixed for you but for others, you must submit a support ticket and we will run a plug-in to switch the application from manual to marketplace. If you are upgrading/setting up a new installation of IPB, IPB will take you through a similar process.
  20. Yes, that would happen as everything, fronted and a backend are under that module. I will look into it!
  21. So we tried that and it removes the application backend module aswell.. we are looking for the ability to close applications but still be able to process any pending applications
  22. Can you just turn the module “off” under the IPB applications settings?
  23. Yes, this has always been a plan to do! We’ve started the build on it already!
  24. Hi Jon, Is there any chance of adding the option to turn off applications? I.e turn them off and provide a message to people who try to apply saying we are not currently accepting applications or something along them lines? And ofcourse the ability to turn them back on? Maybe make it so its group based or something? Thanks
  25. Glad to hear. Kinda comical how they have refused to fix this bug before there next major release. No hot fix or anything. Seems like an important bug to fix in my opinion.
  26. Hi Jon, is there a way to remove the email part on the application forum post? We are getting some people that are saying they dont want their email public so would be helpful if we had the ability to remove that. Thanks
  1. Load more activity


×
×
  • 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.