Forum Replies Created

Viewing 15 replies - 61 through 75 (of 201 total)
  • Plugin Author steveush

    (@steveush)

    Hi @kooba,

    Could you please let me know what you currently have selected for the Justified Gallery > General > Last Row option?

    Thanks
    Steve

    Plugin Author steveush

    (@steveush)

    Hi @tinalewis,

    This is a by product of the captions allowing clickable content within them as well as them being displayed over the original anchors in the page. The right click option to “Open link in new tab” is only available on anchor elements within a page and when you are right clicking with a caption visible you are not clicking the actual anchor but an overlay on top of it.

    That said if you do not intend to have clickable content within captions there is some CSS you can apply that will effectively make the captions invisible to the mouse or touches allowing the right click behavior of the anchor and show the expected context menu.

    .foogallery .fg-caption,
    .foogallery .fg-image-overlay {
    	pointer-events: none;
    	touch-action: none;
    }

    This can be inserted into your sites styles.css file to apply it globally.

    Thanks
    Steve

    Plugin Author steveush

    (@steveush)

    Hi @smit_ralph,

    @bradvin is correct that the issue here is being caused by the way Owl Carousel is cloning the DOM but it is only occurring due to FooBox initializing itself before Owl has performed its manipulations. Simply calling FOOBOX.init() again fixes the issue as FooBox can then inspect the altered DOM and bind itself appropriately.

    To fix this I would make two changes, the first one is simple as you have done it on your test site https://mghia.nl/vin/. Simply add the foobox class to the owl-carousel element in the DOM. This lets FooBox see that DIV as a container for items and creates a single modal containing multiple items rather than multiple modals with a single item in each as is currently happening on your https://crystallize.nl/ site.

    The second change requires some custom JS however this should also be fairly straight forward as I see you have created a child theme to house your modifications, onelight-child. Inside this child theme you have an includes/extras.js file. At the top of this file you initialize Owl Carousel and also have a callback for the onInitialized event on line 26. This is the same place where you created the custom JS to add the foobox CSS class to the owl-stage, which is not required. In this callback we should just need to add the code FOOBOX.init() so that your callback looks like the following:

    onInitialized: function(e) {
    	if (carItems >= e.item.count) {
    		car.trigger('stop.owl.autoplay');
    	} else {}
    	FOOBOX.init();
    }

    Once that’s done I’m hoping everything should be working as expected.

    Thanks
    Steve

    Plugin Author steveush

    (@steveush)

    Hi @pairfumlondon,

    These warnings are being generated as WordPress has upgraded the built-in version of jQuery from the old 1.12.4 to the newest 3+. These are simply deprecation warnings for us developers to give us a heads up to change our code before a function we are currently using is removed.

    We have already released one update to resolve quite a number of these warnings and will continue to work to remove the rest of them from our various plugins with the next updates.

    So to answer your question, no you should not be worried about this, we are actively working to resolve these warnings.

    Thanks

    Plugin Author steveush

    (@steveush)

    Hi,

    Please see the comments in this thread, I believe this is related. There is an issue with autoptimize at the moment.

    Thanks
    Steve

    Plugin Author steveush

    (@steveush)

    Hi @extinctdisney,

    Which page are you expecting to see a gallery on? Apologies I could not find one on the home url of your site.

    Thanks
    Steve

    Plugin Author steveush

    (@steveush)

    Hi,

    Something seems to be a miss here with the enqueueing of the scripts. FooGallery has a dependency on jQuery however it is currently being included in the page before jQuery is. jQuery itself is being combined into a single autoptimize script that is inserted in the very bottom of the body after the FooGallery script.

    FooGallery itself should have been combined into that autoptimize script, I’m not sure why it has not been. Can you try clearing the cache and rebuilding the cached files to see if autoptimize correctly picks up and combines FooGallery after that?

    Thanks
    Steve

    Plugin Author steveush

    (@steveush)

    Hi,

    I had to do some testing with this to see why there was a cookie being reported.

    We don’t actually make use of any localStorage or cookies in the standard workings of FooGallery. I have double checked and the only place in our code that relates to either is part of a debug utility which makes use of localStorage but it has to be manually run from the console.

    Part of this utility checks as the script is parsed if the window.localStorage object exists. It does not read from or to the localStorage, simply checks if it exists. This is what Chrome is reporting as a cookie even though there is none. Essentially I think Chrome is reporting a false positive here.

    That said I’ll be making some code changes to make sure the debug utility never touches the window.localStorage object until its needed.

    Thanks

    Plugin Author steveush

    (@steveush)

    Hi @rizn,

    This actually seems like a rendering issue, the image as well as the item containing it are the same height yet the items background color is bleeding through on the edges for some images.

    It’s not a subpixel display issue as I created a gallery locally with fixed whole numbers for the item sizes and the white background still bled through for some images.

    The below CSS should fix the problem by simply removing the background color from the items giving it nothing to actually bleed through.

    .foogallery.fg-justified.fg-light .fg-item-inner {
    	background-color: transparent;
    }

    Include the above in the page by using the Custom CSS option in FooGallery or by adding it to your styles.css file for your site.

    Thanks
    Steve

    Plugin Author steveush

    (@steveush)

    Hi @extrapaul,

    That would be great as I suspect there might be other CSS on your site that is affecting the bar. I’ve tested locally on IE11 on 3 different machines and all of them display the text correctly.

    Unfortunately without being able to inspect the DOM and check the rules myself it will be quite difficult to resolve your issue.

    Please let us know when there is a url we could take a look at.

    Thanks
    ~Steve

    Plugin Author steveush

    (@steveush)

    Hi @benzinozor & @bradvin,

    No the title is not stripped by the JS, however there are various hover options such as the icon or caption that may place an overlay on top of the image. If any of the overlays are present the image title attribute will not be visible when hovering an item as your mouse cursor is in fact hovering over the overlay and not the image itself.

    Thanks

    Plugin Author steveush

    (@steveush)

    Hi @marrie80,

    Apologies, I seem to have missed Brad’s initial mention on your ticket. Unfortunately the built-in hover icons can not be styled with CSS as they are simply background images.

    The only way to change the icons would be to create your own image and then add some custom CSS to replace the original icon with your custom one.

    To replace the built-in Zoom icon you could use the below CSS:

    /* This is used for the default overlays: Light Foreground/Dark Background */
    .foogallery.fg-hover-zoom .fg-image-overlay:before,
    .foogallery.fg-hover-zoom .fg-caption-inner:before {
    	background-image: url('URL-TO-LIGHT-ICON') !important;
    }
    
    /* This is used for the light overlays: Dark Foreground/Light Background */
    .foogallery.fg-light-overlays.fg-hover-zoom .fg-image-overlay:before,
    .foogallery.fg-light-overlays.fg-hover-zoom .fg-caption-inner:before {
    	background-image: url('URL-TO-DARK-ICON') !important;
    }

    Then in the settings for the gallery you would select the Hover Effects > Icon > Zoom option to enable the custom icon.

    Thanks
    Steve

    Plugin Author steveush

    (@steveush)

    Hi @vizzitor,

    We’re looking to put out a performance improvement update within the next month or so to tackle some issues like this CLS one.

    That being said some templates simply due to how they work will naturally incur a high CLS score. As you pointed out the Justified and Masonry galleries would be two such templates as they manually position every item within them with JavaScript to achieve the desired look.

    Part of the CLS score is determined by the layout shift, or the height change between frames, and this is where these templates would incur the largest penalty as the items are positioned for the first time on page load. Also some templates like Masonry use 3rd party libraries under the hood which we have no control over other than logging a ticket ourselves.

    We will endeavor to provide the best performing templates we can but in the end it would be up to the end-user like yourself to determine a cost/performance ratio you’re happy with and this could change depending on whatever metric is next introduced.

    Thanks
    Steve

    Plugin Author steveush

    (@steveush)

    Hi @irina1975,

    Ok, so there’s a bit of confusion going on here. Firstly that is not the CSS I provided from the previous ticket. That is the original CSS provided by our first line support @influxfooplugins which is what is causing the last item to be displayed at full width. As they said in their response:

    The code above enables the gallery items to fill the width on both mobile and desktop to fill the voids.

    You replied after that stating you instead wanted two columns on mobile instead of one, so I was asked to provide you with that CSS. I expected you to remove the CSS provided by @influxfooplugins and replace it with the CSS I provided, the CSS I provided is currently not included in the page at all.

    Steps to fix:

    Just to be clear I’ll refer to the below CSS provided by @influxfooplugins as old CSS;

    /* fill foogallery maximum width */
    .fg-simple_portfolio .fg-item {
    	max-width: 100% !important;
    }

    1. Remove the old CSS from your style.css file.
    2. Remove the old CSS from the gallerys Custom CSS option.
    3. Now do you want the two column mobile layout to apply to all portfolio galleries?

    If your answer to #3 is Yes then add the below CSS to the bottom of your style.css file and you should be done.

    @media only screen and (max-width: 480px){
    	.foogallery.fg-simple_portfolio .fg-item {
    		margin: 5px !important;
    		width: calc(50% - 10px) !important;
    		min-width: calc(50% - 10px) !important;
    		max-width: calc(50% - 10px) !important;
    	}
    }

    If your answer to #3 is No and you only want the two column layout to be applied to a specific portfolio gallery then add the below CSS to the gallerys Custom CSS option and change the gallery ID to the current gallery. In the below CSS I used your gallery ID of foogallery-gallery-839 from the screenshot. You can see the current gallery ID within the Custom CSS option displayed above the text area.

    @media only screen and (max-width: 480px){
    	#foogallery-gallery-839.fg-simple_portfolio .fg-item {
    		margin: 5px !important;
    		width: calc(50% - 10px) !important;
    		min-width: calc(50% - 10px) !important;
    		max-width: calc(50% - 10px) !important;
    	}
    }

    Once you have done these steps and cleared any cache your issues should hopefully be resolved.

    Thanks

    Plugin Author steveush

    (@steveush)

    Hi @irina1975,

    The old CSS you quoted above is still present in your page. I’m not sure where it was added to on your end but it is appearing in your page at line 287. This old CSS needs to be removed and then everything will work correctly.

    Thanks

Viewing 15 replies - 61 through 75 (of 201 total)