Fatal Error on loading external library

  • Resolved sgot

    (@sgot)


    3 years, 6 months ago

    Hi Doeke!
    I noticed that there was other people having a similar issue, but I decided to open another thread because I didn’t want to mix things up.

    I have a website in my local env. These are the specs:
    Windows + Laragon
    PHP 7.4.20
    Gravity Forms Entries in Excel 1.8.14
    GravityForms 2.5.8
    Wordpress 5.8
    So everything is up to date and works fine.

    My staging env is Linux/unix machine but it has pretty the same specs.
    When it had installed:
    Gravity Forms Entries in Excel 1.8.4
    GravityForms 2.4.18
    Wordpress 5.7.2
    everything worked well, but when I deploy all my code I get the following error:
    PHP Fatal error: require(): Failed opening required '[...]/plugins/gf-entries-in-excel/vendor/composer/../markbaker/matrix/classes/src/Functions/adjoint.php' (include_path='.:/usr/share/pear7:/usr/share/php') in [...]/plugins/gf-entries-in-excel/vendor/composer/autoload_real.php on line 71

    Those two dots between /composer/ and /markbaker/ (as if it’s trying to go one directory up) in my humble opinion are really the point, as the file is not found because of a wrong path.
    In the plugin, the directories composer and markbaker are at the same level, that is the vendor directory, and not one inside the other.

    Can you please point me to the solution?
    Could maybe the server set in a particular way to not be able to interpret the dots get the correct file?

    Thanks a lot!

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Doeke Norg

    (@doekenorg)

    Hi @sgot, the path is actually correct, because the autloader is inside the composer folder. So it needs to go one up to vendor en from there on to markbaker. It think the files are missing. I see you have 1.8.4 installed. Any chance you could bump that to the latest version? Could be a flawed version.

    Thread Starter sgot

    (@sgot)

    Hi Doeke,
    sorry, maybe I didn’t explain well…
    I wrote:

    When it had installed:
    Gravity Forms Entries in Excel 1.8.4

    and then

    when I deploy all my code (new versions from my local environment, described above) I get the following error…

    Anyways, to answer to your advice, the files are deployed correctly and they are there, in the right directory.

    BUT, just now, while I’m writing you, I just triple checked and I realized that the remote server (accessed via SSH) has the Functions directory written in lowercase…

    Could it be the DAMN problem??!?
    If so, WHO told the server to lowercase it? In my local env I have it in uppercase…
    ??

    • This reply was modified 3 years, 6 months ago by sgot.
    Thread Starter sgot

    (@sgot)

    This is the result of the ls command:

    Builder.php Decomposition Exception.php Functions.php Matrix.php Operators functions operations

    Together with functions, operations directory is also lowercase, while Decomposition and Operators have capital letters…

    In my PC all files in this particular directory (vendor\markbaker\matrix\classes\src) have capital letters.
    How is this possible?

    • This reply was modified 3 years, 6 months ago by sgot.
    Plugin Author Doeke Norg

    (@doekenorg)

    Ah, I believe the markbaker plugins were changed recently from lower case to capital. So it used to be lower during 1.8.4.

    Maybe when you copied the files it didn’t update the folder name to the uppercase. I think you can update it by hand and it should work.

    Thread Starter sgot

    (@sgot)

    Hi again Doeke,
    I confirm that the problem was the capital letter issue…

    The files copy in my case was made via BitBucket, deploying the code on AWS.

    For the record, and to try to help others in my same situation, the problem is that the rsync command, ignores changes in files and directories names.
    It checks only differences in files content.

    Thanks a lot for your kindness.

    Plugin Author Doeke Norg

    (@doekenorg)

    Cool. Glad you got it fixed. And thank you for sharing your solution!

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Fatal Error on loading external library’ is closed to new replies.