Forum Replies Created

Viewing 15 replies - 106 through 120 (of 201 total)
  • Plugin Author steveush

    (@steveush)

    Hi @dantianhealth,

    Thanks for the URL update. I think I have found the issue in the method that determines the parent scrollable container that FooGallery binds its lazy loading to. Basically at the moment due to a combination of how this method determines the element and your themes CSS FooGallery is binding lazy loading to your <body/> instead of the <html/> so it never triggers the additional loading of images on scroll.

    I’ll create a fix for the issue I am seeing and will get back to you once I’ve had a chance to test it a bit more.

    Also unfortunately this issue will affect lazy loading across all templates as its code is shared between them.

    For now I would temporarily disable lazy loading until the fix is available to ensure all images are loaded on your site.

    Thanks

    Plugin Author steveush

    (@steveush)

    Hi @marilyn1998,

    Could you please clear your cache and test again as the JavaScript being served from it for FooGallery is not the latest version.

    @dantianhealth without a URL there is not much I can do except say try clearing your cache as well.

    Thanks

    Plugin Author steveush

    (@steveush)

    Hi @wincam,

    Unfortunately this is not something we expose through the FooGallery settings as by default WordPress does not expose it. The functionality exists purely in the JavaScript for users who want to customize how images are grouped by manually adding the rel attribute value to thumbnails within their page.

    In this case I believe another plugin or theme is parsing the page content and adding the value as the page ID is 167 and all thumbnails are decorated with lightbox[167]. I would suggest finding the plugin or theme setting performing this action and to either disable or modify it through those settings.

    Thanks

    Plugin Author steveush

    (@steveush)

    Hi @sofcarlson,

    @bradvin is indeed correct and this has to do with the widths however this is more an issue with the theme CSS than the gallery. This template has absolutely positioned items, so they effectively take up “no” space in the page layout so the template relies on the parent elements available width. With how the themes CSS is currently setup with the content set to float left this effectively collapses the content area to be the smallest possible.

    You need to add the following CSS to either the Custom CSS meta box in the gallery settings or add it to you sites styles.css file:

    @media screen and (max-width: 1024px){
    	.content {
    		width: 100%;
    	}
    }

    This is effectively telling the theme that the content should be shown full width once the size goes below 1024px. Currently the theme does not do this and instead relies on the content of the page to push the container to the full size. Unfortunately as I stated previously this template relies on its parent width for layout purposes and the theme CSS basically doesn’t provide any.

    Thanks
    Steve

    Plugin Author steveush

    (@steveush)

    Hi @wincam,

    In each of the image viewers you have on the thumbs the attribute rel=”lightbox[167]”. This is what is causing the issue. As these galleries share the same rel value the lightbox is picking up on that and trying to combine all the images into a single lightbox.

    Please remove these rel attribute values and everything should work as expected.

    Thanks

    Plugin Author steveush

    (@steveush)

    Hi @andrewh7777,

    Ok, this may go on for a bit but applying the following changes should get FooBox looking pretty similar to your old site and get rid of the delays during resizing and changing images.

    1. First things first, I would suggest removing your current customization’s and start from what is basically a fresh install of FooBox. Backup your changes in case you’re not happy with the result of my code.

    2. Next let’s get rid of the delays during resizing and changing images. Unfortunately in the free version there is no easy way to supply custom JavaScript options to the lightbox. To work around this you can use the following PHP code in your functions.php file or by using a plugin that lets you register custom scripts.

    if ( ! function_exists( 'custom_foobox_script' ) ){
    
    	/**
    	 * Enqueues a custom script for FooBox allowing us to alter advanced options
    	 * not exposed in the options UI.
    	 */
    	function custom_foobox_script(){
    		// first check if FooBox should actually enqueue its' scripts
    		if (!apply_filters('foobox_enqueue_scripts', true)) return;
    
    		// here we set some hidden options allowing us to alter the transition and resize speeds
    		// allowing for near instant transitions between images.
    		$custom_js = 'if ( !!FOOBOX ){
    	FOOBOX.customOptions = {
    		resizeSpeed: 0,
    		transitionInSpeed: 0,
    		transitionOutSpeed: 0
    	};
    }';
    
    		// actually enqueue the script registering it to be inserted before the main FooBox script.
    		wp_add_inline_script(
    			'foobox-free-min',
    			$custom_js,
    			'before'
    		);
    	}
    
    	/**
    	 * Enqueue the custom scripts register function.
    	 */
    	add_action('wp_enqueue_scripts', 'custom_foobox_script', 99);
    
    }

    The above script simply registers an inline script block with FooBox that then sets three options not exposed in the settings UI: resizeSpeed, transitionInSpeed and transitionOutSpeed. Setting these three speed options to 0 effectively cancels the transitions used during there associated phases.

    3. Now that all the hidden options are taken care of let’s set some through the UI to let the custom CSS in step 4 work correctly.

    a. Enable the General > Show Counter option.
    b. Set the General > Count Message option to simply be a forward slash “/”. This will be used to separate the previous and next buttons.
    c. To match the old site you can also enable the General > Hide Captions option.

    4. Last, but certainly not least, is the custom CSS to style FooBox to mimic your old lightboxs’ style. Unfortunately there are a number of duplicate CSS class names as I only wanted these customization’s to affect the desktop and tablet layouts for FooBox as the mobile view is vastly different. I have commented every class so you can get an idea of what everything is doing so you can make adjustments in the future.

    /* Set the background color of the modal to be solid white */
    .fbx-modal.fbx-tablet,
    .fbx-modal.fbx-desktop {
    	background-color: #FFF;
    }
    /* Create the "title" seen in the top left of the modal */
    .fbx-modal.fbx-tablet:before,
    .fbx-modal.fbx-desktop:before {
    	display: inline-block;
    	content: "Andrew Kimber";
    	position: absolute;
    	top: 50px;
    	left: 50px;
    	font-family: "Times New Roman", serif;
    	font-size: 24px;
    	font-weight: 100;
    	text-transform: uppercase;
    	letter-spacing: 4px;
    }
    /* Adjust the internal spacing for the modal to account for the above "title" */
    .fbx-modal.fbx-tablet .fbx-inner-spacer,
    .fbx-modal.fbx-desktop .fbx-inner-spacer {
    	padding: 124px 40px 50px;
    }
    /* Adjust the loader to account for the above "title" */
    .fbx-modal.fbx-tablet .fbx-loader,
    .fbx-modal.fbx-desktop .fbx-loader {
    	margin-top: 0;
    }
    /* Strip the border and rounded corners off the various elements that no longer require it */
    .fbx-modal.fbx-tablet .fbx-inner,
    .fbx-modal.fbx-desktop .fbx-inner,
    .fbx-modal.fbx-tablet .fbx-item-current,
    .fbx-modal.fbx-desktop .fbx-item-current,
    .fbx-modal.fbx-tablet .fbx-item-next,
    .fbx-modal.fbx-desktop .fbx-item-next,
    .fbx-modal.fbx-tablet .fbx-item-next,
    .fbx-modal.fbx-desktop .fbx-item-image {
    	border: none;
    	border-radius: 0;
    }
    /* Strip the drop shadow off the various elements that no longer require it */
    .fbx-modal.fbx-tablet .fbx-loader,
    .fbx-modal.fbx-tablet .fbx-inner.fbx-inner-shadow,
    .fbx-modal.fbx-tablet .fbx-close.fbx-btn-shadow,
    .fbx-modal.fbx-tablet .fbx-close.fbx-btn-shadow:hover,
    .fbx-modal.fbx-tablet .fbx-prev.fbx-btn-shadow,
    .fbx-modal.fbx-tablet .fbx-prev.fbx-btn-shadow:hover,
    .fbx-modal.fbx-tablet .fbx-next.fbx-btn-shadow,
    .fbx-modal.fbx-tablet .fbx-next.fbx-btn-shadow:hover,
    .fbx-modal.fbx-desktop .fbx-loader,
    .fbx-modal.fbx-desktop .fbx-inner.fbx-inner-shadow,
    .fbx-modal.fbx-desktop .fbx-close.fbx-btn-shadow,
    .fbx-modal.fbx-desktop .fbx-close.fbx-btn-shadow:hover,
    .fbx-modal.fbx-desktop .fbx-prev.fbx-btn-shadow,
    .fbx-modal.fbx-desktop .fbx-prev.fbx-btn-shadow:hover,
    .fbx-modal.fbx-desktop .fbx-next.fbx-btn-shadow,
    .fbx-modal.fbx-desktop .fbx-next.fbx-btn-shadow:hover {
    	box-shadow: none;
    }
    /* Set some base styles and reset some others used by the various UI elements */
    .fbx-modal.fbx-tablet .fbx-close,
    .fbx-modal.fbx-tablet .fbx-prev,
    .fbx-modal.fbx-tablet .fbx-next,
    .fbx-modal.fbx-tablet .fbx-count,
    .fbx-modal.fbx-desktop .fbx-close,
    .fbx-modal.fbx-desktop .fbx-prev,
    .fbx-modal.fbx-desktop .fbx-next,
    .fbx-modal.fbx-desktop .fbx-count {
    	font-family: "Segoe UI", "Helvetica", "Arial", "Sans Serif", serif;
    	font-size: 12px;
    	font-weight: 100;
    	font-style: normal;
    	line-height: 1.5em;
    	letter-spacing: .04em;
    	margin-top: 0;
    	top: auto;
    	right: auto;
    	left: auto;
    	bottom: auto;
    	width: auto;
    	height: auto;
    	border: none;
    	padding: 5px;
    }
    /* Position the close button in the top right of the modal and adjust its' size */
    .fbx-modal.fbx-tablet .fbx-close,
    .fbx-modal.fbx-desktop .fbx-close {
    	position: fixed;
    	top: 0;
    	right: 0;
    	font-size: 24px;
    	min-width: 24px;
    	line-height: 24px;
    }
    /* Specify the close button to use the &times; HTML entity. */
    .fbx-modal.fbx-tablet .fbx-close:before,
    .fbx-modal.fbx-desktop .fbx-close:before {
    	content: "×";
    }
    /* Center the "count" which is now just displaying "/" */
    .fbx-modal.fbx-tablet .fbx-count,
    .fbx-modal.fbx-desktop .fbx-count {
    	position: absolute;
    	bottom: -25px;
    	left: 50%;
    	transform: translateX(-50%) translateY(50%);
    	padding: 5px 0;
    	width: 10px;
    }
    /* Position the prev and next buttons below the image */
    .fbx-modal.fbx-tablet .fbx-prev,
    .fbx-modal.fbx-tablet .fbx-next,
    .fbx-modal.fbx-desktop .fbx-prev,
    .fbx-modal.fbx-desktop .fbx-next {
    	position: absolute;
    	bottom: -25px;
    	transform: translateY(50%);
    }
    /* Adjust the prev button to be positioned to the left of the "count" */
    .fbx-modal.fbx-tablet .fbx-prev,
    .fbx-modal.fbx-desktop .fbx-prev {
    	left: calc(50% - 5px);
    	transform: translateX(-100%) translateY(50%);
    }
    /* Set the prev button text */
    .fbx-modal.fbx-tablet .fbx-prev:before,
    .fbx-modal.fbx-desktop .fbx-prev:before {
    	content: "prev";
    }
    /* Adjust the next button to be positioned to the right of the "count" */
    .fbx-modal.fbx-tablet .fbx-next,
    .fbx-modal.fbx-desktop .fbx-next {
    	left: calc(50% + 5px);
    }
    /* Set the next button text */
    .fbx-modal.fbx-tablet .fbx-next:before,
    .fbx-modal.fbx-desktop .fbx-next:before {
    	content: "next";
    }

    That should be it.

    Thanks
    Steve

    • This reply was modified 7 years, 1 month ago by steveush. Reason: Fixed list number
    Plugin Author steveush

    (@steveush)

    Hi @andrewh7777,

    I’ll be looking into this today, I was unavailable over the weekend and should be able to give you an update a bit later on today.

    Thanks
    Steve

    Plugin Author steveush

    (@steveush)

    Hi @trek-themes,

    Thanks for giving us a live example. I’ve found the issue and the fix should be in the next release.

    Thanks
    Steve

    Plugin Author steveush

    (@steveush)

    Hi @mrprainx,

    I’ve just tested now and the swipe is working on my test devices. As Brad said the latest update should have resolved the issue. With that being said as you have been testing recently and only just updated the plugin I think your S9 device may have the old version of the JS cached. Mobile devices have very aggressive caching strategies which I think this time is causing some confusion.

    Please try clear the browser cache for the page on your S9 device and retest as I believe the latest version should have resolved the issue. If you need help doing this take a look at the following page:

    https://www.samsung.com/uk/support/mobile-devices/how-do-i-clear-the-cache-history-or-cookies-on-the-internet-browser-on-galaxy-device/

    Note: In the above post for the Samsung Internet Browser you only want to delete the Cache option. For Chrome you only want to delete the option called Cached images and files.

    Thanks
    Steve

    Plugin Author steveush

    (@steveush)

    Hi @vikasgunjeti,

    A reworked and updated fix has been applied to our code base which definitely resolves the issue however it has not yet been released in the free version. I’ll follow up with our PHP developer to see when the next free release is scheduled to go out however there is no quick fix I could supply to you now. You will need to wait until the new free version is released to resolve the issue as the changes required altering certain parts of the portfolio template which can not be supplied as a temp fix.

    Thanks
    Steve

    Plugin Author steveush

    (@steveush)

    Hi @vikasgunjeti,

    A reworked and updated fix has been applied to our code base which definitely resolves the issue however it has not yet been released in the free version. I’ll follow up with our PHP developer to see when the next free release is scheduled to go out however there is no quick fix I could supply to you now. You will need to wait until the new free version is released to resolve the issue as the changes required altering certain parts of the portfolio template which can not be supplied as a temp fix.

    Thanks
    Steve

    Plugin Author steveush

    (@steveush)

    Hi @swan1305,

    You should be able to use the following to adjust the caption title size and color:

    .foogallery .fg-caption-title {
    	font-size: 16px;
    	color: #FFF;
    }

    If however you are using one of the preset options for captions you may need to use the following depending on which should allow you to adjust the preset sizes:

    .foogallery.fg-preset .fg-caption-title {
    	font-size: 16px;
    	color: #FFF;
    }

    Thanks
    Steve

    Plugin Author steveush

    (@steveush)

    Hi @wpz118,

    I’ve just had a look at your site and you’re not using FooBox on that page at all. If you’re needing help with the lightbox used with the feature image I believe that might be part of your theme?

    Thanks
    Steve

    Plugin Author steveush

    (@steveush)

    Hi Klaus,

    Glad to hear it resolved the issue for you. Please note though that if you update your theme you will need to apply this fix again as that JS file will be replaced.

    I’ll mark this as resolved.

    Cheers
    Steve

    Plugin Author steveush

    (@steveush)

    Hi @klauswaushb,

    The issue here is your theme is wrapping all <figure/> elements in your page in a <p/> tag as a work around for featured overlay thumbnails in posts. This can be seen in your themes JS file found at ~/wp-content/themes/photo-diary/js/jquery-photo_diary_theme_functions.js on line 47. Basically it is executing the following code:

    $('.entry-content figure').not('.gallery-item').wrap('<p></p>');

    While this works for the built-in WordPress gallery it is interfering with FooGallery as our items figures are decorated with the class fg-item-inner and not gallery-item.

    As for why this has only started occurring in the 1.7.x updates it is due to performance changes made in those updates. Previously when FooGallery parsed an item it didn’t care about the item’s exact DOM structure, as long as the required elements existed somewhere within the item. While this worked great the method used to perform the element lookup was quite taxing. To increase the speed of parsing it was changed so that our JS uses alternative methods that directly query each element as we know the exact structure as we output it to the page. The additional <p/> tag being inserted by your theme into each of our items is breaking the parsing as it is changing the structure of the item.

    At present the only options available to fix this would be rolling back to a 1.6.x version of FooGallery before we released the performance changes or get your theme fixed so that it doesn’t simply wrap every <figure/> with a <p/> tag. I’ll discuss our changes with @bradvin however as this issue lies with your theme and our changes improve the performance of FooGallery I don’t think we will roll back our changes.

    At it’s simplest you could change the previously mentioned line 47 in your theme JS to the following:

    $('.entry-content figure').not('.gallery-item,.fg-item-inner').wrap('<p></p>');

    However this would only fix the issue with FooGallery and not any other gallery/media plugins that output a <figure/> element. Ideally your theme should be updated/fixed so that it’s work around for featured overlay thumbnails does not interfere with anything else in the page and only wrap the actual featured thumbnail.

    Thanks
    Steve

Viewing 15 replies - 106 through 120 (of 201 total)