Announcement

Collapse
No announcement yet.

Disable PHP.ini edition for customers

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Disable PHP.ini edition for customers

    Hello,

    We are testing the latest LVEManager but dont want our customers to be able to edit several PHP.ini options like Memory limits, etc.
    Can we disable that option?
    Can we completely disable php.ini edition for customers?
    It would be great if we had the same editor on WHM, for all Cloudlinux PHP versions, and not on Cpanel

    If it is not possible to disable that option, can we uninstall latest lvemanager and go back to the older one?

    Best Regards,

  • #2
    You can disable individual options that you dont want user to be able to change:
    It is done using: /etc/cl.selector/php.conf

    Here is more info: http://docs.cloudlinux.com/index.htm...i_options.html

    Comment


    • #3
      Thanks Igor,

      You could just say RTFM!

      Comment


      • #4
        Hello,

        Just detected a BIG problem.
        After the upgrade, all costumers PHP config was set to native and lost configurations.

        Any idea on what has caused that?

        Thanks

        Comment


        • #5
          Hello Paulo!

          There is a bug in lvemanager & cl-selector.
          They show current version of php incorrectly (in some cases).
          But correct php version remains selected actually.
          Could you please verify php versions by executing phpinfo() via web server or by executing
          su -s /bin/bash -c "/usr/bin/php -v" username
          where username is account which is enabled in CageFS.

          The bugfix will be released in two days.

          Comment


          • #6
            yea i noticed this the other day too, my phpinfo was showing 5.3.22 but the php selector had changed back to native (even thought it was still running 5.3)

            Comment


            • #7
              Hi Again,

              One thing we detect is if we disable the edition of some options and set them using piniset, if the user changes any of the allowed options, it will delete the other options we set with piniset.
              How about having two config files, one for the customer and other for the administrator?This way we could have precedence and define custom config options that even if the customer changes them, they are ignored.

              piniset is working, but only after we restart apache.

              Comment

              Working...
              X