Support » Plugin: WooCommerce Skrill Gateway Plugin » doesnt work

Viewing 4 replies - 1 through 4 (of 4 total)
  • I can upload screen how plugin wont work. When you install you get info:
    “Plugin “Aelia – WooCommerce Skrill Gateway” could not be loaded due to missing requirements.
    Note: even though the plugin might be showing as “active”, it will not load and its features will not be available until its requirements are met”

    and this is the “not to work” code in the plugin:
    require_once(dirname(__FILE__) . ‘/src/lib/classes/install/aelia-wc-skrillgateway-requirementscheck.php’);
    // If requirements are not met, deactivate the plugin
    if(Aelia_WC_Skrill_Gateway_RequirementsChecks::factory()->check_requirements()) {
    require_once dirname(__FILE__) . ‘/src/plugin-main.php’;

    Be fair and make pure commercial plugin and dont waste users time. thx

    Plugin Author Diego


    Checking the requirements is a perfectly normal practice, and you do not need support to make the plugin work. It works out of the box, as long as you install what it needs (which is entirely free).

    If you took the time to read the “missing requirements” message to the end, you will see that it tells you exactly what is missing, and where to get it (there’s a simple link to click). Without knowing what the message say, I guess that the missing requirement is a shared library, that you can download free of charge from our site.

    Don’t be hasty to judge other people’s effort.

    Moderator Jan Dembowski


    Forum Moderator and Brute Squad

    What’s the library for and what’s the library license?

    Plugin Author Diego


    The library is a set of classes on which other plugins are based. It’s an “install and forget” plugin. By itself it doesn’t do much, it simply provides classes that other plugins can use, and it’s 100% GPL. We developed internally to speed up WooCommerce development.

    We got asked a couple of times if we were planning to incorporate the library in the plugins themselves. The answer is no: a separate, shared library is a design choice we explicitly made, moving away from monolithic plugins. We used to have it incorporated in the various products, but it just resulted in code duplication and it increased maintenance exponentially due to multiple plugins trying to load different versions of it.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘doesnt work’ is closed to new replies.