wohali

+Clients
  • Content count

    199
  • Joined

  • Last visited

  • Days Won

    1

wohali last won the day on December 4 2015

wohali had the most liked content!

3 Followers

About wohali

  • Rank
    Member
  • Birthday

IPS Marketplace

  • Resources Contributor
    Total file submissions: 5

Recent Profile Visitors

3,065 profile views
  1. No, not easily. To target multiple HTML elements I'd need to instantiate multiple copies of the JS snow effect. This JS implementation is already kind of a pig on browsers, so multiple instances will *really* slow things down. Yeah, I can't test this against all themes out there...especially commercial ones that I don't have the budget to purchase. Sorry about that :/
  2. New Snow version 1.2.0 posted. Changelog: New feature to enable/disable snow on specific themes only.
  3. I worked out how to add this functionality. Just finishing testing; the new version will be uploaded within the next hour. There's already a setting for on/off for mobile in the plugin settings - click the Edit pencil next to the plugin, then toggle the "Enable snow effect on mobile platforms?" option. IPS plugins are very simple and don't have the concept of adding individual user on/off settings. I'd have to convert it to a full-blown IPS application to provide a per-user on/off setting in their Profile page. A secondary option would be via a browser cookie with an on/off toggle link in the footer, but this would be difficult to ensure that it worked with 3rd party themes. It'd also default back to on for new browsers, or if they cleared their browser cookies. In other words, it'd be a sub-par solution.
  4. New version 1.1.0 adds the following features: You can now Enable/Disable the plugin for specific themes Fix for css selector now works with more 3rd party themes Available now from the Marketplace.
  5. Works fine on 4.1.17.1 on my board. What error are you getting?
  6. The add-on is stable. Is there any sort of functionality you'd like to see added? Good question. Let me look into feasibility. I don't know if I can retrieve the names of all of the installed themes, and/or check which theme is active at the time of page render, but I'll give it a go.
  7. v1.2.4 released to fix a minor regression where the new URL path was not displaying correctly in the ACP details for an OAuth integration.
  8. v1.2.3 posted to fix a regression with the token expiry task. Note: If tasks refuse to run in your IPS instance, it may be necessary to run the following command against your IPS SQL database to fix the OAuth 2installation: DELETE FROM enco_core_tasks WHERE `key` = 'expire_tokens'; The alternative would be to fully uninstall, then reinstall the OAuth2 Server application.
  9. v1.2.1 posted. New features: Language strings are now used for all text in the authorization form template displayed to first-time users of the OAuth integration. New scope support for user reputation points. Request user.reputation in the scope string for this data. (Thanks @Recouse!)
  10. v1.2.0 is uploading now. Here are the release notes: Fixes for IPS 4.1.14. Note that v1.2.0 is not backwards compatible with 4.1.13 and below. For older IPS releases, please continue to use v1.0.1. Scope support is complete and now recommended for Rocket.Chat integration. Allowed scopes can be specified in the ACP on a per-application basis Scopes can (and should!) be specified on initial authorization requests. If none is specified, all allowed scopes for the application are authorized. The initial form that displays to users asking them to approve the authorization request lists which scopes are being requested by the OAuth Application (Client) User primary and secondary group information is available by adding the user.groups scope to your initial authorization request. Rocket.Chat integration steps are documented in an included RocketChat-Readme.html file which is viewable on GitHub. Up-to-date documentation can always be found at GitHub.
  11. Excellent, glad to see there is a workaround for now. I have a plan to support scopes in the plugin but it's going to take a little bit of time. I will see if I can fix the scope support before releasing 1.1.0, but if it takes too long will get this fix out there so people are not blindsided by the 4.1.14 release.
  12. Shoot. I can't reproduce this on my site, the integration works correctly now for me. Can you try full uninstalling then reinstalling the OAuth integration from IPS, then install the beta for me and try again?
  13. OK @RevengeFNF and others, I'm attaching a beta of Oauth 2 Server 1.1.0 to this message. This should solve your problems, and should be backward compatible with IPS 4.1.13 and lower. The issue was not, in fact, the Url class, but an undocumented change to the IPS Dispatcher class. After installing this new version, only if you are running IPS 4.1.14 or newer, you are going to have to change the 3 URLs you use to integrate in your client application (such as Rocket.Chat). Previously the URL had the form: https://sitename.com/applications/oauth2server/interface/authorize.php Now they have this form: https://sitename.com/applications/oauth2server/interface/oauth/authorize.php The ACP page has been updated with this change. If you can test this out and let me know it works for you, I'll upload this to the Marketplace. oauth2server-1.1.0-beta.tar
  14. Hi @RevengeFNF, thanks for the heads up. Indeed it's likely that the changes to the Url constructor are at fault. I'll have time to diagnose this later this week. Hopefully I can get a fix made before 4.1.14 is released, but given the new classes it will have to be a non-backwards-compatible release to the integration.
  15. Also, you should be able to change the order of display somewhat by changing the order of the applications in the Applications page in the ACP. Try dragging the badges higher in the list - it may, for instance, display about the Steam plugin that way at least.