Hide ACF Menu about bea-plugin-defaults HOT 7 CLOSED

Putting this here #9 (comment)
We use out own constants because there is no WordPress constants that are filling our needs.
Sage and Bedrock are using WP_ENV and we are now on every project as they are part of the config files.

ACF interface is for creating fields from admin (and some tools) and isn't related to the debugging process, as our fields are exported to PHP/JSON they aren't displayed into any environments except development mode (and some particular cases).

So keep using ACF_LITE is an acceptable solution

• not introducing any other constant
• have a back compatibility
• may already be widely used by most of the community

from bea-plugin-defaults.

re ^^

from bea-plugin-defaults.

ok guys but what's the point of a github repository if we only use our own constants ?

from bea-plugin-defaults.

I feel that you @tweetpressfr and @Rahe are finally sharing the same point of view about the constant name.
In my opinion, it seems to be the good one 👌

from bea-plugin-defaults.

@Rahe so ? 🤗

from bea-plugin-defaults.

Go for ACF_LITE imho

from bea-plugin-defaults.

Added on the ACF file

from bea-plugin-defaults.