Natalie MacLees

Well, it seems to have magically fixed itself today. Sigh.

I swear it was broken on both dev and local yesterday. Sorry!

Hi @randmanrjr ,

One of the plugin developers here. Our plugin doesn’t use the Fancy Box library and has no code that initializes Fancy Box. We aren’t initializing Fancy Box in the JS code and we aren’t using any data attributes with fancybox. You’ll find no instances of the word fancy in our entire codebase.

We’ve seen this issue before, and I’ve been all through the Fancy Box documentation and codebase to try and figure out how it’s getting triggered by Draw Attention images, but haven’t been successful so far. It doesn’t make any sense at all. Draw Attention images are SVGs and the hotspots are paths. I can’t figure out how clicking on an SVG with no fancybox data attributes triggers Fancybox.

• This reply was modified 3 years, 6 months ago by Natalie MacLees.

@kisabelle Just a note to let you know that in our next release, we’ll have support for using an image optimization plugin that supports webp. We tested with Imagify, ShortPixel, and Optimole and all worked fine. That should be out in a few weeks.

• This reply was modified 3 years, 7 months ago by Natalie MacLees.

@kisabelle Thanks for sending this over. If you need a solution very quickly, you could drop this code into your theme’s functions.php file to make Draw Attention work when Imagify’s webp format option enabled without waiting for us to make any changes to Draw Attention. It just prevents Imagify from replacing Draw Attention images with the webp image format.

We’re still planning to investigate fully supporting webp image format with Draw Attention, which would work with any plugin that is replacing images with the webp format. That way we wouldn’t need to include any plugin-specific code for handling different formats. We’ll keep you posted on what we find out.

Hello @prendergast ,

The options for showing more information with the plugin are limited to what the plugin itself offers and we don’t have an out of the box way to integrate with custom JavaScript to do other actions when the images are clicked. That would require a good bit of customization to the plugin’s JavaScript to get that working.

Let us know if you have any other questions we can help with.

Hello @jackmattison –

Please feel free to use our pro support at [email protected] if you don’t wish to publicly post links to your pages and settings.

I see that you’ve set ‘always show hotspots’ and set a style for this particular hotspot so that it’s always visible. It’s behaving the way it’s been configured – the spot is always visible on the image, whether it’s currently activated or not.

I think what you may have been looking for instead is not for the spot to always be visible, but for the spot to be activated when the page loads, does that sound correct? We don’t have a way to indicate that one particular spot is active, but you can link to a hotspot from another page, activating the spot when the page loads. We have more information on that in our documentation here: https://wpdrawattention.com/document/build-link-opens-hotspot-page-load/

Let us know if you need more help with this.

Hello @ramm86 ,

You can place a shortcode in the more info area, so you could use a plugin that adds a shortcode for displaying posts to accomplish this.

For example:

• Display Posts
• WP Show Posts

Let us know if you have any other questions.

Hello @hanszamorano ,

Sorry to hear that you’re experiencing some issues with the plugin. If you’re using our Google Calendar integration, it sounds like you’ve upgraded to one of our premium plugin editions and are entitled to priority support through our [email protected] email address if you’d prefer to use that instead of the forums. Sometimes that’s helpful for sharing some information that can help us debug that you wouldn’t necessarily want posted publicly to the forums.

I’ll address the issues you’re reporting below.

Emails are not working correctly. For example, I am using 3 emails to test: [email protected], [email protected], [email protected]. On admin notifications I use the default admin email by the default interpolation “{{admin_email}}”, and manually added [email protected] as a co-recipient. On customer notifications I send to [email protected] which is obtained by the interpolation “{{customer_email}}”. When scheduling an appointment, or cancelling them, just [email protected] receives notifications. I tested using only {{admin_email}} which is the default, without CC, and nothing happens on Admin email (that’s why tested with other two emails). When receiving admin notifications at [email protected] as CC, it says it is sent to [email protected], and [email protected], just copied that and resended to them and it worked. The workaround I’m using right now is to not use admin_email interpolation and write them manually. I would say is a server level malfunction, but when not using the interpolation all works perfectly. Note that in both cases the emails are being sent instantly in the next minute since the event (scheduling, or cancelling).

