haydnjames

Ah! In that case, ignore me ??

I could have sworn it was automatic for the Euros in 2021 but I’ll take your word for it. ????

Brilliant, thank you!

@antoineh Thanks for confirming.

Do you recommend simply editing the Match details to select the teams moving forward, or renaming the Team placeholders?

Thank you so much! Just that little pointer made solving this problem so much easier!! ??

Thanks @antoineh ??

After delving into the templates to make some other modifications I think I’d come to the realisation this was by design. Thanks for responding though and thanks for a great plugin!

I found there was a setting for this for the USER page, but nothing for the predictions form page.

• This reply was modified 3 years, 6 months ago by haydnjames.

@veronalabs

This issue IS caused by WP Statistics 13.0.4.

The issue relates to this line of CSS:

.ui-sortable {
 min-height:100px
}

On line 934 of admin.min.css loaded by WP Stastics. You’re forcing a min-height on all the available slots. So if the chart is either disabled or shown in a different place within the page (i.e. below the editor area) it leads to the excessive space between the title and the editor box.

• This reply was modified 3 years, 11 months ago by haydnjames.

It is failing to pass a mod security rule. But this looks to be false negative as it refers to an earlier version of UM – but I have the latest version installed.

Investigations continue!

Hey @champsupertramp

I have spoken to my host and they have found that by disabling ModSecurity on the domain – UM email settings can be saved as expected. However. On the existing domain that I had where it was working fine – ModSecurity is still enabled. So whilst that has ‘resolved’ it with the new host, I’m not sure it really is fixed and that is just masking another problem.

I don’t believe having ModSecurity disabled is recommended so its not something I want to keep! So I think there is more troubleshooting to be done. I’ve asked the host if they can track specifically where the action may be getting blocked – is there anything specifically they should be looking at do you think?

@champsupertramp Hey, is this something you’ve had chance to investigate or is there some further advice of what I could check? ??

No, they are separate servers. Both Apache.

**EDIT** Some extra info. OLD server being the one where this is working.

Cpanel version: NEW: 92.0 OLD: 90.0
Apache version: Both 2.4.46
Server PHP version: 7.1.33
MySQL Version: NEW: 5.7.32 OLD: 10.3.20-MariaDB
Architecture: Both x86_64
OS:Both Linux
Perl Version: Both: 5.16.3

• This reply was modified 4 years ago by haydnjames.

This is really bugging me!

I came across the problem as we are re-building our UAT site. This functionality works as expected on our live and existing UAT sites.

The only difference between those and the new UAT site where we are seeing the problem are:

• We’re not upgrading from a previous version of UM, its a clean install
• The MySQL DB version is newer (5.7.32 on the new install and 5.5.5 on the existing setup.)

Apologies, this is the email templates that cannot be edited/saved, not a users email address.

It was on UM > Settings > Email. The area where you can switch the different notifications on/off and change the wording, etc.

@ultimatemembersupport I have confirmed, no server side caching on our test site. I have deactivated and cleared the cache plugin entirely. On the latest version, I see the invalid nonce error intermittently and on roll back, no issues.

So whilst cache settings may be “fixing” this for some people, it seems the problem may actually sit with something that changed in the latest update.

@dmcknight

Your solution is 99% there for me. The fields are showing and ‘saving’ but for dropdowns, the wrong info is being saved. Its saving the option order number and not the actual value. So for example: a dropdown option like: <option value=”0″>Marketing</option> is saving as ‘0’ not ‘Marketing’ which means the info cannot be used elsewhere using um_user(‘field_name’).

Any idea on how the code could be modified to fix that? ??