CiviCRM Community Forums (archive)

I'm using themekey to change the theme for each of my three donation pages (our organisation has two sub-organisations that need to accept donations, and need their own theme).

Everything works fine on the main donation page, but since themekey works by URL, when one hits submit, whether there's an error or one moves to the confirmation page, the theme reverts back to the default theme.

At the moment my rules are set to work by ID (so if the contribution page's ID is 2, one theme is on, and if it's 3, a different one is used). Does anyone know of a different way to set this up, so that the theme will hold for the whole donation process (donation page, confirmation page, and thank you page)?

Right - had no problem with the ?, you can create rules in themekey for what comes before and after it, but when you move on from the first screen of the donation page, the path becomes totally generic (civicrm/contribute/transact), so themekey has no idea you are on a page that should be treated like the contribution page with ID 3.

I'm wondering if anyone knows of a solution to this.

I've solved the problem using jquery. By adding an ID to the form's "action" attribute's destination, the theme sticks.

I've added this jquery code to a custom "main.tpl" custom file:
<script type="text/javascript">
cj("form#Main").attr('action', '/civicrm/contribute/transact?&id=3');
</script>
The original action attribute didn't have an ID attached to it (/civicrm/contribute/transact). Since themekey works using the ID in the URL, simply adding it to the action attribute solves the issue completely.

I really do think this should be something addressed by the civiCRM devs - by somehow making sure the ID stays, so much can be done using themekey... This solution works, but it's not the prettiest, and there are probably situations in which it won't work quite as well as it did for me.