.gabriel.

I had the same issue updating from 2.9.0 to 2.9.1 via wp-cli. I uninstalled the plugin and a fresh install of 2.9.1 didn’t throw any errors initially. However any subsequent wp-cli commands (update core, update theme, etc) immediately threw out the same errors referencing simple-lightbox. Same for 2.9.0 or 2.9.1. I downgraded to 2.8.1 and manually changed the version higher than 2.9.1 as a workaround for now.

I was wondering that too. Their GitHub repository shows:

= 3.1.0 =
Add escaping to output
Remove the svgxuse.js script

There is a recent support topic started by alex4e that references a potential issue with svgxuse.js, so I assume that’s why it was removed.

• This reply was modified 2 years, 11 months ago by .gabriel..

Open your WordPress admin dashboard and click Plugins > Add New.

Click “Upload Plugin” and either drag-and-drop the classic-widgets.0.2.zip file you downloaded, or click “Browse…” to locate it.

Click “Install Now”, and then click “Activate”. Once the plugin is active, the widget block editor will be disabled.

Open your WordPress admin dashboard and click Plugins > Add New.

Type “Classic Widgets” in the “Search plugins…” box and the first result should be this plugin by WordPress Contributors. Or, if you downloaded the plugin zip file, you can click “Upload Plugin” and either drag-and-drop the zip file you downloaded, or click “Browse…” to locate it.

Click “Install Now”, and then click “Activate”. Once the plugin is active, the widget block editor should be disabled.

I noticed the same Server time: NaN-NaN-NaN NaN:NaN:NaN issue. Deleted the plugin, installed 0.8.2.2, and that fixed it. Thanks

Check the plugin settings, which are found under Plugins > Conditional CAPTCHA. The default behavior for “When a CAPTCHA is not completed correctly” is “Leave the comment in the spam queue”, so you may not notice a difference since the comments end up in the same place. Try changing to “Trash the comment”, and you should see most comments end up in Trash instead of the Spam folder. Once you’re satisfied it’s working, you might want to change it to “Delete the comment permanently”.

I also recommend using reCAPTCHA; it requires a signup to get a key set, but it’s free.

On one of my sites over the past 1.5 years:

279,248 spam comments have been blocked by Conditional CAPTCHA

Love this plugin! ??

In addition to changing from “bold” to “normal” on line 7 of /plugins/yet-another-related-posts-plugin/style/related.css, make the change on line 12 too. That worked for me.

That worked, thanks!

I’ve run both options once so far and had no issues, having removed 80 transient options and over 6,000 orphaned postmeta. The amount of orphaned postmeta was about what I expected for the site and after the removal everything checked out OK.

That being said, you should always backup your WordPress database before trying new or updated plugins; if there is a problem, you can restore the backup.

We’ve been using Genesis framework for a little over a year (2.0.1 currently, with WP 3.7.1) and have had no issues with this plugin.

To create custom templates for Nextgen-Galleryview:

1) Create a sub-folder named “nggallery” in the folder of your WordPress theme, i.e. /wp-content/themes/twentytwelve/nggallery/

2) Copy the file /wp-content/plugins/nextgen-galleryview2/view/gallery-galleryview.php to the folder you created in Step 1.

3) If you want to make any changes to the default behavior of Galleryview, edit the copy of gallery-galleryview.php in your theme’s /nggallery/ folder instead of the one in the plugin’s /view/ folder; that way your changes aren’t lost when upgrading the plugin.

4) Make additional copies of gallery-galleryview.php in your theme’s /nggallery/ folder, renaming them with unique identifiers before the .php extension, i.e. gallery-galleryview-template2.php

5) Edit gallery-galleryview-template2.php. There are 30 different options for controlling the look and behavior of Galleryview.

6) When inserting the Nextgen shortcode, use the new Galleryview template name. I.e. instead of [nggallery id=1 template=”galleryview”], you would use [nggallery id=1 template=”galleryview-template2″]

After posting this, I see from another thread you have this figured out now, but maybe this will be useful to someone.

We upgraded the plugin to 1.3.0 and it stopped working in Firefox 21.0 with flash 11.7.700.202, on Windows 7 Home Premium. I tried disabling the other Firefox plugins and extensions, but that didn’t help.

1.3.0 also stopped working in Firefox 20.0.1 and IE 8, but worked fine with IE 10 and latest version of Chrome.

We downgraded the plugin to 1.2.9 and it’s working great again in all browser versions we tested.

To change order of images, edit a gallery and click the “Sort gallery” button; look for it above the list of images, between the “Apply” and “Save Changes” buttons.

The “Sort gallery” button will open a new page where you can choose to sort by “Unsorted | Image ID | Filename | Alt/Title text | Date/Time | Ascending | Descending”, or you can drag images around for a custom sort order.

Here is our solution for showing # photos, or # galleries for sub-albums.

If gallery or sub-album is empty, it shows 0 photos or 0 galleries. If the count is singular, it shows 1 photo or 1 gallery.

Change the following code in album-compact.php (or album-extend.php). To avoid having your changes overwritten when upgrading Nextgen, copy /wp-content/plugins/nextgen-gallery/view/album-compact.php to a sub-folder /nggallery/ under your theme (i.e. /wp-content/themes/twentyeleven/nggallery/album-compact.php) and edit the copy.

Old code:

<?php if ($gallery->counter > 0) : ?>
<p><strong><?php echo $gallery->counter ?></strong> <?php _e('Photos', 'nggallery') ?></p>
<?php endif; ?>

New code:

<p><strong><?php echo $gallery->counter ?></strong> <?php if ( $gallery->gid ) {
	if ( $gallery->counter == 1 ) {
		_e('Photo', 'nggallery');
	} else {
		_e('Photos', 'nggallery');
	}
} else {
	if ( $gallery->counter == 1 ) {
		_e('Gallery', 'nggallery');
	} else {
		_e('Galleries', 'nggallery');
	}
} ?></p>

Using Nextgen version 1.9.12 and WordPress 3.5.1

Same issue in the latest release of Nextgen, 1.9.12. Thanks for posting your workaround.