Roundcube 0.9 released

I did fix the issue, was myroundcube plugin_manager causing the issue, updated it and all relative plugins and now everything is working fine.

Thanks everyone for help and suggestions.

Regards
 
We have a lot of servers still running php 5.2. Is there a way to stop receiving the daily emails about roundcube updates from custombuild?
 
ViAdCk said:
We have a lot of servers still running php 5.2. Is there a way to stop receiving the daily emails about roundcube updates from custombuild?
Click to expand...
If you don't need any further updates, setting roundcube=no would likely be the simplest way to do it.

John
 
By the way, for whose who is still using PHP-5.2, and wants to keep roundcube updated, here is a wokring idea how to bypass the issue.

You should create a tech sub-domain, let's say webmail.hostname.com and redirect all requests for roundcube, phpmyadmin, etc to that tech sub-domain, for which you can specify PHP 5.3. Of course, the solution currently is not supported by custombuild, you need some manual steps applied to get it working.

So when your customer tries to open:

customerdomain.com/roundcube

he will be redirected to

webmail.hostname.com/roundcube

For those who wants the solution, and doesn't know how to implement it, please PM me for a quote, as I'm ready to set it up for you, as well as other members of the forums here.
 
I would like to add that in CustomBuild 2.0 it is possible to specify that aliases would be redirected to hostname.com/alias, so for that .htaccess or Apache configuration change to select PHP 5.3 for hostname is needed only.
 
smtalk said:
I would like to add that in CustomBuild 2.0 it is possible to specify that aliases would be redirected to hostname.com/alias, [cut..]
Click to expand...

I don't understand how to do that. I am running cb 2.0. I just did this: I changed /usr/local/directadmin/custombuild/options.conf by editing this line:

Code: 
use_hostname_for_alias=no
and changed that line to be this:
Code: 
use_hostname_for_alias=yes

Then I run:
Code: 
./build update
service directadmin restart
service httpd restart

However, if I try to visit https://domain.com/roundcube , it does not redirect me to https://server.hostname.com/roundcube , but it stays at https://domain.com/roundcube without being redirected.

The only different is that the redirect work when visiting https://domain.com:2222 wich redirect to https://server.hostname.com:2222 - but why does the redirect not work for roundcube and phpmyadmin?
 
smtalk said:
I would like to add that in CustomBuild 2.0 it is possible to specify that aliases would be redirected to hostname.com/alias, so for that .htaccess or Apache configuration change to select PHP 5.3 for hostname is needed only.
Click to expand...

Yes, that's a good idea, as it would solve the issue with accessing webmails and phpmyadmin in case with PHP-FPM. Of course another implementation of PHP should be installed as well.
 
ditto said:
I don't understand how to do that. I am running cb 2.0. I just did this: I changed /usr/local/directadmin/custombuild/options.conf by editing this line:

Code: 
use_hostname_for_alias=no
and changed that line to be this:
Code: 
use_hostname_for_alias=yes

Then I run:
Code: 
./build update
service directadmin restart
service httpd restart

However, if I try to visit https://domain.com/roundcube , it does not redirect me to https://server.hostname.com/roundcube , but it stays at https://domain.com/roundcube without being redirected.

The only different is that the redirect work when visiting https://domain.com:2222 wich redirect to https://server.hostname.com:2222 - but why does the redirect not work for roundcube and phpmyadmin?
Click to expand...

Only "./build rewrite_confs" could do the changes to the alias file.
 
smtalk said:
Only "./build rewrite_confs" could do the changes to the alias file.
Click to expand...

I have now tested. It does not work. Also it creates new problems.

I am running cb 2.0 rc4. I changed use_hostname_for_alias=no to be use_hostname_for_alias=yes, then I did ./build rewrite_confs

After that server.hostname.com/phpmyadmin does not work anymore, only server.hostname.com/phpMyAdmin (with capital letter M and A) still work. To fix this I must add back this in /etc/httpd/conf/extra/httpd-alias.conf

Code: 
Alias /roundcube /var/www/html/roundcube/
Alias /phpmyadmin /var/www/html/phpMyAdmin/

I also had to add back the roundcube alias, all the alias was overwritten/deleted.

Next, I would now expect domain.com/phpmyadmin or domain.com/roundcube to redirect to server hostname.com/phpmyadmin and server.hostname.com/roundcube - but it does not redirect, so still it does not work.

It only creates new problems because of the changes to /etc/httpd/conf/extra/httpd-alias.conf

Please fix these bugs.

Edit: Here is some of my settings in options.conf, if it helps replicate the bug (let me know if you need more information about my setup):

Code: 
use_hostname_for_alias=yes
redirect_host=server.hostname.com
redirect_host_https=yes
 
Last edited:
I confirm, we had to disable it and set to use_hostname_for_alias=no, as mod_rewrite rules does not work as we'd expect it.
 
ok since the update.. i can RECIEVE messages.. but not SEND messages. with my email adress from direct admin.. now what to do?

i NEED those messages.

sincerly,
kristof
 
I just updated Roundcube via Custombuild, but I got two errors on the end:
Code: 
Executing database schema update.
sh: /usr/local/php/bin/updatedb.sh: No such file or directory
sh: /usr/local/php/bin/indexcontacts.sh: No such file or directory
Which is not strange, because a /usr/local/php/ directory does not exist.

I have looked for those files and in fact they are present in:
/var/www/html/roundcubemail-0.9.1/bin/indexcontacts.sh
Same goes for updatedb.sh which is also in that directory.

Seems the custombuild update is not 100% correct. How can this be fixed?
 
Got this error now on all 3 servers. Nobody else having this problem?
Or can this warning just be ignored?
 
Hello,

I think updating the DB would be important.... indexing the contacts, less important.

Looking at their code, the line that is likely not working correctly is from the bin/update.sh:
Code: 
define('INSTALL_PATH', realpath(dirname(__FILE__) . '/..') . '/' );
which should be setting INSTALL_PATH to be /var/www/html/roundcubemail-0.9.1.. but instead, seems to be setting /usr/local/php, which is odd.

Are there any custom changes to the php.ini?
Perhaps resetting it to a default value might help..

If you want to manually extract the tar.gz again into /var/www/html, then could change the above line to be set manually, eg:
Code: 
define('INSTALL_PATH', '/var/www/html/roundcubemail-0.9.1/' );
and then run the script from the roundcubemail-0.9.1 directory
Code: 
bin/update.sh '--version=?'
If anyone else is noticing this, let us know.

John
 
On 2 servers there are made custom settings, which are in fact only adding some options to the "disable_functions =" line and changing the date.timezone to date.timezone = "Europe/Amsterdam"
However, on 1 server only has the date.timezone change.
Alle php.ini's have short_open_tag set to On again.
Other changes are only made by custombuild by adding zend and ioncube.

But all of these things are not things which would change path-related things.

Edit: Just tried with a new php.ini (taken the production php.ini from the tar.gz file in custombuild), restarted httpd but same problem.
 
Last edited:
Sorry my bad. Initial post removed.

Manually extraction, editting the update.sh and calling it the way you stated is working fine:
Code: 
bin/update.sh '--version=?'
Executing database schema update.
Indexing contacts for user 1...done.
Indexing contacts for user 2...done.
Indexing contacts for user 3...done.
Indexing contacts for user 4...done.
This instance of Roundcube is up-to-date.
Have fun!

Edit 2: Installer directory is gone after update with custombuild (sql directory is present).
 
Last edited:
Is this something that can be added to custombuild, so that the install off roundcube works again automatically? (the problem is since roundcube 9.0.0)
 
You must log in or register to reply here.
Back
Top