Forum replies created

    Sapere Aude
    Spectator
    Posts: 75
    July 4, 2017 at 6:10 pm #34167
    This reply has been marked as private.
    Sapere Aude
    Spectator
    Posts: 75
    July 4, 2017 at 1:13 pm #34165
    This reply has been marked as private.
    Sapere Aude
    Spectator
    Posts: 75
    July 4, 2017 at 1:12 pm #34164

    ignore this

    Sapere Aude
    Spectator
    Posts: 75
    July 4, 2017 at 2:16 am #34158

    OK. Somewhere we are losing each other. 🙂 Here’s what I did after purchasing evolve+

    1: Downloaded evolve+

    2: Downloaded Theme4Press Core+Composer plugin

    3: Installed evolve+ theme and ACTIVATED the theme

    4: Installed Theme4Press Core +Composer plugin

    5: DEACTIVATED Theme4Press Core Standard plugin

    6: ACTIVATED Theme4Press Core + Composer plugin (so I could try composer).

    7: The error from my original post occurred.

    8: DEACTIVATED Theme4Press + Composer

    9: ACTIVATED Theme4Press Standard

    10: The error no longer occurs.

    11: Just to be sure of the issue I DEACTIVATED Theme4Press Core Standard and DELETED the files.

    12: ACTIVATED Theme4Press Core + Composer

    13: The exact same error came back.

    14: Switched to my old theme and completely removed evolve+ AND it’s associated plugins.

    15: Cleared all caches

    16: Reinstalled evolve+

    17: ACTIVATED evolve+ and related plugins.

    18: DEACTIVATED Theme4Press Core standard plugin.

    19 Installed Theme4Press Core+Composer plugin

    20. ACTIVATED Theme4Press Core+Composer plugin

    21: Same error as my original post came back.

    20: DEACTIVATED Theme4Press Core+Composer plugin

    21: ACTIVATED Theme4Press Core standard plugin

    22: NO ERROR.

    SO, this tells me that something in the Theme4Press+Composer plugin is making this error occur as it does NOT occur with only the Theme4Press Core STANDARD plugin ACTIVATED.

    Sapere Aude
    Spectator
    Posts: 75
    July 3, 2017 at 11:47 am #34154

    Hello again,

    Maybe I did not word this correctly. The error above comes up ONLY when Theme4Press Core + Composer is ACTIVE.

    If I DEACTIVATE Theme4Press + Composer and then activate the standard Theme4Press Core, the error does NOT occur.

    I do understand that Composer is in beta.

    Thank you!