Robert Gadon

@ankordesign I just inspected the site in mobile view using both Chrome and Firefox. The popup renders fine and I was able to close it in both browsers. However, the Console tab in Chrome Developer Tools and FF’s Web Developer Inspector are showing errors, which indicates that there’s something amiss with the JavaScript/jQuery scripts on your site. We do have some documentation on troubleshooting JS/jQ errors with Popup Maker. Run through those suggestions and see whether they resolve your problem.

• This reply was modified 7 years, 10 months ago by Robert Gadon.

@newsshop Please open a support request at wppopupmaker.com so that we may better track and respond to your issue. Plus, you will be able to provide a link or upload your video demonstrating the issue you wrote about.

• This reply was modified 7 years, 10 months ago by Robert Gadon.

Hello @rooksads,

We need to isolate the issue. There could be confounding factors going on due to plugins or the active theme.

First off, read this article from our documentation. See if anything addressed there helps you resolve your issue.

Next, try the following:

1) Switch to a default WordPress theme (e.g. ‘Twenty Seventeen’);

2) Deactivate all plugins (PI) except Popup Maker.

3) Go the front of your site and refresh the browser.

Does the popup appear based on the Condition(s) and Triggers that you set within the plugin?

Use either Google Chrome Developer Tools or Firefox Web Developer Inspector to inspect the page. Open the Console tab in the inspector. Are there any errors or warnings? Note those if any. Those indicate possible JavaScript/jQuery errors.

See this article for guidance on how to troubleshoot possible JS/jQ errors.

4) If the Inspector console is clean, then slowly reactivate PI either one at a time or in small batches. Recheck the Console repeatedly with the web inspection tools.

If the Console still reports no errors, reinstall the theme you were using, and check the popup again.

I hope this helps you resolve your issue. If not, write back and tell us what you did and what you found. A link to your site woulD be helpful.

• This reply was modified 7 years, 10 months ago by Jan Dembowski.

Hello Vad,

Can you describe the steps you’ve taken to generate a popup after you installed the plugin, and the actual result you received?

Have you used either Chrome Developer Tools or Firefox’s Web Developer Inspector to inspect your site? Are you able to observe the popup markup within the Element inspector? Are there any JavaScript errors reported on the Console tab?

More information here would assist us in helping you.

• This reply was modified 7 years, 10 months ago by Jan Dembowski. Reason: Please do not use signatures in these forums

Hello @waalker,

Could you please elaborate on why you want your popup to trigger only once a month? Most users want their popup to open when a visitor requests a specific page, or post (based on preset conditions), and then to trigger based on some event (time page is open, exit intent).

Hello @vharel,

There is currently no means provided in the ‘back end’ of the plugin to change the font-size of your popup content. You will have to modify your theme’s ‘style.css’ file to change the font-size of your popup content. We’ve provided users several ways to find the CSS selectors they will need to target.

See: https://docs.wppopupmaker.com/article/147-getting-css-selectors

You can also view and copy the core plugin and popup theme styles from the back end of our plugin for use in your stylesheet.

1) Log into your site, and open the WP Admin.

2) Go to ‘Settings’ >> ‘Assets’ and select the button ‘Show Popup Maker CSS’. Both ‘Core Styles’ and ‘User Themes Styles’ for the plugin and popup themes will display respectively. Paste this CSS directly into your theme stylesheet in order to work with it. You cannot modify the plugin’s CSS styles from this options page.

You will need to target the .pum-content class attribute with a font-size property set to whichever value you want. If you need additional guidance on CSS properties, consult this reference: https://tympanus.net/codrops/css_reference/

I hope this response was helpful.

• This reply was modified 7 years, 10 months ago by Jan Dembowski.

Hello @bdanzer29:

Did the link above to our documentation help you fix your problem?

• This reply was modified 7 years, 10 months ago by Jan Dembowski.

Hello @waalker:

In response to your second post above:

1) Go to ‘PopUp Maker’ in the left side of the WP Admin, and select ‘All Popups’.

2) Find the Popup that you want to work with and below the name, select ‘Edit’.

3) Scroll down the page to find the ‘Cookies’ metabox (custom field) located below the editor.

