Title: Save Button
Last modified: May 27, 2024

---

# Save Button

 *  Resolved [bruine](https://wordpress.org/support/users/bruine/)
 * (@bruine)
 * [2 years ago](https://wordpress.org/support/topic/save-button-16/)
 * Hello Antoine,
   On the **[Website]\pool** page I would like to have a “Save button”
   below every match. (Prevent scrolling on the page )I succeeded this by adding
   a row of code (**in Bold**) in the extra Plugin (football-pool-stadium-name-on-
   match-row.php) :The result is also seen on the **[Website]/user** pageHow can
   I prevent this ?Or maybe there is another way. Regards Edwin
 *     ```wp-block-code
                                       <div class="match-card-footer">
                                           <span class="buttonblock button-matches pool-page form-1"><input type="submit" name="_submit" value="Save"></span>
                                           <div class="user-score">%user_score_txt%</div>
                                           <div class="fp-icon">%stats_link%</div>
                                           <div class="fp-icon">%joker%</div>
                                       </div>
       ```
   

Viewing 4 replies - 1 through 4 (of 4 total)

 *  Plugin Author [AntoineH](https://wordpress.org/support/users/antoineh/)
 * (@antoineh)
 * [2 years ago](https://wordpress.org/support/topic/save-button-16/#post-17784344)
 * Quick & dirty hack would be to hide the button block via CSS. You can target 
   it specifically for the user page only like this:
 *     ```wp-block-code
       div.matchinfo:not(.input) .buttonblock {
       	display: none;
       }
       ```
   
 * A ‘cleaner’ way would be to only output the button on the prediction form, but
   this requires some extra coding (and understanding of how filters in WordPress
   work). The prediction form filters have an argument `$is_user_page` as you can
   see in the second link of [this example](https://wordpress.org/support/topic/extension-plugins-for-the-football-pool-plugin/#post-8998113).
   You can use it to make a difference in the HTML template (the example does this),
   or in the template parameters (these parameters define the values that are used
   in the `%placeholders%` in the templates). In your case I would opt for the params.
   Because then you can combine a check to only show the button for matches that
   are still editable and when you are not on the user page.
 * p.s. there is also an auto-save option in the plugin settings. That one uses 
   automatic AJAX calls on every change on the form.
 *  Thread Starter [bruine](https://wordpress.org/support/users/bruine/)
 * (@bruine)
 * [2 years ago](https://wordpress.org/support/topic/save-button-16/#post-17785469)
 * Goodmorning Antoine,
   Option 1: div.matchinfo:not(.input) .buttonblock { display:
   none; } Worked for me. Many thanks.Option 2:Needs more time for me. Somehow it
   didn’t work for me after activating this Plugin.Maybe I have conflict somewhere.
   I will look in to this later.I have to understand and find this first:_You can
   use it to make a difference in the HTML template (the example does this), or 
   in the template parameters (these parameters define the values that are used 
   in the `%placeholders%` in the templates_Option 3:Wow. Didnt see this option.
   This also worked.Is this option a reliable option ? Finding: Using a Phone and
   Laptop I have seen items not changing. But maybe because I was online with 2 
   devices. Sorry for that.Regards, Edwin
 *  Plugin Author [AntoineH](https://wordpress.org/support/users/antoineh/)
 * (@antoineh)
 * [2 years ago](https://wordpress.org/support/topic/save-button-16/#post-17786904)
 * Regarding 3: Because it is an asynchronous save there is always a possibility
   that something goes wrong without the user noticing it. Especially on slow connections
   the save might take longer than expected. Or something goes wrong and the user
   clicks away thinking it saved successfully before checking the result. There 
   are some visual indicators during the save, but still, they can miss it. So, 
   if they want to be absolutely sure, then they have to double check when this 
   option is activated.
 * Using multiple devices should not make a difference. There might be race conditions(
   which request is handled first?), but I can see no reason why someone would want
   to do that. And if it then goes wrong, well, it is their own predictions that
   they are messing with 😉
 * The save button is less error-prone because the feedback to the user is more 
   direct.
 *  Thread Starter [bruine](https://wordpress.org/support/users/bruine/)
 * (@bruine)
 * [2 years ago](https://wordpress.org/support/topic/save-button-16/#post-17787504)
 * ⌊Ja⌉⌊Ja⌉ Thanks !

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Save Button’ is closed to new replies.

 * ![](https://ps.w.org/football-pool/assets/icon-256x256.png?rev=983880)
 * [Football Pool](https://wordpress.org/plugins/football-pool/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/football-pool/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/football-pool/)
 * [Active Topics](https://wordpress.org/support/plugin/football-pool/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/football-pool/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/football-pool/reviews/)

 * 4 replies
 * 2 participants
 * Last reply from: [bruine](https://wordpress.org/support/users/bruine/)
 * Last activity: [2 years ago](https://wordpress.org/support/topic/save-button-16/#post-17787504)
 * Status: resolved