deanes

@novaleks Thank you for the CSS snippet.
That works around the problem.
I hope Estatik Support/Devs provide a fix in an update soon.

Hi
Thanks for your feedback.
My 2nd point perhaps not explained well.

Currently if a currency symbol is set in Settings it is applied to all price entries regardless of the values in the price field.

I have a menu that contains lots of ‘normal’ prices so I like the auto-formatting of the price and the addition of the currency symbol taken from Settings.
But I have a couple of menu items where I don’t want to show only a numeric price. I want the price field to show; “Ask for price” or something similar.
As things are now the currency symbol will be added to this text on the menu.

Is there a workaround for this?

I was thinking that if alphanumeric characters are detected in the price field then the currency symbol is not added.

Hi . Thanks for the fix.
Would it now be possible to have an option to hide or display decimal places?
I see now when the currency symbol is set in Settings, the numeric price is formatted with ‘,’ as a thousand separator and 2 decimal places added. This auto formatting is good and useful. But, I have clients in countries with currencies where typically decimal places are not shown.

Being able to use the auto formatting but not show decimal places would good.

Also, but perhaps more complex, if the currency symbol is set but non-numeric values are detected in the price field then the currency symbol is not applied to that price?

thanks

Yes it’s a change from the last update.

I had price details entered as though the Menu Item Price field was a text field but now the values in that field are only being seen as integers/numbers.

So 5,200.00 is now displayed as 5.00

I had some entries as text eg”Ask for price” that is now displayed as “0.00”

resolved

Thanks for the guidance. That has fixed the issue, no more Apache errors.

Thanks.
I’ll try that and update here.

Hi
I think I may have found the issue that threw me.
I think that I built the pages with images and then went back to the WP Media Library and added Alt Text and edited Alt Text.
I discover now that making changes to the Alt Text in the WP media Library doesn’t update to either the native Gutenberg Image Block nor to the Kadence Advanced Image Block.
For updates the image blocks have to be edited independently. Either ‘Replace’ the image with the same one or manually edit in the block’s Alt Text field.

For the last couple of years I have been working with Elementor. In Elementor the image widget does read changes from the WP Media Gallery Alt Text.

Not a perfect world, but now I see what’s happening it’s not so hard to compensate for.

regards

• This reply was modified 2 years, 6 months ago by deanes.

Hi Hannah
Thanks for your update.
I will do some testing – hopefully this week – and let you know if I can repeat the problem.
regards
Simon

Hi Hannah
Thanks for checking.
I am not 100% sure but it is possible I copy/pasted Row/Section layouts containing Advanced Image Block from one page to another.
If that was the case I have since changed the image within the Block and was still seeing no Alt text in the HTML code of the page.

Is my assumption correct that the intended function would be to use the Image’s Alt Text from the WP Media Gallery if the Alt Text field in the Block is left blank?

Please confirm or otherwise, and I’ll do some more testing this week to see if I can replicate the issue.

thanks again

resolved

Thanks for the quick solution.
That does the job.
I set background-color too, as it was transparent on hover.
And went with -20px to give a bit of space.

thanks again

Hi
Thanks for checking and the update.
I did see that but didn’t know the error from one plugin would have this effect on another plugin.
I have now tested by deactivating the plugin causing the JS error and WP Review Slider then appears and functions normally.
Not your problem.
I am getting in touch with the other plugin developers now.
thanks again for your time.

HI
Thanks for the quick response – on a Sunday too!
The css has helped – nothing to be afraid of, I was missing the .forminator-row class.
I notice there’s a few issues with CSS resolutions like this here in the support forum – perhaps you could collate them and add to your website’s support doco section as CSS Snippets, it may save some queries here?
thanks again
Simon

Hi
Thanks for the update and comments on our site.
Your CSS code workaround functions OK.
We can wait for your next theme update.
regards