Aiwa

@Rubik Support for IPS 4.7 has been released and is publicly available. https://github.com/kacx9c/steam

Per previous announcement, Steam Profile Integration will be free and publicly available. I'm happy to announce that version 3.0.0, developed against IPS 4.7.12, is now publicly available. https://github.com/kacx9c/steam/releases/tag/3.0.0 Note: This does not include the OAuth login handler. The Login Handler is intentionally being broken out of this application. This is in the best interest for clients as code updates will be isolated to only the login handler, and more efficiently updatable.

Hook installation fixed. Now with all features working, going through settings to ensure they operate as intended. Also fixing a couple styling issues.

Uninstall works. Extension/hook installations aren’t all working. Rebuilding them with the base 4.7 templates and continuing testing installation routine. Almost there.

Working on the upgrade and install scripts. Once that’s done, I’ll build the app and publish it in the repo, and make the repo public. I’m developing against 4.7.12

98% of the code is complete and has been pushed to Github. Again, if pressured I could make the repo public but would be lacking thorough testing in some areas. The only portion remaining is testing of the groups portion of the application.

90% of the completed code has been pushed to github. If pressured, at the current time, I could make the repository public with reduced functionality. Users, currently, would need to have a means to build the application from the dev files on their own. I have not yet implemented a GitHub action to perform the build. Note: The Login handler will be in a separate repository. That has yet to be migrated out. License has been chosen, MIT License.

User Profile Hover card

The repository is close be being opened up to the public. Entire Steam profiles are being pulled and displayed in the users profile, the profile API is complete. Still need to work on Groups, but that will be done after profile view is complete. I've also got some work that needs to be done on error handling. There are a few other places on the website that need their view set-up, but with SQL being updated completely, those are just a matter of getting the hooks in place and getting the data out of SQL. Note: The Login handler and application will be separated. I'll either create a new repository for the Login handler, or will update Lavo's repository. Either way, both the application and Login handler will become open source. I've not yet chosen a license, but will have one chosen before release.

The application is under development to clean up the code base. This will not, necessarily, make it fully compatible with any IPS version. Once the code cleanup is complete, a GitHub repository will be made public. This is in response to IPS's announcement of Marketplace closure. Support will also be transitioned to GitHub issues. This will open up the repository for other developers to contribute to bugs fixes and/or application updates, if I'm unable to keep the application up to date. Medical issues have been a constant distraction during each update, see previous posts, causing justified frustration for many customers. These changes are being made in the best interest of all customers.

Sadly I do not have pictures to show you with this update. All efforts have been focused on the back-end structure. The efforts made in the back-end will greatly improve maintainability for continued updates. I look forward to posting screenshots once the back-end is updated and data can make it to the front-end. This is still very much in active development.

Active Login sync. Working on the profile tab.

Updates have been made, the login handler works with IPS 4.7. The trouble is, it's deeply coupled with the rest of the Profile Integration logic. It's not simply the login handler. There is the choice to break this apart into two separate items, but there is no guarantee everyone would pick up both. Breaking them apart would also cause additional work on the Profile Integration portion. I'm pretty sure I know most everyone's vote. Give me a little bit to see what kind of progress I start making on the rest of the app with 4.7. Next posts with pictures of updates.

Not forgotten about.

Update for full IPS 4.5 compatibility is well under way. We're taking this time to also tackle tech debt from prior versions. This will make the code base more easily maintainable moving forward. This re-write will also make review of the code easier on IPS Marketplace management. I thank everyone for their patience as we're working through this re-write. Everyone be safe with COVID on the loose!

It does not currently support hex id’s. That said, it wouldn’t be hard to add that feature based on what I’m reading. Can you be a bit more clear about what features you’re looking for? Just a hex ID decode? Or more? Feel free to submit a support ticket, support [at] aiwa [dot] me, and reference this topic if you would prefer to keep the discussion private.

In the future, please use the prescribed support, and new feature request, channel and provide your board URL. I’ve put your new feature request in the backlog. Thank you

I'll add the feature request to my backlog. Thank you for the suggestion.

GDPR, General Data Protection Regulation... While many have heard this term, not everyone knows what it means. I'll come out of the gate saying I'm not an expert, nor a lawyer. In a very general sense, it's about online privacy and giving individual users more control over their information what is shared with whom. To that end, Steam has rolled out a change of their own with regards to profile privacy. Whether this is related to GDPR or not, no one will know, but the timing is quite coincidental. How this impacts the Steam Profile Integration application... By default, Steam is setting everyone's privacy settings pretty secure. Meaning less data will be pulled for you users. You'll start seeing Profiles with: 0 hours played in the last 2 weeks quite a bit more frequently No statistics for recently played games (games played in the last 2 weeks) No statistics for owned games No, or limited, statistics for total playtime for games. This doesn't mean the Steam Profile Integration is going anywhere. I'll have some updates coming out in the coming months. One feature to direct users to manage their Steam profile privacy to allow the pulling of data. Another to streamline the user interface to not display empty playtime in the last 2 weeks when that data is simply private, etc. It's a challenging time for developers as we have to work with smaller and smaller data sets. But it's ultimately a good thing for your users. They have more granular control over their data.

As soon as I get this hot fix version released for Steam Login, I'll look into this to see if i can find out what's going on.

I've done some work on pulling PUGB game stats from a 3rd party tracker. Haven't yet fleshed out how I'd lay it out. It's behind a couple other things in queue. I'll have to look into why your profile isn't returning all of the information... I cleared my profile, re-updated it and everything loaded correctly. Something seems to be up with your profile specifically.

As you may know, PHP 7.x offers many performance enhancements over PHP 5.x. Up until now, Steam Profile Integration has had to maintain backwards compatibility with PHP 5.x, while trying to leverage as many benefits from PHP 7.x as possible. Well, it's time to pull off the bandaid. Steam Profile Integration 2.1.9 will be the last version to officially support PHP 5.x. Starting in Steam Profile Integration 2.2, PHP 7.x will be required as the minimum version of PHP. If you're able to control what version of PHP you're running on your server, I highly recommend updating to PHP 7 as soon as possible. For those that simply can't upgrade to PHP 7 just yet, 2.1.9 will continue to work with both IPS 4.2 and 4.3 and be the last stable version you can use. Steam Profile Integration 2.2 is a major optimization and re-factor of the code-base. More efficient code Better error handling and diagnostics Abstraction of the API layer Opens up the possibilities of collecting game stats from alternate API sources efficiently and effectively Increased consistency with the IPS UI / UX. It's exciting being able to leverage the newest technology freely so that I am able to deliver the best product to you, the customer.

We've been pulling individual users for quite some time, but there was always something missing that tied them all together... Steam Community Groups. Now, you can add Steam Community Groups to a setting in your AdminCP, and display information about the group on any page within your community! The users displayed within the group widget are users on YOUR community that are a part of the group. You can configure how many users you'd like to display along with how many lines of description text to show by default, with a 'Read More' link to show the full description.

The bug fix release is built, I'll try and get it released tonight.

I went about this a slightly different way. 1) I disabled storing of empty profiles. 2) Added a filter to only show Active profiles in the table, any profile with a valid SteamID 3) Added an uninstall routine that delete all steam_no_steamid profiles. Policy is to only store profiles with some kind of steam value, even if it's bad, or they manually attempted to update their profile.