Warnings when I update EasyBlog
By Douglas McCarroll on Sunday, 20 January 2019
Posted in Installation Issues
Replies 6
Likes 0
Views 687
Votes 0
Hi,

I just updated to the most recent version of EasyBlog. I get a message saying "Updating component was successful" and the blog seems to be working correctly, but I get these warning messages:

Warning
Copy failed: /home/langcollab_admin/languagecollaborative.com/tmp/install_5c43e2a6315f2/archive/precompiled/stylesheets/site/cobalt/style-5.2.11-rtl.min.css to /home/langcollab_admin/languagecollaborative.com/components/com_easyblog/themes/cobalt/styles/style-5.2.11-rtl.min.css
Copy failed: /home/langcollab_admin/languagecollaborative.com/tmp/install_5c43e2a6315f2/archive/precompiled/stylesheets/site/cobalt/style-5.2.11.min.css to /home/langcollab_admin/languagecollaborative.com/components/com_easyblog/themes/cobalt/styles/style-5.2.11.min.css
Copy failed: /home/langcollab_admin/languagecollaborative.com/tmp/install_5c43e2a6315f2/archive/precompiled/stylesheets/site/lithium/style-5.2.11-rtl.min.css to /home/langcollab_admin/languagecollaborative.com/components/com_easyblog/themes/lithium/styles/style-5.2.11-rtl.min.css
Copy failed: /home/langcollab_admin/languagecollaborative.com/tmp/install_5c43e2a6315f2/archive/precompiled/stylesheets/site/lithium/style-5.2.11.min.css to /home/langcollab_admin/languagecollaborative.com/components/com_easyblog/themes/lithium/styles/style-5.2.11.min.css
Copy failed: /home/langcollab_admin/languagecollaborative.com/tmp/install_5c43e2a6315f2/archive/precompiled/stylesheets/site/radium/style-5.2.11-rtl.min.css to /home/langcollab_admin/languagecollaborative.com/components/com_easyblog/themes/radium/styles/style-5.2.11-rtl.min.css
Copy failed: /home/langcollab_admin/languagecollaborative.com/tmp/install_5c43e2a6315f2/archive/precompiled/stylesheets/site/radium/style-5.2.11.min.css to /home/langcollab_admin/languagecollaborative.com/components/com_easyblog/themes/radium/styles/style-5.2.11.min.css
Copy failed: /home/langcollab_admin/languagecollaborative.com/tmp/install_5c43e2a6315f2/archive/precompiled/stylesheets/site/zinc/style-5.2.11-rtl.min.css to /home/langcollab_admin/languagecollaborative.com/components/com_easyblog/themes/zinc/styles/style-5.2.11-rtl.min.css
Copy failed: /home/langcollab_admin/languagecollaborative.com/tmp/install_5c43e2a6315f2/archive/precompiled/stylesheets/site/zinc/style-5.2.11.min.css to /home/langcollab_admin/languagecollaborative.com/components/com_easyblog/themes/zinc/styles/style-5.2.11.min.css

What does this mean?

What impact might this have?

Is there something that I can do to avoid this when I update EasyBlog in the future?

Thanks,

Douglas
Hey Douglas,

I am really sorry for the delay of this reply as it is a weekend for us here. You are hitting this error because the web server wasn't able to copy these files into the respective folders. This is often caused by folder permission issues which prevents the web server from being able to write on these folders.

To solve this, all you need to do is to ensure that the web server user has write privileges to these folder. It depends on the setup of the server and it's best to consult with your hosting company as to what is the best permission to set for the folders on your site.
Mark
·
Sunday, 20 January 2019 22:20
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks for your response. Just curious - what do these files do? - do I really need them?
Douglas McCarroll
·
Sunday, 20 January 2019 22:30
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Douglas,

It depends if you are using any of these themes in EasyBlog. If you don't then you don't really need them but if you do, then it could be problematic.
Mark
·
Sunday, 20 January 2019 23:07
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Douglas,

We have received several similar reports and upon investigating, you may ignore these notices as it looks like the single click updater is trying to copy the css files from the developer version into your site. Since you are on the Pro version, and these themes doesn't exist in your environment, this is why it is generating such notices but you may ignore this.
Mark
·
Monday, 21 January 2019 14:56
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks for the update
Douglas McCarroll
·
Monday, 21 January 2019 21:35
·
0 Likes
·
0 Votes
·
0 Comments
·
Not a problem at all Douglas.
Mark
·
Monday, 21 January 2019 21:38
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post