Answers.Body: <p>This sounds like a problem on your site specifically.</p>
  
  <p>You can always verify this by checking the <a href="https://civicrm.org/demo" rel="nofollow">public CiviCRM/WP demo site</a>.</p>
  
  <p>To me this sounds like a general javascript error on your site, likely caused by a bad WP plugin or theme. Check the <a href="https://forum.civicrm.org/index.php?topic=35850.0" rel="nofollow">javascript troubleshooting guide</a> for more details.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-19T19:21:26.347Z
Answers.Text: Yes, the demo site works as I would expect it to. It must be something on my site then... Yuck. Gonna be hard to figure this out...
Answers.UserDisplayName: osarusan
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-20T14:21:10.797Z
Answers.Text: Try switching to a basic theme and see if the problem continues. I have seen similar issues that are usually related to the theme.
Answers.UserDisplayName: KilakwaBT
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-11-10T20:54:05.457Z
Answers.Text: Disabling Jetpack fixed this problem for me.
Answers.UserDisplayName: osarusan
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-10-19T18:42:08.087Z
Answers.LastActivityDate: 2015-10-19T18:42:08.087Z
Answers.UserDisplayName: Coleman
Body: <p>I formerly used CiviCRM with a Drupal website and recently moved over to the same Civi install on a Wordpress website. The CiviDB is the same, but the CMS has changed.</p>
  
  <p>Previously, when using CiviEvent, there was a dropdown calendar for selecting the time. Also, when choosing the event location, I could select a formerly used event and it would auto-populate the fields with the event data from that previous event.</p>
  
  <p>Now, on Wordpress, those functions do not work. I have to manually enter the time and date, and while I can select a previously used event, it does not auto-populate the fields (I have to manually re-enter the info, and it will erase any fields that are left blank in the other events that share the location).</p>
  
  <p>My question is whether this is a limitation of the Wordpress version of CiviCRM, or if something was messed up when moving from Drupal to Wordpress. Do other Civi/WP users have this problem?</p>
  
Tags: <wordpress>
Title: CiviEvent & Wordpress
ThreadText: # CiviEvent & Wordpress
  
  (Asked by: username_0 on 2015-10-19)
  
  I formerly used CiviCRM with a Drupal website and recently moved over to the same Civi install on a Wordpress website. The CiviDB is the same, but the CMS has changed.
  
  Previously, when using CiviEvent, there was a dropdown calendar for selecting the time. Also, when choosing the event location, I could select a formerly used event and it would auto-populate the fields with the event data from that previous event.
  
  Now, on Wordpress, those functions do not work. I have to manually enter the time and date, and while I can select a previously used event, it does not auto-populate the fields (I have to manually re-enter the info, and it will erase any fields that are left blank in the other events that share the location).
  
  My question is whether this is a limitation of the Wordpress version of CiviCRM, or if something was messed up when moving from Drupal to Wordpress. Do other Civi/WP users have this problem?
  
  **Tags:** wordpress
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2015-10-19. Score: 1 | Accepted answer
  
  This sounds like a problem on your site specifically.
  
  You can always verify this by checking the [public CiviCRM/WP demo site](https://civicrm.org/demo).
  
  To me this sounds like a general javascript error on your site, likely caused by a bad WP plugin or theme. Check the [javascript troubleshooting guide](https://forum.civicrm.org/index.php?topic=35850.0) for more details.
  
  > **Comments:**
  > **username_0**: Yes, the demo site works as I would expect it to. It must be something on my site then... Yuck. Gonna be hard to figure this out...  
  > **username_2**: Try switching to a basic theme and see if the problem continues. I have seen similar issues that are usually related to the theme.  
  > **username_0**: Disabling Jetpack fixed this problem for me.  
  
  ---
  
  