Maciek Palmowski

I will try to check this out next week. Although not all parameters work with ACF. If they are compatible, I'll add them,

I think it may be related to the fact I'm using locate_template. Could I ask you for a zip with simplest example of your case?

Installing it inside of a theme is the recommended way. However maybe it could be possible to make it working while installing in the root composer file. czw., 25 lis...

So if I understand correctly - you would like to register all the fields and block parameters in one place, right? As I see the logic of doing something like...

I'm using Couscous on W10 without any problem. theme files shouldn't be in root directory - look at my example http://screencloud.net/v/AicXt - and in couscouse.yml: ``` template: directory: theme #...

The first problem is that the: ``` Show Password export default { mixins: [Fieldtype], data() { return { show: false }; }, computed: { inputType() { return this.show ? 'text'...

As there is a PR waiting I use something like this: ``` { "type": "package", "package": { "name": "advanced-custom-fields/advanced-custom-fields-pro", "version": "5.8.0-beta3", "type": "wordpress-plugin", "dist": { "type": "zip", "url": "https://connect.advancedcustomfields.com/index.php?p=pro&a=download" },...

I'm having some doubts here. I mean - having those separate is a bit strange, don't you think? Or maybe we should set it like this: if no WP_ENVIRONMENT_TYPE is...

Looking at this https://core.trac.wordpress.org/ticket/33161 - I don't think there is hope for WP_ENV :/ But aside - so in short: - if both are defined - we just define theme...

Before I would push a PR - could you take a look: ``` Config::define('WP_ENVIRONMENT_TYPES', env('WP_ENVIRONMENT_TYPES') ? explode(',', env('WP_ENVIRONMENT_TYPES')) : ['production', 'staging', 'development']); if (env('WP_ENV') || env('WP_ENVIRONMENT_TYPE')) { Config::define('WP_ENV', env('WP_ENV') ?:...