Releases: buzzingpixel/executive-ee
Releases · buzzingpixel/executive-ee
3.0.2
3.0.1
3.0.0
3.0.0 Release Notes
This is a major update and might be slightly painful to upgrade.
Breaking
- Executive now requires PHP 7.1 or later
- Executive now works exclusively and only with Composer.
composer require buzzingpixel/executive-eeandphp ee composerProvisionis the cliff notes to get up and running - Executive 2.x was registered with packagist as
tjdraper/executive-eeand was available at the same GitHub repo path. That package has been abandoned/moved tobuzzingpixel/executive-ee - Migrations must now implement the new
MigrationInterface - The
MigrationAbstractclass replacesBaseMigrationand instead of making things like the Query Builder availabe directly, it now has Factory classes for those tools. - The migration location and migration namespace must now be configured in the config file
BaseCommandhas been removed. Commands can now be any PHP class method. That means your existing commands will break until refactored to remove theextends BaseCommandBaseTaghas been removed. Tags can now be any PHP class method. That means your existing tags will break until refactored to remove theextends BaseTag- The
ChannelDesignerservice now lives at\buzzingpixel\executive\services\ChannelDesignerService - The
ExtensionDesignerservice now lives at\buzzingpixel\executive\services\ExtensionDesignerService - The
LayoutDesignerservice now lives at\buzzingpixel\executive\services\LayoutDesignerService - The
UserViewServicehas been relaced by\buzzingpixel\executive\services\ViewServiceand its use is somewhat different (though not a lot) - A views base path must be set in the config for the
ViewService - Autoloading of classes in the
system/userdirectory has been removed. Since Executive 3 is exclusively Composer based, leverage composer to set up your custom class autoloading scheme
Deprecated
- The
ChannelDesignerservice has been deprecated. It was trying to do too much and it can all be done with EE's models fairly easily.
New
- Added
composerProvisioncommand - Added
listMigrationscommand - Added
syncTemplatescommand - Added an easy to use dependency injector and exposed access to add to it through the config file
- Any time Executive now tries to new up a class (for a tag, an extension, a command, etc.), it tries to get the class from the Dependency Injector first. DEPENDENCY INJECTION ALL THE THINGS!
- Replaced the specific template maker commands with one unified command that is configured in the config file
- Added ability to route to custom class methods. See documentation for how it works
- Added custom action routing via post or get request. See documentation for how it works
- Added a new featured called the Action Queue
- The action queue is a queue that can be used programatically to put class methods in to be processed
- This requires something like Supervisor on the server to be continuously running the queue
- Added a new EETemplateService that renders an EE template and returns a string of the rendered template
- Added Twig template rendering!!! You can render Twig templates and return the string from your routes
- Added ability to actually reverse migrations (gasp)
- Added ability to list the status of all migrations
Updated
- Executive now elevates console sessions to "Super Admin" because some operations, particularly legacy operations, expect the user to be a Super Admin and get very cranky about the console user not being a Super Admin, or not being a logged in user at all
- Much better error handling at a higher level (hopefully) with more specific Exception classes thrown
- Executive now lists its out of the box commands in alphabetical order
3.0.0-rc.1
RC.1 Changes
- Added command to sync templates. This command does the following:
- If a group exists without an index.html template, one will be added with a redirect to 404 to help prevent a 200 response on an invalid route
- Deletes all Template Variables, Partials, and Templates from the database not present in the filesystem
- Runs EE's internal methods to make sure the database is up to date from the filesystem
- Added action queue
- The action queue is a queue that can be used programatically to put class methods in to be processed
- This requires something like Supervisor on the server to be continuously running the queue
- Added Twig template rendering!!! You can render Twig templates and return the string from your routes
- Deprecated the
ChannelDesignerservice. Use EE models to accomplish migrations.
Beta 7 changes
- Provision command will now show the file and line if an error occurs
- Fixed an error that would occur on provisioning if user addons or user themes directory did not yet exist
- Fixed an additional issue where composer might complain about the HOME environment variable in some environments (#7)
- Added the ability to provision EE from THE OFFICIAL OPEN SOURCE REPO WOOHOO
Beta 6 changes
- Fixed an issue where composer might complain about the HOME environment variable in some environments (#7)
Beta 5 changes
- Added custom action routing (TODO: add documentation)
- Improved CLI error handling
Beta 4 changes
- Updated dependency injector with make method
Beta 3 changes
- Fixed an issue where user tag classes would be required to return string (instead of not returning, for instance)
Beta 2 changes
- Fixed an issue with composer provisioning from download where several downloads in a row might get throttled (by GitHub particularly)
3.0.0 Release Notes
This is a major update and might be slightly painful to upgrade.
Breaking
- Executive now requires PHP 7.1 or later
- Executive now works exclusively and only with Composer.
composer require buzzingpixel/executive-eeandphp ee composerProvisionis the cliff notes to get up and running - Executive 2.x was registered with packagist as
tjdraper/executive-eeand was available at the same GitHub repo path. That package has been abandoned/moved tobuzzingpixel/executive-ee - Migrations must now implement the new
MigrationInterface - The
MigrationAbstractclass replacesBaseMigrationand instead of making things like the Query Builder availabe directly, it now has Factory classes for those tools. - The migration location and migration namespace must now be configured in the config file
BaseCommandhas been removed. Commands can now be any PHP class method. That means your existing commands will break until refactored to remove theextends BaseCommandBaseTaghas been removed. Tags can now be any PHP class method. That means your existing tags will break until refactored to remove theextends BaseTag- The
ChannelDesignerservice now lives at\buzzingpixel\executive\services\ChannelDesignerService - The
ExtensionDesignerservice now lives at\buzzingpixel\executive\services\ExtensionDesignerService - The
LayoutDesignerservice now lives at\buzzingpixel\executive\services\LayoutDesignerService - The
UserViewServicehas been relaced by\buzzingpixel\executive\services\ViewServiceand its use is somewhat different (though not a lot) - A views base path must be set in the config for the
ViewService - Autoloading of classes in the
system/userdirectory has been removed. Since Executive 3 is exclusively Composer based, leverage composer to set up your custom class autoloading scheme
Deprecated
- The
ChannelDesignerservice has been deprecated. It was trying to do too much and it can all be done with EE's models fairly easily.
New
- Added
composerProvisioncommand - Added
listMigrationscommand - Added
syncTemplatescommand - Added an easy to use dependency injector and exposed access to add to it through the config file
- Any time Executive now tries to new up a class (for a tag, an extension, a command, etc.), it tries to get the class from the Dependency Injector first. DEPENDENCY INJECTION ALL THE THINGS!
- Replaced the specific template maker commands with one unified command that is configured in the config file
- Added ability to route to custom class methods. See documentation for how it works
- Added custom action routing via post or get request
- Added a new featured called the Action Queue
- The action queue is a queue that can be used programatically to put class methods in to be processed
- This requires something like Supervisor on the server to be continuously running the queue
- Added a new EETemplateService that renders an EE template and returns a string of the rendered template
- Added Twig template rendering!!! You can render Twig templates and return the string from your routes
Updated
- Executive now elevates console sessions to "Super Admin" because some operations, particularly legacy operations, expect the user to be a Super Admin and get very cranky about the console user not being a Super Admin, or not being a logged in user at all
- Much better error handling at a higher level (hopefully) with more specific Exception classes thrown
- Executive now lists its out of the box commands in alphabetical order
3.0.0-b.7
Beta 7 changes
- Provision command will now show the file and line if an error occurs
- Fixed an error that would occur on provisioning if user addons or user themes directory did not yet exist
- Fixed an additional issue where composer might complain about the HOME environment variable in some environments (#7)
- Added the ability to provision EE from THE OFFICIAL OPEN SOURCE REPO WOOHOO
Beta 6 changes
- Fixed an issue where composer might complain about the HOME environment variable in some environments (#7)
Beta 5 changes
- Added custom action routing (TODO: add documentation)
- Improved CLI error handling
Beta 4 changes
- Updated dependency injector with make method
Beta 3 changes
- Fixed an issue where user tag classes would be required to return string (instead of not returning, for instance)
Beta 2 changes
- Fixed an issue with composer provisioning from download where several downloads in a row might get throttled (by GitHub particularly)
3.0.0 Release Notes
This is a major update and might be slightly painful to upgrade.
Breaking
- Executive now requires PHP 7.1 or later
- Executive now works exclusively and only with Composer.
composer require buzzingpixel/executive-eeandphp ee composerProvisionis the cliff notes to get up and running - Executive 2.x was registered with packagist as
tjdraper/executive-eeand was available at the same GitHub repo path. That package has been abandoned/moved tobuzzingpixel/executive-ee - Migrations must now implement the new
MigrationInterface - The
MigrationAbstractclass replacesBaseMigrationand instead of making things like the Query Builder availabe directly, it now has Factory classes for those tools. - The migration location and migration namespace must now be configured in the config file
BaseCommandhas been removed. Commands can now be any PHP class method. That means your existing commands will break until refactored to remove theextends BaseCommandBaseTaghas been removed. Tags can now be any PHP class method. That means your existing tags will break until refactored to remove theextends BaseTag- The
ChannelDesignerservice now lives at\buzzingpixel\executive\services\ChannelDesignerService - The
ExtensionDesignerservice now lives at\buzzingpixel\executive\services\ExtensionDesignerService - The
LayoutDesignerservice now lives at\buzzingpixel\executive\services\LayoutDesignerService - The
UserViewServicehas been relaced by\buzzingpixel\executive\services\ViewServiceand its use is somewhat different (though not a lot) - A views base path must be set in the config for the
ViewService - Autoloading of classes in the
system/userdirectory has been removed. Since Executive 3 is exclusively Composer based, leverage composer to set up your custom class autoloading scheme
New
- Added
composerProvisioncommand - Added
listMigrationscommand - Added an easy to use dependency injector and exposed access to add to it through the config file
- Any time Executive now tries to new up a class (for a tag, an extension, a command, etc.), it tries to get the class from the Dependency Injector first. DEPENDENCY INJECTION ALL THE THINGS!
- Replaced the specific template maker commands with one unified command that is configured in the config file
- Added ability to route to custom class methods. See documentation for how it works
- Added custom action routing via post or get request
Updated
- Executive now elevates console sessions to "Super Admin" because some operations, particularly legacy operations, expect the user to be a Super Admin and get very cranky about the console user not being a Super Admin, or not being a logged in user at all
- Much better error handling at a higher level (hopefully) with more specific Exception classes thrown
- Executive now lists its out of the box commands in alphabetical order
3.0.0-b.6
Beta 6 changes
- Fixed an issue where composer might complain about the HOME environment variable in some environments (#7)
Beta 5 changes
- Added custom action routing (TODO: add documentation)
- Improved CLI error handling
Beta 4 changes
- Updated dependency injector with make method
Beta 3 changes
- Fixed an issue where user tag classes would be required to return string (instead of not returning, for instance)
Beta 2 changes
- Fixed an issue with composer provisioning from download where several downloads in a row might get throttled (by GitHub particularly)
3.0.0 Release Notes
This is a major update and might be slightly painful to upgrade.
Breaking
- Executive now requires PHP 7.1 or later
- Executive now works exclusively and only with Composer.
composer require buzzingpixel/executive-eeandphp ee composerProvisionis the cliff notes to get up and running - Executive 2.x was registered with packagist as
tjdraper/executive-eeand was available at the same GitHub repo path. That package has been abandoned/moved tobuzzingpixel/executive-ee - Migrations must now implement the new
MigrationInterface - The
MigrationAbstractclass replacesBaseMigrationand instead of making things like the Query Builder availabe directly, it now has Factory classes for those tools. - The migration location and migration namespace must now be configured in the config file
BaseCommandhas been removed. Commands can now be any PHP class method. That means your existing commands will break until refactoredBaseTaghas been removed. Tags can now be any PHP class method. That means your existing tags will break until refactored- The
ChannelDesignerservice now lives at\buzzingpixel\executive\services\ChannelDesignerService - The
ExtensionDesignerservice now lives at\buzzingpixel\executive\services\ExtensionDesignerService - The
LayoutDesignerservice now lives at\buzzingpixel\executive\services\LayoutDesignerService - The
UserViewServicehas been relaced by\buzzingpixel\executive\services\ViewServiceand its use is somewhat different (though not a lot) - A views base path must be set in the config for the
ViewService - Autoloading of classes in the
system/userdirectory has been removed. Since Executive 3 is exclusively Composer based, leverage composer to set up your custom class autoloading scheme
New
- Added
composerProvisioncommand - Added
listMigrationscommand - Added a easy to use dependency injector and exposed access to add to it through the config file
- Any time Executive now tries to new up a class (for a tag, an extension, a command, etc.), it tries to get the class from the Dependency Injector first. DEPENDENCY INJECTION ALL THE THINGS!
- Replaced the specific template maker commands with one unified command that is configured in the config file
- Added routing to custom class methods. See documentation for how it works
- Added custom action routing via post or get request
Updated
- Executive now elevates console sessions to "Super Admin" because some operations, particularly legacy operations, expect the user to be a Super Admin and get very cranky about the console user not being a Super Admin, or not being a logged in user at all
- Much better error handling at a higher level (hopefully) with more specific Exception classes thrown
- Executive now lists its out of the box commands in alphabetical order
3.0.0-b.5
Beta 5 changes
- Added custom action routing (TODO: add documentation)
- Improved CLI error handling
Beta 4 changes
- Updated dependency injector with make method
Beta 3 changes
- Fixed an issue where user tag classes would be required to return string (instead of not returning, for instance)
Beta 2 changes
- Fixed an issue with composer provisioning from download where several downloads in a row might get throttled (by GitHub particularly)
3.0.0 Release Notes
This is a major update and might be slightly painful to upgrade.
Breaking
- Executive now requires PHP 7.1 or later
- Executive now works exclusively and only with Composer.
composer require buzzingpixel/executive-eeandphp ee composerProvisionis the cliff notes to get up and running - Executive 2.x was registered with packagist as
tjdraper/executive-eeand was available at the same GitHub repo path. That package has been abandoned/moved tobuzzingpixel/executive-ee - Migrations must now implement the new
MigrationInterface - The
MigrationAbstractclass replacesBaseMigrationand instead of making things like the Query Builder availabe directly, it now has Factory classes for those tools. - The migration location and migration namespace must now be configured in the config file
BaseCommandhas been removed. Commands can now be any PHP class method. That means your existing commands will break until refactoredBaseTaghas been removed. Tags can now be any PHP class method. That means your existing tags will break until refactored- The
ChannelDesignerservice now lives at\buzzingpixel\executive\services\ChannelDesignerService - The
ExtensionDesignerservice now lives at\buzzingpixel\executive\services\ExtensionDesignerService - The
LayoutDesignerservice now lives at\buzzingpixel\executive\services\LayoutDesignerService - The
UserViewServicehas been relaced by\buzzingpixel\executive\services\ViewServiceand its use is somewhat different (though not a lot) - A views base path must be set in the config for the
ViewService - Autoloading of classes in the
system/userdirectory has been removed. Since Executive 3 is exclusively Composer based, leverage composer to set up your custom class autoloading scheme
New
- Added
composerProvisioncommand - Added
listMigrationscommand - Added a easy to use dependency injector and exposed access to add to it through the config file
- Any time Executive now tries to new up a class (for a tag, an extension, a command, etc.), it tries to get the class from the Dependency Injector first. DEPENDENCY INJECTION ALL THE THINGS!
- Replaced the specific template maker commands with one unified command that is configured in the config file
- Added routing to custom class methods. See documentation for how it works
- Added custom action routing via post or get request
Updated
- Executive now elevates console sessions to "Super Admin" because some operations, particularly legacy operations, expect the user to be a Super Admin and get very cranky about the console user not being a Super Admin, or not being a logged in user at all
- Much better error handling at a higher level (hopefully) with more specific Exception classes thrown
- Executive now lists its out of the box commands in alphabetical order
3.0.0-b.4
Beta 4 changes
- Updated dependency injector with make method
Beta 3 changes
- Fixed an issue where user tag classes would be required to return string (instead of not returning, for instance)
Beta 2 changes
- Fixed an issue with composer provisioning from download where several downloads in a row might get throttled (by GitHub particularly)
3.0.0 Release Notes
This is a major update and might be slightly painful to upgrade.
Breaking
- Executive now requires PHP 7.1 or later
- Executive now works exclusively and only with Composer.
composer require buzzingpixel/executive-eeandphp ee composerProvisionis the cliff notes to get up and running - Executive 2.x was registered with packagist as
tjdraper/executive-eeand was available at the same GitHub repo path. That package has been abandoned/moved tobuzzingpixel/executive-ee - Migrations must now implement the new
MigrationInterface - The
MigrationAbstractclass replacesBaseMigrationand instead of making things like the Query Builder availabe directly, it now has Factory classes for those tools. - The migration location and migration namespace must now be configured in the config file
BaseCommandhas been removed. Commands can now be any PHP class method. That means your existing commands will break until refactoredBaseTaghas been removed. Tags can now be any PHP class method. That means your existing tags will break until refactored- The
ChannelDesignerservice now lives at\buzzingpixel\executive\services\ChannelDesignerService - The
ExtensionDesignerservice now lives at\buzzingpixel\executive\services\ExtensionDesignerService - The
LayoutDesignerservice now lives at\buzzingpixel\executive\services\LayoutDesignerService - The
UserViewServicehas been relaced by\buzzingpixel\executive\services\ViewServiceand its use is somewhat different (though not a lot) - A views base path must be set in the config for the
ViewService - Autoloading of classes in the
system/userdirectory has been removed. Since Executive 3 is exclusively Composer based, leverage composer to set up your custom class autoloading scheme
New
- Added
composerProvisioncommand - Added
listMigrationscommand - Added a easy to use dependency injector and exposed access to add to it through the config file
- Any time Executive now tries to new up a class (for a tag, an extension, a command, etc.), it tries to get the class from the Dependency Injector first. DEPENDENCY INJECTION ALL THE THINGS!
- Replaced the specific template maker commands with one unified command that is configured in the config file
- Added routing to custom class methods. See documentation for how it works
Updated
- Executive now elevates console sessions to "Super Admin" because some operations, particularly legacy operations, expect the user to be a Super Admin and get very cranky about the console user not being a Super Admin, or not being a logged in user at all
- Much better error handling at a higher level (hopefully) with more specific Exception classes thrown
- Executive now lists its out of the box commands in alphabetical order
3.0.0-b.3
Beta 3 changes
- Fixed an issue where user tag classes would be required to return string (instead of not returning, for instance)
Beta 2 changes
- Fixed an issue with composer provisioning from download where several downloads in a row might get throttled (by GitHub particularly)
3.0.0 Release Notes
This is a major update and might be slightly painful to upgrade.
Breaking
- Executive now requires PHP 7.1 or later
- Executive now works exclusively and only with Composer.
composer require buzzingpixel/executive-eeandphp ee composerProvisionis the cliff notes to get up and running - Executive 2.x was registered with packagist as
tjdraper/executive-eeand was available at the same GitHub repo path. That package has been abandoned/moved tobuzzingpixel/executive-ee - Migrations must now implement the new
MigrationInterface - The
MigrationAbstractclass replacesBaseMigrationand instead of making things like the Query Builder availabe directly, it now has Factory classes for those tools. - The migration location and migration namespace must now be configured in the config file
BaseCommandhas been removed. Commands can now be any PHP class method. That means your existing commands will break until refactoredBaseTaghas been removed. Tags can now be any PHP class method. That means your existing tags will break until refactored- The
ChannelDesignerservice now lives at\buzzingpixel\executive\services\ChannelDesignerService - The
ExtensionDesignerservice now lives at\buzzingpixel\executive\services\ExtensionDesignerService - The
LayoutDesignerservice now lives at\buzzingpixel\executive\services\LayoutDesignerService - The
UserViewServicehas been relaced by\buzzingpixel\executive\services\ViewServiceand its use is somewhat different (though not a lot) - A views base path must be set in the config for the
ViewService - Autoloading of classes in the
system/userdirectory has been removed. Since Executive 3 is exclusively Composer based, leverage composer to set up your custom class autoloading scheme
New
- Added
composerProvisioncommand - Added
listMigrationscommand - Added a easy to use dependency injector and exposed access to add to it through the config file
- Any time Executive now tries to new up a class (for a tag, an extension, a command, etc.), it tries to get the class from the Dependency Injector first. DEPENDENCY INJECTION ALL THE THINGS!
- Replaced the specific template maker commands with one unified command that is configured in the config file
- Added routing to custom class methods. See documentation for how it works
Updated
- Executive now elevates console sessions to "Super Admin" because some operations, particularly legacy operations, expect the user to be a Super Admin and get very cranky about the console user not being a Super Admin, or not being a logged in user at all
- Much better error handling at a higher level (hopefully) with more specific Exception classes thrown
- Executive now lists its out of the box commands in alphabetical order
3.0.0-b.2
Beta 2 changes
- Fixed an issue with composer provisioning from download where several downloads in a row might get throttled (by GitHub particularly)
3.0.0 Release Notes
This is a major update and might be slightly painful to upgrade.
Breaking
- Executive now requires PHP 7.1 or later
- Executive now works exclusively and only with Composer.
composer require buzzingpixel/executive-eeandphp ee composerProvisionis the cliff notes to get up and running - Executive 2.x was registered with packagist as
tjdraper/executive-eeand was available at the same GitHub repo path. That package has been abandoned/moved tobuzzingpixel/executive-ee - Migrations must now implement the new
MigrationInterface - The
MigrationAbstractclass replacesBaseMigrationand instead of making things like the Query Builder availabe directly, it now has Factory classes for those tools. - The migration location and migration namespace must now be configured in the config file
BaseCommandhas been removed. Commands can now be any PHP class method. That means your existing commands will break until refactoredBaseTaghas been removed. Tags can now be any PHP class method. That means your existing tags will break until refactored- The
ChannelDesignerservice now lives at\buzzingpixel\executive\services\ChannelDesignerService - The
ExtensionDesignerservice now lives at\buzzingpixel\executive\services\ExtensionDesignerService - The
LayoutDesignerservice now lives at\buzzingpixel\executive\services\LayoutDesignerService - The
UserViewServicehas been relaced by\buzzingpixel\executive\services\ViewServiceand its use is somewhat different (though not a lot) - A views base path must be set in the config for the
ViewService - Autoloading of classes in the
system/userdirectory has been removed. Since Executive 3 is exclusively Composer based, leverage composer to set up your custom class autoloading scheme
New
- Added
composerProvisioncommand - Added
listMigrationscommand - Added a easy to use dependency injector and exposed access to add to it through the config file
- Any time Executive now tries to new up a class (for a tag, an extension, a command, etc.), it tries to get the class from the Dependency Injector first. DEPENDENCY INJECTION ALL THE THINGS!
- Replaced the specific template maker commands with one unified command that is configured in the config file
- Added routing to custom class methods. See documentation for how it works
Updated
- Executive now elevates console sessions to "Super Admin" because some operations, particularly legacy operations, expect the user to be a Super Admin and get very cranky about the console user not being a Super Admin, or not being a logged in user at all
- Much better error handling at a higher level (hopefully) with more specific Exception classes thrown
- Executive now lists its out of the box commands in alphabetical order