Plugin v5 not showing on wordpress dasboard

Marketplace Integration Help
1

Problem Description

The Auth0 plugin is installed and appears in the plugins directory but does not show up in the WordPress admin panel for activation.

Operating System:

  • Name: Debian GNU/Linux
  • Version: 11 (bullseye)

PHP Configuration:

  • Version: 8.2.13
  • memory_limit: 512M
  • upload_max_filesize: 80M
  • post_max_size: 80M

Database:

  • Database Server: MariaDB
  • Version: 11.1.3

WordPress:

  • Version: 6.5.3

Other Relevant Directories:

  • WordPress Installation: /opt/bitnami/wordpress
  • Plugins Directory: /opt/bitnami/wordpress/wp-content/plugins
  • Vendor Directory (within plugins): /opt/bitnami/wordpress/wp-content/plugins/vendor

Plugin Details:
/opt/bitnami/wordpress/wp-content/plugins/
├── auth0 → …/vendor/auth0/wordpress (symbolic link)
└── vendor
├── auth0
│ ├── auth0-php
│ └── wordpress
├── autoload.php
├── bin
├── composer
├── nyholm
├── php-http
├── psr
├── psr-discovery
└── symfony

2

I ran it from the wp-content/plugins sub-directory.

composer require symfony/http-client nyholm/psr7 auth0/wordpress:^5.0

4

edit: corrected tree path

image
image901×570 5.39 KB

5

Hi @seranca, thanks for the detailed breakdown. Can you please open a shell, cd into wp-content/plugins/auth0, run composer install and see if that changes anything for you?

6

There is no folder Auth0, I made a symbolic link to try to make wordpress recognize the plugin.

image
image1072×61 4.74 KB

plugins/auth0 points to /vendor/auth0

auth0 → …/vendor/auth0/wordpress

I run composer install but it won’t do anything as it is already installed

image
image1738×275 32.3 KB

7

@evansims Thanks for your help. I solve it by restarting the apache server.

sudo /opt/bitnami/ctlscript.sh restart apache

8

Hi, for anyone wondering.

The problem lies because Wordpress won’t detect the plugin. So creating a symbolic link or creating a custom Plugin Loader which summons Auth0 might do the trick

9

Hi @seranca :wave: Glad you got it sorted out!

A custom plugin loader and/or symlink should not be at all necessary, but the particular configuration of the server software you’re using may have unique constraints around it’s PHP search pathing. I only note it here as a caution, as that would not be one-size-fits-all advice to follow.

1 Like