FWIW
I was having a issue of "saving..." dialog hanging forever after the 2.1.1 upgrade. after a couple of days of going nowhere, I solved my problem by doing the following.
0.I backed up my whole install and database in case something goes wrong.
1.My install is in the subfolder /modx/. This install points to mysql database "DataSet"
2.I installed another 2.1.1 in a new subfolder /modx2/. this install points to a newly created database "newDataSet"
3.I kept modx2/setup files undeleted.
4.I added all the package that /modx/ install had on /modx2/ : /modx2/ only have copies of the latest packages
5.I copied all static data from /modx/ to /modx2/ : In my case, those were image files and flash files under /modx/Assets/
6.I modified /modx2/core/config/config.inc.php from pointing "newDataSet" to "DataSet" and any /modx2/ reference to /modx/ reference, then saved.
7. copied /modx/.htaccess to /modx2/.htaccess
8. I renamed /modx/ to /modx.old/ and then /modx2/ to /modx/
9. ran /modx/setup and did a fake upgrade and this time, I let the program delete the "setup" folder
10. I deleted "newDataSet" database from mySQL.
After this, the site is back in business and I can save resources or change template.
I don’t know what part has solved my particular issue. I think most of the steps maybe redundant. but I think the above process forced me to have...
a. very clean install. Just 2.1.1 stuff and the latest packages only. No legacy files or misplaced files in the new install
b. If there were any missing files, they are now reinstalled
c. all the cache data has been deleted
and I am happy
