Installing Packages on 5.4.1 not working
Permalink
Hi,
Here's my problem:
Fresh install of 5.4.1 - I put a package in the packages/ directory and then open up the Add Functionality page in the Dashboard.
The package shows up fine - I then click Install and get the following error:
An unexpected error occurred.
not found. Please check that the block controller file contains the correct class name.
As you can see the class variable is empty for some reason (usually that error should display the classname which it cannot find, as far as I can gather)
The package now shows up as installed - but doesn't work.
This happens with ALL packages. I have checked file permissions and rights - and everything looks peachy. What could be going on here??
I have looked a bit at concrete\models\block_types.php where this error is thrown - and it seems to me it is finding the file OK - and all the require_once statements are fine (i.e. I should be seeing a different error if C5 wasn't able to open the controller.php file)
So something else is funky. Another install with C5.0.5 on the same server works just fine.
Could something in my config (site.php) be affecting package installation?
Thanks!
Psst
Here's my problem:
Fresh install of 5.4.1 - I put a package in the packages/ directory and then open up the Add Functionality page in the Dashboard.
The package shows up fine - I then click Install and get the following error:
An unexpected error occurred.
not found. Please check that the block controller file contains the correct class name.
As you can see the class variable is empty for some reason (usually that error should display the classname which it cannot find, as far as I can gather)
The package now shows up as installed - but doesn't work.
This happens with ALL packages. I have checked file permissions and rights - and everything looks peachy. What could be going on here??
I have looked a bit at concrete\models\block_types.php where this error is thrown - and it seems to me it is finding the file OK - and all the require_once statements are fine (i.e. I should be seeing a different error if C5 wasn't able to open the controller.php file)
So something else is funky. Another install with C5.0.5 on the same server works just fine.
Could something in my config (site.php) be affecting package installation?
Thanks!
Psst
is this a custom package? if so, can you post the controller (just the top part)
Hi Mnkras,
Thanks for wanting to help out. Unfortunately it doesn't matter whether I post a part of controller.php or not - as the problem presents itself with ALL packages I have tried from the marketplace (which work fine in other installations of C5)
So the problem is NOT with the packages. Something is going wrong at the system-level.
I am focusing on differences between 5.0.5 and 5.4.1 right now, as that seems to be the most promising approach. This is a very mysterious problem however... I might have to go as far as start debugging the core C5 code to track this one down.
Thanks for wanting to help out. Unfortunately it doesn't matter whether I post a part of controller.php or not - as the problem presents itself with ALL packages I have tried from the marketplace (which work fine in other installations of C5)
So the problem is NOT with the packages. Something is going wrong at the system-level.
I am focusing on differences between 5.0.5 and 5.4.1 right now, as that seems to be the most promising approach. This is a very mysterious problem however... I might have to go as far as start debugging the core C5 code to track this one down.
are you on windows/linux,
are you running from the /updates folder,
are you running from the /updates folder,
Debian LAMP stack - and no I am not running from the /updates folder (not really sure what that means...)
I.E. Fresh install of C5 - Nothing fancy or customized going on
I.E. Fresh install of C5 - Nothing fancy or customized going on
can you post a <?php phpinfo(); ?>
What does;
"are you running from the /updates folder, " mean?
"are you running from the /updates folder, " mean?
when you do the easy upgrade in concrete5, the core is run out of the /updates folder,
since its a fresh install that is not the case,
since its a fresh install that is not the case,
Ok so what does that mean about the core installation that I have (the contents of the concrete folder). If I read what you are saying correctly I now have two cores installed at my server one in the updates folder and one in the concrete folder off of root.
no, you have 2 cores only if you upgrade, but you didn't since its a fresh install,
can you re-upload the entire /concrete directory
can you re-upload the entire /concrete directory
Hi Mnkras,
First of all: Thanks a million for wanting to help out - it is much appreciated :)
And Brian: Are you having the same problem, or just trolling around?
In any case - I don't want to post a phpinfo here. I don't think it would help you much in any case as it is a standard PHP5 environment. It would help more if you were to tell me what you were thinking you might discover if you saw a phpinfo - I am a developer as well, so I'll follow whatever you have in mind ;)
I will put in some hours now debugging this thing and stepping through the code in concrete/models/block_types.php and see if I can't figure out this problem
I will let you know what I find - Thanks for your time so far!
Psst
First of all: Thanks a million for wanting to help out - it is much appreciated :)
And Brian: Are you having the same problem, or just trolling around?
In any case - I don't want to post a phpinfo here. I don't think it would help you much in any case as it is a standard PHP5 environment. It would help more if you were to tell me what you were thinking you might discover if you saw a phpinfo - I am a developer as well, so I'll follow whatever you have in mind ;)
I will put in some hours now debugging this thing and stepping through the code in concrete/models/block_types.php and see if I can't figure out this problem
I will let you know what I find - Thanks for your time so far!
Psst
Hello Psst,
No I don't have the same problem and I have started a new thread about the issue of the updates folder. What I have is an installation that I can't update and I am trying to understand the directory structure.
Hope I didn't confuse things to much.
No I don't have the same problem and I have started a new thread about the issue of the updates folder. What I have is an installation that I can't update and I am trying to understand the directory structure.
Hope I didn't confuse things to much.
Ok this is as far as I have gotten:
The reason why package installation fails is because the method
$pkgHandle = $this->getPackageHandle();
called from function _getClass() in block_types.php (around line 555)
Fails. I.e. it results in $pkgHandle being NULL - which in turn causes the following if else file_exists statements in this function - which try to include controller.php from the package - to fail (it ends up looking for controller.php in my blocks subdir - which is wrong)
looking at getPackageHandle(); this directs me to PackageList::getHandle($this->pkgID);
Which is where I get stuck - as now we are so deep in the core, that I can't quite wrap my head around what is going on. Seems like the package I am trying to install hasn't been added to an internal list yet - and this is why the handle ends up being NULL - I could be wrong though.
I would like to bring this to the attention of the developers - tips? - Thanks! :)
Psst
The reason why package installation fails is because the method
$pkgHandle = $this->getPackageHandle();
called from function _getClass() in block_types.php (around line 555)
Fails. I.e. it results in $pkgHandle being NULL - which in turn causes the following if else file_exists statements in this function - which try to include controller.php from the package - to fail (it ends up looking for controller.php in my blocks subdir - which is wrong)
looking at getPackageHandle(); this directs me to PackageList::getHandle($this->pkgID);
Which is where I get stuck - as now we are so deep in the core, that I can't quite wrap my head around what is going on. Seems like the package I am trying to install hasn't been added to an internal list yet - and this is why the handle ends up being NULL - I could be wrong though.
I would like to bring this to the attention of the developers - tips? - Thanks! :)
Psst
can you show me the directory tree of your /packages directory, and have you tried re-uploading the /concrete directory,
