Forum Replies Created

Viewing 12 replies - 1 through 12 (of 12 total)
  • Thread Starter ashikai

    (@ashikai)

    Oh ok. I did get it to work then. I just had to remove everything and replace it with echo do_shortcode('[products category="clothing" paginate="true" limit="24" columns="3"]'); and now the filters work.

    Thanks!

    Thread Starter ashikai

    (@ashikai)

    Ok, so the issue has been resolved after a lot of testing.

    In case anyone else runs into this issue – it was caused by one of the images not being large enough to generate a srcset. I uploaded a larger(dimensions) file and the srcset generated just fine. Not sure if there’s a way to add some kind of fallback, but this is what worked for me.

    @danieliser Yes, everything is the latest version, however I am using Underscores rather than Twentytwenty, but I don’t think that makes a difference? Jetpack is also active, so I’ll try deactivating and seeing if either of those things may be impacting it.

    Thread Starter ashikai

    (@ashikai)

    Thank you! I’ll give this a try and report back after some troubleshooting!

    Just chiming in – I’m working with a fresh install of wordpress + woocommerce and this is also occuring. Simply activating the plugin (I have no other plugins outside of woocommerce enabled) makes the “who can see this” dropdown in each menu item appear twice.

    I was haging the exact same issue. I’ve been trying on and off for two weeks to get this plugin to just ACTIVATE. Looks like a ton of people in the reviews area are having the same problem too (hence the sudden influx of 1* reviews).

    Now, I DID SOLVE THIS PROBLEM…

    Whenever I downloaded the plugin via WP.org (through the plugins menu) I would constantly get the “invalid header” issue. But then I went to woocommerce.com and downloaded that version of WooCommerce Square, installed that via FTP and activated it with no header issues whatsoever.

    Is it possible the wrong package is uploaded to the Wp repository?

    Hope this helps someone!

    Thread Starter ashikai

    (@ashikai)

    Hmmm I see… I’ve never done that before so I’ve got no clue where to start. But thanks for the input! I’ll do some research and see what I can find out.

    Thread Starter ashikai

    (@ashikai)

    Thanks for the reply. I do get what you’re saying and honestly this was the very first time I’d ever altered the core files and it was just as a bandaid until I could figure out how to do what I wanted without it. Is it something I can live without, yes, but this was a client website and it’s not something they feel they can live without, so I’m a bit stuck.

    The link I supplied in the OP was to a snippet that worked in WordPress 3.7-3.9 but I think the code that it looks for and adjusts has changed and I can’t figure out where. That becomes my fundamental problem. ??

    Forum: Fixing WordPress
    In reply to: Unwanted tags
    Thread Starter ashikai

    (@ashikai)

    Hmm. I find that hard to believe. I’ve been finding this issue only after updating to 3.5.1 for all of my sites. Seems weird that it would just appear now.

    Forum: Fixing WordPress
    In reply to: Unwanted tags
    Thread Starter ashikai

    (@ashikai)

    Ok, I’ve found a kinda weird work-around…

    While trying to debug an entirely unrelated issue on another WordPress site, I found that WordPress 3.5.1 has an extremely buggy editor, and to fix it, I told WordPress to use Google libraries instead. THEN I told it to remove the wpautop(); and that worked… kinda. I mean, it doesn’t work 100% of the time, but for now it’s passable.

    I really hope someone can fix the WordPress editor. This is really frustrating.

    Forum: Fixing WordPress
    In reply to: Unwanted tags
    Thread Starter ashikai

    (@ashikai)

    No, no. I’ve moved it outside of the <p></p> tags several times, and wordpress continues to re-wrap the image. I’m only using the text editor, so that’s not the problem either.

    I would enclose the image in its own div EXCEPT that this is a client website, and the client needs to be able to insert/remove images on their own as they please. I don’t think telling them that they need to use div tags around every image is very acceptable.

    https://talesstudio.com/capcon/industries/

    The image is already floated left as it is. There’s nothing wrong with the CSS. The fundamental problem is the unwanted addition of <p></p> tags around every element in the editor.

    Forum: Fixing WordPress
    In reply to: Unwanted tags
    Thread Starter ashikai

    (@ashikai)

    https://talesstudio.com/capcon/industries/

    Sorry. I didn’t think it was necessary in this case. But that’s the page I was working with when I found the issue. I can move the image out of the <p></p> tags, but wordpress just adds more. Nothing I mentioned in my original post works. =\

Viewing 12 replies - 1 through 12 (of 12 total)