diff --git a/plugins/content_types/rules_panes.inc b/plugins/content_types/rules_panes.inc
index 824d333..c86d92f 100644
--- a/plugins/content_types/rules_panes.inc
+++ b/plugins/content_types/rules_panes.inc
@@ -97,9 +97,9 @@ function rules_panes_admin_info($subtype, $conf, $context = NULL) {
 /**
  * Admin edit form for the content pane.
  */
-function rules_panes_edit_form($form, $form_state) {
+function rules_panes_edit_form($form, &$form_state) {
   // Create alias for the configuration, for improved code readability.
-  $conf = &$form_state['conf'];
+  $conf = $form_state['conf'];
 
   $form['button_text'] = array(
     '#type' => 'textfield',
@@ -117,7 +117,7 @@ function rules_panes_edit_form($form, $form_state) {
 /**
  * Config submit function, to store form values in pane configuration.
  */
-function rules_panes_edit_form_submit(&$form, &$form_state) {
+function rules_panes_edit_form_submit($form, &$form_state) {
   // Move important values to the 'conf' part of form_state, to allow them to
   // be saved. Note that the 'subtype_name' also goes here – this is the name
   // of the Rules component, and will be used when rendering the pane.
@@ -150,11 +150,11 @@ function rules_panes_render($subtype, $conf, $args, $context) {
  * @return
  *   The form array.
  */
-function rules_panes_render_form($form, $form_state) {
+function rules_panes_render_form($form, &$form_state) {
   // Dig out some information we will need, and create a new temporary component
   // to be able to build a suitable form.
-  $conf = &$form_state['build_info']['args'][0];
-  $contexts = &$form_state['build_info']['args'][1];
+  $conf = $form_state['build_info']['args'][0];
+  $contexts = $form_state['build_info']['args'][1];
   $component = rules_config_load($conf['component']);
   // The line here is magic to me. Thanks to VBO maintainers, again.
   $element = rules_plugin_factory($component instanceof RulesActionInterface ? 'action' : 'condition', 'component_' . $component->name);