3a) If the ‘Cookies’ metabox is not visible to you, go to the top right corner of your page and look for ‘Screen Options’ tab. Select ‘Screen Option’ and a hidden set of checkboxes will open. Make sure that the ‘cookies’ checkbox is selected. Then select the ‘Screen Options’ tab to close the settings.

4) If you already have a Cookie generated called ‘On Popup Close’, then you’re all set with cookies. That cookie will work for all triggers created for your site. The cookie should also have a name, which will begin with the string ‘pum-‘ and a number after it. If it doesn’t, select the ‘Edit’ feature (pencil icon) and give it a name.

5) Scroll up one metabox to ‘Triggers’. You should have at least one trigger set. Select ‘Edit’ for that trigger (pencil icon). A box will open with two tabs on the left side; ‘General’ and ‘Cookie’. Select ‘Cookie’. If there’s a name for the cookie, select and delete it. Then select ‘Save’.

5a) If you have no ‘Trigger’ generated, then create one. Select the ‘Add New Trigger’ button. The only trigger available in the base plugin (without extensions) is ‘Auto Open’. Select ‘Auto Open’ (or whatever additional trigger you want based on what your extensions make available). You will be redirected to a ‘click trigger settings’ box >> General tab. Is no additional CSS will be added, select ‘Add’. By default, no cookie will be generated.

I hope this is helpful. Let us know whether it resolved your problem.

• This reply was modified 7 years, 10 months ago by Robert Gadon.
• This reply was modified 7 years, 10 months ago by Jan Dembowski.

Hello Rob,

The Popup Maker plugin had a change in support staff over the past weekend. I just picked up this support thread, and am investigating the matter. I am consulting with the plugin author @danieliser about your issue, and will get back with you later today. Sorry for the delay in a response.

• This reply was modified 7 years, 10 months ago by Jan Dembowski.

Good news! Clearing the input field for Accept request from these HTTP referrers at Google Developer’s Console >> API Manager >> Credentials returned the map on both the production and development site! I waited 5 minutes after making the change, and then added the web domains back into the API Mgr >> Credentials page. We’re good to go. Thank you for responding so promptly to my support request, and helping to solve the problem. I’ll go show some love by giving your PI a 5-star rating. Cheers!

One thing I’ve been thinking about is to spin up a local test site with a default WP theme and just install the GMW PI in a widget area. Add in my API key to the GMW settings page, and see if I can output the Google Map or not.

Hi Folks,

I appreciate the suggestion to add in specific web domains on the API key Developer’s Console page. I did that weeks ago, but it did not make a difference. I’m still getting an error message when selecting the map link presented by GMW.

@rammiro: Images already uploaded to your site will show based on a default image size set in your theme. If you want to resize your existing images to a small size then use this plugin. All new images uploaded to your site after the installation of this plugin will create a new custom image size per your settings.

If you’re not confident or entirely clear about what the code snippet above will do to your theme, I would not add it to ‘functions.php’. The value of adding a plugin (particularly this one) is that: 1) you can turn it on and off, and it won’t affect the performance of your core WordPress files, 2) the PI author is diligent about checking their code against updates to WordPress core (a good thing; not all authors do this).

Good luck.

Upon further digging (and reviewing a newly posted documentation video posted by the theme author), the problem appears to be caused by the Grunt taskrunner packaged with the theme not executing in my local development site’s root directory. Grunt is supposed to launch a ‘sass –watch’ command to watch for changes in the SCSS partial files, which precompile inside the ‘style.scss’ file, and then output as compiled CSS to the child-theme’s ‘styles.css’ file. So the code snippet posted above is not necessary to attain compiled SCSS. The solution is to get the Grunt taskrunner working.

For anyone reading this, the solution is simple. Nick’s explanation above left out a key piece of information: substitute the HTML in place of the short code. If you embed your HTML inside the short code, you won’t change anything.

For example, the shortcode [footer_child_theme_link before=”” Utility Pro after=”child theme”] outputs: utility-pro child theme.

But ‘The <a href="https://store.carriedils.com/downloads/utility-pro/">Utility Pro</a> child theme' returns: The Utility Pro child theme.

Just leave out the short code when using the HTML.