Forum Replies Created

Viewing 15 replies - 346 through 360 (of 725 total)
  • Plugin Author fullworks

    (@fullworks)

    Thanks for letting me know

    Plugin Author fullworks

    (@fullworks)

    I don’t know anywhere that provides testing of MapQuest API keys, you could try the MapQuest Developer Forums.

    And as mentioned, using the browser console will show you any errors.

    Plugin Author fullworks

    (@fullworks)

    WordPress.org rules forbid me from supporting pro version on the free forum, so I can’t go into detail.

    The free version does not have past events.

    All the pro features ( including past events ) can be seen here https://fullworks.net/products/widget-for-eventbrite/eventbrite-shortcode-demo/

    And you can contact me for pre sales info here https://fullworks.net/#contact

    Plugin Author fullworks

    (@fullworks)

    You don’t need to put anything in the Callback URL, it is not used by the plugin.

    Thread Starter fullworks

    (@fullworks)

    I was investigating a report from one of my plugin users that the widget kept disappearing, I couldn’t replicate the issue specifically – as far as a know it is coded correctly when I noticed the notice.

    So I then tested with the standard ‘search’ widget and that had the same notice.

    But what is really strange is I created and tested several variations and now there is no notice at all – so I expect it is an edge case when it is first used.

    Thread Starter fullworks

    (@fullworks)

    <span class="fl-builder-settings-title-text-wrap"><?php echo $widget_title; ?></span>

    Here is the full log

    [08-Apr-2020 15:19:25 UTC] PHP Notice:  Undefined variable: widget_title in /var/www/html/wp-content/plugins/beaver-builder-lite-version/modules/widget/includes/settings-general.php on line 50
    [08-Apr-2020 15:19:25 UTC] PHP Stack trace:
    [08-Apr-2020 15:19:25 UTC] PHP   1. {main}() /var/www/html/index.php:0
    [08-Apr-2020 15:19:25 UTC] PHP   2. require() /var/www/html/index.php:17
    [08-Apr-2020 15:19:25 UTC] PHP   3. wp() /var/www/html/wp-blog-header.php:16
    [08-Apr-2020 15:19:25 UTC] PHP   4. WP->main() /var/www/html/wp-includes/functions.php:1274
    [08-Apr-2020 15:19:25 UTC] PHP   5. do_action_ref_array() /var/www/html/wp-includes/class-wp.php:748
    [08-Apr-2020 15:19:25 UTC] PHP   6. WP_Hook->do_action() /var/www/html/wp-includes/plugin.php:544
    [08-Apr-2020 15:19:25 UTC] PHP   7. WP_Hook->apply_filters() /var/www/html/wp-includes/class-wp-hook.php:311
    [08-Apr-2020 15:19:25 UTC] PHP   8. FLBuilderAJAX::run() /var/www/html/wp-includes/class-wp-hook.php:287
    [08-Apr-2020 15:19:25 UTC] PHP   9. FLBuilderAJAX::call_action() /var/www/html/wp-content/plugins/beaver-builder-lite-version/classes/class-fl-builder-ajax.php:42
    [08-Apr-2020 15:19:25 UTC] PHP  10. FLBuilderUISettingsForms::render_legacy_settings() /var/www/html/wp-content/plugins/beaver-builder-lite-version/classes/class-fl-builder-ajax.php:232
    [08-Apr-2020 15:19:25 UTC] PHP  11. include() /var/www/html/wp-content/plugins/beaver-builder-lite-version/classes/class-fl-builder-ui-settings-forms.php:791
    [08-Apr-2020 15:19:25 UTC] PHP Notice:  Undefined variable: widget_form in /var/www/html/wp-content/plugins/beaver-builder-lite-version/modules/widget/includes/settings-general.php on line 57
    [08-Apr-2020 15:19:25 UTC] PHP Stack trace:
    [08-Apr-2020 15:19:25 UTC] PHP   1. {main}() /var/www/html/index.php:0
    [08-Apr-2020 15:19:25 UTC] PHP   2. require() /var/www/html/index.php:17
    [08-Apr-2020 15:19:25 UTC] PHP   3. wp() /var/www/html/wp-blog-header.php:16
    [08-Apr-2020 15:19:25 UTC] PHP   4. WP->main() /var/www/html/wp-includes/functions.php:1274
    [08-Apr-2020 15:19:25 UTC] PHP   5. do_action_ref_array() /var/www/html/wp-includes/class-wp.php:748
    [08-Apr-2020 15:19:25 UTC] PHP   6. WP_Hook->do_action() /var/www/html/wp-includes/plugin.php:544
    [08-Apr-2020 15:19:25 UTC] PHP   7. WP_Hook->apply_filters() /var/www/html/wp-includes/class-wp-hook.php:311
    [08-Apr-2020 15:19:25 UTC] PHP   8. FLBuilderAJAX::run() /var/www/html/wp-includes/class-wp-hook.php:287
    [08-Apr-2020 15:19:25 UTC] PHP   9. FLBuilderAJAX::call_action() /var/www/html/wp-content/plugins/beaver-builder-lite-version/classes/class-fl-builder-ajax.php:42
    [08-Apr-2020 15:19:25 UTC] PHP  10. FLBuilderUISettingsForms::render_legacy_settings() /var/www/html/wp-content/plugins/beaver-builder-lite-version/classes/class-fl-builder-ajax.php:232
    [08-Apr-2020 15:19:25 UTC] PHP  11. include() /var/www/html/wp-content/plugins/beaver-builder-lite-version/classes/class-fl-builder-ui-settings-forms.php:791
    Plugin Author fullworks

    (@fullworks)

    OK I have just spent the last 15 minutes testing with Beaver Builder Lite and my plugin on Twenty19 and the Widget works normally and does not disappear.

    So I don’t think the issue is Beaver Builder.

    • This reply was modified 6 years, 1 month ago by fullworks.
    Plugin Author fullworks

    (@fullworks)

    @lbmschneider WidgetForEventbriteAPI\Includes\EventBrite_API_Widget is the class that generates the Widget ( extends WP_Widget )

    Why that class should disappear is certainly not something that can happen without something ‘corrupting’ it.

    The obvious suspect is Beaver Builder. Again I would suggest testing without Beaver Builder and with Beaver Builder and if it only happens with Beaver Builder – raise a support ticket with them.

    Plugin Author fullworks

    (@fullworks)

    @lbmschneider if it works OK without Beaver Builder but disappears with Beaver Builder – then have you asked Beaver Builder support why that happens?

    Plugin Author fullworks

    (@fullworks)

    @steveman1234 TwentyNineteen has footer widget areas, just add the widget to one of those.

    Plugin Author fullworks

    (@fullworks)

    Any chance of a screen shot of the error message?

    Plugin Author fullworks

    (@fullworks)

    Hi sorry to be a pain, but we simply are not allowed to provide pro support on the free forum, that is WordPress.org rules.

    You can contact me directly, using the contact tab in the plugin settings.

    Alan

    Thread Starter fullworks

    (@fullworks)

    Hi Christian,

    I think now I have covered all the bases

    Yes all this custom code posted on github https://github.com/alanef/civi-member-sync-custom

    I generate the random email with md5 like

    do {
        $contact_data['email'] = md5( time() ) . '@fullworks.net';
    } while ( false !== email_exists( $contact_data['email'] ) );

    Also I had also to identify Relationship changes, as if the relationship is added or changed later it needs to have look for emails – to ensure they get changed.

    Alan

    Thread Starter fullworks

    (@fullworks)

    I think I have a solution that doesn’t require rebuilding the world.

    The issue is if the relationship or email doesn’t exist, it doesn’t create a WP user. The only bit I’m using is the email. So a solution would be to generate a random email string if the relationship/email is not there.

    OK so I’m going to get a load of extra WP users, but I already have the code that will sync the emails when / if they are eventually set up.

    Thread Starter fullworks

    (@fullworks)

    So the events would be – relationship ( id =7 ) added trigger an attempt at adding user.

    Or email added to the related record ( that didn’t have an email ) trigger an attempt at adding a user.

    I did create an action that fires on ‘civicrm_post’ to handle email changes ( based on some of your code in profile sync

    https://github.com/alanef/civi-member-sync-custom/blob/master/civi-member-sync-custom.php

    I guess the bit of the puzzle I have not got is the trigger to check / attempt to create the WP user.

Viewing 15 replies - 346 through 360 (of 725 total)