FormIt CMP is blank after hardening of core file

Quote from: andytough at Jul 27, 2017, 11:34 PM

Both are set to /server/hosting/web/domain/core/ which is what I swapped it to after hardening the core folder.

I am sure I understand your meaning here, and that you have simply written an abbreviated answer, but I want to double check...

Your MODX_PROCESSORS_PATH does end with model/modx/processors/ doesn't it?

Correct

This is bugging me, because I am sure I had a similar problem with an extra after harding an install of MODX.

If I remember correctly I did something like this...

1. Uninstalled and removed formit via the package manager
2. Manually deleted any remaining formit folders in the /core/packages folder
3. Manually deleted any remaining formit folders in the/core/components
4. Re-downloaded and installed formit via the package manager

I'm not sure what effect this might have on any existing formit data in the database, but a backup might be a good idea before trying it.

Quote from: andytough at Jul 28, 2017, 12:14 AM

This is bugging me, because I am sure I had a similar problem with an extra after harding an install of MODX.

If I remember correctly I did something like this...

1. Uninstalled and removed formit via the package manager
2. Manually deleted any remaining formit folders in the /core/packages folder
3. Manually deleted any remaining formit folders in the/core/components
4. Re-downloaded and installed formit via the package manager

I'm not sure what effect this might have on any existing formit data in the database, but a backup might be a good idea before trying it.

I'll give it a whirl and report back. Whenever I uninstalled it was always through the manager and I wouldn't remove the folders so that may do the trick.

Thanks for the help Andy

No dice

Should I try deleting the modx_formit table from the database?

I feel the issue is DB related as it's the only thing I haven't really touched.

I presume you cleared the cache afterwards.

I suppose if you have a backup of the database deleting the table shouldn't be a problem.

I just noticed that there is a tmp folder in /assets/components/formit/tmp.

On my installation this folder is empty but perhaps there is something in yours that could be deleted?

The permissions on the tmp folder are 775. All other folders on mine are 755, so could be worth checking that.

Quote from: andytough at Jul 28, 2017, 04:25 PM

I presume you cleared the cache afterwards.

I suppose if you have a backup of the database deleting the table shouldn't be a problem.

I just noticed that there is a tmp folder in /assets/components/formit/tmp.

On my installation this folder is empty but perhaps there is something in yours that could be deleted?

The permissions on the tmp folder are 775. All other folders on mine are 755, so could be worth checking that.

Nothing in that folder but the perms were a little wonky. I swapped them to reflect your suggestion, cleared cache both on the site and via my browser and still blank

I think I'm out of ideas!

But I suppose it might be worth re-running Setup if you haven't already done that?

Have you also checked the Update your Database part of the Moving Your Site to a New Server, or to Root from Subfolder (publishing subfolder or development site) document.
https://docs.modx.com/revolution/2.x/administering-your-site/moving-your-site-to-a-new-server

I think it is also discussed in Hardening MODX Revolution so I expect you have.
https://docs.modx.com/revolution/2.x/administering-your-site/security/hardening-modx-revolution#HardeningMODXRevolution-ChangingDefaultPaths

Quote from: andytough at Jul 28, 2017, 05:22 PM

I think I'm out of ideas!

But I suppose it might be worth re-running Setup if you haven't already done that?

Have you also checked the Update your Database part of the Moving Your Site to a New Server, or to Root from Subfolder (publishing subfolder or development site) document.
https://docs.modx.com/revolution/2.x/administering-your-site/moving-your-site-to-a-new-server

SELECT `path` FROM `your_revo_db`.`workspaces`;

I think it is also discussed in Hardening MODX Revolution so I expect you have.
https://docs.modx.com/revolution/2.x/administering-your-site/security/hardening-modx-revolution#HardeningMODXRevolution-ChangingDefaultPaths

I've re-run setup and the path is set properly in the DB. As a side note, it is writing to the DB 100%. And works normally outside of the CMP not displaying.

Welp, I've discovered that the CMP actually renders if I use Internet Explorer...

This is odd