Changelog
This is the changelog for infomaker/everyware-project-plugin
Last updated
Was this helpful?
This is the changelog for infomaker/everyware-project-plugin
Last updated
Was this helpful?
Current version: 0.10.2
Removed unused property $formHandler from Everyware\ProjectPlugin\Components\Metabox. The property was of the type of the deprecated class Infomaker\Everyware\Base\Admin\Form.
The support for PHP v8 has been added to composer.json.
We are now using Everyware Twig with all its benefits.
Moved abstract class Metabox here from everyware-base. Old method edit() has been replaced by formContent().
Introduced new WordPress admin theme with Naviga colors.
Added new FormBuilder method for generating radio buttons through twig-templates.
Created a TwigSetup class to be a facade for Twig that can be used by themes and other components.
The following static methods are available:
addExtension(Twig\ExtensionInterface $extension): void;
addFilter(string $name, $callable = null, array $options = []): void;
addFunction(string $name, $callable = null, array $options = []): void;
addGlobal(string $key, $value): void;
addWpFunction(string $functionName, string $name = null): void;
registerTwigFolder(string $namespace, string $path): void;
Minor changes and optimizations
\Everyware\ProjectPlugin\Components\SettingsHandler - Do not get settings value if the field is not string.
Add everyware as dependency.
\Everyware\ProjectPlugin\Html\FormBuilder - Prevent array_filter from removing value 0 when combining attributes in.
Now running ViewSetup->init(). Without doing this, the project plugin crashes if there is no theme that runs this function.
The WP function translate is now always made available as __
Now using Collection->get() instead of Collection->pull() in CollectionDBProvider->getSingle()
Composer constraints
Update build flow
Add Settings to be use in templates when rendering widgets on page
Create a specific WidgetSettingsForm class to be used on Widgets
Refactor WidgetAdapter into an abstract class to be inherited in order to work with WP and Everyboard
Move rendering of widgets from Admin to Widget -class
Update SettingsHandler to return SettingsFields instead of array
Remove SettingsHandler as dependency for ComponentSettingsForms
Remove import of form-handler.twig in component admin
getCurrentPage now return null if no plugin is active.
Update of admin -style and -scripts
Minor fixes in FormBuilding
Minor fixes and optimizations
Added new support for handling Components by adapters
Added new support for handling Component settings with separated classes
Added support for special form-components like tooltips, toggle-buttons and multi-selects
Changed namespace to originate from Everyware and not Infomaker.
Moved static classes for handling Metaboxes and Widgets to ProjectPlugin from Everyware/Base
Moved SettingsParameters to a separate plugin
New support for creating and managing Components that will deprecate the old support from Everyware/Base.
Added Support for Form-building that can be used to render forms to administrate components
Added Twig templates for rendering component admin forms
Changed the way project-plugin hooks into Twig
Fixed package deployment. To not include unnecessary files.
Add Component Admin-page for handling of Metabox-components
Updated the way Twig is set up to make it possible for Components to fetch and reuse the namespaces created by ProjectPlugin.
Change type to MU-Plugin for removing of possibility to deactivate plugin
Fix bug where Component breaks if there are no components to find.
Update call to undefined functions
Changed twig setup
Added dependency to Everyware Base
Added dev-dependency to Wordpress Core
Updated current dependencies
Removed message classes for use of everyware-base classes instead
Removed SettingsParameter model for use of everyware-base class instead
Removed JsonImporter for use of everyware-base class instead
Fixed error on SettingsPage
Minor fixes and optimizations
Updated to correct License
Added this file and boilerplate and markup example for the future