Uploaded image for project: 'eZ Publish / Platform'
  1. eZ Publish / Platform
  2. EZP-27558

5.x documentation must be more clear about zeta components

    Details

      Description

      In the 5.x installation procedure it says ...

      As of eZ Publish 5.2, if you plan to use eZ Publish legacy only, as standalone (as in pointing apache to ezpublish_legacy folder or extracting only ezpublish_legacy), then Zetacomponents must be installed if you don't already have it via PEAR.

      If we install the site via composer we will get zetacomponents/archive 1.5
      If we install the zetacomponents via PEAR we will get components.ez.no/Archive-1.4.1

      If the installation of zetacomponents via PEAR is not supported anymore (since it was intended for legacy), the documentation must be clear about it.
      Otherwise, if it should be supported, the PEAR repository ezc/eZComponents should be updated.

        Activity

        Hide
        André Rømcke added a comment - - edited

        From what I can see we can remove the For all 5.x versions : Install Zetacomponents for a pure legacy setup section.

        Zeta Components are:

        It basically uses Composer to autoload Zeta, which is again telling Composer to dump class map for Zeta files, which is why $baseEnabled is set to false here as we don't need to handle it ourselves.

        But, this is theory, this needs to be checked by someone.

        Show
        André Rømcke added a comment - - edited From what I can see we can remove the For all 5.x versions : Install Zetacomponents for a pure legacy setup section. Zeta Components are: Defined in composer.json: https://github.com/ezsystems/ezpublish-legacy-ee/blob/5.4/composer.json Also it seems to be taken automatically into account: https://github.com/ezsystems/ezpublish-legacy-ee/blob/5.4/autoload.php In the following section: // Composer if in eZ Publish legacy context else if ( file_exists( "{$legacyVendorDir}/autoload.php" ) ) { require_once "{$legacyVendorDir}/autoload.php"; $baseEnabled = false; } It basically uses Composer to autoload Zeta, which is again telling Composer to dump class map for Zeta files, which is why $baseEnabled is set to false here as we don't need to handle it ourselves. But, this is theory, this needs to be checked by someone.
        Hide
        Jacek Foremski (Inactive) added a comment -

        I tested it a little and this is what I gather:

        • The autoload file in Legacy tries to load the Zeta Components from the eZ Publish 5. If there is no autoload file there, then it proceeds to try to load them from the Legacy vendor dir. If there is no autoload file there, then it proceeds to load the Zeta Components from the PEAR.
        • The documentation refers to the second option (loading the Zeta Components from the Legacy vendor dir). I guess it is correct that you need to do composer install from the Legacy directory if you are using the Legacy only.
        • If we advise against using the PEAR repository with outdated Zeta Components and we are not planning on updating them, then I think we should just delete the if you don't already have it via PEAR fragment from the documentation. Even if someone has them installed through PEAR, the ones from the composer will be used if they are installed.
        Show
        Jacek Foremski (Inactive) added a comment - I tested it a little and this is what I gather: The autoload file in Legacy tries to load the Zeta Components from the eZ Publish 5. If there is no autoload file there, then it proceeds to try to load them from the Legacy vendor dir. If there is no autoload file there, then it proceeds to load the Zeta Components from the PEAR. The documentation refers to the second option (loading the Zeta Components from the Legacy vendor dir). I guess it is correct that you need to do composer install from the Legacy directory if you are using the Legacy only. If we advise against using the PEAR repository with outdated Zeta Components and we are not planning on updating them, then I think we should just delete the if you don't already have it via PEAR fragment from the documentation. Even if someone has them installed through PEAR, the ones from the composer will be used if they are installed.
        Hide
        André Rømcke added a comment -

        [~jacek.foremski@ez.no] Does the updated doc work for you? https://doc.ez.no/display/EZP/Installing+eZ+Publish+on+a+Linux-UNIX+based+system

        Note: Given 5.2 has not been supported for years I took the liberty to simplify the section and add all relevant information in the Composer section.

        Show
        André Rømcke added a comment - [~jacek.foremski@ez.no] Does the updated doc work for you? https://doc.ez.no/display/EZP/Installing+eZ+Publish+on+a+Linux-UNIX+based+system Note: Given 5.2 has not been supported for years I took the liberty to simplify the section and add all relevant information in the Composer section.
        Hide
        Jacek Foremski (Inactive) added a comment -

        André Rømcke Sure, I think it is correct (and more clear), as the documentation now doesn't mention PEAR at all and there is a note about pure legacy setup.

        Show
        Jacek Foremski (Inactive) added a comment - André Rømcke Sure, I think it is correct (and more clear), as the documentation now doesn't mention PEAR at all and there is a note about pure legacy setup.
        Hide
        Rui Silva (Inactive) added a comment -

        Documentation validated by QA.

        Show
        Rui Silva (Inactive) added a comment - Documentation validated by QA.

          People

          • Assignee:
            Unassigned
            Reporter:
            Ricardo Correia (Inactive)
          • Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: