-
Posts
-
Hello
Since updating Popup Maker to version 1.16.10 and newer, popups that should only be displayed on certain pages no longer work properly. The content of those popups can be found in the source code of the corresponding pages, but clicking on the trigger does not display the popup. As trigger we use links with the ID of the popup as target, e.g. href=”#popmake-1234″. The problem only occurs when Enfold is configured to display a page as a footer. As soon as widgets are to be used as footer, all popups work fine. Also, the problem only affects popups that should only be displayed on certain pages.
The problem occurs with older Enfold versions (4.8.3) as well as the latest version.Many thanks
Hey Jeannette,
Thank you for the inquiry.
Did you add the same triggers or links in the footer page? Please provide the site URL and a page containing a popup so that we can check the issue further.
Best regards,
IsmaelHi Ismael
We found that it doesn’t matter if there are triggers in the footer or not. In the example website, the page-specific popup should open when you click the “Jetzt Mietanfrage stellen” button, but unfortunately this does not happen. In contrast, in the footer the text “Abonniere den Newsletter” is linked to another popup, which is included on every page and opens without any problems. If we remove the trigger in the footer, the behavior of the page-specific popup does not change.
Thanks for your support.
Hi,
Thanks for your patience and for the login, I see that your bottom button popup-2090 is not working when the page footer is used, but it does when the standard footer is used.
When you do use the page footer, the popup-2010 in the page footer does work, and it works in the bottom button, even if both are used at the same time.
I see the issue is that the popup-2090 is limited to the page postid-2082, but for some reason the popup plugin thinks the page is no longer the correct page, but the page footer doesn’t change the page ID nor does it add a page ID, so I believe the popup plugin is somehow stumped.
I recommend removing the page ID limitation from the trigger, since the button is only on the page that you want it to work on adding a limitation is moot.Best regards,
MikeHello Mike
Thank you very much for your analysis. I agree with you that the button is only present on this page and therefore the popup cannot be triggered on other pages. In this respect I could really remove the restriction of the page ID. However, this restriction also ensures that the popup’s content only appears in the source code of the relevant pages. And since there are a total of 22 popups defined for the entire site, each of which is only needed on individual pages, I’m unnecessarily blowing up the source code of the remaining pages if I remove the restriction. Therefore, this doesn’t really seem like a viable solution to me.
Kind regards
JeannetteHi,
Thanks for the feedback, but unfortunately I don’t know how the popup plugin is triggering its conditions, I would assume that it would just check for the page ID but since this is failing when the footer page is used then the plugin seems to be checking something else.
The use of the footer page doesn’t change the page ID, or the post type, or anything else that I can see, so I don’t see any reason for it to not work.
Try reaching out to the plugin author, perhaps they have a function that you can use to just check the page ID as the condition.Best regards,
MikeHi
I can confirm that the problem has been fixed in Popup Maker version 1.17.0.
Kind regards
Jeannette
- The topic ‘Compatibility issues with Popup Maker 1.16.10 and newer’ is closed to new replies.