Civicrm v2 and Joomla 1.5

[penguinhead]

The current version of Civicrm is an extremely resource intensive component when run on Joomla 1.1.13. So much so that it is very difficult to find a good economical shared host server to run it on.

Is it expected that Civicrm v2 will be less demanding when run on Joomla 1.5?

I am currently using siteground.com as my host, but the administrators at Siteground agree that the current version of civicrm (1.9) will not run on their shared servers. Dissapointing given that siteground are a preferred host for Joomla, although in every other way they are fanastic.

 

[lcdweb]

Bluehost is my preferred shared hosting provider. They give you much more control over key settings than Siteground.

[lcdweb]

On your other question --
I understand from the core team that 2.0 will introduce a number of efficiencies to the program that will improve performance. This is mostly through the rewrite of many of the sql queries to be more efficient. However, those efficiencies are expected to be most readily experienced in organizations with very large databases.

[feaker]

From what Bluehost told me, they don't support any of the needed features for civimail. How are you configuring this?

[lcdweb]

I had previously setup CiviMail on BH using the alternate setup (imap2soap). However, I just went through the exercise again and ran into several problems. It appears they changed how email functions on their servers. There are two issues I ran into -

1) The return-path is used by CiviMail as a mechanism to catch slow bounces. BH servers use it as an authentication mechanism. If CiviMail makes use of the return-path, outgoing emails bounce as not sender-verified.

2) Perhaps more challenging, BH has recently disabled the catchall email account capability because people were using it unknowingly and it was killing their spam cleansing tools (with the volume of spam generated). This causes problems with replies to CiviMail emails (which include a token value) and also the unsubscribe/opt-out email links (this can be overcome by using the http links instead of the emails). It also means you lose the ability to automatically process bounces.

If you can live with reduced functionality, these issues can be hacked. But you're right, CiviMail really can't be used on their servers with the full functionality. Bummer.

-Brian

-Brian

[sbrawner]

Just installed CiviCRM 2.0 beta 3 on a Joomla 1.5.1 site, had to use the upload - unzip - install from directory function. Note you will have to use the FULL root directory when pointing Joomla to the dir, i.e. /home/<youraccount>/public_html/<wherever_you_put_it>/

Interesting that I had to put the com_civicrm inside the /administrator dir in order to get it to work. when I put it in a dir off the www root, it wouldn't work no matter what. Could have been perms.

I'm using hostmonster (bluehost) and had to mod the php.ini memory_limit from 32M to 64M to get it to install properly.

Now I actually have to learn how to utilize this thing.

Wish me luck!

[TrvlFox]

I'm using HostMonster as well and am having a hard time finding the file that I need to adjust the size.  Any help here?

[sbrawner]

I'm using HostMonster as well and am having a hard time finding the file that I need to adjust the size.  Any help here?

If you haven't created and dumped a default php.ini using the CPanel PHPConfig app and selecting "Install Default php.ini", there won't be one. Do that and then you will have something to work with.  Otherwise your install will use the bluehost/hostmonster default php.ini (they're the same company).


It's in the php.ini file, under 'resource limits'

Code: [Select]

;;;;;;;;;;;;;;;;;;;
; Resource Limits ;
;;;;;;;;;;;;;;;;;;;

max_execution_time = 30     ; Maximum execution time of each script, in seconds
max_input_time = 60 ; Maximum amount of time each script may spend parsing request data
memory_limit = 64M      ; Maximum amount of memory a script may consume (32MB)
Also you need to replicate the php.ini file to all dirs in your tree that have php files. There is no 'master'.

Do this by creating an empty file (in the dir you have your proper php.ini file) called copyphpini.php and inserting this:

Code: [Select]

<pre><?php system("find * -type d|xargs -i cp --verbose php.ini {}/."); ?></pre>COMPLETE!
Then execute this file from the web and when it is done, move that copyphpini.php file OUT of the public html root.

I had one that was a lot better but I can't find it.