Error message when loading
Permalink
After I upload the ProBlog package and go the Add Functionality page, I get the following error message:
Warning: require_once(/var/www/html/packages/problog/controller.php): failed to open stream: Permission denied in /var/www/html/concrete/core/libraries/loader.php on line 328
Fatal error: require_once(): Failed opening required '/var/www/html/packages/problog/controller.php' (include_path='/var/www/html/libraries/3rdparty:/var/www/html/concrete/libraries/3rdparty:.:/usr/share/php:/usr/share/pear') in /var/www/html/concrete/core/libraries/loader.php on line 328
Does anyone know how to fix this error? ProBlog support says this is a Concrete5 issue.
Thanks!
Warning: require_once(/var/www/html/packages/problog/controller.php): failed to open stream: Permission denied in /var/www/html/concrete/core/libraries/loader.php on line 328
Fatal error: require_once(): Failed opening required '/var/www/html/packages/problog/controller.php' (include_path='/var/www/html/libraries/3rdparty:/var/www/html/concrete/libraries/3rdparty:.:/usr/share/php:/usr/share/pear') in /var/www/html/concrete/core/libraries/loader.php on line 328
Does anyone know how to fix this error? ProBlog support says this is a Concrete5 issue.
Thanks!
Thanks for the reply —
I've tried that, and I get this error when I assign full 777 permissions.
I've tried that, and I get this error when I assign full 777 permissions.
Does anyone have any other suggestions on this problem?
Thanks!
Thanks!
Bumping this again to see if anyone has suggestions - thanks!
Any more detail available from ChadStrat other than just "ProBlog support says this is a Concrete5 issue"
Does he tell you what issue he is referring to?
Does he tell you what issue he is referring to?
This was the entire response:
"Hi, sounds like you will want to go to your C5 profile here on this site and go to your projects area and release the addon from the project. Once you do so, you can go to your transactions -> licenses area and manually download the addon and FTP it to your web server's /packages folder of your C5 site. Once doing so you should be fine. Or, you can post a support ticket in the main C5 support area as this is not anything that we can help you with. i.e. - this is Concrete5 issue, not an addon issue here."
I've already uninstalled, trashed and re-uploaded the add-on. Everything is fine until I give it full permissions and then I get the error message.
"Hi, sounds like you will want to go to your C5 profile here on this site and go to your projects area and release the addon from the project. Once you do so, you can go to your transactions -> licenses area and manually download the addon and FTP it to your web server's /packages folder of your C5 site. Once doing so you should be fine. Or, you can post a support ticket in the main C5 support area as this is not anything that we can help you with. i.e. - this is Concrete5 issue, not an addon issue here."
I've already uninstalled, trashed and re-uploaded the add-on. Everything is fine until I give it full permissions and then I get the error message.
What directories are you assigning '777' to. Why are you needing to do that?
I'm uploading to a server that will not read my files unless I open the permissions.
When I upload the problog package, it doesn't show up under my waiting to install. If I open all the permissions to that folder, I'm getting the error I mentioned above.
The package was loaded before, but wasn't performing properly, so I uninstalled and trashed it. Then I've uploaded the latest Problog version.
I assumed the reason it wasn't showing up under the Awaiting installations was because the permissions weren't allowed. What am I missing?
When I upload the problog package, it doesn't show up under my waiting to install. If I open all the permissions to that folder, I'm getting the error I mentioned above.
The package was loaded before, but wasn't performing properly, so I uninstalled and trashed it. Then I've uploaded the latest Problog version.
I assumed the reason it wasn't showing up under the Awaiting installations was because the permissions weren't allowed. What am I missing?
It seem sthat is a right permission on files.