Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #1469112

    I know this is probably a taboo subject right now, but in the interests of trying to shore up dev stacks and liabilities, has the team been watching over the slow moving train wreck that is the battle between Matt and WPEngine? There are a lot of factors at play, and good and bad things both sides are saying and doing right now. The potentially huge implications for both the platform (Enfold included), the way licenses are managed, outward appearances of open source versus corporate guidance, and if there are other side-effects that we don’t see yet on the horizon, make it something of a need to know as much as possible, since the two major players are acting so erratically at the moment.

    I am not asking for the team to pick a side, but more of opening the door to knowing how it affects you, the development and whether there are any needs from us as end users and promoters of Enfold.

    Thank you, as always for an amazing theme, backed by one of the best dev teams on the platform.

    -jason

    #1469161

    Hey Jason,

    What’s going on right now doesn’t affect Enfold or Enfold users in any way.

    We added the Dynamic Content feature ( https://kriesi.at/documentation/enfold/custom-layout-and-dynamic-content/ ) and made it compatible with the ACF plugin. This feature works as expected with the SFC ( https://wordpress.org/plugins/advanced-custom-fields/ ) plugin as well.

    If you notice any compatibility issues with the SCF plugin, please let us know.

    Regards,
    Yigit

Viewing 2 posts - 1 through 2 (of 2 total)
  • The topic ‘WordPress v. WPEngine fiasco’ is closed to new replies.