Forum Replies Created

Viewing 8 replies - 1 through 8 (of 8 total)
  • Thread Starter jacktester

    (@jacktester)

    Thanks both, that’s good to know, I’ve been trying to find that out, but all I could find were threads giving theoretical maximum numbers of files, and never an explanation as to what problems it may cause having more than that in a single folder.

    We don’t perform ant other functions in the uploads folder anyway, so not too much of an issue by the sounds of it.

    I worked around the issue that was affecting me by temporarily moving the files out of the directory, as they were just in relation to an importing plugin moving them out doesn’t affect anything unless someone tries to run the import.

    But I think an option to either regex match folders you want to exclude from the scan, or an option to include folders that you do, would be good, and possibly a simple checkbox option using the regex above for those less comfortable creating regexes?

    Thread Starter jacktester

    (@jacktester)

    Hi Jordy

    We don’t use the YYYY/MM folders, in hindsight this might have been a bad idea as we now have 177,000 files in our uploads folder, but we didn’t anticipate that at the time and somewhat surprisingly it doesn’t appear to be causing any performance issues, as most pages on the website load between 600ms and 1200ms with Chromes browser cache disabled in DevTools.

    That said I’m sure it may still be useful for some people who might be in a similar boat, as there are many plugins that store files in sub-folders of the uploads directory.

    Would it also however not be possible to scan /uploads excluding sub-folders that don’t have the YYYY/MM naming format. Presumably anything in the WordPress media library would either be in /uploads or in a YYYY/MM directory, anything else would likely be plugin related files? Naturally this would be best in the form a check-box as you say, as it would also be handy to be able to scan for files leftover by removed plugins.

    In terms of a regex it would look like this: ^\/uploads(\/([0-9]{4})?\/([0-9]{2}))?$

    Thread Starter jacktester

    (@jacktester)

    Hi @maheshmaharjan

    Thanks for that, it’s much appreciated.

    Would you know approximately when the next update will be available so we can roll it out to our live site?

    And I presume I’m ok to remove the account I created for you from our dev site?

    Many thanks,
    Jack

    Thread Starter jacktester

    (@jacktester)

    @maheshmaharjan

    I’ve created you an administrator account on our dev site, you should have received an email.

    I’ve also set the address on your account so you can checkout, as we use address filtering. The Sage Pay card processing plugin is in test mode the test card details are shown on the checkout page.

    If you input those the next page loads an iframe which should connect to Sage Pay’s 3d secure testing page, with To Top off it loads with To Top on it returns a 404.

    Thread Starter jacktester

    (@jacktester)

    Hi @maheshmaharjan

    Yes, if I disable To Top the sage plugin works fine.

    We currently have To Top disabled, as being able to accept card payments directly on our site is very important, though obviously ideally we’d like both to work together.

    Regards
    Jack

    Thread Starter jacktester

    (@jacktester)

    That seems to be working perfectly.

    I hope to be able to bring us up to the latest version of WooCommerce soon, but need to find time to look at possible workarounds for the grouped product issue on the dev site first.

    Thanks for responding with a solution so quickly, it’s much appreciated.

    Thread Starter jacktester

    (@jacktester)

    Hi

    Thanks for the quick response.

    We are currently stuck on an older version (2.6.14) due to the changes that have been made to the relationship between grouped and child products in WooCommerce version 3.0+.

    I’ve tried deactivating all plugins except this one and WooCommerce and it is still searching hidden products, so I presume it must be to do with the WooCommerce version.

    Also experiencing the same issue.

    I get the following 19 times on each page load:
    data:image/gif;base64,R0lGODdhAQABAPAAAP///wAAACwAAAAAAQABAEACAkQBADs=

    and then, as CEMBTW describes, 1 of the following:
    [domain/shop/category/product]/image/gif;base64,R0lGODdhAQABAPAAAP/wAAACwAAAAAAQABAEACAkQBADs=

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