Upgrading to this particular version results in a fatal error on the website!
I had to downgrade to the previous and stable version, 2.11.3.
The page I need help with: https://cdn-0.simplifygardening.com/wp-content/uploads/uag-plugin/assets/19000/uag-js-19324-1679399748.js?ver=2.4.0
]]>BSF releases UAG as a stand-alone plugin (perhaps with a different name) on version 1.25.6. The plugin need not have new features but would need to be maintained from a security/bug level.
I have reverted to 1.25.6 on all my sites. However, how long this is safe is an unknown.
I am unwilling to upgrade to Spectra’s latest version. As an intermediate user I really do not have the time to get my head around the new settings, although I acknowledge that for those who do have this time and are on a suitable WordPress knowledge level, Spectra’s new functionality does appear to be superior to UAG.
I am very happy with UAG 1.25.6 and wish to stay on this version, rather then being forced to change to a plugin that I did not ask for.
From a commercial point of view for BSF (that is for prospective buyers of Astra Pro), I feel this would be an advantage. Users thinking about using Astra and who checkout forums like this, will see that Astra coupled with UAG is still a powerful combination. Those more advanced in WordPress will have the choice of having UAG or going for Spectra.
Is there anything you can do for users like us?
]]>My immediate problem is how to stop WordPress auto-updating UAG to Spectra. Grateful for help.
]]>Note: The CF7 Styler widget does not use the usual CF7 shortcode to display the form.
Do you have a test/developer license I could test this out with?
David.
]]>I am having issues with the Star Ratings widget not displaying the stars on mobile and aligning to the left instead of center. This is having an impact on my website as it does not now look very professional or attractive.
Will the coming update address this?
Many thanks.
]]>The screenshot at the link below shows it regular, a view in Firefox (has less details like the section padding), and how it looks in Chrome.
I was just wondering if anyone else has noticed this issue, or if they have a fix for it. For now, I just reverted back to WP 5.8.3.
Thanks.
You can view my screenshot below.
]]>