As an instructor, I want to be able to visualise a number of aspects of when my students are accessing my courses and materials. My institution refuses to give me DB access, and won't let me install a plugin. Is there any way I can pull this data? I could easily do it with a few lines of code in Canvas, so using moodle feels like stepping back in time. I've been exploring developing an LTI app as an option (I've got the demo LTIJS app working) Any ideas?
You can access user logs in a course by going to Participants then click on the user you want to track and you will be taken to their course profile. From there, you can choose any option in the "Reports" section. You will need to have the proper capabilities. The reports shown in the screenshot are from a site admin account.
Related
I work for a company that generates calendars for professionals and we'd like our users to synchronize their calendar on their phone for simplicity's sake. We initially had an ICS file, but we started hitting issues out of our control and we're looking to switch to a full CalDav support.
However, the steps necessary to create a CalDav account can be a bit tedious
( https://www.youtube.com/watch?v=BfPtH8fOLfw ) especially since in our mobile app, we already have an authentified user, we were wondering if there was any way we could do the setup for the user, so he/she doesn't have to switch back and forth to copy/paste the CalDav Account Credentials.
Surprisingly, we've found nothing. No NPM package, no way to simplify this. We did found a way to generate a configuration profile with the data, but we were told to steer clear this idea since some of our customers may be using a company-provided phone and it was possible to prevent any sort of installation through configuration profiles.
Anyone has an idea on how we can make it simple for our users and give them the best UX as possible ?
Thanks :)
I'm submitting my first app through iTunes Connect. It is a social networking community so I have to provide a demo account for the submission. My app already has a live database of users as there is currently an active web version.
I'm new to this and confused as to how I should handle this. Should I be creating a demo account that will not show up in any other live user's search results? Are the testers going to be attempting to interact with other live users? I am assuming I will need to show the various functions of the app, like messaging and events. In that case should I be creating a few "demo" users for the testers to interact with?
Alternatively, should I be linking them to the development version and development database? If that's the case, then the build that I send them would only be a development build then?
I am confused on how this is supposed to work and can't seem to find any information to help?
In my experience, you'll need to give them the production version that will go into the store. So not the development build.
When we submit an app for approval, it seems to get installed and activated on a couple of devices, but nothing much ever happens. They barely use it, as far as we can tell. We can tell that it's installed and run. We have previously been rejected when the network connectivity wasn't working right, so we know that they do look at the app after it's installed.
I'd suggest you make them an account that looks relatively anonymous (or even "Test Account" which you real users are hardly likely to try to interact with). You could create another account and say "If you want to send a message, send it to account xxxx". We've never had them interact with our app enough to utilise the suggestions we've made.
If you have an active / inactive flag, you could think about making these accounts inactive once the app is approved, then re-activating it when you next want to submit your app.
We are moving to Chromebooks in our school and would like to know if it's possible to retrieve the users browser history. Every month we perform a device check in where the teacher physically inspects each students device for anything "suspicious". This generally entails looking at their browser history for things like pornographic or other unsavory URLs.
I would be very handy to build a nightly process that slurps up the student's browser history, checks it for any anomalies, and reports that to the administration. Is this possible? Is there another way to do this?
I don't think this is fully supported yet. chrome.history from Chrome API can only
interact with the browser's record of visited pages. You can add, remove, and query for URLs in the browser's history; that's as far as API goes.
Is there a way to automatically (i.e. programatically, via a specified URL, or by some other means) switch team after logging into the Apple Developer portal, but without using Fastlane? I have the following scenario:
I have a user who is admin on 2 different Apple Developer accounts
I want to log into the Apple Developer portal as the user, and do the following:
Access the 'Certificates, IDs & Profiles' section, and switch to using the team that I specify
Access iTunes Connect using the team that I specify
The reason I need this is that I want to automate logging into the Apple Developer portal and perform some maintenance tasks against a specific team, and Fastlane isn't an option right now.
I've tried using the following URL for accessing the 'Certificates, IDs & Profiles' section:
https://developer.apple.com/account/ios/certificate/?teamId=MY_TEAM_ID
however it doesn't switch to the specified team. I've tried a similar thing for iTunes Connect using the 'switch' parameter on the URL, but that doesn't automatically switch either.
It's a little bit tricky:
For the account overview page, the different links are working:
https://developer.apple.com/account/#/overview/ABCDEFGHI
But for the actual certificates page, Apple saves the team ID in local storage. If you change it here, it will show/get you the page you want.
As iTunes Connect is a completely different site, the team selection seems to be based on cookie values, but them look to be encrypted or something.
It really depends on what kind of "Maintenance tasks" you want to do.
I today get Instagram api and add my website live,
I see write:
Client Status: Sandbox Mode GO LIVE
I can't click on ''GO LIVE'' button why ?
You would need to start a submission for approval to go live, though:
Feeds for websites won't be approved; these will remain in sandbox mode and be limited to 500 requests per hour and 20 images. This doesn't sound like much especially for large clients, but if you cache your responses, it's not a problem.
The main confusion is because they have made it sound like every app/feed has to be approved and out of sandbox mode to work, where as the reality is that only fully functioning apps for phones, or a widget plugin really ever need to be.
You will no longer be able to display feeds based on hashtags, only a users own photo's. By getting a client to be a sandbox user, is how you can access their feed without their login information.
Older apps/feeds will need to be updated to use the new code before June or they may stop working.
It's mainly to stop apps hammering instagram's servers for unlimited requests on any hashtag/users they like.
Here is an example of how to fetch and cache images using WordPress's 'set_transient' - you will need to use a loop to output the data.
WordPress Instagram Gist
Here is the relevant piece of information in the dev docs:
Here are some examples of scenarios that will not be approved:
To display content for a personal website. If you are a developer and you want to showcase Instagram content on a website, then you do not need to submit your app for review. By using a client in sandbox mode, you will still be able to access the last 20 media of any sandbox user that grants you permission.
One-off projects. If you are an agency building websites or other integrations, note that we don't grant permissions to clients created for one-off projects. If you are interested in building a product, platform, or widget that will be used as a service across multiple projects, then you may submit a single client_id that you can use across multiple projects.
To use a widget. If you are installing a widget for your website, then you do not need to submit for review. Some widgets may ask you to create a new client id, but you do not need to submit it for review for the widget to work. Your client can remain in sandbox mode and the widget will have access to your last 20 media.
Hope that helps clear some confusion.