• Resolved yogiman

    (@yogiman)


    I am getting the following error when I try to activate the WP PhpMyAdmin plugin on my Azure WordPress App service + MySQL Instance (not using in app DB).

    Fatal error: Trait ‘default_methods__ProtectPages_com’ not found in
    D:\home\site\wwwroot\wp-content\plugins\wp-phpmyadmin-extension\index.php on line 36

    The same error is also mentioned here: https://plugintests.com/plugins/wp-phpmyadmin-extension/latest seems to be an issue with the latest build.

    Thanks

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thanks for report, nice catch. I’ve tested it specially on Azure App-Service and I confirm the issue (only happens there).
    I will try to fix it and update this topic.

    Plugin is now updated. You can check and please confirm if it works.

    Thread Starter yogiman

    (@yogiman)

    Hi Tazo, Appreciate the quick fix. I was able to activate the plugin, but now it does not let me login. In the Welcome to phpMyAdmin, Login page I get this error below username/password

    Error while working with template cache: Failed to write cache file “./tmp//twig/f6/f6dd8681e6c232e111b59c5409d9c6c1aa3b25c4ca5a3e3156eed54ca547df64.php”.

    Then when I enter my credentials it gives me this error in addition to the previous one. mysqli_real_connect(): (HY000/9002): The connection string may not be right. Please visit portal for references.

    Just to clarify, I used the WordPress Template in the Azure Marketplace with App service and Azure DB for MySQL Instance to provision WordPress.

    Hope this helps and Thanks for the excellent Plug-in.

    well, i am not much prof in Azure.
    will this help?

    https://stackoverflow.com/a/37591502/2377343
    you might need to set permission 755 to that tmp folder.

    or this:

    https://social.msdn.microsoft.com/Forums/vstudio/en-US/9146580e-84ba-4405-9d2d-bc4dcbc968fe/azure-mysql-preview-issue-with-connectivity-firewall-rules?forum=ssdsgetstarted

    there is said, that connection server should be in such example format:

    [email protected]

    so, in wp-config.php, see how the DB_HOST address is setup.
    if its not like above, then this could be reason.
    to fix that, you might need to change that at first in wp-config.php, then delete and reinstall plugin, or directly modify the config file of the plugin at:

    wp-content/plugins/wp-phpmyadmin-extension/lib/ ***PHPMYADMIN_FOLDER***/config.inc.php

    and in the 13th line, set the host-name like discucced above, then try to login again.

    • This reply was modified 8 years, 1 month ago by tazotodua.
    Thread Starter yogiman

    (@yogiman)

    I am able to login now. The host-name was setup correctly. I tested in MySQL Workbench and found out that we need to specify username on the phpmyadmin login page in the myuser@myserver format. Regarding the cache issue, I checked the permissions and they appear to be set to 755.

    drwxr-xr-x 1 Unknown+User Unknown+Group 0 May 2 20:10 twig

    It seems the PHP temp path reference, it has two slashes in the path before twig, could this be the issue?

    “./tmp//twig/f6/f6dd8681e6c232e111b59c5409d9c6c1aa3b25c4ca5a3e3156eed54ca547df64.php”

    Appreciate your help.

    well, actually that issue is not coming from plugin, but maybe from phpMyAdmin itself (it is not handled by me). can you tell me exactly which file fires that error?

    I even think that doesnt come from PMA, maybe something other plugin/file causes WP error in general?

    • This reply was modified 8 years, 1 month ago by tazotodua.
    Thread Starter yogiman

    (@yogiman)

    You’re correct. I have fixed it, at least for now, by adding this to the config.inc.php it seems the default value was ‘./tmp/ causing the ./tmp//twig I mentioned earlier.

    $cfg[‘TempDir’] = ‘./tmp’;

    Thanks for your help. cheers!

    good.
    i’ll close the topic. if you want, you can leave the review.
    https://ww.wp.xz.cn/support/plugin/wp-phpmyadmin-extension/reviews/?filter=5

    thanks

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

The topic ‘Fatal Error when Activating Plugin in Azure’ is closed to new replies.