quicksilver03

I’ve seen this today as well, this is unacceptable but at least the information is logged so anyone who watches the logs can decide what to do.

The information includes a public key, the PHP and WordPress versions, the web server, the MySQL version, the OpenSSL version, the curl version, the admin email, and all the other installed plugins.

For what is worth, I have uninstalled this plugin and I will not install any further plugin from WPBrigade.

@postmastergs @benjaminowens

Thanks for you replies, I appreciate your help but I have to say that I haven’t yet tried your suggestions, because in the meantime I’ve been testing a migration to a different gallery solution and it has worked well enough that the people in charge of producing content want to try it on the live site.

I’ve been able to port our custom template in a couple of hours of work, and I have to say that the documentation was clear. Whether or not this project will continue using NextGen Gallery depends on what those people prefer to use in the end.

Thanks @postmastergs, I’m trying to follow a similar process for albums but it just doesn’t work for me, the custom template file in the wp-content/ngg directory structure doesn’t show up at all in the NextGen Gallery settings for albums (compact or extended).

Unfortunately with no documentation and no actual working examples I’m stuck, at the moment the best option seems to use whatever time is left before the removal of the legacy templates functionality to migrate to a different gallery plugin.

I too would like to know the answer, I tried following the documentation https://www.imagely.com/docs/legacy-templates-deprecation but my own template did not seem to get called.

Do I have to specify a particular template in the shortcode? And if for example my shortcode is

[album id="1" template="custom"]

what file should I create, and where exactly in the path? Is

wp-content/ngg/modules/photocrati-nextgen_basic_album/templates/custom-view.php

or something else?

Thanks for that, and for your quick reply (on a Sunday no less!).

I have removed my edit to wp-config.php and tried the modification you suggested: it has worked well for me, wp-cli now shows the expected output and exits successfully while Ninja Firewall is active.

This modification seems quite safe to me, do you plan to include it in an update to Ninja Firewall?

I’m on wp-cli 1.5.1 as well:

[www@bravo htdocs] $ wp --version
WP-CLI 1.5.1

Adding the –user switch didn’t change anything, and I couldn’t find any error message in the php log, nor in syslog nor in the system journal.

The only way I could make wp-cli work without deactivating Ninja Firewall was changing the wp-config.php file in the following way:

if (!defined("WP_CLI")) {
  // BEGIN NinjaFirewall
  if (file_exists(dirname(__FILE__) . '/wp-content/plugins/ninjafirewall/lib/firewall.php') && ! defined("NFW_STATUS")) {
     @include_once(dirname(__FILE__) . '/wp-content/plugins/ninjafirewall/lib/firewall.php');
     define("NFW_WPWAF", 1);
  }
  // END NinjaFirewall
}

I got the idea from 2 wp-cli issues on GitHub, https://github.com/wp-cli/wp-cli/issues/2476 and https://github.com/wp-cli/wp-cli/issues/1881. It’s not ideal and probably it comes with a slight performance degradation, but at least I can keep both Ninja Firewall and wp-cli.

• This reply was modified 6 years, 5 months ago by quicksilver03.

Hello,

Thanks for your quick reply, I’ve tested the new version and it works well for me, the directory contents are deleted and the directory itself stays in place.

This is a problem for me: I use wp-cli and git to control the updating of plugins and themes, a plugin writing to wp-content/plugins breaks this process.

I think that placing those css files in something like wp-content/uploads/sassy-social-share/admin/css is a better option which follows the principle of least surprise, and which shouldn’t impact the working of your plugin.

Kyle,

As a user of your plugin, and one of the $10 donors, I fully support your decision and I’m looking forward to purchase the paid version.

I imagine that you’re probably targeting semi-professional bloggers and small companies, I just hope that there will be a pricing tier for hobbyist users like me.