Wordpress Toolkit does not operate properly on Cloudlinux server with alt-php

Follow

Comments

14 comments

  • Avatar
    Lenor

    Hi, when will there be a fix? 

    this problem exists since month now :-( 

    1
    Comment actions Permalink
  • Avatar
    Yulia Plokhotnikova

    @Lenor,

    This bug is planned to be fixed in the WordPress Toolkit release 5.0. The release date is not available now. You may subscribe to this article to be notified when the bug would be fixed.

    0
    Comment actions Permalink
  • Avatar
    Michele

    Hello Yulia... 5.0 version will be the next version of WordPress Toolkit (4.6) or we need to expect other versions (e.g. 4.7, 4.8, 4.9) before to see the bug fixed?

    Another question, this bug it was fixed because I've given you (and CloudLinux tech support) the possibility to enter on my server to see what happened when I realized the situation had become unmanageable, so... once it is solved should I expect more control on your part (Plesk) on the compatibility with CloudLinux or as your colleague Igor said on the public forum this operating system does not have priority in your development plans?
    Mod_isapi is a killer feature for my websites hosted on the server and and having it deactivated leaves me "quite" bitter.

    Thanks.

    0
    Comment actions Permalink
  • Avatar
    Yulia Plokhotnikova

    Hi @Michele,

    We can expect WordPress iterations like 4.7, but developers noted that the bug is expected to be fixed starting from the next major version which is 5.0 version.

    As for CloudLinux, indeed there are no plans for new features so far, but you can share your suggestions on the User Voice, the portal that is being monitored by our developers closely. This would be more suitable portal for discussing development plans. The most popular features have the priority in Plesk development.

    0
    Comment actions Permalink
  • Avatar
    Kris

    Any news about this since april, 4 months ago?

    Thank you

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello Kris,

    Currently, there's no news about the issue. The error originally is caused by alt-php limitation.

    For now, please, use the proposed workaround.

    0
    Comment actions Permalink
  • Avatar
    Michele (Edited )

    The reference about "5.0 version" is disappeared, so I was wondering when this problem will be solved definitively.
    What is the new time reference?

    0
    Comment actions Permalink
  • Avatar
    Julian Bonpland Mignaquy

    Michele Have you tried the workaround provided? Our developers have concluded that this is not a Plesk bug but an alt-php bug that should be addressed by them.

    0
    Comment actions Permalink
  • Avatar
    Lenor (Edited )

    Julian Bonpland Mignaquy .... CloudLinux Support syas its up to Plesk Support. 

    Plesk support says, its CloudLinux fault. 

    Great. Anyone wants to help here? 

    Maybe you could have a Call with CL Support??

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov (Edited )

    @Lenor and others signed to this article,

    My previous reply iteration was imprecise. I've discussed this behavior with the CL representative.

    The cause of such behavior is due to the CloudLinux PHP Selector implementation so that Alt-PHP can be used in conjunction with Plesk PHP Selector. More information may be found here: https://docs.cloudlinux.com/cloudlinux_os_components/#php-extensions

    0
    Comment actions Permalink
  • Avatar
    Michele (Edited )

    I confirm you that using the workaround the issue is fixed (I added "pdo_mysql.so" because WordPress requires it and it's disabled like the other two):
    extension=json.so
    extension=mysqli.so
    extension=pdo_mysql.so

    Very important, is necessary to disable them on the "PHP selector" for each hosting to avoid PHP errors as "Module 'mysqli' already loaded at Unknown#0".

    Anyway, I hope that in the future Cloudlinux will be more integrated with Plesk because these workarounds don't convince me too much, especially when we will have to update the PHP handler or Plesk/CL(8).

    0
    Comment actions Permalink
  • Avatar
    Leonid Gukhman

    @Michele

    Hi, thanks for the tip, the article has been updated accordingly.

    1
    Comment actions Permalink
  • Avatar
    Lenor

    Ivan Postnikov thank you (all). 

    So this Workarround seems working. But i don't loose Features of CL PHP Versions right? 

    It seems, that the Domain still delivers alt-php74-fastcgi which i think is good. So the normal Wordpress/ PHP Version which is used, is alt-php74-fastcgi (from CL) and the Toolkit somehow makes something else, right? 

    0
    Comment actions Permalink
  • Avatar
    Leonid Gukhman

    @Lenor

    Extensions will be still available after applying the workaround.

    Alt-PHP is used for the domain, with 'normal' PHP installed from Plesk being disabled.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request