Feature #32701
closed
Enable customer postProcessors in different folder
Added by Jan Schreier almost 13 years ago.
Updated about 6 years ago.
Description
This may be a feature request for a manual extension actually: I like the idea of postprocessores. however so far I only managed to integrate a postprocessor by having the php file holding my postprocessor class in the sysext/form/.../PostProcessor/-folder. Is there a way to define the source of this class elsewhere? e. g. under my fileadmin folders?
I would love to see some typoscript code like
postProcessor {
1 = mail
1 {
...
}
2 = myPostProc
2 {
classFile = /fileadmin/myPostProc.php
...
}
}
If there is any existing solution to add a postProcessor easily, please tell me (and I will come up with a suggestion for the manual)
Files
- Target version set to 4.7.0-alpha3
- Complexity set to easy
Hey Jan,
I'd suggest to use something like that:
2 = tx_myext_WhateverProcessor
2.whatever = setting
In Classes/System/Postprocessor/Postprocessor.php the method process() should be enhanced to check for
class_exists($key)
and if that does not exist, try to create it with the
tx_form_System_Postprocessor_
namespace. Besides that, defining an interface for that would be great - the public method process() is mandatory then.
- Status changed from New to Accepted
Hi Oliver,
what ever you suggest. You got waaaaay more experience with Typo3 and programming than I do.
best regards! jan
- Target version changed from 4.7.0-alpha3 to 4.7.0-beta1
Hey everybody,
I implemented Olivers suggestions in a local git-branche. Before committing it I'd like to run a test. Can please someone help me to write an unit-test (e.g. by pointing to some documentation)?
Thx
Hi again,
I tested my changes by writing a 'Hello World'-postprocssor extension. Everything seems to work.
How do I commit my changes? Is it sufficient to post the diff here (see previous post)?
Regards
- Status changed from Accepted to Under Review
Draft documentation is attached in issue #34021.
- Target version deleted (
4.7.0-beta1)
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved to Closed
Also available in: Atom
PDF