reswild

If you don’t need the Styles Manager, the easiest way to clear this error is to just disable the Styles Manager addon in the settings: You’ll find a checkbox for this if you go to EditorsKit in the admin menu, and then to the tab for Styles Manager.

If you want to see if you can get the Styles Manager to work, you can try to edit the file includes/addons/styles-manager/blocks/gutenberghub-styles-manager-block.php and change line 37 from

        EDITORSKIT_PLUGIN_DIR . 'build/styles-manager-addon.js',

to

        EDITORSKIT_PLUGIN_URL . 'build/styles-manager-addon-block.js',

I never got Styles Manager working though, so there might be other errors that needs fixing as well.

Someone posted a proposed fix for this at https://www.ads-software.com/support/topic/validaterequired-js79-uncaught-typeerror-currentvalue-trim-is-not-a-function/

Downgrading to the previous version of Ninja Forms is probably the easier option though.

I had the same issue, but I got it working with just a small change to the Flying Scripts plugin code. In html-rewrite.php, I changed line 52 from
else {
to
elseif ($script->innertext) {

I’ve checked your code, and I can see that the members_review_prompt_removed option is only set if you click on ‘let us know what we can do better’ (assuming you first clicked on ‘Not really’ to liking the plugin). If you on the other hand choose ‘No thanks’ to leaving a comment, only members_review_prompt_delay is set, and you never get rid of the notifications.

I’m not sure why you think that annoying your users is a winning marketing strategy, but after being nagged about this about 100 times, I have decided to remove this plugin from all of my sites, and find another plugin for managing my user roles.

• This reply was modified 4 years ago by reswild.

@jordonedavidson Setting 777 on your upload folder won’t help you in this case, as the WordPress Filesystem API will refuse to write to the folder unless it is owned by the same user as is executing the script. It will then try to use the FTP method for saving the file, which is what is causing the error. If you just want to get rid of the error message, you can always disable asset caching in Popup Maker > Settings > Misc.

The way the caching is implemented by this plugin isn’t ideal, as this will fail with some server configurations, and it will then continuously try and fail to save the file, which fills up the log with error messages. It ought to first check if the folder can be written to by using a request_filesystem_credentials call, and not continue if this fails.

Yeah, I’ll need to have another look at the initial setup. I think what is supposed to happen is that the plugin shouldn’t be active until you edit the settings page for the first time, but that doesn’t seem to be the case.

Thanks for reminding me about that.

To bypass login through CAS, just add “?wp” after the login link.
So “wp-admin?wp” or “wp-login.php?wp”.

If you just need CAS attributes, you could try my custom version of the plugin from https://github.com/reswild/cas-maestro.

Se also https://www.ads-software.com/support/topic/support-for-cas-attributes-certificate-validation-and-more

I think you can just change the “New User Default Role” under Settings > General, and CAS Maestro will use whatever role is set as default.

This ought to be made clear in the description on the module settings page, though.

You ought to be able to pick what video from the playlist to start with, though, by using the index option. This seems to be working as it should with the standalone playlist player, but not with the gallery view.

So listType=playlist&list=UUm2BPn6XXrYMegTkrvDEkuw&index=2 will start with the third video in the playlist, but listType=playlist&list=UUm2BPn6XXrYMegTkrvDEkuw&index=2&layout=gallery will start with the first.

The problem with just removing this line is that the password fields will then show up on the users’ profile page, which might be confusing if they are expected to log in with CAS.

A better approach might be to replace the line with something like

global $pagenow;
if ($pagenow == 'profile.php') {
  add_filter('show_password_fields', array(&$this, 'show_password_fields'), 999);
}

to still hide the password fields on the profile page.