tnightingale

Using latest version of PMPro…

I looked at the article on CSS Nesting. Also another article about browser support. IMO it’s too new to be used on many sites: “Since?December 2023, this feature works across the latest devices and major browser versions”. Many of the members of the sites I manage that use PMPro have older browsers and operating systems (myself included, for now) and it’s just not good practice to use the latest cutting edge methods with no fallbacks. This is the first time I’ve come across this issue. I would strongly suggest you include a non-nested stylesheet option that can be chosen in the Design settings. That way people who know their audience is 100% going to have newer browsers and operating systems can choose the nested version, and the rest of us can have something that works for everyone.

As a workaround for now I’ll use the “minimalist” option and copy all the styling over to my theme.

Additional info:

The required post title issue can be bypassed by saving the submission as draft and continuing later.

(another clue)

Hello, sorry for the time delay, I have been very busy with other projects. This is not resolved unfortunately.

I have made a staging site where I disabled all other plugins and switched to 2024 theme, and the problem persists. An offset of 2 days still makes it possible to select the next day. On the live site, where I have it set to an offset of 3 days, a few site visitors have complained they are only able to select from the 3rd day from the start date (e.g. July 1st start date, July 4th end date) – so it is working as expected for certain device/browser configurations (a minority). Maybe that gives a clue as to what’s causing this.

I hope this can be figured out as Forminator is by far the best form plugin in every other way.

It’s a different thing… it’s the PMPro edit profile form which is coming from PMPro with the PODS PMPro extension adding the extra user fields to the profile.

I will test things in the staging site and let you know.

Thanks!

Thanks!! amazing.

I am using this for PMPro members when editing their Member profile – the POD is an extension for PMPro Membership – will it work for that? (front-end form for logged in members)

Update: I ended up rolling back the other plugin (that required PHP 8.0+) and then reverting to 7.4 and the slides are all working fine again. So it’s a problem with PHP8.1 and MS, apparently. Hopefully this can be fixed in the next update?

Just wanted to add, for others looking to do the same, to change the admin name as well as the email address (it shows up in the “Dear ___” header):

function my_pmpro_admin_email_header_name( $data, $email ) {
if ( strpos( $email->template, '_admin' ) !== false ) {
$data['header_name'] = 'Custom Admin Name';
}
return $data;
}
add_filter( 'pmpro_email_data', 'my_pmpro_admin_email_header_name', 10, 2 );

Is it as simple as this? (put in child/custom theme functions file)

remove_filter( 'pmpro_email_filter', 'pmpro_add_user_fields_to_email', 10 );

it’s working, must have been some typo on my previous snippet. Thanks. I’m not a newbie.

Thank you! I actually tried that already (using the same filter, just a different field name for recipient email) but it caused a site crash as soon as I did something that triggered an admin email. That’s why I posted here. However, I’ll try again using this code recipe you provided, maybe there was a typo before.

Thanks, this works!

Sorry but how is that relevant?

Hi – thanks but that’s not at all what I was asking. I can already hide or show events based on membership levels using the PMPro events add-on. (We don’t need to do that – events are for members and non-members.) I was asking about tickets. Please re-read my original question.

We have lower priced tickets for members. I want only actual members to see the member tickets (not anyone who is logged in). This would be related to the settings for individual tickets, where they can be restricted to “everyone”, “members”, or “guests”. But “members” is not checking for membership levels.

Hope that is clearer.

The latest plugin update seems to have regressed this functionality. Editor can’t view subscriber list again. The new setting is on to allow editor access. It was working until about 2 days ago.

Same error message, “sorry you cannot list resources”.

“For example, if?{date-1}?is set to February 3, and the offset of?{date-2}?field is?+2, the result should be calculated like this: 3+2=5. So February 5 is going to be the first available date for?{date-2}.“

But that is not what is happening. With an offset of +2, Feb 4 is the first available date for {date-2} when {date-1} is Feb 3. To make Feb 5 the first available date, I have to set the offset to +3, not +2. So the math is incorrect in the plugin. I can’t make it any clearer.

Thank you for investigating this issue.