tobiaszander

There’s no need anymore to install the dependencies manually. 1.0.1 is covering that for you.

You can simply activate the plugin by clicking “Activate” in the Installed Plugins menu. No need for an extra issue.

@shokid I’m sorry for the experience you had. The plugin was automatically deactivated on your first try when using v1.0.0. v1.0.0 required to install the composer-dependencies manually, which is a good practice in the PHP world, but we also understand that it’s more convenient for some users to get the dependencies packaged in the repository.

v1.0.1 contains now the dependencies also in the repository which should ease up the installation process.

The plugin is already running in production for our reference customers, safe, secure and tested. But we can definitely improve the first-time-installation-experience, point taken.

@shokid I’m sorry for the experience you had. The plugin was automatically deactivated on your first try when using v1.0.0. v1.0.0 required to install the composer-dependencies manually, which is a good practice in the PHP world, but we also understand that it’s more convenient for some users to get the dependencies packaged in the repository.

v1.0.1 contains now the dependencies also in the repository which should ease up the installation process.

The plugin is already running in production for our reference customers, safe, secure and tested. But we can definitely improve the first-time-installation-experience, point taken.

@shokid Can you please upgrade to version 1.0.1 which was just released? This fixes the dependency issue.

Best,
Tobias.

Thanks we’re now able to reproduce the issue and will release a fixed version early next week.

Hi,

thus actually sounds like composer was not executed sucessfully.

Could you please tell us how you installed the plugin and which WordPress-version you’re using?

Did you encounter any log messages during install?

Best,
Tobias.