Forum archive
vTiger v5.3
Hello gentlemen!
We have an installation at work of vTiger 5.2.2 that we are running on a non-TKL platform because you guys didn't have it in TKL when we started to use it. The database has grown, as has the number of users, and we are seriously considering going to an on-demand platform rather than self-hosting it. vTiger also just released a new version (5.3RC) that will be frozen in 2-3 weeks. This is putting the impetus on us now to upgrade and decide on a long-term solution at the same time.
So, my questions:
- vTiger has an automated migration function in the new 5.3 version that will take one form 5.2 -> 5.3 without any difficulty (Supposedly -- Haven't tried it yet. :-| ). If we move to TKL's vTiger appliance now, will you or we be able to use that migration tool to upgrade?
- Is TKL going to release a vTiger 5.3 appliance when it officially released?
- What would the timing be on that?
Other than that, I just wanted to take the time to thank you all for some really excellent products. I use a TKL Core at home for some file hosting and backup (CrashPlan) activity, and it works just flawlessly, even on a meager Atom chip. Well done!
Peter
Replies (5)
You'll be able to migrate to a newer version with TKLBAM
Reply 1I wouldn't set 777!
Reply 2Although I guess for testing it's not that big a deal... Though if the files/folders are owned by the webserver user account (www-data - ie chown www-data) and permissions are 755 then that should be more than adequite.
Perhaps check the Apache error log and see what that's saying? I think it should be /var/log/apache2/error.log
Another possibility is that there is an errant .htaccess file that is causing your problems. I don't know much about them though...
Sorry I don't know anything about vTiger
Reply 3So I have no idea where your problems are coming from. First thing I'd do is make sure you have enough RAM. The vTiger docs recommend 2GB.
Beyond that I'd suggest that you have a read through the vTiger wiki and/or forums. If you don't find anything of any value (or even if you do) it may be worth also posting on their forum to ask what sort of performance enhancements others are using.
If you have any joy making yours work better, be great if you post back. If they are suitable for a generic vTiger appliance, they may even make it into the next release as TKL pre-configurations!
Glad to hear you got it working!
Reply 4And glad that I could be of assistance.
FYI all of the configured sites are in /etc/apache2/sites-available then the sites that are actually enabled have symlinks in /etc/apache2/sites-enabled (pointing to the actual files in /etc/apache2/sites-available). The desirable way to enable and disable sites is via the a2ensite and a2dissite commands, and the configuration should be done via the config files in /etc/apache2/sites-available.
I suspect that the reason why "One of the files (sites-enabled directory) was already changed back" was because for that one you had already edited the 'real' file (in /etc/apache2/sites-available) so when you opened the symlink it opened the 'real' file and it had already been done.
So to make sure all is as it should be, I'd check that the contents of sites-enabled to make sure anything in there is only a symlink. I'm not sure how the TKL vTiger appliance is configured, but I suspect that you will only want the vtigercrm file there.
Migration turned off, how to turn it on?
Reply 5Hi
In the notes for vtiger, it is mentioned that migration capability was turned off for security reasons. How can I turn it back on? Is there a flag in some file somewhere?
Yes, the next major version of TurnKey vTiger will most likely be based on vTiger 5.3. We've been working on a new batch, but I can't give you a timeline yet. We release when everything is working to our satisfaction.
You'll be able to use TKLBAM to migrate between versions and then run vTiger's migration tool to update the database schema (I'm assuming that's what it does).
PS: Thanks for the positive feedback!