moving modX to remote

REVO 2.0.6 (traditional download with upgrade from 2.0.4 done in Package Management.)
local: MAMP MacOSX CSS developed with Dreamweaver CS4
PHP 5 mySQL phpMyAdmin

I have several long-hour days invested in creating a great looking ModX site that really meets the unique and flexible CMS needs of the client. It works perfectly on my local MAMP environment in MAC OSX. I have reached the point where I have spent almost the same amount of time that was spent on development just into trying to deploy the new site on their remote server. (basic lunarpages account)

The WIKI tutorial is disjointed, out of sequence, and missing several componants and obviously refers to a lot of files and folders that can only be found in EVO. I made a point of trying to follow the WIKI to the letter. It is literally impossible.

Some Forum readers offered variations of procedures, but none of these worked either.

Not sure what to do?? Start over in WordPress??? I would be willing to hire someone more proficient than I in the task of investigating and assisting in my deployment issues and writing a more accurate tutorial, but my budget has been pretty much blown to hell by two and a half days of failed attempts to deploy this site to the remote. I find it hard to believe that I am the only designer who is totally left out in the cold with this issue.

In my final attempt, I was able to deploy the site to the point where the login would function and would receive the administrators login without login error. But immediately after login, I am directed to this error:

Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 19456 bytes) in /home/earth26/public_html/lent45/core/model/smarty/sysplugins/smarty_internal_templateparser.php on line 2464

Please note that I had already previously uploaded a php.ini file to the server as follows:

[PHP]
;;;;;;;;;;;;;;;;;;;
; 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 = 50M ; Maximum amount of memory a script may consume (50MB)
;
;;;;;;;;;;;;;;;;;
; Data Handling ;
;;;;;;;;;;;;;;;;;
;
; Maximum size of POST data that PHP will accept.
post_max_size = 50M
;
;;;;;;;;;;;;;;;;
; File Uploads ;
;;;;;;;;;;;;;;;;
;
; Maximum allowed size for uploaded files.
upload_max_filesize = 50M

Are you able to do a new install of Revo 2.0.6 pl2 to your host?

Actually, a test install on a new directory just failed as well.

char set utf-8 collation: utf_general_ci

I have, in the past, installed a few EVO sites in this same environment before

I was just now able to install and run a test version of 2.0.4 on the remote. Is there a way to reverse my local upgrade from 2.0.6 back to 2.0.4??
I used Package Management to upgrade.

To my limited knowledge there is no reason why 2.0.4 should install and 2.0.6 will not.

2.0.4 is available to download but I would first try to find the cause of the failure.

Have you checked if your server is capable of installing Revolution ie does it meet all the requirements?

Strange I see you can install 2.0.4 maybe a corupt 2.0.6 (mabe re download 2.0.6 PL2

You could try your install of 2.0.4 then try upgrade install to 2.0.6 PL2

Re the out of memory error, try putting a php file with the following code somewhere:


And see what the limit is. Not all hosts allow you to change the memory limit in that fashion.


As Allanb said, there shouldn’t be a reason for 2.0.6 NOT working, while 2.0.4 would work.. that’s just plain odd.

Have you checked the requirements for Revolution? They are very different then the ones from Evolution. http://rtfm.modx.com/display/revolution20/Server+Requirements

This is the installation doc for Revolution Traditional, maybe you had a different one? http://rtfm.modx.com/display/revolution20/Basic+Installation

OK, here’s the thing. The successful 2.0.4 remote install was a totally blank install. No templates or anything. So was the failed test version remote 2.0.6 (weird) I see that the php.ini is not working on the new remote site. Also very weird because I copied it from a site of another client also hosted by the same company, (same type of account)

On the problem remote host, I also have an older EVO site in a different directory, but that should be totally inconsequential.

Is my remote host actually a dark room in a haunted house?

I’ll give a shout to the hosting company, but I am not sure I will be tell them where to look, other than to tell me why that php.ini is being ignored.
The remote 2.0.4 install - with a 2.0.6 upgrade - then importing the developed site into that sounds reasonable, but I am running out of time to try things. People are startin’ to worry about me.

I no longer have a 2.0.4 version of this project, as if reverting was a viable solution. Baffled, but very appreciative of the community’s feedback and insight. Could use a little more.

Did you check the installation requirements against your server? Perhaps there’s something missing you should ask your host for.

What does PhpInfo() tell you about the value of memory_limit (see post above)?