You can also just go through login_next to the Python Script Controller (you can also distinguish other similar objects in the / plone _login area of ββthe Plone main product, which end with the extension ".cpy") that you write, which sends (maybe notifyMangersUponLogin), and not the default for switching to login_success.
Then try passing CPT Script to login_success to continue the MVC sript / page stream that is supplied by Plone if you need it.
To use the controller page templates (.cpt files) / Scripts (.cpy files), it allows not only copying the user version of login_next.cpy to its own path to the product outline, but also the login.cpy.metadata file, which defines the success actions / MVC / script page logical flow failure.
In Plone 4.0.2, you will find Plone-dependent scripts / templates under a path such as: / buildout -cache / eggs / plone-4.0.2-py2.6.egg / Products / CMFPlone / skins / plone_login regarding your structure assembly.
source share