CiviCRM Community Forums (archive)

Me again with another problem I just noticed.

I cannot edit communication preferences fields (e.g., Email greeting, Postal greeting, Addressee) once I select something in a drop-down and save the changes, nor when there are already values set in those fields.

I can highlight text in any of those fields, but I cannot change the text and there are no drop-downs for selecting a different format to use.

All other fields for the contact (e.g., in the Address area) remain editable.

Thoughts? Advice? Bug?

Paul

Well, that was a smart suggestion. I keep forgetting the demo sites are out there.

Those fields are indeed editable on the demo site. Each of the fields has a small "edit" icon to the right of it. Clicking on the icon brings up the drop-down selections for that field.

I wonder why that icon is missing from my CiviCRM/Wordpress installation and the fields are not editable?

Paul

After lobo's sensible suggestion to check the demo site for similar behavior (and not seeing it), I thought I'd do some more experimental troubleshooting -- and I hope that someone with expertise in how the database works can give me some advice.

What I did:

-- Backed up my stuff
-- Exported my CiviCRM data
-- Got rid of Wordpress and CiviCRM
-- Installed Wordpress and CiviCRM scratch

Running CiviCRM now works exactly like the demo site -- no problems at all. The tab drop-downs on the edit page work. I can click on the checkbox to use another contact's address and the appropriate search field shows up right there.

Then, if I import all of my CiviCRM data that originated with my Drupal site, the problems mentioned at the start of this thread show up:

