moabman1

I've created four mambo sites, 2 on my own computer (running macosx) and two at a remote server (which happens to be macosxserver). Permissions are all the same. On my own computer, everything works fine, components update correctly and the template manager functions great.

On my remote server, everything functions correctly on the front end, but on the back end a couple curious things happen.

a) when the template manager is selected, the webbrowser talks with the server and then nothing happens. After much sleuthing, I found it was related to the size of the xml file in the peeklime template. When I took out a large portion of the <image>image.png</image> lines then it finally worked correctly.

b) when trying to upload remository, simpleboard, and docman, once the component.zip file is located and I press the upload button, nothing happens -- yet all other components load fine. I was able to get both simpleboard and docman loaded by copying up the files/folders and using phpmyadmin to sql in the database info. Most recently, on the component heavy site of the two remote sites, the components install/un menu started behaving like the template manager, in that now it doesn't launch at all.

Fortunately, I've developed workarounds for everything. I thought at first it was a corrupt file or two. So, when I created my second mambo site on the remote server, I uploaded the files from a PC. Since it is behaving exactly like my other remote server site, I suspect the issue is either php or apache related. I've tried increasing the post_max_size of the php.ini file to 32M. I also increased the memory_limit default to 32M. Neither helped.

Below is my remote server configuration:

PHP Version: 4.3.2
Web Server: Apache/2.0.47 (Unix) DAV/2 PHP/4.3.2
WebServer to PHP interface: apache2handler
Mambo Open Source Version: 4.5 Stable-1.0.7 [Sinatra] 07/04/2004 13:20 GMT

Except for these small glitches, everything else works extremely well. As a newbie to mambo, I'm very impressed with the system.

Any thoughts?

Thanks,

Dave

moabman1

Update:
I found a post from a user who had a component problem similar to mine. http://www.tsmf.jigsnet.com/componen...limitstart,18/
They too had the same php (4.3.2) and same apache version (2.0.47).

Anyone else running this combination and having no problem?

Thistledown

I have the same problem on Apache 1.3.27 and PHP 4.3.1. I haven't looked at any workarounds yet.

moabman1

I resolved all my "timing out" or non-response issues by moving to php 4.3.4 with apache at a 1.x version.