allysonsouza / wp-presets Goto Github PK

The goal with this redesign is to make it possible to apply the same action multiple times using different data (such as changing details for different users or different WooCommerce Products on the same preset).

• Create repeater group field to apply the actions.
• Move Notes feature to be part of the Presets core.
• Turn the WordPress core into a module (instead of being part of a Presets core).

This would require manage_options capability for using the plugin, so mostly only administrators would be able to do it. I don't think that this issue would be top priority as this plugin should work mostly for testing.

Check following our coding standard.

In general, you would select a Preset, and it would run as part of the other preset.

Add which commands we need to run and what needs to be done for the dependencies to work as expected. Indicate the extension and tools that we are using on our default text editor.

Create a page, or top bar button, or widget, to execute preset application on the site. The user must have a dropdown (or other interface component) to select which preset they want to apply.

PS: Maybe we should create a default entry on plugin activation, storing the woocommerce settings and customer meta on it.

Register presets post types meta boxes to user fill the WooCommerce settings and user meta to be override on preset application.

WooCommerce Settings

Store Address

• Address line 1
• Address line 2
• City
• Country / State
• Postcode / ZIP

Currency options

• Currency
• Currency position
• Thousand separator
• Decimal separator
• Number of decimals

Customer meta

Billing address

• First name
• Last name
• Company
• Address line 1
• Address line 2
• City
• Postcode / ZIP
• Country / Region
• State / County
• Phone
• Email address

Shipping address

• First name
• Last name
• Company
• Address line 1
• Address line 2
• City
• Postcode / ZIP
• Country / Region
• State / County

This new module would allow you to add a text that would show up after the presets get applied.

The best way to do it might be adding this text on the notice that shows up with the action confirmation. Maybe we can use the site bio text instead of a new field/metabox. Both ways should work from what I see.

You are required as default to select the plugins that you want activated/deactivated when the preset gets triggered. The goal would make it optional.

In this case, it would work better if a user wants to only change something on the user meta without activating or deactivating plugins.

The goal with that would be having a button or something like that that takes a screenshot of your current settings and create a new preset out of it.

That is something that maybe we can use the native WP tool instead, but could be nice if we have a way of exporting/importing the presets.

I see that WooCommerce presets will indeed be the main feature for this specific plugin, but I believe that we actually have the opportunity here for having it more like a WP generic plugin instead of a Woo extension. Mostly because if we go more generic we could add other plugins presets or even more WP native settings that aren't related to WooCommerce.

With that in mind, the proposal would be changing everything from Woo specific to a WP generic format:

• Name: From Presets for WooCommerce to WP Presets
• Text Domain and Repository Name: From presets-for-woocommerce to wppresets
• Prefix: From prewoo_ to wppresets_

These are some of the things that came to my mind, but it would require a full review in case we need to rename functions and such.

When you apply the presets it currently redirects you to /wp-admin/edit.php?post_type=wppresets. It would make more sense to apply without this redirection.

The goal would be creating a metabox with a field for activating a set of plugins. It would allow you to search and select the plugins that you want activated as part of the preset.

If this field is filled, all the other plugins would be deactivated except for WP Presets and the plugins added on the field.

This would allow you to activate a specific set of plugins when applying a specific preset.

Note: I don't think that a checkbox would work great here as the site could have an infinite amount of plugins. Maybe something like a CMB2 Field Type: Select2 could work great here using a Multi-value select box.

We are currently importing CMB2 files as part of the plugin. The goal would be to add using Composer.

Register presets post types meta boxes to user fill the WordPress settings and user meta to be override on preset application.

WordPress Settings

User

• First Name
• Last Name
• Nickname
• Website
• Bio
• Email

Currently, you are only able to trigger Presets on the WP Admin. It would be great to allow the users to do the same on the site itself.

Register presets custom post type.

After introducing #19, change the entry title to be the selected action for the entry instead only Entry #1 text or something like that.