mjs1974

Thanks a lot for this Ben. All is working again with the divider and the icon on the shop page. I appreciate your help.

Cheers,

Mark

Hi Ben,

I completely understand about WooCommerce being it’s own custom post type and that the shop page is an archive with it’s own page template making it different to “posts” and “pages”. It was just odd that this worked fine a month or two ago in WordPress 5.7.2 with WooCommerce 5.1.0, Kadence Blocks 1.10.7 and Kadence 1.0.19 as the only thing I am doing is adding a hero section containing a heading, text, an icon and shape divider which is technically before the actual WooCommerce products loop which outputs the products onto the page (I am not doing or require any other customisations which need a custom design to override anything else outputted onto the page by WooCommerce).

Is there any possible code fix to correct this or is the only solution (unless you make an update) to just use the Kadence Theme page customiser settings in the same way you set the shop archive page in the shop demo https://demos.kadencewp.com/blocks-store/shop/? It would be a shame if the latter is the only option as it would break away from the hero design I have used on the other pages of the site which use the shape divider.

Thanks,

Mark

Hi, is there any news when the next update of the P2G plugin will be released with access for the shop manager? It is about 6 weeks since I first asked about this however I still not seen any new updates.

Thanks!

Thanks for that Ben. I did come across that plugin (apparently not 100% safe) as well as “Safe SVG” which sanitises all SVGs on upload. I couldn’t though remember from where I got the SVG files as I downloaded them a few months back so wasn’t sure if it would be 100% secure.

I recently found this website https://iconify.design. Once you find the icon you require, if you copy the code from the SVG tab, you can then go to this website:

https://yoksel.github.io/url-encoder/

and paste the code into “Insert SVG”.

You then use the code in the “ready for css” section taking only the code between the opening and closing speech marks “”. In WordPress itself, you can then use the url (not including the speech marks) in the WordPress image block.

I should have probably made it clearer that I am using Kadence Blocks too to help page performance rather than using another 3rd party block plugin. I was trying to set up an info box with a face icon expressing fear but couldn’t find anything suitable so had to use the ghost icon. If the image option on the info box allowed the use of urls like the standard Gutenberg image block then I could have pulled in an SVG from an external source. I think you only allow custom icons in the pro version of Kadence blocks so I appreciate you needing to charge for it. It’s not a deal breaker at the end of the day as I have still been able to put together the section of the site using the included info box icons.

I really like the fact that the theme does so much without needing extra plugins such as the contact form with the honey pot feature. I recently came across a plugin which does the same thing but I won’t be needing that now.

I will be keeping an eye on your website later this month.

Cheers!

Thanks for your reply Ben. Flexbox does work on iOS 9 to an extent as I have checked this on caniuse.com. I do however appreciate the rest of your comments about supporting older browsers if it’s not something specifically on your roadmap. I just wanted to check as I’ve used Oxygen which uses Flexbox in the header and it works fine. Maybe it is the CSS grid which is messing things up and in which case that definitely does not work earlier than iOS 10.3.

If you can’t sort the JS thing out then not to worry. I know it’s impossible to get every everything working for every browser. If only all browsers worked the same!

Thanks anyway and well done for a great theme! (if only you allowed custom icons in the free version!)

I wrote directly to P2G and had a reply on 12/10/20 saying that a request would be submitted by a member of the dev team to review this issue. A period of 2 weeks was mentioned however as to date, I have not seen any new updates so not sure why someone has marked it as resolved unless it is now work in progress with an update to arrive soon. It is though badly needed and seems strange to have been overlooked in the access roles. Fingers crossed for the update!