jayahn4

Hi Riza,

Thanks for taking initiative there, but would it be possible if we communicate with my own email? ([email protected]). That email belonged to a former member of the client company, and is actually no longer active or accessible.

Once we communicate with my email, I can also send you a link to a staging copy of the site that has the same settings.

Cheers,
Jay

Sure thing, the account name is
[email protected]

Hi again Riza,

I attempted to open a new support ticket, but I’m constantly being directed to log in and thus can never open a new support ticket.

So I instead clicked the option for support for non-members, and it directs to these forums. Would you please open a new ticket since we seem to be unable to?

Thanks,
Jay

Thanks for the suggestion Riza. I’ll be contacting the premium support with the client’s account.

No luck with that Riza.

I’ve also tested by deleting one of the Custom Roles called State Editor (NSW). A user with the Editor role who was in this Custom Role, now has no custom role, but is still unable to see comments as long as the plugin is active. This seems to suggest to me that Permissions Pro is doing something with the default Editor WordPress role.

Hi there. Any luck on finding a way to toggle comments on for the above config? I’d like to let our client know whether it’s possible or not.

Sure thing. The first screenshot contains the custom groups, and the second screenshot is in one of those groups.

Thanks for the solution sumitsanadhya

Can we expect the next version of the plugin to include this line of code? Just so this manual update to the plugin doesn’t need to be done again.

Hi Saurabh,

Apologies for the late reply, as I have been on leave and just returned.

The code has worked! I didn’t make use of a MU plugin and threw it into a functions file instead, but Mailhog confirms the email has sent.

Thank you so much for your assistance here and Happy New Year!

Jay

Hi @pjmorgan622

I’ve just fixed this issue on my own site. You’ll have to edit the shortcode that calls the form.

Until now, I have had a subscribe form with an ID of 1066 but my shortcode had been calling 938, like this:

do_shortcode('[contact-form-7 id="938" title="Subscribe Form"]')

But since the id is wrong, the shortcode was then relying on the “title” to find a form. But now that CF7 no longer supports this, the shortcode couldn’t find the right form, and broke the page. It’s best to remove the title attribute altogether and make sure the id you’re calling is correct.

Great news @glenwpcoder

ManageWP seems to have fixed this and now the plugin isn’t flagged as vulnerable anymore. Thank you!

@glenwpcoder

Hi Glen,

I’m having the same issue. ManageWP is flagging the plugin as vulnerable below version 2.11.0, but the latest version for this plugin is 1.3.6.7, which I have already updated to. Also downloaded manually from here and uploaded, but still vulnerable.

So I went into classes/class.field.php and edited line 146 and added ‘static’

From
function saveFile($user_id, $name, $value)

To
static function saveFile($user_id, $name, $value)

And now it is working. Since PHP 8.0 is more strict with syntax, it doesn’t allow static calling of non-static methods. Perhaps this should be updated all throughout the plugin, or does anybody have any other workarounds?

• This reply was modified 2 years ago by jayahn4.