Coronium Core - Version 2.4.0

Third Party Coronium
#1

Coronium Core 2.4.0  is now available for installation.
 
_ This is a mammoth update so before upgrading be sure to create a snapshot or backup of your current system and back up your databases. _

Once updated you will need to reboot your server.
 
Added

  • Server-side Users module, allowing for custom user logic and types. Includes new methods getGroup, getWithQuery, and getAndMerge for advanced user queries, record associations, and more.
  • Server-side and client-side OAuth API which is a  Users  module extension to support OAuth client IDs, access tokens, and expirys from Facebook login, Google sign-in, etc.
  • MySQL module EZ Query method  mysql.selectMerge  to select from multiple databases and tables in a single call. See the client-side selectMerge or server-side **selectMerge **documentation for more details.
  • MySQL module EZ Query method  mysql.selectCount  to get records counts based on queries. See the client-side selectCount or server-side selectCount documentation for more details.
  • Server-side MySQL module time based methods can now accept a UNIX timestamp for conversion.
  • Server-side MySQL module logQueries method to enable logging of the raw queries being created under the hood for debugging purposes.
  • Modules that accept a where key can now benefit from a new special table type clause. See The WHERE Key for more information.
  • A new field in the  Users  module called group to help partition your users within a scope.
  • A new incoming parameter scope for use in custom server-side API methods (see Input).
  • Logging is now split into api, pages, and nginx logs for less noise and more specificality.
  • Lots of new and revised documentation.

Fixed

  • Users module Field ‘extra’ doesn’t have a default value error.
  • Administration database collation type inconsistencies.
  • Trigger privilege unavailable for external MySQL admin clients.

Updated

  • Client connection count increased significantly.
  • Almost all server-side methods now support error, and error status codes that can be returned to the client. See Status Codes.

API Changes

  • mysql.selectBatch  key parameter is now optional per entry. If not specified the table name will be used instead. Be sure to provide a key if multiple entries use the same table.
  • mysql.selectBatch  now returns a single record (similar to  mysql.selectOne ) if the limit for an entry is set to 1.

Webmin Update 1.2

  • Now supports multi-file server-side API projects.
  • New Webmin settings area in the  Config  section.
  • Log viewer updated to view newly split log files.
  • Log displays with (optional) colorized output. Increased line output.
  • Dark theme now available for the code editor.
  • New user keys oauth and group added to the user details page.
  • Filter by group added to the user search page.
  • Code editor completions for all new methods.
  • Lots of updates and fixes both under and over the hood.

Install : https://develephant.github.io/coronium-core-docs/server/installation/digitalocean/
Update : https://develephant.github.io/coronium-core-docs/server/updates/#232-to-240
Documentation : https://develephant.github.io/coronium-core-docs/

Plugin : https://marketplace.coronalabs.com/plugin/coronium-core
 
Free Trial : https://forums.coronalabs.com/topic/71279-coronium-core-new-friction-less-install-and-free-trial
 
_ Before upgrading be sure to create a snapshot or backup of your current system. _
 
Please post any issues or questions in this forum. Enjoy!
 
-dev

#2

Hi,

I wanted to add a few pieces of information for those migrating to the 2.4.0 release.

Debug Log

In previous versions there was only one main log file. The logs have now been split up into three different categories (see release notes above).

When doing an upgrade, you will now see a new Log Viewer in the Webmin. The default log for debugging is now the api.log and is shown by default when loading up the Log Viewer. If you’ve just updated, you probably won’t see anything in this log yet.

If you need access to any pre-update log entries, then switch to the nginx.log in the Log Files dropdown. After the update, you will no longer use the nginx.log to debug your apps. Use the api.log instead.

Application Scopes

As in previous versions, application scopes are added “on demand” the first time you add one in your application and run either an Analytics or Users module method.

In the past you would usually need to refresh your browser to get the application scopes to update in the Webmin. Now, to activate any newly added scopes, go to the Config section of the Webmin and click the “Update” button in the Update Scope Cache setting.

Remember, an application scope wont be “registered” until you’ve run at least one Analytics or Users module method.

If you have any questions about how things work now in the Webmin, ask away. :slight_smile:

-dev

#3

Hi,

I wanted to add a few pieces of information for those migrating to the 2.4.0 release.

Debug Log

In previous versions there was only one main log file. The logs have now been split up into three different categories (see release notes above).

When doing an upgrade, you will now see a new Log Viewer in the Webmin. The default log for debugging is now the api.log and is shown by default when loading up the Log Viewer. If you’ve just updated, you probably won’t see anything in this log yet.

If you need access to any pre-update log entries, then switch to the nginx.log in the Log Files dropdown. After the update, you will no longer use the nginx.log to debug your apps. Use the api.log instead.

Application Scopes

As in previous versions, application scopes are added “on demand” the first time you add one in your application and run either an Analytics or Users module method.

In the past you would usually need to refresh your browser to get the application scopes to update in the Webmin. Now, to activate any newly added scopes, go to the Config section of the Webmin and click the “Update” button in the Update Scope Cache setting.

Remember, an application scope wont be “registered” until you’ve run at least one Analytics or Users module method.

If you have any questions about how things work now in the Webmin, ask away. :slight_smile:

-dev