One more thing: In the code above, the CSS class for the second module is .module-customtext2 (that's the first variable in open_module). If the custom text module has some existing styling it would be better to leave it to the usual 'customtext' so the styling applied to both modules. If you want to be able to CSS style the second module differently, you can add a second class by changing the name to 'customtext membersmodule'. However, if you used .membersmodule in your CSS customizations, keep in mind that any code savvy person would deduce this module existed if they looked at the CSS for the journal.
Re: Adding a second module, tied to the first one
One more thing: In the code above, the CSS class for the second module is .module-customtext2 (that's the first variable in open_module). If the custom text module has some existing styling it would be better to leave it to the usual 'customtext' so the styling applied to both modules. If you want to be able to CSS style the second module differently, you can add a second class by changing the name to 'customtext membersmodule'. However, if you used .membersmodule in your CSS customizations, keep in mind that any code savvy person would deduce this module existed if they looked at the CSS for the journal.
Re: Adding a second module, tied to the first one
Good point. I guess I could always name it to something less suspicious like "ct2" or "potato" or something.
Re: Adding a second module, tied to the first one
Re: Adding a second module, tied to the first one