WebGUI Blog

News, tips, and tutorials about the WebGUI Content Management System.
Recent Tweets @plainblack

The simplest, shortest answer is as follows:

It will require upgrading.

WebGUI 8 has API changes to WebGUI::Session and to WebGUI::Asset, and those changes pretty much require that most custom code will need to be upgraded.  Many simple macros and form plugins may not need changes, but by far and large it is safest to assume that they will.

That was the bad news, this is the good news.

  1. We had to migrate WebGUI itself over to the new API so it can be done.  Between Plain Black support and the WebGUI forums you have resources for help in doing that.
  2. We have a script to help automate some of the Asset work.  It will be released to the Add ons and Plugins section on webgui.org.
  3. The migration document has a full list of the API changes.
  1. steroids-uk-co reblogged this from webguiblog
  2. webguiblog posted this