• Resolved edmonaft

    (@edmonaft)


    It says:

    Plugin could not be activated because it triggered a fatal error.

    Fatal error: Uncaught Error: Class ‘WeDevs\ERP\CRM\Google_Auth’ not found in C:\xampp\htdocs\wp-content\plugins\erp\wp-erp.php:260 Stack trace: #0 C:\xampp\htdocs\wp-content\plugins\erp\wp-erp.php(123): WeDevs_ERP->instantiate() #1 C:\xampp\htdocs\wp-content\plugins\erp\wp-erp.php(92): WeDevs_ERP->setup() #2 C:\xampp\htdocs\wp-content\plugins\erp\wp-erp.php(337): WeDevs_ERP::init() #3 C:\xampp\htdocs\wp-content\plugins\erp\wp-erp.php(341): wperp() #4 C:\xampp\htdocs\wp-admin\includes\plugin.php(1897): include(‘C:\\xampp\\htdocs…’) #5 C:\xampp\htdocs\wp-admin\plugins.php(178): plugin_sandbox_scrape(‘erp/wp-erp.php’) #6 {main} thrown in C:\xampp\htdocs\wp-content\plugins\erp\wp-erp.php on line 260

    The page I need help with: [log in to see the link]

Viewing 4 replies - 1 through 4 (of 4 total)
  • Hello @edmonaft,

    You need to follow the following steps in case of cloning from the GitHub:

    • Clone the repository inside /wp-content/plugins/
    • CD into folder cd wp-erp and run composer install
    • Lastly, run composer dump-autoload -o

    Thanks

    Thread Starter edmonaft

    (@edmonaft)

    Hi @thebengalboy,

    I am running XAMPP under Windows
    In that directory there are 2 “composer” files that I don’t know how I can run under Windows.
    – composer.json
    – composer.lock

    Thank you.

    Hello @edmonaft,

    It’s really tough to help you configuring composer actually as you are on your local site. In that case, I’d recommend you to use the current released version from the WordPress.org.

    Regards

    Thread Starter edmonaft

    (@edmonaft)

    Hi @thebengalboy,

    No worries. I am just taking a practice to always download the latest one from github to ensure that all latest fixes i get.

    So far, the build prior to this latest works. Therefore I am keeping this for now until i can try a newer update to this current build.

    Regards,

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Latest github package error in activating’ is closed to new replies.