Fatal error when Relevanssi is not activated

  • Resolved Felds

    (@felds)


    3 years, 10 months ago

    When this plugin is installed and activated before Relevanssi, it returns a fatal error, blocking me from installing and activating Relevanssi itself.
    The only solution I found was to edit the database or wiping it off and starting from scratch; both being not ideal.

    This is especially bad when using something like TGM Plugin Activation for bulk installation, since it breaks the whole installation workflow.

    My only option currently is to ask my users to activate REST API for Relevanssi separately after everything is installed.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Sergiy Dzysyak

    (@dzysyak)

    That seem to be normal behavior to prevent activation of API prior to Relevanssi itself. This would cause help requests like API is not working for some unknown reason.
    If you have some suggestions, you may explain your vision.
    Should not TGM Plugin Activation install/activate plugins in order defined in plugin array?

    Thread Starter Felds

    (@felds)

    It would be nice not to have the whole admin blocked from use. Maybe an alert on the top of the dashboard?

    Is the code on github? I could implement it myself and send you a pull request…

    Plugin Author Sergiy Dzysyak

    (@dzysyak)

    I have removed blocking requirement on plugin activation. Now API request will return error, if Relevanssi is not activated. This should solve your problem.

    Thread Starter Felds

    (@felds)

    Awesome!!
    Thank you for helping! ??

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Fatal error when Relevanssi is not activated’ is closed to new replies.