Timeline for Adding a block to login onepage checkout
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 30, 2013 at 1:54 | comment | added | Sylvain Rayé | @mybluevan I don't understand the downvote (if you did it). A downvote is deserved for these cases stackoverflow.com/privileges/vote-down My answer is put here to show an alternative solution. It's not the best I know but it allows to have captcha and the customized module layout. I was not clear by saying that it will prevent the use by other modules. I wanted to mean that if you want to add a child to this block, it will still continue to be a problem. I'm still investigating a cleaner way. The Fabian's one doesn't work at all, I invite you to test it by yourself in the same condition | |
| Jan 30, 2013 at 1:44 | history | edited | Sylvain Rayé | CC BY-SA 3.0 |
added 22 characters in body
|
| Jan 29, 2013 at 16:34 | comment | added | mybluevan |
As you state, this will prevent any other modules from using this block as well, and will also cause problems with upgrades. The <reference name="form.additional.info"> and <depends> solution above is much cleaner and more maintainable.
|
|
| Jan 28, 2013 at 22:21 | history | answered | Sylvain Rayé | CC BY-SA 3.0 |