Forum Replies Created

Viewing 15 replies - 1 through 15 (of 39 total)
  • Thread Starter jbonlinea

    (@jbonlinea)

    Hi there,

    Thank you for investigating this issue.

    Basically in wp html block I do exactly like you, and in L&L my code is pretty simple :

    <Loop type=event id="{Field id /}">
      <span class="dashicons dashicons-email-alt"></span>
    <Shortcode>
     <h6>[eo_events p="<Field id />"]%start{l j F Y à H:i}{}% - %event_venue%[/eo_events]</h6>
      
      </Shortcode>
      </Loop>
    
    

    Here, the shortcode work as expected, but I do get a square like this in place of the dashicon : ?

    EDIT : hum, actually, if I use the L&L template in a wordpress shortcode block it works, but I use the L&L template in “custom layouts” plugin template (that I use to display search and filter results), and there it do not work !

    I have no clues why ??

    Regards

    • This reply was modified 12 months ago by jbonlinea.
    • This reply was modified 12 months ago by jbonlinea.
    Thread Starter jbonlinea

    (@jbonlinea)

    Hi there,

    Sorry, I was trying to grasp everything before coming back to you.

    The link you provided greatly clarify the situation, yet, there is something “weird” to my mind.

    you write : “Unless you really want a membership to expire after a certain time frame, you usually DO NOT want to set BOTH a recurring billing amount AND an expiration date on your levels

    Ok, but… how about the case where we want a recurring payment each calendar year, but not an automatic renewal for two reasons

    • to policy is not to “force” renewal
    • some users may not or can’t register online, but on site with the “organization admin” in front of him physically
    • Some users may want to pay by check (or cash in the above case – ei. sport organization, event entrance, etc.)

    If I understand well, we can’t offer this possibility out of the box (without extra/paid plugin).

    It seems that recurring payment, in your mind is associated with auto-renewal… while in mine, it is only associated with the fact that the membership last for the current calendar year.

    In my use case it seems that the path to follow is indeed

    • not to use recuring paiement
    • use and expiration date and
    • use the set expiration date module (to set it on Y2-01-01)

    Fine

    That’s actually what I did

    7 day before the end of the mebership period, an expiration warning email was sent, which is great

    the fact is some members attempted to renew their membership within thoses 7 days

    • Attempted: because they actually paid a second time for the current calendar year, and not the next one; the received a membership confirmation email for the curent year (and not the next one) which is pretty puzzling, and that we had to manually change their membership expiration date to next year.

    So the question could be :

    • how could we make sure that if someone who is already a member of a given level, “renew” his membership, will not pay twice for the same year, but will pay in advance for next year and see his membership extended on his account page
    • then the related question is how to make sure the above behaviour stand when the “renewal” is done within the two month preceding the expiration
    • and ultimately, how do we set pmp so that if a new member, that has never been a member before, will only have to pay once for the current year (Y) and the next one (Y+1) if he register in november or december or Y ?

    Thank’s for your support

    Thread Starter jbonlinea

    (@jbonlinea)

    Hi,

    Ok that waht I though, I just wasn’t sure which filter should be used.

    In the end this page helped build what I needed

    Here is y code snippet if someone needs it

    Cheers

    
    

    add_filter(‘bcn_breadcrumb_url’, ‘my_breadcrumb_url_changer’, 3, 10);
    function my_breadcrumb_url_changer($url, $type, $id){

    $taxonomy = ”;

    if(in_array(‘category’, $type) ){

    $term = get_term( $id );

    if ( false !== $term ) {
    $taxonomy = $term->taxonomy;

    if ($taxonomy === ‘category’ && $id != 371){
    $url = get_permalink(’23’) .’?_sft_’ . $taxonomy . ‘=’ . $term->slug ;
    }
    }

    }
    return $url;
    }

    Thread Starter jbonlinea

    (@jbonlinea)

    Hi

    it indees seems that now the template use the default font, which is great
    thank’s for tackling this issue

    Thread Starter jbonlinea

    (@jbonlinea)

    Hi,

    Ok I see now,

    The code on the documentation page is

    do_action while it should be add_action, like in your gist.

    My problem solved, but the documentation remains missleading

    Cheers

    Thread Starter jbonlinea

    (@jbonlinea)

    Ok cool souds easy to set!

    As a general rule, finding native wp dashboard icons could be great.

    Of course, one could always use a third party service like FA, but it’s overrated for a couple of icons ??

    Thank’s

    Thread Starter jbonlinea

    (@jbonlinea)

    Hi,

    well, when you import the wp-users your plug-in also import the admin… so we’re in a bad situation from start.

    Then why on earth resetting of the plug-in would delete any wp-users ! that’s crazy non-sense !

    I think this is a truely dangerous behaviour, I did exeperience it on a test site, but I can’t imagine the drama for anyone doing it on a production site !

    Otherwise there is a lot to love in it.

    Cheers

    Thread Starter jbonlinea

    (@jbonlinea)

    hi,

    May I ask if there is any documention on the the Newsletter Class, or if it is not advised to use it, if you could provide here or on the documentation (the later might even be better) a basic php example of the api rest usage ?

    Thank’s in advance

    Thread Starter jbonlinea

    (@jbonlinea)

    Hi,

    Thank’s for your reply
    Ok if the list must be public, then there is at least one reason for the above code to fail.
    But I really don’t want the list to be public, and thus used your wordpress user plug-in a a starting point, and have seen that there is a class Newsletter which seems to provide much more possibilities than TNP.

    The weird thing is that I couldn’t find any documentation on this class, thus I “reversed engineered” based on your wordpress user plug-in to find out that these very few line of code can unlock many situations

    Case when Newsletter-Subscriber is linked to Wp-User

    
    // you'll need to populate this vars with a wp user id
    // $user_id 
    // get the subscriber thank's to its linked wp_user ID
    $subscriber = Newsletter::instance()->get_user_by_wp_user_id($user_id);
    
    //  create an array that you'll use to update the subscriber
    $nl_user = array();
    
    // specify which subscriber you'll update
    $nl_user['id'] = $subscriber->id; 
    
    // populated the array with the values you want (not all of them are needed)
    $nl_user['email'] = '[email protected]'; // update the subscriber
    $nl_user['status'] = 'C'; // update the subscriber statute ; C for confirmed S for unconfirmed
    $nl_user['list_1'] = 1; // subscribe the subscriber to list_1 ; to unsbubsciber from the list set the value to 0
    
    // save the subscriber
    Newsletter::instance()->save_user($nl_user);

    if your subscriber is not linked to a wp user, just select it thank’s to his email,

    
    $subscriber_email= '[email protected]';
    $subscriber = Newsletter::instance()->get_user(Newsletter::instance()->normalize_email($subscriber_email));

    Now I have two question :
    Is there any documentation about the Newsletter Class, and if not why ?

    If the recommended way to achieve this is through the API Rest V2, could you kindly provide a snippet in the same veins as above ? it would most certainty enable many to actually use the API which documentation lacks a basic PHP and JS example/boilerplate

    Regards

    • This reply was modified 3 years ago by jbonlinea.
    • This reply was modified 3 years ago by jbonlinea.
    Thread Starter jbonlinea

    (@jbonlinea)

    Hi
    thank’s for your reply
    yes I’m aware of all that, i just think in some use case segmenting by capabilities might be very powerfull (if you grant capabilities based on membership registration, event attendence, etc…)

    regards

    Thread Starter jbonlinea

    (@jbonlinea)

    Hi there,

    you’ll find the info below, to simplify the situation, I’ve desactivated every plug-in not involved in this, but the behaviour remains the same.

    Just to make sure you get the behaviour I’m facing right.

    • I can set custom field valuer from wp-dashboard > account > UserXX account edit page
    • when I’m logged in I can broswe to a page with [pmpro_account], here the custom field are not displayed at all despite I’ve set a value, no header, no group or field title/name, no nothing
    • when I’m logged in and go the the [pmpro_member_profile_edit], then the filed groups and field name/label are diplayed, but not the fields themselves
    • when I’m not logged in, and end on this page [pmpro_checkout] which is the only one suposed to display the pods field; the field group and field name/label are displayed, but not the field themselves (I don’t know why I have said something diferent abouththis page last time, I probably miss read what was the active theme
    • And again switching to twentyXX soleve the issue

      Regards

      
      ### wp-core ###
      
      version: 5.8.1
      site_language: fr_FR
      user_language: fr_FR
      timezone: Europe/Zurich
      permalink: /%postname%/
      https_status: true
      multisite: false
      user_registration: 1
      blog_public: 1
      default_comment_status: undefined
      environment_type: production
      user_count: 4
      dotorg_communication: true
      
      ### wp-paths-sizes ###
      
      wordpress_path: /home/www/amjhl.eu/dev
      wordpress_size: 61,84 Mo (64847086 bytes)
      uploads_path: /home/www/amjhl.eu/dev/wp-content/uploads
      uploads_size: 55,86 Mo (58569176 bytes)
      themes_path: /home/www/amjhl.eu/dev/wp-content/themes
      themes_size: 55,34 Mo (58024009 bytes)
      plugins_path: /home/www/amjhl.eu/dev/wp-content/plugins
      plugins_size: 118,75 Mo (124519115 bytes)
      database_size: 12,08 Mo (12664832 bytes)
      total_size: 303,86 Mo (318624218 bytes)
      
      ### wp-active-theme ###
      
      name: Blockbase (blockbase)
      version: 1.2.21
      author: Automattic
      author_website: https://automattic.com/
      parent_theme: none
      theme_features: core-block-patterns, widgets-block-editor, post-thumbnails, responsive-embeds, editor-styles, html5, automatic-feed-links, block-templates, align-wide, experimental-link-color, title-tag, block-nav-menus, editor-style, menus, custom-logo
      theme_path: /home/www/amjhl.eu/dev/wp-content/themes/blockbase
      auto_update: Désactivé
      
      ### wp-themes-inactive (6) ###
      
      BlockbaseChild: version: 0.0.1, author: Anonyme, Mises à jour auto désactivées
      Nominal Block: version: 1.0.1, author: Theme404, Mises à jour auto désactivées
      Quadrat: version: 1.1.17, author: Automattic, Mises à jour auto désactivées
      Twenty Nineteen: version: 2.1, author: L’équipe WordPress, Mises à jour auto désactivées
      Twenty Twenty: version: 1.8, author: L’équipe WordPress, Mises à jour auto désactivées
      Twenty Twenty-One: version: 1.4, author: L’équipe WordPress, Mises à jour auto désactivées
      
      ### wp-plugins-active (5) ###
      
      Gutenberg: version: 11.8.2, author: Gutenberg Team, Mises à jour auto désactivées
      Paid Memberships Pro: version: 2.6.4, author: Stranger Studios, Mises à jour auto désactivées
      Paid Memberships Pro - Pods Add On: version: 1.0, author: Paid Memberships Pro, Mises à jour auto désactivées
      Pods - Custom Content Types and Fields: version: 2.8.3, author: Pods Framework Team, Mises à jour auto désactivées
      View Admin As: version: 1.8.7, author: Jory Hogeveen, Mises à jour auto désactivées
      
      ### wp-plugins-inactive (24) ###
      
      Advanced Custom Fields: version: 5.10.2, author: Delicious Brains, Mises à jour auto désactivées
      Amjhl extended Functionality: version: 2.0.0, author: Jonathan Benabou, Mises à jour auto désactivées
      Captcha Code: version: 2.7, author: Vinoj Cardoza, Mises à jour auto désactivées
      CoBlocks: version: 2.18.1, author: GoDaddy, Mises à jour auto désactivées
      Contact Form 7: version: 5.5.2, author: Takayuki Miyoshi, Mises à jour auto désactivées
      Custom Layouts - Post + Product grids made easy: version: 1.4.4, author: Code Amp, Mises à jour auto désactivées
      Event Organiser: version: 3.10.8, author: Stephen Harris, Mises à jour auto désactivées
      Instant Images: version: 4.5.0, author: Darren Cooney, Mises à jour auto désactivées
      Layout Grid: version: 1.7, author: Automattic, Mises à jour auto désactivées
      Lightbox for Gallery & Image Block: version: 1.9.0, author: Johannes Kinast <[email protected]>, Mises à jour auto désactivées
      MailPoet 3 (New): version: 3.73.1, author: MailPoet, Mises à jour auto désactivées
      Max Mega Menu: version: 2.9.5, author: megamenu.com, Mises à jour auto désactivées
      Paid Memberships Pro - Mailchimp Add On: version: 2.3.2, author: Stranger Studios, Mises à jour auto désactivées
      Paid Memberships Pro - Roles Add On: version: 1.4.1, author: Paid Memberships Pro, Mises à jour auto désactivées
      Paid Memberships Pro - Set Expiration Dates Add On: version: 0.6.1, author: Stranger Studios, Mises à jour auto désactivées
      Really Simple SSL: version: 5.1.3, author: Really Simple Plugins, Mises à jour auto désactivées
      VOD Infomaniak: version: 1.4.4, author: Infomaniak Staff, Mises à jour auto désactivées
      WordPress Importer: version: 0.7, author: wordpressdotorg, Mises à jour auto désactivées
      WP Super Cache: version: 1.7.4, author: Automattic, Mises à jour auto désactivées
      Yoast Duplicate Post: version: 4.1.2, author: Enrico Battocchi & Team Yoast, Mises à jour auto désactivées
      
      ### wp-media ###
      
      image_editor: WP_Image_Editor_Imagick
      imagick_module_version: 1673
      imagemagick_version: ImageMagick 6.8.9-9 Q16 x86_64 2019-12-29 https://www.imagemagick.org
      imagick_version: 3.4.4
      file_uploads: File uploads is turned off
      post_max_size: 300M
      upload_max_filesize: 300M
      max_effective_size: 300 Mo
      max_file_uploads: 100
      imagick_limits: 
      	imagick::RESOURCETYPE_AREA: 12 Go
      	imagick::RESOURCETYPE_DISK: 1.844674407371E+19
      	imagick::RESOURCETYPE_FILE: 6144
      	imagick::RESOURCETYPE_MAP: 12 Go
      	imagick::RESOURCETYPE_MEMORY: 6 Go
      	imagick::RESOURCETYPE_THREAD: 2
      imagemagick_file_formats: 3FR, AAI, AI, ART, ARW, AVI, AVS, BGR, BGRA, BIE, BMP, BMP2, BMP3, BRF, CAL, CALS, CANVAS, CAPTION, CIN, CIP, CLIP, CMYK, CMYKA, CR2, CRW, CUR, CUT, DCM, DCR, DCX, DDS, DFONT, DJVU, DNG, DOT, DPX, DXT1, DXT5, EPDF, EPI, EPS, EPS2, EPS3, EPSF, EPSI, EPT, EPT2, EPT3, ERF, EXR, FAX, FITS, FRACTAL, FTS, G3, GIF, GIF87, GRADIENT, GRAY, GROUP4, GV, HALD, HDR, HISTOGRAM, HRZ, HTM, HTML, ICB, ICO, ICON, INFO, INLINE, IPL, ISOBRL, JBG, JBIG, JNG, JNX, JPEG, JPG, JSON, K25, KDC, LABEL, M2V, M4V, MAC, MAP, MASK, MAT, MATTE, MEF, MIFF, MNG, MONO, MOV, MP4, MPC, MPEG, MPG, MRW, MSL, MSVG, MTV, MVG, NEF, NRW, NULL, ORF, OTB, OTF, PAL, PALM, PAM, PANGO, PATTERN, PBM, PCD, PCDS, PCL, PCT, PCX, PDB, PDF, PDFA, PEF, PES, PFA, PFB, PFM, PGM, PICON, PICT, PIX, PJPEG, PLASMA, PNG, PNG00, PNG24, PNG32, PNG48, PNG64, PNG8, PNM, PPM, PREVIEW, PS, PS2, PS3, PSB, PSD, PTIF, PWP, RADIAL-GRADIENT, RAF, RAS, RAW, RGB, RGBA, RGBO, RGF, RLA, RLE, RMF, RW2, SCR, SCT, SFW, SGI, SHTML, SIX, SIXEL, SPARSE-COLOR, SR2, SRF, STEGANO, SUN, SVG, SVGZ, TEXT, TGA, THUMBNAIL, TIFF, TIFF64, TILE, TIM, TTC, TTF, TXT, UBRL, UIL, UYVY, VDA, VICAR, VID, VIFF, VIPS, VST, WBMP, WMF, WMV, WMZ, WPG, X, X3F, XBM, XC, XCF, XPM, XPS, XV, XWD, YCbCr, YCbCrA, YUV
      gd_version: bundled (2.1.0 compatible)
      gd_formats: GIF, JPEG, PNG, WebP, BMP, XPM
      ghostscript_version: unknown
      
      ### wp-server ###
      
      server_architecture: Linux 4.9.0-0.bpo.12-amd64 x86_64
      httpd_software: Apache
      php_version: 7.4.24 64bit
      php_sapi: fpm-fcgi
      max_input_variables: 10000
      time_limit: 60
      memory_limit: 640M
      max_input_time: 0
      upload_max_filesize: 300M
      php_post_max_size: 300M
      curl_version: 7.52.1 OpenSSL/1.0.2l
      suhosin: false
      imagick_availability: true
      pretty_permalinks: true
      htaccess_extra_rules: true
      
      ### wp-database ###
      
      extension: mysqli
      server_version: 10.4.17-MariaDB-1:10.4.17+maria~jessie-log
      client_version: mysqlnd 7.4.24
      
      ### wp-constants ###
      
      WP_HOME: undefined
      WP_SITEURL: undefined
      WP_CONTENT_DIR: /home/www/amjhl.eu/dev/wp-content
      WP_PLUGIN_DIR: /home/www/amjhl.eu/dev/wp-content/plugins
      WP_MEMORY_LIMIT: 640M
      WP_MAX_MEMORY_LIMIT: 640M
      WP_DEBUG: false
      WP_DEBUG_DISPLAY: false
      WP_DEBUG_LOG: false
      SCRIPT_DEBUG: false
      WP_CACHE: false
      CONCATENATE_SCRIPTS: undefined
      COMPRESS_SCRIPTS: undefined
      COMPRESS_CSS: undefined
      WP_LOCAL_DEV: undefined
      DB_CHARSET: utf8
      DB_COLLATE: undefined
      
      ### wp-filesystem ###
      
      wordpress: writable
      wp-content: writable
      uploads: writable
      plugins: writable
      themes: writable
      
      ### pods ###
      
      pods-server-software: Apache
      pods-user-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0
      pods-session-save-path: /home/clients/bbc72ce255869f60b780c5b2eda42100/tmp
      pods-session-save-path-exists: Oui
      pods-session-save-path-writable: Oui
      pods-session-max-lifetime: 1440
      pods-opcode-cache-apc: Non
      pods-opcode-cache-memcached: Non
      pods-opcode-cache-opcache: Non
      pods-opcode-cache-redis: Non
      pods-object-cache-apc: Non
      pods-object-cache-apcu: Non
      pods-object-cache-memcache: Non
      pods-object-cache-memcached: Non
      pods-object-cache-redis: Non
      pods-memory-current-usage: 53,948M
      pods-memory-current-usage-real: 18,500M
      pods-network-wide: Non
      pods-install-location: /home/www/amjhl.eu/dev/wp-content/plugins/pods/
      pods-developer: Non
      pods-tableless-mode: Non
      pods-relationship-table-enabled: Oui
      pods-light-mode: Non
      pods-strict: Non
      pods-allow-deprecated: Oui
      pods-api-cache: Oui
      pods-shortcode-allow-evaluate-tags: Non
      pods-sessions: Disable sessions
      pods-can-use-sessions: Oui
      
      ### pmpro ###
      
      pmpro-cron-jobs: pmpro_cron_stripe_subscription_updates (missing) | 
      pmpro_cron_expire_memberships (2021-11-09 11:00:47) | 
      pmpro_cron_expiration_warnings (2021-11-09 17:00:48) | 
      pmpro_cron_admin_activity_email (2021-11-10 09:30:00) | 
      pmpro_cron_credit_card_expiring_warnings (2021-12-07 05:00:47)
      pmpro-gateway: Stripe
      pmpro-gateway-env: Enironnement de test
      pmpro-orders: 2 orders
      pmpro-discount-codes: 0 discount codes
      pmpro-membership-levels: {
          "1": {
              "id": "1",
              "name": "Adh\u00e9sion normale",
              "description": "",
              "confirmation": "",
              "initial_payment": 50,
              "billing_amount": 0,
              "cycle_number": "0",
              "cycle_period": "",
              "billing_limit": "0",
              "trial_amount": 0,
              "trial_limit": "0",
              "allow_signups": "1",
              "expiration_number": "12",
              "expiration_period": "Month"
          },
          "2": {
              "id": "2",
              "name": "Adh\u00e9sion gratuit\u00e9",
              "description": "",
              "confirmation": "",
              "initial_payment": 0,
              "billing_amount": 0,
              "cycle_number": "0",
              "cycle_period": "",
              "billing_limit": "0",
              "trial_amount": 0,
              "trial_limit": "0",
              "allow_signups": "1",
              "expiration_number": "0",
              "expiration_period": ""
          }
      }
      pmpro-custom-templates: No template overrides
      pmpro-getfile-usage: PMPRO_GETFILE_ENABLED is not set
      pmpro-htaccess-cache-usage: Off
      
      
    Thread Starter jbonlinea

    (@jbonlinea)

    Hi Scott,

    Thank’s for your investigation.

    The fact is I do not use any PMPro Add On, si it really is the “basic” [pmpro_account] shortcoe/page that fails displaying the PMP-Pods fields, while, again it is all right with the [pmpro_member_profile_edit] shortcode/page.

    It’ll try to reach them as they may help solve this as well, but at the moment it really seems to be a theme related issue ; mayne a full site editing ? issue, since it also fails with quadrat (from automatic) and other editor full site editing enabled theme (I tried a couple randomly)

    regards

    i may provide you some admin access in private if you want to try out on my specific install and get more clues ??
    ps :

    • This reply was modified 3 years ago by jbonlinea.
    jbonlinea

    (@jbonlinea)

    Hi there,

    I’m new to using this plug-in so my answer is a thumb guess

    maybe w email user do not add capability for itself, it “just” use one built in wordpress capability,

    If this capability is manage site, then it is normal that the plug-in is only available for admin..

    if so, it may be painfull indeed as we may not want to give editors the manage-site capability, while enabling them to use this plug-in…

    It would require further investigation, but it’s an idea to understand the actual situation and maybe modify the plug-in to solve it

    regards

    Thread Starter jbonlinea

    (@jbonlinea)

    Ok thank you for your reply, I’ll follow up over there ??

    Thread Starter jbonlinea

    (@jbonlinea)

    Hi

    if I’m logged in, and try to edit my member/account/user, no js error (in firefox)

    if i’m not logged in, and thus on the registration/paiement page, where I can/have to create my account and pay, the pods fields are displayed and editable, but I do have js errors (in chromium – I’m switching broswer to save time)
    Actually these js errors remains event if I switch to TwentyXX theme

    ?level=1:304 GET https://mysite.net/wp-content/plugins/pmpro-pods/src/Pods/assets/pmpro-pods.css?ver=1.0 net::ERR_ABORTED 404
    pods-dfv.min.js?ver=46d5919355edbbb0cf27c2cd62c0a9dd:1 Pods init with initial values: {pmpro_membership_user-0-0: {…}}

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