Why didt i look here first before asking you / disturb you..
No worries. Happy to help.
I would prefer to have the save button after each “round/week”
That one is also possible, but a bit more work and basically combines the idea of both examples. It depends on how you divide your matches, but if you use match types per week/round, you could change the match type row template with this hook: footballpool_predictionform_match_type_template
. And then append the button code before the outputted html. The match row example is a good start point.
If you want to base it on match date, then you could keep using the match row template, but then some extra logic is needed in the params filter: a condition to check if the %save_button% placeholder should be empty or not based on the match date.
This requires a bit of PHP knowledge, though. I think the match type is the easiest route.
Another idea: do not use the prediction page, but construct one yourself with the shortcodes. Disadvantages: manual work everytime you add a new week/rpund and the players cannot save the entire form with one click (because every shortcode acts as a single form).