houfton

The issue with permalinks was one of them. The other was to do with WP Rocket. It is a while ago now and I can’t remember exactly, but I have a note that there was a warning that it could not write to htaccess. This may be linked with having WordPress in a sub-directory. Sorry to be so vague.

Sorry, 4.1.8 is OK, not 4.1.7.

If you have FTP access you can disable the plugin (go to wp-content>plugins and change name of plugin directory to something like xxx-mailchimp-for-wp), check the site is back up, then download the latest version 4.1.7 which has just been updated I think. Unzip the plugin files if they are zipped and upload them all into xxx-mailchimp-for-wp. Change name back to mailchimp-for-wp. Worked for me!

I have tried adapting the script Customizr script and it seems to be working.

The trick I believe is to get it to hook into the link properly. Customizr uses a[rel*=tc-fancybox-group] but the value for rel on my pages is a random string for each gallery like rel=”01914ae0c5d688d0e4cb36be92a9cf44″ not rel=”tc-fancybox-group”.

add_action ('wp_footer' , 'set_fancybox_title');

function set_fancybox_title() {
	?>
		<script id="tc-fancybox-title" type="text/javascript">
			jQuery(document).ready(function ($) {
			        $('a[class*=ngg-fancybox]').each( function() { // edited here
			            var title = $(this).find('img').prop('title');
			            var alt = $(this).find('img').prop('alt');
			            if ( typeof title !== 'undefined' && 0 != title.length) {
			                $(this).attr('title',title);
			            }
			            else if (typeof alt !== 'undefined' &&  0 != alt.length) {
			                $(this).attr('title',alt);
			            }
			        });
			});
		</script>
	<?php
}

Seems to work. Now to try to get the left right buttons to work!

• This reply was modified 7 years, 9 months ago by houfton. Reason: code tags wrong

After looking for a long time I found a solution here. The trick is to override the default inline width given to the fancybox-outer div (which is 20px wider than the image to accommodate a 10px border) using display: table-cell. With the border set to 0px there is now no 20px on the right.

#fancybox-outer {
	display: table-cell;
}
#fancybox-outer #fancybox-content {
	border: 0px;
}

I have tested it a bit and it seems to be working!

This is with the built-in Fancybox Lightbox Effect in NextGEN Gallery 2.1.62.

• This reply was modified 7 years, 10 months ago by houfton. Reason: code block display
• This reply was modified 7 years, 10 months ago by houfton. Reason: small code simplification

I found that the images had to be in my parent theme. The nextendpath parameter showed both parent and child paths but only the parent path worked.

Changing line 21 fixed it (using the latest WordPress plugin download).

[There also seemed to be a problem with using the colorise option with jpgs rather than pngs.]

I have got the same issue I think. The tooltip shows “post_snippets.desc” which is not a disaster but not very descriptive. I am using Version 2.3.5 on WordPress 4.2.2. I am not using any language translation.

The problem seems to be the title in editor_plugin.js:

// Register example button
			ed.addButton('post_snippets', {
				title : 'post_snippets.desc',
				cmd : 'mce_post_snippets',
				image : url + '/post-snippets.gif'
			});

Same here for me. I have emailed you.

That does it, thanks. I should have tried that…

(Don’t forget to amend the snippet in the text on your “Where shall they be displayed?…Place them manually” section.)

I feel a donation coming on…

The shortcode is working on this page.

I do have another widget showing social icons at the moment in the footer in case you are confused! I want the – page specific – icons to appear at the bottom of the content as with my second link.

I have it working on 4.1.1. Tried it with a couple of widgets, including Meta, on a page.

Do what Jose says but, if you want to use phpMyAdmin, you can use the “SQL” tab and enter a query like this:

SELECT * FROM wp_options WHERE option_name LIKE '%mfbfw%'

NOTE: the prefix for your table might be something other than “wp_”.

It is a simple select command so will not do any harm and, when I do it, it returns two lines (option_names: “mfbfw” and “mfbfw_active_version”).

You can also use the ‘Search’ tab and search the whole database or, better, just the wp_options table, for “mfbfw” but you need to make sure it is a wildcard type of search (i.e. LIKE ‘%mfbfw%’).

I think the problem might be that the database seems to retain the old version value (e.g. 3.0.2) and Google (Webmaster Tools in fact I think) reads that?

Check wp_options, option_name: mfbfw_active_version. Make sure that value matches the actual version.

I had this problem and I believe it was the malware script which had been inserted into the database (wp_options, option_name: mfbfw) was causing a javascript error that prevented the Fancybox for WordPress settings page from loading properly. (If I remember rightly the string for the padding setting is a maximum of 7 characters but the script that had been put in there was 144 characters and the console error was all about that.)

Deleting that line before upgrading might be one way to fix that. A complete uninstall of the plugin and reinstall would probably also do it but you would lose any settings you had.

The other option, mfbfw_active_version, needs to be changed as well for a different reason as far as I can tell. It seems to retain the old version value (e.g. 3.0.2) which causes Google Webmaster Tools (if you are using it) to send warning emails saying “As of the last crawl of your website, you appear to be running FancyBox for WordPress 3.0.2 or below”. See the other support thread.

I think Pippin might be fixing this so it does not require a code hack, but in the meantime this works for me:

either change the number in the php file (simple-google-map-short-code.php line 55 maybe) where it says “zoom: 15,”;

or, for more flexibility, change that line to
zoom: <?php echo $atts['zoom']; ?>,
and use zoom=”5″ (or whatever number) in the shortcode itself.