sarahsas

Is this a joke? I am asking YOU why it’s not loading – IT’s YOUR PLUGIN!!! I have already troubleshooted the issue FOR YOU by adding the test button on that page and SHOWING YOU that the only time the data loads properly is when it’s in the main body content, and it will NOT load properly when it’s ONLY in the HEADER or FOOTER! It’s YOUR JOB to fix it, NOT MINE!!!

I am astounded that I have to say this again…this is the worst support I have ever encountered… I feel like I’m beating my head against a wall…

My “hack” solution is going to be to add a hidden div in the main content on every page and assign the div class to it, so that it forces the data to load in the header and footer, but this is NOT a proper solution, and since it’s YOUR plugin, I assumed you would want to investigate and fix it properly?

Have you even bothered to test your plugin as I suggested in any other wordpress installation you have to see if it loads properly when ONLY in the header and footer in any other site??? That would be my starting point if I were you. But I guess you’re not interested in actually fixing the issue…

Thanks, but I think because all the elements are “fixed” position, and the positions seem to be auto-generated on load based on the image size so that it’s responsive, I don’t think changing the container size would work… I thought about changing the positions to relative and trying to work out the layout from there, but I suspect that’s going to REALLY mess with the overall functionality…

Example here: https://new.designwell.com.au/projects/

Notice when you click on any of the images in the gallery, once you are in the lightbox, the X to close out of the lightbox is always in the far upper right corner? absolute position 30px from top and right…

Client wants the X to be at the top right corner of the actual IMAGE, not top right corner of the actual screen window… make sense?

For this to happen I think there would need to be an extra container div around the X element and the IMG together… but I want clarification from the makers of the plugin to see if they know another way…

@sygnoossupport hello, anyone home?? This is a big issue, as it is TOTALLY blocking the whole functionality of your plugin, can you please provide any update?

Hi @pickplugins just wondering on the status of this? I saw you issued an update, but it doesn’t seem to have fixed this issue for me? I still can’t access the GRID SETTINGS menu while FILTERABLE is toggled on…

Also, after the most recent update, I can now see a very ugly “Post Grid lazy load” text appearing before all the grids load – this is happening on ALL of my sites that I have run the most recent update on, but here is one example – https://sarahshahinian.com/news/

See screenshot: https://imgur.com/ikRHQVQ

Please advise?

This was a much-discussed issue last week, but it looks like NextGen just issued a plugin update and this issue seems to be fixed on all of my galleries now – update the plugin and see if it’s still happening for you now?

FYI all, it seems with the latest update, this issue has now been resolved ?? yay!

@sygnoossupport any update on this please?

Yep I’ve just discovered the same thing… also this new “pagination” after the most recent update is also showing up on ALL galleries even if they don’t have a second page, so EVERY album I have across hundreds of sites now just has a random grey box under it with the number 1 in it… VERY annoying… and there doesn’t seem to be a way to disable it, other than just hiding it will CSS?? which will takes AAAAGES to update across dozens of different websites? NextGen team, please help???

@sygnoossupport The settings for the pop up are already set to display EVERYWHERE, see screenshot: https://imgur.com/neXFy5Y

…which is what I need – the “login” button in the top menu will appear on All Pages as well as All Posts and All custom post types, so I don’t want to change it to only work on pages and not posts…

Nevertheless, I tested this option and there was no change anyway.

Also, I cannot use the shortcode method in this instance, because I’m attaching the pop-up action to a MENU ITEM, as explained before with this screenshot: https://imgur.com/ciXH29S, so there is nowhere to put the shortcode, I can only assign a class to the menu item.

Any other ideas? It seems like a triggering issue to me? As in – your plugin is only triggering the action associated with the class when it appears within the #content or .site-content section of the page. The class does NOT work properly when executed in either the #masthead or .site-header, nor in the #colophon or .site-footer – can you test this theory locally on your end and confirm or disprove it?

Thanks for your reply, yes I can see that additional bit of code is being added to the button on the test page, which is making it work properly, however I am not manually adding it. I am simply adding the class to the button in the block editor, and presumably your plugin is generating that extra bit of code because the class has been added??

So the issue seems to be that your plugin is NOT automatically generating the extra bit of code when the pop up class is added to an object in the header or footer. Here are some screenshots to illustrate my point in step by step fashion:

1. On the test page with the test button on it, here’s what the code looks like prior to me adding the class for your plugin: https://imgur.com/3gZYCUQ

2. Then I go into the block editor and I add this class (sg-popup-id-2139) to the block button, see screenshot: https://imgur.com/L1Ai7Lt

3. as a result, the code looks like this, with both the class I added, AND the addition of the data pop-up id, as you pointed out: https://imgur.com/MzkC4dw

4. now with the test button in the footer, the code looks like this, JUST with the class added, exactly same as I did for the button: https://imgur.com/MAqWael

5. Here’s what that button looks like on EVERY page of the site EXCEPT the one that has the working test button in the main page content: https://imgur.com/0L9nBTM

6. and without changing ANYTHING, if I load the page that has the working test button in the main content, the test button in the footer AUTOMATICALLY generates the data pop up id, https://imgur.com/DNDzXML

I understand that I can just manually add the data pop up id to the code in the footer button because it’s simply html, but doesn’t that defeat the purpose of how your plugin is supposed to work? If it’s supposed to work simply by adding the class?

Also, the REAL issue is that I want this code to work in the header menu button, which is a custom url wordpress menu item, so I CAN’T manually add the data pop up id, I can only add the class to the menu item, see screenshot: https://imgur.com/ciXH29S

And the same exact thing occurs here. This is the login menu item on ALL pages of the site except the one that has the test button in the main page content: https://imgur.com/GNwpm1Y

And here is EXACTLY the same menu item (having made NO changes whatsoever) on the page that has the test button in the main page content: https://imgur.com/iLc2zKL

So the issue I’m seeking your help with is finding out WHY the data pop up id is being automatically generated ONLY when the class appears somewhere in the main page content, but it does NOT automatically generate when that class appears in JUST the header or footer.

I hope I have clarified the issue? Please let me know, thanks.

FYI just got a response from Divi support team:

I am afraid that this is a known bug in Divi that recently occurred. When using template to posts or page created via Theme Builder with Post Title Module, the style of the Title Text gets applied to the heading text when editing a post with Guttenberg.
Our Development Team is already aware of this and is currently working to fix this. Unfortunately, there is no ETA on a solution that I can provide at this time. Though I can assure you that issues are addressed as quickly as possible based on our development team’s current workload and the severity of the issue when compared to the severity of other open issues.
Please make sure to keep your theme updated though as new features and bug fixes are served and delivered via an update.
I am truly sorry for the inconvenience.

Hey guys, I’m having the same issue with Divi posts, did you find a solution. I suspect it’s a Divi issue, not the plugin?? But I’d still love help solving it if you managed to fix it? thanks!!

Gotcha, ok thanks! Appreciate the quick response.

Sorry, Client wanted to go live so I had to switch to a different plugin to resolve the issue.