• Resolved emanuel2000

    (@emanuel2000)


    Hello Roland,

    I have been using this plugin for a very long time, including with several paid add-ons, and I would like to take this opportunity to thank you, Roland, for all your efforts!
    I use several sign up forms and to differentiate them, I use a hidden field that simply records a value present in the shortcode like this “shortcode->source”. Exactly as described in the “Capturing a Literal Value from the Shortcode” tutorial. And everything went perfectly until a few days ago when version 2.5.2 appeared.
    After the update, the record gets the value “shortcode->source” instead of the value defined in the call line of the command [pdb_signup source=”homepage”].

    I downgraded to version 2.5.1 and everything returned to normal (the record gets the value “homepage”). I wouldn’t want to fall behind with the updates, so maybe something can be done with this problem.

    Thanks again Roland!

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author xnau webdesign

    (@xnau)

    I just did a bunch of testing with this and wasn’t able to duplicate the problem, so probably I have failed to duplicate the circumstances you have there.

    From you description, it sounds like the hidden field isn’t getting included in the signup form, so it’s using the default value directly.

    Is there anything unusual about your setup?

    Do you have multiple Participants Database shortcodes on the page with your signup form?

    Also, try checking and re-saving the field configuration. After doing that open the page on your site with the signup form. Using the HTML inspector, check the value of the hidden field in the form. It should have the literal value from the shortcode in there.

    Thread Starter emanuel2000

    (@emanuel2000)

    I have a normal site, I think. And everything goes well with version 2.5.1.
    Today I tried to see what happens if I reinstall 2.5.2. and I did prinscreen for both versions in the HTML inspector. I discovered that in the case of version 2.5.2. value is null, no value is assigned to the hidden field. And if I downgrade to 2.5.1. then everything returns to normal and the value of the field in the pdb_signup code is assigned correctly.

    To answer the question related to other codes on the page, the answer is yes, I also use another code on the same page. It is about [pdb_list orderby=date_recorded order=desc search=true filter=”typologie=denon&villa_field=Residence Poesia” ]. It is a code that should display exactly those records that already exist, from the same registration form…

    I’m not a programmer and I don’t know what could be relevant in this situation. I use the following plugins (I list them here, it may help): Code Snippets, Divi Contact Form 7, DP Preloader, Manager WP files, Jetpack Boost, MC4WP : Mailchimp for WordPress, Participants Database, Participants Database Chosen Selector, Participants Database Custom Templates, Participants Database Datepicker, Participants Database HTML5 Form Elements, Participants Database Multi-Relational Db, ParticleJS Background, Performance Lab, Phoenix Media Rename, Popups for Divi, Slider Revolution, Slider Revolution Bubblemorph AddOn, Slider Revolution Mousetrap Add-On, Slider Revolution Transitionpack Add-On, Supreme Modules Lite – Divi Theme, Extra Theme and Divi Builder, Ultimate Member, WP Cerber Security, Antispam & Malware Scan, WP Rollback,
    WP Statistics, WP-Optimize, WPvivid Backup Plugin, xnau Plugin Updates, Yoast SEO.

    Version 2.5.2.:

    Version 2.5.1.:

    Plugin Author xnau webdesign

    (@xnau)

    I do have code in the next release of Participants Database that should fix the problem, which I believe has to do with there being multiple shortcodes on the page.

    Thread Starter emanuel2000

    (@emanuel2000)

    Thanks Roland! I hope that everything will be allright with the new relase. I will let you know!

    Thread Starter emanuel2000

    (@emanuel2000)

    Thanks Roland!

    With version 2.5.3 everything is going well!

    Emanuel

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Problems with “shortcode->source”’ is closed to new replies.