Author

Powered By

  • OpenWGA Blogs 2.4.2 Build 132
    Running on:
    womodo CMS Server 7.6.4 Maintenance Release (Build 680)
    www.openwga.com

Searchresult for: KEYWORDS:"dev-studio"

Sort by:


OpenWGA 7.1 is released

As delay is somehow part of the game we today released OpenWGA 7.1 CMS Server, some weeks late on schedule. Nevertheless, we hope you find it to be worth the wait.

See our summary page of what's new in 7.1 to have an overview of what's in store for this release.

As always, please take note of our update guide before pulling the update trigger to ensure a smooth transition.

OpenWGA 7.1 of course is accompanied with a new OpenWGA Developer Studio 3.1 release. You can update your WDS 3.0 installation to this new release using the integrated update functionality ("Help > Check for Updates" on the menu).

[Update 23.03.2015]

Today we released OpenWGA 7.1.0.2 which fixes a security vulnerability regarding the new "error incident pages" feature in OpenWGA 7.1. Customers already using this feature are advised to upgrade to this new release.

OpenWGA 7 is released!

The new server base release is available on the usual distribution channels. The same goes for OpenWGA Developer Studio 3, which offers development support for this new server platform.

Find out about everything that is included in this release on the What's new in 7.0 page.

Of course there is also an updated documentation for this release, including an update guide to assist you in the task of performing a smooth transfer from your current version to this one. As this is a base release it also contains detailed instructions for the case when you are updating directly from the previous 6.0 base release.

And speaking of base releases: This release also marks the start of the last year of maintenance support for OpenWGA 6.0.  So we encourage all customers using this version to update to 7.0 until September 2015.

New tutorial: Going live from OpenWGA developer studio

A new tutorial is available in our Support section describing the task to bring a website, that has been created locally in OpenWGA developer studio, to an OpenWGA live server. The OpenWGA platform features some unique functionality to make this crucial and often tedious step easier.

Have a look at:

  • The setup an OpenWGA standalone server and making it secure for being exposed to the internet
  • Features to move/synchronize application design and data from WDS to the live server
  • Configuring the web application and its access control on the live server


Upgrade to OpenWGA Developer Studio 1.1

The first feature release of the OpenWGA Developer Studio is ready for download:
  • One of the main features in this release is the code completion for TMLScript which will make coding script blocks faster and more reliable (see this post).
  • WDS 1.1 contains support for OpenWGA 5.1
  • You can define headers for new created files global or per project. This is very useful when each source file must contain for e.g. an OSS license header.
For a complete list of changes please visit the tracker.

Read more to find out how to update your existing installations.

Preview OpenWGA Developer Studio 1.1

OpenWGA contains a huge featured script engine. If you are suffered from jumping between code and a browser window for reading the script reference to lookup the right methods, you should read more about the upcoming TMLScript code completion support in OpenWGA Developer Studio 1.1.

OpenWGA Developer Studio 1.0.2 released

We just released the next maintenance version 1.0.2 of the OpenWGA Developer Studio.

For more details about bug fixes and changes please visit the the tracker.

OpenWGA updated to Version 5.0.1

We just updated the OpenWGA Server to version 5.0.1 and the OpenWGA Developer Studio to version 1.0.1.
Visit tracker.openwga.com for more information.

In the meantime we started the development of OpenWGA 5.1 and will post some of the things we are working on in the next days.

Development in Teams

Most CMS products do not really support developer teams:
Templates are edited on a shared file system on a central development server. When saving a template from your editor you can't avoid overwriting changes other developers made in the meantime on the same file. If your template does not work as expected other developers may be disturbed because they are working on the same development server.
In addition to all that pain the developers suffer you need to install and maintain one development server for each customer you work for leading to a complex and expensive server infrastructure.

Entry 1 to 8 of 9   >>