Forums

Unable to update addons

Permalink
Hello,

If anyone could offer any recommendations it would be greatly appreciated. I am unable to update my addons. Although I am currently in 5.6.0.2, these has been an issue in previous versions.

I would like to mention that my site is running on a IIS 7.0 server.

Here is a breakdown of what is occuring:
When I login to my site, I will notice their is an addon that requires an update. When I click on this addon to download and install the update I get the following message:
Unable to backup old package directory to e:\web\public_html\HopesHome
\[root]/files/trash

As a workaround I have been uploading the addons zip file to the correct directly, and then opening directly from their to update it.
I thought I may have put in a bug report for this a while ago. But I was unable to locate it through the bug tracker.

I have no problem uploading the zip file to update my addons. However I am currently in discussion to build a Concrete5 site for another company who is on the same ISP I am currently on. So from an end user perspective, the inability to update their own addons in Concrete5 may cause some confusion.

I could switch them to a different ISP that offers Linux hosting. But if their are any resolutions for this update addon issue that would be ideal. They are very happy with the support from their current ISP. (And also very excited about the prospect of a Concrete5 site!)

Please note I am going to be updateing to 5.6.1.1 once it is released through the auto-updater.

Thanks in advance for any advice,

Here is my environment

# concrete5 Version
5.6.0.2
# concrete5 Packages
Auto-Nav Pro (1.2), Automatic 
Email Obfuscator (1.2.3), Bootstrap (2.1.1.2), Bootstrap Buttons (2.1.1.1), 
Bootstrap Carousel (2.1.1.1), Document Library (1.6.3), MindNet Clear Cache 
(1.0), Pro Image (1.2), Superhero (1.2.2), Ticker (1.0.1), Tweetcrete 
(1.6.6), Vimeo Player (1.0.6).
# concrete5 Overrides
css/my-custom.css
# Server 
Software
Microsoft-IIS/7.0
# Server API
cgi-fcgi
Viewing 15 lines of 54 lines. View entire code block.
SteadyIT
 
mhawke replied on at Permalink Reply
mhawke
I have been finding it increasingly difficult to set up concrete5 on IIS so all my new installs go on Linux servers.
SteadyIT replied on at Permalink Reply
SteadyIT
@mhawke,

I also reside in Canada. Do you have any recommendations for Canadian ISPs that you use to host C5 sites on Linux servers?
Adreco replied on at Permalink Reply
Adreco
Just out of curiosity; Have you checked your files folder to see if a "trash" folder exists there? If not, you can add it manually and the updates should then work.

Adrian
mhawke replied on at Permalink Reply
mhawke
Or if it does exist, check permissions on [root]/files/trash folder to make sure it's writable?
SteadyIT replied on at Permalink Reply
SteadyIT
Thanks, for the response. I do have a trash folder, and it is writable.

I wonder if part of the issue is that it is trying to connect to \[root]/files/trash and on my server the path is
/[root]/files/trash

I don't have alot of experience in IIS. But is their a chance the \ character in the update string is not allowed in IIS? Or maybe the path simply doesn't exist?
mkly replied on at Permalink Reply
mkly
Hello,
Are you able to get in touch with your Hosting provider? This is the code where the error is occuring and maybe they could shed some light on that.

in /concrete/core/models/package.php
public function backup() {
  if ($this->pkgHandle != '' && is_dir(DIR_PACKAGES . '/' . $this->pkgHandle)) {
    $ret = @rename(DIR_PACKAGES . '/' . $this->pkgHandle, DIR_FILES_TRASH . '/' . $this->pkgHandle . '_' . date('YmdHis'));                                                   
    if (!$ret) {
      return array(Package::E_PACKAGE_MIGRATE_BACKUP);
    }
  }
}


For a local test, could you try removing the "@" symbol from the front of that line and see what error it gives you? It might give us a bit more insight into the issue.

Best Wishes,
Mike
SteadyIT replied on at Permalink Reply
SteadyIT
Hello mkly,

Sorry about the late reply. I am going to go ahead and contact my ISP. Thanks for pointing out which section the code is coming from.

Much appreciated.