Change submitted data before it is written

Couldn’t you do that with javascript? Onsubmit(), so to speak?

Hey Eric,

May I get a bit more information on which text field you are trying to modify? Also, by clicking the list of extension hooks you may access a page with information regarding the hook.

Justin:

I am looking to modify the contents of any text field on the page.

Thanks for the link. I was familiar with that resource. I think what I will have to do is week through the code and learn where the best hook would be. I tried some of the hooks and things happened at times that I was not expecting.

If you can’t find a hook that will do what you need, you might want to consider processing your GET / POST data in the path.php file, which is processed early in the EE request cycle.

Jesse: Interesting idea. Of course the intent of the extensions and hooks is to be able to not have to go back and edit source files that get overwritten with new versions. Does the path.php get overwritten with new upgrades?

I’m not sure, it might. But consider the following:

• Customizing certain settings is an official use of path.php. For example, setting custom variables. See Path.php Global Variables

• There are a lot of situations that the extension hooks don’t cover. path.php allows you to exert a lot of control that EE normally would deprive you of.

• If you’re worried about it, put your custom code in it’s own file and just include() it in path.php – then you’ll only have one or two lines to maintain in path.php. It’s a small price to pay for the control it gives you.

An alternative that might work for your purposes is to use the ‘sessions_start’ hook, which is called pretty early in the EE request process.

No, path.php does not get overwritten by upgrades. In fact, if you remove it or accidentally overwrite it, EE will no longer function properly.