I am completely sure that MODx developers made a great effort with the system. No doubt AJAX is a great issue. But in designing anything, when the basics doesn´t work, "the flowers" doesn´t look nice. I have just installed MODx yesterday. Quite a painful process I must say. By chance I found that one access problem to the Manager section was that there were some files missing in the Media folder, within the domain/www.whatever.com/modx/manager/media. Right now, when trying to acces the Manager, it just does not recognize the page, www.whatever.com/modx/manager/ and "Page not found"!!. The server is running fine as I accessed some other pages from it.
Could anyone please help me with the complete uninstalling process of MODx?. I´m sure this will be helpful for some people other than me. I know it´s a matter of deleting files but I don´t want to delete some essential file from my host.
I´m aware that probably this is "one in a hundred" problem but I don´t have time to find out more issues about this CMS.
Thank you very much.
Fernando
just delete folder manage, assets, install and index.php and index-ajax.php an ht.acces file
thats is and maybe empty or delete your database.
its a shame that you had so much problems installing modx it should normaly be a 10minit operation.
Dimmy
-
MODX Staff
- 12,272 Posts
When folks run into problems like this it’s almost universally a result of a bad initial upload. FTP isn’t unfortunately always bullet-proof and it’s even happened to me.
Ryan Thrash, MODX Co-Founder
Follow me on Twitter at @rthrash or catch my occasional unofficial thoughts at thrash.me
Having a corrupted download has happened to me more than once and, of course, it’s equally likely with any CMS.
At some point, it might be worth having a function in the MODx install to at least verify the existence of all the files (if not do a checksum on them individually). It could be like the option to verify the database connection. A really simple version could be to just count all the files and see if the number is right.
Bob
-
☆ A M B ☆
- 24,524 Posts
I used to have a big problem with scripts being uploaded with no line endings, then of course any comment line would simply break the script at that point. It had something to do with how the files were generated, with Windows file endings, Mac file endings, or Unix file endings; I never did exactly get to the bottom of it. I changed my ftp client, and haven’t had a problem since.
Quote from: sottwell at Jan 21, 2008, 12:22 AM
I used to have a big problem with scripts being uploaded with no line endings, then of course any comment line would simply break the script at that point. It had something to do with how the files were generated, with Windows file endings, Mac file endings, or Unix file endings; I never did exactly get to the bottom of it. I changed my ftp client, and haven’t had a problem since.
WS_FTP has three choices for download type: text, binary, and auto. I wonder if what you were using was doing binary downloads of text files? That way you’d get the native EOF and EOL characters.
I’m always kind of disgusted that the computer world hasn’t yet standardized EOL and EOF (and probably never will).
Bob
-
☆ A M B ☆
- 24,524 Posts
Not to mention charsets... dec8, utf8, the various iso-8859 ones, etc etc...
-
MODX Staff
- 2,502 Posts
I find the best/fastest way to upload MODx on most *nix servers--especially with cPanel is to upload the whole zip or tar and unzip/untar it on the server. It takes less time to upload than to upload via FTP a few files at a time as many shared hosts limit the number of connections to FTP and I can eat up those quick. I had even thought of writing a script to request the MODx files directly from the MODx site instead of uploading it but I thought that might be heavy on the MODx server so I didn’t bother.
If you have never had a file get corrupted or go astray during an FTP upload you are either lucky, lying or living in fantasyland.
Cheers,
Jay
Author of zero books. Formerly of many strange things. Pairs well with meats. Conversations are magical experiences. He's dangerous around code but a markup
magician.
Blog ✦
Twitter ✦
LinkedIn ✦
GitHub