bxbdev

Thank you.

Thank you.

I ended up editing the role title in the database, but I am still curious why the option to edit it via the plugin settings isn’t available.

Unfortunately, that isn’t working.

Is there a reason that editing a role title isn’t natively part of the Ultimate Member plugin?

On the plugin’s www.ads-software.com page there is a link titled, “Advanced View”, on the right side of the page, under the “Tags”.

From there you can find previous versions of the plugin at the bottom of the page.

https://www.ads-software.com/plugins/vimeo/advanced/

Marking as resolved.

@missveronicatv That worked perfectly. Thanks!

I am also experiencing this issue on version 1.18.1.

Hosting sites on Flywheel. This was their response:

“It looks like the plugin is still working despite that Warning message in the plugin settings area. The .user.ini file would typically be found in the site root but it looks like the plugin developers are using ABSPATH to try to find the root when on our Cloud platform, where we secure the WordPress core, that constant points to /wordpress/ instead.

All that said, we still recommend that plugin for easy access to add headers to WordPress sites, and it is still functional, but we recommend reaching out to the developers to fix the warning noise there.”

The issue only appears for the sites using Flywheel’s Google Cloud hosting.

For sites hosted on Flywheel’s legacy hosting I don’t get that error and the sites (using the exact same HTTP Headers settings) score better for security than they do on the Google Cloud hosting.

I’m including links to screenshots which hopefully clears things up.

Here is a variation from the variable subscription product:
https://imgur.com/a/yBIQttp

You can see on the product page that instead of “90-day” it is saying “90-month”:
https://imgur.com/a/8vP8lZ0

And on the checkout page it also says, “90-month”, and has the first renewal date as April 13, 2028:
https://imgur.com/a/cdvgHBj

Again, this only happens for variable subscriptions. Simple subscriptions seem to work as expected.

Thanks for the quick implementation!

Alright, so I turned off “Optimize JavaScript Code?” completely and the conditional Gravity Form loads and works properly.

If I turn “Optimize JavaScript Code?” back on and have the following exclusions:

seal.js, js/jquery/jquery.js

the form no longer loads. This is the state the site is currently set to.

I have also cleared cache with no luck.

This page has a conditional form on it:

https://bxblayout06.flywheelsites.com/review/

• This reply was modified 6 years, 11 months ago by James Huff.
• This reply was modified 6 years, 11 months ago by bxbdev.

I figured out what was causing the CSS file to be render-blocking, though I’m not sure why it works this way…

I use comment blocks to make the SCSS file easier to navigate. Here’s an example of the format I use:

//=======================================================
// VARIABLES
//=======================================================

This resulted in a render-blocking CSS file. However, if I remove just the first line of the comment, making it look like this:

// VARIABLES
//=======================================================

The resulting CSS file is NOT render-blocking!

Again, I’m not sure why this makes a difference, but it does. I’ve tested it multiple times to make sure it wasn’t a fluke.

After removing the first comment line from each of the comment blocks I ran the PageSpeed test again and it worked! No more render-blocking and my Speed score went from 80 to 87!

I had the API set to ‘none’ so that was probably the issue.

I couldn’t figure out how to get the API key. I tried following the directions under the plugin’s FAQ page but I think Google has changed their layout because they didn’t match up with what I was seeing.

Anyway, I finally got the API key and it looks to be working properly now!

Thanks for your help and thanks again for a great plugin!