Package install failure

Developing with Concrete
#1

I’m developing (updating) a package locally. The package loads fine in docker (running concrete 9.1.2)

I just went to deploy the update to my dev site (EC2 instance in AWS) as I have always done:

  • upload the package folder via ssh
  • login to the dashboard and apply the update via the dashboard

This time, however, when I attempt to install the package I get an error:

error source: /opt/bitnami/concrete5/updates/concrete-cms-9.1.3_remote_updater/concrete/src/View/View.php
line 552: include $_file;
Message: "include(/opt/bitnami/concrete5/packages/esperanto_cards/elements/dashboard/install.php): failed to open stream: No such file or directory"

The site uses a bitnami image, and my package name is “esperanto_cards”.

My package has no dashboard components at all. It has no root level /elements folder, and it has no install.php file anywhere in it.

Why the update process is looking for an install.php file within a non-existent folder in my package path is beyond me.

Note: There was one thing that I did differently this time - I allowed my site (a dev site) to update to concrete 9.1.3 before updating my package. I have no idea if this is related to the problem I now see, but I mention it for completeness.

At this point, I can’t risk deploying it to my production site, but I get no errors when deploying to docker. I don’t know what to try.

I really would appreciate some help, I am at my wit’s end with concrete lately. :stuck_out_tongue: To get this far and now not be able to load the update to my site is nearly the last straw.

#2

Hi @Davo - does your package install on a fresh 9.1.3 install?

I would try clearing the cache on your development site and then try installing your package again. You might also try running the upgrade process again in case something didn’t quite finish or something there.

It’s hard to know much more without knowing how your package is constructed, and also the bitnami image is another bit of an x factor there.

#3

If what @EvanCooper suggests doesn’t work, you could hack your way around it by adding that element file to your package. It’s just a file Concrete will show right before installing your package. It’s used to give users installation options, but it can also be simply a message or even an empty file.

1 Like