Can you please double-check the admin settings to be sure that the admin email address is correct there and there isn’t a typo or other issue with it? From the WordPress dashboard, go to Appointments > Settings > General Settings and make sure the admin email is correct. We haven’t any other reports that using the token for the {{admin_email}} when addressing the emails has caused any deliverability issues, so I suspect that there’s just a typo here.

Cancelled appointments are not being removed from calendar, just prefixes “Cancelled:” to the event.

This is correct and is working as intended. In addition to having Canceled prepended to the event title, the Google Calendar event is also changed from Busy to Free so that it is not blocking any other events from being booked into the canceled spot.

When editing appointment information, it says the phone number it’s invalid, in this case I rewrite one number, or add and delete one to “refresh” the validation of the field.

I’ve verified that this is the case and we’ll include a bug fix for this in a future release of the plugin.

Appointment modification event in notifications is not working, when modifying an appointment, just cancels and reschedules.

Can you clarify this one? Are you selected to Reschedule the appointment? Or just to edit the appointment information? If you’re rescheduling, then it’s correct that we book a new event, and then cancel the old one. This helps to avoid a number of potential complications with just adjusting the date/time/appointment type/duration of an existing appointment. If you’re just editing information like the customer name or email address and that’s resulting in the appointment being canceled and a new one booked, then that’s a bug that we haven’t seen before and we’ll work with you to sort out what’s going wrong there to get that corrected.

Hello @ctcottagemom ,

In the free version of Draw Attention, there’s only one image, so [drawattention] is the correct shortcode. In the Pro version, you can have multiple images, so it’s necessary to add an ID to the shortcode.

You should be able to paste the shortcode into a Text widget in your sidebar. Please note that by default, shortcodes aren’t supported in custom HTML widgets, so please be sure that you’re pasting your shortcode into a Text widget as described here: https://www.wpbeginner.com/wp-tutorials/how-to-use-shortcodes-in-your-wordpress-sidebar-widgets/

Hover vs click triggers for hotspots is available in the Pro version of the plugin. If you have further questions about the Pro version of the plugin, please contact our support at [email protected] as we are not permitted to offer support for the Pro version of the plugin on these forums.

Great, thank you!

Hi Gary,

I’m glad you were able to sort out the issue and find the cause. We’ve had similar issues with that settings in iThemes security and we’re not alone – several other plugins have issues with this setting, which is a bit overly aggressive and unfortunately, not at all adjustable. It would be really helpful if iThemes offered a way to mark certain URLs as safe so that you could continue to use that setting but allow certain requests through. We’ve made that request to the iThemes team, and we’ve found threads where other plugin authors have requested the same, but so far we haven’t had much luck.

There doesn’t seem to be anything we can do from our side to get around that setting, but we’ll keep asking the iThemes team for some flexibility there so we can get our plugin working with theirs. You can add your voice to the request to get some flexibility with that setting from the iThemes team – the more people ask, the more likely they are to implement it.

Hi there! Sorry, just a note that while the for attributes of the labels and the name attributes of the form inputs now match, it’s actually an id attribute on the form inputs that is used to link those up with the labels.

Is it possible to have an id attribute added to each form input that would match the value in the for attribute on the label?

Current HTML:

<div class="meow-contact-form__group">
	<label class="meow-contact-form__group-label" for="mcfb_name">Name</label>
	<input class="meow-contact-form__group-input" type="text" name="mcfb_name" value="" required="">
</div>

Correct HTML for accessibility:

<div class="meow-contact-form__group">
	<label class="meow-contact-form__group-label" for="mcfb_name">Name</label>
	<input class="meow-contact-form__group-input" type="text" name="mcfb_name" id="mcfb_name" value="" required="">
</div>

More information here: https://www.w3.org/WAI/tutorials/forms/labels/

Hello @brightbluegum ,

Just a quick note to let you know our release today (1.9.0) has improved support for keyboard navigation and it’s now possible to reveal the more info area with the keyboard. Let us know if you need anything else.

We answered this via our premium support channel: [email protected] since we are not allowed to use these forums for support of our premium edition.

We were able to track down the issue. An image was uploaded and hotspots were drawn. Later, a new image was substituted for the original image. Either WordPress’s new handling for large images or an image optimization plugin re-sized the image on upload, causing the hotspots to appear out of place.