You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is just a "catch all" ticket to jot down things that should be added, removed, or changed in the new version.
As folder structure, we are breaking away from the public/admin structure which became pointless (and never really had a point) and instead approach it with the only somewhat globally accepted "standard" in PHP.
This will also allow more freedom in the actual application structure itself.
Full autoloader should be implemented, thus, all classes should likely reside inside one single folder, and access controls should be done on a more granular base and not like in the old approach on a more "global" level
Potentially it should include more examples for newbies, as it is always easier to remove than to add: so we should add a menu page, shortcode (already there in current version), perhaps some more examples on filters and actions, localised AJAX script, and so on.
Also, a very important point is to NOT abstract the add_action and add_filter (which is currently the case in the plugin boilerplate)
This has not only confused people but also is based on pure "personal opinion" by the original author, and makes no real sense, as it is just adding clutter code and does not really improve anything: filters and actions are not going to change and do not require plugin-side abstraction.
While the concept is a good idea, it is futile in this case and teaches the user nothing useful.
The abstraction can be better brought to example in a admin-side page or menu with settings, or custom /user field implementation
Thinking of which, the plugin should show how to add custom fields of all kinds, custom field tables, taxonomy, post type, settings and options (best exampled on the admin page) as well.
The plugin should and will keep full WPCS compliance, overruling any other PCR rule
The text was updated successfully, but these errors were encountered:
This is just a "catch all" ticket to jot down things that should be added, removed, or changed in the new version.
As folder structure, we are breaking away from the public/admin structure which became pointless (and never really had a point) and instead approach it with the only somewhat globally accepted "standard" in PHP.
This will also allow more freedom in the actual application structure itself.
Full autoloader should be implemented, thus, all classes should likely reside inside one single folder, and access controls should be done on a more granular base and not like in the old approach on a more "global" level
Namespaces should be used
See full list of "no go" here https://github.com/szepeviktor/starter-plugin/blob/wp-63/README.md#what-to-avoid
Potentially it should include more examples for newbies, as it is always easier to remove than to add: so we should add a menu page, shortcode (already there in current version), perhaps some more examples on filters and actions, localised AJAX script, and so on.
Also, a very important point is to NOT abstract the add_action and add_filter (which is currently the case in the plugin boilerplate)
This has not only confused people but also is based on pure "personal opinion" by the original author, and makes no real sense, as it is just adding clutter code and does not really improve anything: filters and actions are not going to change and do not require plugin-side abstraction.
While the concept is a good idea, it is futile in this case and teaches the user nothing useful.
The abstraction can be better brought to example in a admin-side page or menu with settings, or custom /user field implementation
Thinking of which, the plugin should show how to add custom fields of all kinds, custom field tables, taxonomy, post type, settings and options (best exampled on the admin page) as well.
The plugin should and will keep full WPCS compliance, overruling any other PCR rule
The text was updated successfully, but these errors were encountered: