xmarksthespot

@carolm29 and @beautyofcode

I’ve just run a quick check having installed 8.6.1. Initially things looks OK now, but let’s see…

As I, others posting here and my theme support suspected the issue was with woocommerce. It looks like it was introduced in woocommerce version 8.6.0 on 13 Feb and was resolved in 8.6.1.

I did smile at the mention of wordpress forum guidelines – my favourite one being that in all circumstances woocommerce support must first always claim that their product is not at fault : – )

I am having a similar issue/error, and it also only started today.

Unlike you I am using the Blocksy theme. I am trying to add attribute filters to the woocommerce sidebar.

I see the error in the Customiser but also in Appearance/Widgets in the dashboard irrespective of whether I’m using the Block editor or Classic editor.

I suspect it is a woocommerce issue as I’m not seeing this for other customisations/edits/plug-ins. Perhaps there is a limit as to how many attribute filters or items I can add? – as it is ok initially but seems to get to a point where it falls over. When I start again – having cleared the sidebar, cleared cache and done largely all the things you did – it tends to get to a similar point before falling over with the error again.

• This reply was modified 1 year, 1 month ago by xmarksthespot.

Hi Maybellyne,

All current, i.e. wordpress 6.2.2, woocommerce 7.8.2, Yoast 20.11

I’ve looked again and the primary category setting IS present. Sorry. I seem to recall that it could be set in ‘edit post’ against the post hierarchy. Similarly for product. I now see that it is in a drop down box below the hierarchy. I simply missed it!

Thank you for confirming (in your option 2) that what I had already done is an acceptable solution.

@c0nst – since my last post I’ve stumbled across this thread, which may be relevant:
https://stackoverflow.com/questions/2989263/disable-auto-zoom-in-input-text-tag-safari-on-iphone/

It seems as if Safari (and maybe other browsers?) will zoom if the font-size is less than 16px. Your default css specifies font size of 14px.

So as a ‘fix’ to disable unwanted zoom on focus I’ve added the following to the ‘Additional CSS’ section of my theme:

.dgwt-wcas-sf-wrapp input[type=search].dgwt-wcas-search-input {
font-size: 16px;
}

I’m not a developer, and I appreciate this may not suit everyone, so I’m wondering if you have a better solution?

• This reply was modified 2 years, 7 months ago by xmarksthespot.

@c0nst – thank you for your reply.

On 1, thank you, this works

On 2, this does not solve the problem. Just to clarify, the problem on mobile (I’ve only tested iphone) is that when I tap the desktop-style search box, it zooms in on the search box and presents the keyboard. The keyboard is expected but the zooming makes the site width wider than the viewport and presents an unwanted horizontal scrollbar.

However, if I use a normal WP search box the keyboard is presented but the zooming does not occur.

See for yourself on mobile on the link I provided earlier. Below the header is a fibosearch search box on the left and WP search box on the right so you can compare.

Hi Mikko,

Thank you for the clarification.

To help others, especially newbies, I suggest it might be worthwhile putting this in your online instructions for the free version.

Thank you, this works.

Is the gap between columns a single setting that applies to all devices? If so, when you’re considering changes, then I think it would improve the product if it was possible (when required) to set a different column gap for each device screen size, i.e. large/medium/small/extra small.

I have set up a temporary page: https://d.xmarksthespot.co.uk/test-layout/

Thank you, but it didn’t work fully.

The gap on the left is removed, but the gap on the right remains. In fact, changing the value of margin-right to something other than -50px appears to make no difference.

• This reply was modified 2 years, 8 months ago by xmarksthespot.

Thanks for your reply.

Interesting to hear that it’s a bug that you’ve failed to fix, let alone publicise! Neither approach is very helpful for customers! – many of whom might go on and buy the commercial version. So it creates a bad impression regarding your company, product and level of support.

In fact, I was considering buying the commercial version (as I may use the product category filter) but am left wondering if it is buggy too, and if there are issues with it that are also not publicised or communicated to customers.

Consequently, as I feel I can’t trust the product and your company I will take my business elsewhere.

Thanks for the suggestion. Yes, I can see how it would work with custom post types. Problem is that I only want to see each location once, not for each occurrence of Paris (say). Perhaps some sort of category drop down is what I need but with the ability to type in and search too (like the Ajax search lite interface). Am struggling to find something I can tinker with to fit my needs but I’ll keep looking. All suggestions welcome!

Great work with Ajax search lite.

• This reply was modified 6 years, 4 months ago by xmarksthespot.

Perfect. I now have this working. Thanks for your help and glad we both learned something! Win-win!

And further to your recommendation…

I’m probably getting confused on terminology here.

By “Pods custom setting field” do you mean a ‘custom field’ similar, for example, to pet-name in your tutorial? If so, in my case for testimonials, this would then appear against every testimonial? I just need something that describes what the testimonial pod does that can then be displayed above the testimonials, e.g. ‘Read what previous participants say about Scavenger? the leading team building game on smartphone and tablet’

Perhaps you can clear up any confusion at my end.

Thanks for the steer Josh.

Before I look at that, I note that in the Edit POD Admin UA tab there is a ‘Post Type Description’ which is described as a “short descriptive summary of what the post type is”.

This would appear to be what I need? – and would avoid setting up a custom field for each and every custom post type I’m planning.

Any reason why this wouldn’t work? If it’s fine to use, what’s the syntax to get its value into index.php?