Dear Roundcube users
We can proudly announce the first service release to update the stable version 1.0 of Roundcube webmail. It contains some important bug fixes and improvements, primarily a fix for the unintentional redirect from the compose page in Google Chrome which likely started to appear after a recent Chrome update.
It's considered stable and we recommend to update all productive installations of Roundcube with this version. Download it from http://roundcube.net/download, see the full changelog here: http://trac.roundcube.net/wiki/Changelog
Please note that the update includes a small MySQL database schema change, thus make sure you run the update script.
Kind regards, Thomas
just upgraded, all is good. but, one thing is *insane* the new way to get plugins! so much effort now compared to before, please also have an ftp repo for those who want to know what goes on, on their server and not stuff around with adding and editing and re running phar blah blah blah :) programmers might love this, but systems admins not so much and we are the ones you reply on for your code to run :)
On 5/12/14, Thomas Bruederli thomas@roundcube.net wrote:
Dear Roundcube users
We can proudly announce the first service release to update the stable version 1.0 of Roundcube webmail. It contains some important bug fixes and improvements, primarily a fix for the unintentional redirect from the compose page in Google Chrome which likely started to appear after a recent Chrome update.
It's considered stable and we recommend to update all productive installations of Roundcube with this version. Download it from http://roundcube.net/download, see the full changelog here: http://trac.roundcube.net/wiki/Changelog
Please note that the update includes a small MySQL database schema change, thus make sure you run the update script.
Kind regards, Thomas _______________________________________________ Roundcube Users mailing list users@lists.roundcube.net http://lists.roundcube.net/mailman/listinfo/users
On 14 May 2014, at 08:19, Nick Edwards nick.z.edwards@gmail.com wrote:
just upgraded, all is good. but, one thing is *insane* the new way to get plugins! so much effort now compared to before, please also have an ftp repo for those who want to know what goes on, on their server and not stuff around with adding and editing and re running phar blah blah blah :) programmers might love this, but systems admins not so much and we are the ones you reply on for your code to run :)
I think it's insane that you think it's insane :) All it takes now is editing 1 file, and running 1 command. No need to know where the plugin even exists. And upgrading all your plugins is 1 command as well.
But, if thats too easy for you, nothing keeps you from downloading a plugin from where ever it is, and putting it in the plugins folder.
Cor
On Wed, May 14, 2014 at 8:19 AM, Nick Edwards nick.z.edwards@gmail.com wrote:
just upgraded, all is good. but, one thing is *insane* the new way to get plugins! so much effort now compared to before, please also have an ftp repo for those who want to know what goes on, on their server and not stuff around with adding and editing and re running phar blah blah blah :)
I'm desperately trying to avoid another discussion about pros and cons of the various ways to maintain plugins.
Because we didn't want to re-invent the wheel and develop a plugin repository platform from scratch, we chose to use yet existing solutions from packagist and composer. I don't think we'll add an FTP server on top of that but the nice thing about composer and the packagist platform is that all the necessary information is there in a human readable form.
So for you as a sysadmin or packager, you'll find all the links to a plugin's source repository on plugins.roundcube.net and you can learn about the dependencies, the different versions and their restrictions all from there as well. Or directly from the plugin's composer.json file and repository tags respectively. I'm sure we're all able to read JSON nowadays. You can then just pull the plugin sources from the git repository. Composer doesn't do much more actually. And if it does, the composer.json file will tell you what.
Does that work for you?
Kind regards, Thomas
Seem to hit a bug I think... If you go to insert image, to takes the path, the name, but doesnt add the image, it just adds a link to it, which if you attach say /home/foo/blah.png
is no good to anyone else :)
Expected behaviour of :insert image" is it should insert the image into the message.
On 05/19/2014 02:25 AM, Noel Butler wrote:
Seem to hit a bug I think... If you go to insert image, to takes the path, the name, but doesnt add the image, it just adds a link to it, which if you attach say /home/foo/blah.png
is no good to anyone else :)
Expected behaviour of :insert image" is it should insert the image into the message.
It is not a bug, it is just how it works. There's already a future request to replace links with image attachments when the message is being send.
On 19/05/2014 16:02, A.L.E.C wrote:
On 05/19/2014 02:25 AM, Noel Butler wrote:
Seem to hit a bug I think... If you go to insert image, to takes the path, the name, but doesnt add the image, it just adds a link to it, which if you attach say /home/foo/blah.png
is no good to anyone else :)
Expected behaviour of :insert image" is it should insert the image into the message.
It is not a bug, it is just how it works. There's already a future request to replace links with image attachments when the message is being send.
Thanks Alec, hopefully 1.0.2? ;)
Cheers Noel
-
A.L.E.C -
Cor Bosman -
Nick Edwards -
Noel Butler -
Thomas Bruederli