-- Collapse/Expand of tabs (e.g., "Contact details) does not work on edit page
-- Ability to edit completed Communications preferences (e.g., Email greeting) does not work
-- Use another contact's address (clicking checkbox does not bring up the inline contact search) does not work

So . . . the problem lies not with Wordpress or the Wordpress CiviCRM module, but rather in that set of data exported then imported?

Here's where I'm hoping someone with greater expertise can give me clues about where to look and how to fix this.

In phpMyAdmin, I compared the tables in both databases and see two kinds of differences:

-- Tables that exist in the source database that do not exist in a fresh database
-- Tables that exist in both source and fresh databases, but which change in the fresh database when data gets imported

I'm guessing the problems I see are caused by something in one or the other.

Apologies in advance for the massive dump below, but I've copied those differences there in hopes that someone who knows these data structures might be able to point to the likely culprit(s).

And thanks in advance for any such help!

Paul

----------------------------------------------------------

Below are tables in my prior CiviCRM database running on Drupal that do not exist in a fresh Worpress installation. I'm wondering if importing by data into the fresh installation brings over something in the list below that causes the strage behavior on the Edit page in the interface.

Table Ascending    Rows    Type    Collation    Size    Overhead
access    0    MyISAM    utf8_general_ci    1 KiB    -
accesslog    0    MyISAM    utf8_general_ci    1 KiB    -
actions    11    MyISAM    utf8_general_ci    8.8 KiB    -
authmap    0    MyISAM    utf8_general_ci    2 KiB    -
backup_migrate_destinations    0    InnoDB    utf8_general_ci    16 KiB    -
backup_migrate_profiles    0    InnoDB    utf8_general_ci    16 KiB    -
backup_migrate_schedules    0    InnoDB    utf8_general_ci    16 KiB    -
batch    0    MyISAM    utf8_general_ci    1 KiB    -
block    186    MyISAM    utf8_general_ci    25 KiB    -
blocked_ips    0    InnoDB    utf8_general_ci    32 KiB    -
block_custom    0    MyISAM    utf8_general_ci    2 KiB    -
block_node_type    0    InnoDB    utf8_general_ci    32 KiB    -
block_role    0    MyISAM    utf8_general_ci    2 KiB    -
cache    10    InnoDB    utf8_general_ci    256 KiB    -
cache_block    0    InnoDB    utf8_general_ci    32 KiB    -
cache_bootstrap    5    InnoDB    utf8_general_ci    128 KiB    -
cache_field    4    InnoDB    utf8_general_ci    64 KiB    -
cache_filter    0    InnoDB    utf8_general_ci    32 KiB    -
cache_form    0    InnoDB    utf8_general_ci    32 KiB    -
cache_menu    74    InnoDB    utf8_general_ci    432 KiB    -
cache_page    0    InnoDB    utf8_general_ci    32 KiB    -
cache_path    0    InnoDB    utf8_general_ci    32 KiB    -
cache_update    8    InnoDB    utf8_general_ci    128 KiB    -
civicrm_import_job_41bc55ed93b6ec50a85668db7514f447    15    InnoDB    utf8_unicode_ci    16 KiB    -
civicrm_task_action_temp_e763053fa66a416bd8a3be2295f03a31_4212    1,932    MyISAM    utf8_unicode_ci    34.2 KiB    -
civicrm_task_action_temp_e763053fa66a416bd8a3be2295f03a31_4550    1,887    MyISAM    utf8_unicode_ci    33.9 KiB    -
civicrm_task_action_temp_e763053fa66a416bd8a3be2295f03a31_6853    1,887    MyISAM    utf8_unicode_ci    33.9 KiB    -
civicrm_value_constituent_information_1    24    InnoDB    utf8_unicode_ci    80 KiB    -
civicrm_view_case_activity_recent    0    View    ---    -    -
civicrm_view_case_activity_upcoming    0    View    ---    -    -
comment    0    MyISAM    utf8_general_ci    4 KiB    -
d6_upgrade_filter    0    MyISAM    utf8_general_ci    1 KiB    -
date_formats    35    InnoDB    utf8_general_ci    32 KiB    -
date_format_locale    0    InnoDB    utf8_general_ci    16 KiB    -
date_format_type    3    InnoDB    utf8_general_ci    32 KiB    -
field_config    3    InnoDB    utf8_general_ci    144 KiB    -
field_config_instance    6    InnoDB    utf8_general_ci    48 KiB    -
field_data_body    1    InnoDB    utf8_general_ci    128 KiB    -
field_data_comment_body    0    InnoDB    utf8_general_ci    128 KiB    -
field_data_field_test    1    InnoDB    utf8_general_ci    128 KiB    -
field_revision_body    1    InnoDB    utf8_general_ci    128 KiB    -
field_revision_comment_body    0    InnoDB    utf8_general_ci    128 KiB    -
field_revision_field_test    1    InnoDB    utf8_general_ci    128 KiB    -
files    0    MyISAM    utf8_general_ci    1 KiB    -
file_managed    0    InnoDB    utf8_general_ci    80 KiB    -
file_usage    0    InnoDB    utf8_general_ci    64 KiB    -
filter    10    InnoDB    utf8_general_ci    32 KiB    -
filter_format    3    MyISAM    utf8_general_ci    13.1 KiB    -
flood    0    MyISAM    utf8_general_ci    4 KiB    -
history    0    MyISAM    utf8_general_ci    1 KiB    -
menu_custom    6    MyISAM    utf8_general_ci    2.9 KiB    -
menu_links    263    MyISAM    utf8_general_ci    88.8 KiB    -
menu_router    314    MyISAM    utf8_general_ci    213.2 KiB    -
node    1    MyISAM    utf8_general_ci    18.1 KiB    -
node_access    1    MyISAM    utf8_general_ci    8 KiB    -
node_comment_statistics    0    MyISAM    utf8_general_ci    1 KiB    -
node_counter    0    MyISAM    utf8_general_ci    1 KiB    -
node_revision    1    MyISAM    utf8_general_ci    4 KiB    -
node_type    3    MyISAM    utf8_general_ci    3 KiB    -
openid_association    0    MyISAM    utf8_general_ci    4 KiB    -
openid_nonce    0    MyISAM    utf8_general_ci    4 KiB    -
profile_field    0    MyISAM    utf8_general_ci    4 KiB    -
profile_value    0    MyISAM    utf8_general_ci    1 KiB    -
queue    0    InnoDB    utf8_general_ci    48 KiB    -
registry    378    InnoDB    utf8_general_ci    112 KiB    -
registry_file    194    InnoDB    utf8_general_ci    64 KiB    -
role    8    MyISAM    utf8_general_ci    4.2 KiB    -
role_permission    258    InnoDB    utf8_general_ci    32 KiB    -
search_dataset    1    MyISAM    utf8_general_ci    2.1 KiB    -
search_index    10    MyISAM    utf8_general_ci    3.2 KiB    -
search_node_links    0    MyISAM    utf8_general_ci    1 KiB    -
search_total    10    MyISAM    utf8_general_ci    2.2 KiB    -
semaphore    0    MyISAM    utf8_general_ci    4 KiB    -
sequences    1    InnoDB    utf8_general_ci    16 KiB    -
sessions    2    MyISAM    utf8_general_ci    14.6 KiB    -
system    127    MyISAM    utf8_general_ci    101.8 KiB    -
taxonomy_index    0    InnoDB    utf8_general_ci    48 KiB    -
taxonomy_term_data    0    MyISAM    utf8_general_ci    4 KiB    -
taxonomy_term_hierarchy    0    MyISAM    utf8_general_ci    1 KiB    -
taxonomy_term_relation    0    MyISAM    utf8_general_ci    1 KiB    -
taxonomy_term_synonym    0    MyISAM    utf8_general_ci    4 KiB    -
taxonomy_vocabulary    0    MyISAM    utf8_general_ci    4 KiB    -
url_alias    0    MyISAM    utf8_general_ci    4 KiB    -
users    2    MyISAM    utf8_general_ci    13.2 KiB    -
users_roles    0    MyISAM    utf8_general_ci    1 KiB    -
variable    95    MyISAM    utf8_general_ci    23.8 KiB    -
watchdog    86    MyISAM    utf8_general_ci    24 KiB    -
webform    0    InnoDB    utf8_general_ci    16 KiB    -
webform_civicrm_forms    0    InnoDB    utf8_general_ci    16 KiB    -
webform_civicrm_submissions    0    InnoDB    utf8_general_ci    16 KiB    -
webform_component    0    InnoDB    utf8_general_ci    16 KiB    -
webform_emails    0    InnoDB    utf8_general_ci    16 KiB    -
webform_last_download    0    InnoDB    utf8_general_ci    16 KiB    -
webform_roles    0    InnoDB    utf8_general_ci    16 KiB    -
webform_submissions    0    InnoDB    utf8_general_ci    64 KiB    -
webform_submitted_data    0    InnoDB    utf8_general_ci    48 KiB    -


----------------------------------------------------------

Below are that have differences in a fresh installation *after importing* existing data that came from my prior CiviCRM database running on Drupal. I'm guessing that most of these things are differences simply because there's data rather than almost no data in my fresh installation. And I'm skeptical that anything in the data itself would cripple the UI. But is there anything in this list that is not just containing data, but also causing the strage behavior on the Edit page in the interface?

civicrm_acl    64    InnoDB    utf8_unicode_ci    32 KiB    -
civicrm_acl_entity_role    1    InnoDB    utf8_unicode_ci    48 KiB    -
civicrm_activity    0    InnoDB    utf8_unicode_ci    192 KiB    -
civicrm_address    1    InnoDB    utf8_unicode_ci    176 KiB    -
civicrm_cache    19    InnoDB    utf8_unicode_ci    128 KiB    -
civicrm_contact    1    InnoDB    utf8_unicode_ci    288 KiB    -
civicrm_contribution    0    InnoDB    utf8_unicode_ci    224 KiB    -
civicrm_contribution_page    0    InnoDB    utf8_unicode_ci    64 KiB    -
civicrm_custom_field    0    InnoDB    utf8_unicode_ci    48 KiB    -
civicrm_custom_group    0    InnoDB    utf8_unicode_ci    64 KiB    -
civicrm_dashboard_contact    1    InnoDB    utf8_unicode_ci    48 KiB    -
civicrm_dedupe_rule    17    InnoDB    utf8_unicode_ci    32 KiB    -
civicrm_dedupe_rule_group    7    InnoDB    utf8_unicode_ci    16 KiB    -
civicrm_email    2    InnoDB    utf8_unicode_ci    96 KiB    -
civicrm_entity_tag    0    InnoDB    utf8_unicode_ci    48 KiB    -
civicrm_event    0    InnoDB    utf8_unicode_ci    112 KiB    -
civicrm_group    1    InnoDB    utf8_unicode_ci    80 KiB    -
civicrm_group_contact    0    InnoDB    utf8_unicode_ci    80 KiB    -
civicrm_group_nesting    0    InnoDB    utf8_unicode_ci    48 KiB    -
civicrm_im    0    InnoDB    utf8_unicode_ci    96 KiB    -
civicrm_line_item    0    InnoDB    utf8_unicode_ci    80 KiB    -
civicrm_loc_block    1    InnoDB    utf8_unicode_ci    144 KiB    -
civicrm_log    1    InnoDB    utf8_unicode_ci    48 KiB    -
civicrm_mailing    0    InnoDB    utf8_unicode_ci    208 KiB    -
civicrm_mailing_group    0    InnoDB    utf8_unicode_ci    32 KiB    -
civicrm_mailing_recipients    0    InnoDB    utf8_unicode_ci    80 KiB    -
civicrm_mapping    0    InnoDB    utf8_unicode_ci    32 KiB    -
civicrm_mapping_field    0    InnoDB    utf8_unicode_ci    64 KiB    -
civicrm_membership_block    0    InnoDB    utf8_unicode_ci    48 KiB    -
civicrm_membership_type    0    InnoDB    utf8_unicode_ci    96 KiB    -
civicrm_msg_template    57    InnoDB    utf8_unicode_ci    1.5 MiB    -
civicrm_navigation    251    InnoDB    utf8_unicode_ci    96 KiB    -
civicrm_note    0    InnoDB    utf8_unicode_ci    48 KiB    -
civicrm_option_group    79    InnoDB    utf8_unicode_ci    32 KiB    -
civicrm_option_value    680    InnoDB    utf8_unicode_ci    224 KiB    -
civicrm_phone    1    InnoDB    utf8_unicode_ci    96 KiB    -
civicrm_pledge_block    0    InnoDB    utf8_unicode_ci    32 KiB    -
civicrm_premiums    0    InnoDB    utf8_unicode_ci    16 KiB    -
civicrm_premiums_product    0    InnoDB    utf8_unicode_ci    48 KiB    -
civicrm_prevnext_cache    1    InnoDB    utf8_unicode_ci    32 KiB    -
civicrm_price_field    1    InnoDB    utf8_unicode_ci    48 KiB    -
civicrm_price_field_value    1    InnoDB    utf8_unicode_ci    48 KiB    -
civicrm_price_set    2    InnoDB    utf8_unicode_ci    64 KiB    -
civicrm_price_set_entity    0    InnoDB    utf8_unicode_ci    48 KiB    -
civicrm_product    0    InnoDB    utf8_unicode_ci    16 KiB    -
civicrm_relationship_type    9    InnoDB    utf8_unicode_ci    48 KiB    -
civicrm_report_instance    34    InnoDB    utf8_unicode_ci    112 KiB    -
civicrm_setting    42    InnoDB    utf8_unicode_ci    128 KiB    -
civicrm_subscription_history    0    InnoDB    utf8_unicode_ci    48 KiB    -
civicrm_tag    5    InnoDB    utf8_unicode_ci    64 KiB    -
civicrm_tell_friend    0    InnoDB    utf8_unicode_ci    16 KiB    -
civicrm_uf_field    64    InnoDB    utf8_unicode_ci    48 KiB    -
civicrm_uf_join    13    InnoDB    utf8_unicode_ci    48 KiB    -

Initial thought for Paul's issues are that the resource and/or base url settings are still pointing to Drupal locations. Verify CIVICRM_UF_BASEURL in civicrm.settings.php file. And go to CiviCRM > Administer > System Settings > Resource URLs to make sure it's pointing to the correct path.

I suspect you may be seeing jScript errors in FireFox if you check because the resource / base url problem will cause some of the required javascript functions to be missing.

Hi, all . . .

Sorry for the long delay in reporting back, but I only recently returned to this issue -- and your previous replies had ended up in my spam directory anyway!

I ended up not being able to solve this problem in an easy way (e.g., changing base URLs, which were fine), so I did it the difficult way: I exported all of my data, through it into Excel, cleaned out everything I really didn't need, did some detail-level error checking, and re-imported all of the raw data from a CSV file into a fresh install of CiviCRM.

In the process, I encountered the same kind of importing errors other people seem to encounter -- only a portion, not all of the contacts were imported. My contacts numbered only in the low thousands, and I new it wasn't a memory/processing power problem as some of the posts about this issue speculated. I went back to the raw data instead and found a few more anomalies such as commas inside a street address (e.g., ("The Stables, Ash Lane"). Fixing every last one of those types of things eventually led to the entire set of contacts going back in.

As for my original issue . . . with the fresh install and the fresh import of data, CiviCRM as a Wordpress plug-in now works perfectly!

Now on to my next issue to solve: Email and Postal Greeting Options that don't get applied to contacts. I'll have to do a new forum post to inquire about that.

Thanks for weighing in with your advice and reports about your own experiences.

Cheers,
Paul