Forum Replies Created

Viewing 15 replies - 1 through 15 (of 16 total)
  • +1 for this. I had the plugin setup and working properly on 2 different websites for over a year but they both recently stopped working. Some browsers (Chrome) don’t work at all… the login form just redirects back to my site login page and continues to show the login button. Other browsers (Firefox) appear to log the user into Wild Apricot and show the profile information but the rest of my integrations don’t work.

    It looks to me like the WA Plugin is no longer properly logging users into WordPress like it used to so any customizations that check for authenticated users or the WA user roles are now broken.

    I’ve contacted WA but so far they haven’t been helpful at all.

    @jonathanstegall Yep! Whatever fix was added in 1.8.10 did the trick for me. Thanks so much!

    I just got the same error when trying to install the plugin. MySQL version 5.6.45

    I have this same issue… though I found another temporary solution. Under Fields Factory > Settings > Fields Location I changed the selection from “Before Add To Cart Form” to “Before Add to Cart Button” and it now works. That was randomly the only difference between my working dev site and my broken live site so I found it by accident but that did the trick for me. We definitely need a long term fix for this issue though.

    +1 – I’m having the same issue.

    Thread Starter jaybuys

    (@jaybuys)

    Yes… This is just a sandbox site so I have a bunch of other plugins that are creating their own tables (Gravity Forms, Redirection, Yoast SEO, etc.)

    I looked in the database with phpMyAdmin and I do see that the wp_object_sync_sf_object_map table was created, just not the wp_object_sync_sf_field_map table. Very strange that one would be created but not the other. I have no idea why.

    I found the DB code in activate.php and used it to create the table manually. Appears to work now. I just successfully added a fieldmap so I’ll continue to play around with the plugin now that I got past that issue. Thanks for your help.

    Thread Starter jaybuys

    (@jaybuys)

    Definitely not seeing a blank screen. As I said, I fill out the entire field map form and submit it. It just shows me a blank error. Here’s a screenshot that might help – https://oi64.tinypic.com/34htc3s.jpg – It shows what I filled out and the empty error message at the top.

    I’m not sure where the plugin stores it’s log files… but I just found the error below in the main server error log which is definitely at least part of the problem. It looks like the database table the plugin is trying to use isn’t there. I’m assuming that should’ve been created during plugin activation? I tried deactivating and reactivating the plugin but that didn’t help.

    [17-Oct-2017 16:49:21 UTC] WordPress database error Table ‘wpsandbo_wordpress.wp_object_sync_sf_field_map’ doesn’t exist for query SELECT id, label, wordpress_object, salesforce_object, salesforce_record_types_allowed, salesforce_record_type_default, fields, pull_trigger_field, sync_triggers, push_async, push_drafts, weight FROM wp_object_sync_sf_field_map made by require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), include_once(‘/plugins/object-sync-for-salesforce/object-sync-for-salesforce.php’), Object_Sync_Salesforce::get_instance, Object_Sync_Salesforce->__construct, Object_Sync_Salesforce->push, Object_Sync_Sf_Salesforce_Push->__construct, Object_Sync_Sf_Salesforce_Push->add_actions, Object_Sync_Sf_Mapping->get_fieldmaps

    I have the same issue. Anyone fine a solution?

    Works! Thank you.

    Thread Starter jaybuys

    (@jaybuys)

    That appears to have worked! Thanks for the quick fix.

    I’m having this exact same issue and it appears that it’s due to the show_meta_via=’0′ property of the shortcode. Without that, everything works fine. When I add that in, the tweets that it pulls are out of date.

    I have the exact same issue. My code to output the form is this:

    <?php echo do_shortcode(‘[constantcontactapi formid=”1″ redirect_url=”‘ .home_url() . ‘/email-updates-thank-you/”]’); ?>

    When that code runs it outputs the following:
    <input type=”hidden” id=”cc_redirect_url” name=”cc_redirect_url” value=”http%3A%2F%2Fwww.mydomain.com%2Femail-updates-thank-you%2F” />

    When I submit the form, I get no redirect. The page just refreshes and give me the confirmation message instead.

    Awesome. Thanks for the quick fix.

    I’m having this same issue. When will 3.1.5 be released?

    Thread Starter jaybuys

    (@jaybuys)

    I never got a response here so I spent some time figuring out a solution myself. If anyone is interested, I solved this problem with custom fields rather than an actual taxonomy…

    The plugin works great but the Feed to Posts functionality stores on the full URL of the feed source, no reference to the Feed ID that you could use to filter by. You can change this by…

    Opening import_posts.php and adding the following lines:
    Approx. Line 649, under the line that defines the $thisLink variable add:
    $thisCat=trim($items["mycatid"]);

    Approx. Line 799, under the line that adds post_meta for the source link add:
    add_post_meta($post_id, 'rssmi_source_id', $thisCat);

    Now each post that gets imported will have an ID number related to the Feed category it came from. This is a custom field and there are a number of ways to use it to filter / sort / etc.

    My quick & easy solution was just to add a “?source=n” querystring variable and pass the ID to it. Add the following lines to your theme’s functions.php file to make that happen:

    function register_source_qv() {
      global $wp;
      $wp->add_query_var( 'source' );
    }
    add_action( 'init', 'register_source_qv' );
    
    function map_source_qv( $wp_query ) {
      if ( $meta_value = $wp_query->get( 'source' ) ) {
        $wp_query->set( 'meta_key', 'rssmi_source_id' );
        $wp_query->set( 'meta_value', $meta_value );
      }
    }
    add_action( 'parse_query', 'map_source_qv' );

    You could also use the meta_key and meta_value parameters in custom queries.

    Hope that helps anyone who may be thinking of doing something similar.

Viewing 15 replies - 1 through 15 (of 16 total)