Hi Nick

You're welcome to drop me a line about this via brook.hayes@canstudios.com so we can get a few more details and provide you with a quote if you want?

Can Studios is a full-service elearning company that can provide Adapt authoring services, and, if you do want it later, elearning audits/instructional design consultancy. We're UK-based but used to working with clients internationally, including not for profits. 

All the best

Brook

Hi Jason, that's something Can Studios provides. You can find out more about our service at www.canstudios.com/adapt . But do drop me a line at brook.hayes@canstudios.com and I can answer any questions you have, discuss education pricing and so on. 

Hi,

As Matt say it is not something you should take on lightly as you need to to ensure your server is set up securely and kept up to date.

If you do fancy a hosted service we (Can Studios) are one of the companies which offer a hosted version of the tool. 

You can read a bit more about our service here: https://canstudios.com/adapt-toolkit/adapt-from-can-studios/

Or take out a free trial to see if its what you are looking for: https://canstudios.com/adapt-toolkit/adapt-from-can-studios/get-adapt/

Hope this helps.

Paul

Good morning Chuck,

There are two scenarios that could cause a plugin to be categorised as red.

1) The "framework" version in the plugins bower.json is not compatible with the framework version in the AT. If your plugins framework version is ">=2.0.0" and your AT framework is "4.3.0" I would expect this to pass

2) The "version" field in the plugins bower.json is not a valid version number (eg it should be of the form x.y.z)

If the version appears to be of the correct format then I would suggest attempting to import the plugin on it's own to see if there is any more information there.

Thanks

John,

yes, MB in /conf/config.json

In v0.9:
I found "maxFileSize" at adapt_authoring/node_modules/formidable/lib/incoming_form.js, as mentioned above by Daniel. I increased it. AAT import manager's label still reported 200MB max. Attempted import of a file greater than that failed.

Then I found "maxFileUploadSize" in adapt_authoring/lib/configuration.js at line 84. I increased it. AAT import manager's label still reported 200MB max. Attempted import of a file greater than that failed.

Then I found "maxFileUploadSize" in adapt_authoring/conf/config.json. I increased it. AAT import manager's label now reported my limit. Attempted import of a file within that limit and it succeeded.

To satisfy my curiosity, I then reduced the max size only in /conf/config.json, and attempted to import a file greater than that limit. It failed. So I'm concluding that the only place that matters is in /conf/config,json.

No - no adjustments. Have you updated the iOS version in the iphone you were testing on?

Hi Christina. The bg-scroll seems to be working fine in my iphone - both Safari (v12) and Chrome. I'm on iphone 6 iOS 12.3.1. Is this the correct behaviour below?

 . 

Ah the component issue was probably to do with your newer versions of AT/framework. I was using the component version in AT 0.6.5 / 2.3.3 on which I still have a number of courses to maintain.

What's defined for your background-size and background-attachment for the image issue in iOS? Something in iOS safari might be overriding. Happy to inspect and check it out if you can send me a sample zip of the issue. :)