HELP. MODx Update: How Do You Merge Directories

My hosting service File Manager does not merge directories and they do not allow or have SSH access. Odd?

CODA does not support directory merging on a remote server. I believe it only allows it from local to remote or vice versa. Their support confirm this a few weeks back.

Does anyone have any solutions, tips, tricks?

Most cPanel (type) file managers that I've encountered don't "support" file merging. Meaning, there's no option to merge files. However copying the files from one directory into another accomplishes the same thing. It doesn't overwrite the files and updates are smooth. The move option does the same thing, but I always just copy the files and then delete the extracted folder when the update is known to be successful.

In other words, go ahead and use copy. Just back up your site first, in case.

I do have a COPY feature. Used it last night to make copies for a backup and it crashed. myHosting support line gives a busy signal. Got support via chat, and the suggested I call another number. Unfortunately is was for some kind of rewards site. They gave me another number, and it was for a cruise promotion or something. Wheels are off over there.

Anyhooooo, if I can get them on the horn, I'll ask about the COPY feature. That's a really good idea. I can probably test it with some test folder and files.

I emailed a request for SSH to be enabled. Have to log in now and see if it was establish. With SSH anything is possible. Wish me luck.

Can't zip or unzip with SSH, but can tar and merge. I merged. Currently stuck. Full permissions were already on the packages directory. I also changed permission on the core.transport.zip to full rwx rwx rwx and the install still fails. Do I need to unpack that core.transport.zip with my File Manager? Maybe not. I just tried to unpack it using the File Manager and got this error: WebExecutor unpack : File already exists 'core/manifest.php'

The install failed because MODX could not unpack the
/core/packages/core.transport.zip package. Make sure that the
/core/packages/core.transport.zip file exists and is writable, and that you have made the
/core/packages/ directory writable. [ed. note: mmcgee last edited this post 12 years, 7 months ago.]

And things just went south!
I took a chance and set permissions on the core folder to be rwx rwx rwx

Clicked retry and the result:

Warning: array_merge(): Argument #2 is not an array in /usr/local/pem/vhosts/######/webspace/httpdocs/core/xpdo/xpdo.class.php on line 340 Fatal error: Class 'xPDODriver_' not found in /usr/local/pem/vhosts/######/webspace/httpdocs/core/xpdo/xpdo.class.php on line 1867

I inserted ###### in place of the id number

I change the core directory permissions back to their original setting: rwx r x r x
Then hit browser back button, and refreshed screen for myDomain.com/seup. Clicked on en and now there is only a blank white screen.

Maybe I should just trash everything, and just do a clean instal of MODx. My site at this point was basically a template with a full html page. I had some actual MODx resources started, but I was planning to do a complete redesign anyhow. Just trying to do this update has really knocked the wind out of me. Honestly, I think this has more to do with myHosting shared server than it does MODx. [ed. note: mmcgee last edited this post 12 years, 7 months ago.]

Here is the method I use when there's no SSH. It works very reliably: http://bobsguides.com/modx-upgrade-faq.html

Ok. First assume everything you did was wrong, that's what I do when the installs go hinky.

Setting permissions to 777 on most host configurations will come back as a security violation and will be blocked as if the files are not there or intermittently work.

At most you may want directories to be 755 or 750.

Try setting them to the 755 first.

I think you should:

Delete the entire install. All of it.

Per the instructions in the docs:

Download the newest Revolution to your computer.

Unzip it locally - not on the server.

Using Filezilla or some other FTP program unload the tree to your



If your host does not allow FTP switch hosts.

The FTP software on the server already knows which masks to place on the directories and files which are typically all that is needed on most even half-way decent hosts and modx should install without a hitch.

And why is it in the usr directory?

I can think of a dozen linux security mechanisms which would shut it down at that location.

The site should probably be under /var or /srv. You may want to double check that with your provider.

I have not seen anyone in over a decade using a system directory to run sites.

===============================
Make sure you have a database ready to go and sufficient privileges to create tables, etc. before you install Revolution.

http://rtfm.modx.com/revolution/2.x/getting-started/installation
http://modx.com/download/direct/modx-2.2.12-pl.zip
http://rtfm.modx.com/revolution/2.x/getting-started/installation/basic-installation#BasicInstallation-InstallingMODXRevolution
https://filezilla-project.org/



[ed. note: wshawn last edited this post 12 years, 7 months ago.]

Thanks Bob. I thought I had it figured out, but now can't get the setup to run again and my site is down. Don't tell my wife, I will be in soooo much trouble.

Initially I received this error about the core.transit.zip. I changed permissions. No luck. Then I unpacked it and the errors ensued.

After back in out, and attempting to start the setup over, I got more errors. Now even when I just navigate to my site, the is an error.

I tried merging the directories again, thinking perhaps I could start over. Then got errors relating to core/config/config.inc.php

I have a backup of that file from 2 days ago, and am unable to copy it to and replace what I think is a corrupted version.

At this point I am having the hosting tech support move a backed up version of my core/config/config.inc.php file out to the core/config directory.

Oh... I'm pretty confident that everything I did was wrong:) I also know that myHosting has not been MODx friendly and every install and now this update are plagued with issues.

There's no var, no www, it's only webspace/httpdocs
SSH worked great on another site of my but it's a VPS. This is shared, and SSH is limited, though the merging went fine. Just went off the rails with the core.transport.zip, especially after I tried to unzip it.

I'll give it one more go after they host tech support moves my backup of core/config/config.inc.php and replaces the current one. If the setup doesn't work, I will abandoned ship. goDaddy has been much easier to work with, and installs have been as quick and easy as is described by everyone.

In the case of this site? It's really one static html file in a template. I can post that back online and be just fine. Then, I'll set up shop elsewhere and transfer the DNS tomorrow. I was just hoping to fully build on MODx resources now. Guess it's a good thing I've been working with a single static file and not loosing tons and tons of MODX resources.

Thanks for the permission tips. Good to know.

Marc

Quote from: wshawn at Feb 22, 2014, 12:39 PM

Ok. First assume everything you did was wrong.

Setting permissions to 777 on most host configurations will come back as a security violation and will be blocked as if the files are not there or intermittently work.

At most you may want directories to be 755 or 750.

Try setting them to the 755 first.

I think you should:

Delete the entire install. All of it.

Per the instructions in the docs:

Download the newest Revolution to your computer.

Unzip it locally - not on the server.

Using Filezilla or some other FTP program unload the tree to your

/usr/local/pem/vhosts/######/webspace/httpdocs

If your host does not allow FTP switch hosts.

The FTP software on the server already knows which masks to place on the directories and files which are typically all that is needed on most even half-way decent hosts and modx should install without a hitch.

And why is it in the usr directory?

I can think of a dozen linux security mechanisms which would shut it down at that location.

The site should probably be under /var or /srv. You may want to double check that with your provider.

I have not seen anyone in over a decade using a system directory to run sites.

===============================
Make sure you have a database ready to go and sufficient privileges to create tables, etc. before you install Revolution.

http://rtfm.modx.com/revolution/2.x/getting-started/installation
http://modx.com/download/direct/modx-2.2.12-pl.zip
http://rtfm.modx.com/revolution/2.x/getting-started/installation/basic-installation#BasicInstallation-InstallingMODXRevolution
https://filezilla-project.org/

Quote from: mmcgee at Feb 22, 2014, 12:41 PM

I tried merging the directories again, thinking perhaps I could start over. Then got errors relating to core/config/config.inc.php

I would start with the file permissions. If they are 777 quite a few server-side applications will block the file from being access to prevent hacks.