Help!!! My site was previously hacked. I cant get friendly urls to work

ok i.dont know if the hacker put in things that prevent my files from working correctly. i did an upgrade to get the security fix and changed the .htaccess but doesnt work and redirects to the error page. i read to look for evidence of hacking in my index file, but how would I know what it is?? Also I constantly get "a possible csrf attempt was attemlted" please help and walk me through this.
apache
modx 1.0.5
mysql

hello,

Possible solutions and some troubleshooting of similar error was solved on this post.

http://modxcms.com/forums/index.php?topic=36771.0

Good Luck

Ok thanks. That solved the crsf messages. I still have the problems getting the full urls to work. I had modx running fine before the hack. I installed an upgrade 1.0.5 and now it doesnt work, only the homepage. I have researched all weekend and I still cant get it to work. I also came across someone who upgraded and discovered that the .htaccess file didnt work for him either and that he had to use another from another version to work. Is this true?

After a hack, you have to assume that ALL your resources are tainted. Standard procedure here would be to save all your assets that can’t be reinstalled (custom css, images, videos). Create a full backup: your entire site (for the record), and the database. You should do a clean install of EVERYTHING. After you’ve gotten a backup, I would entirely nuke the directory where the site was installed (yes, really -- that guarantees that any malicious mods to .htaccess are gone). Then re-install MODx, reinstall any and every Javascript library you used. Re-install all modules, snippets, and plugins from the MODx repo (in other words, make sure you’re installing a clean fresh version). Go through all your assets and make sure no malicious code ended up in there (be particularly vigilant for modifications to any php or js files). Then import your database (you may need to run the MODx upgrade), but you’ll have to go through the database with a fine-tooth comb to ensure that no malicious code ended up in there. If you miss anything, your site might still be infected, and you’ll end up getting hacked again or blacklisted. It is a huge pain, I know, which is why you should always have rolling backups in place so you can recover more quickly from these.

PM me if you’d like me to spend some time looking through this.

@Bloggerpimp,
fyi, Everett is a security team member, in fact the team leader.

btw,
You probably need to describe your previous system environments.
The "a possible csrf attempt was attempted" usually occurs when your browser can not (isn’t allowed to) store the manager’s session.