• Resolved happymonk

    (@happymonk)


    I’m trying to do a simple text replacement using Loco Translate on my WooCommerce Storefront site. i.e. change the string: “Search products…” to “Search site…”

    When I try to effect this change using the Loco Translate interface, I receive the error: “Remote connections are prevented by your WordPress configuration. Direct access only..” An earlier support question identified that the problem is related to FS_METHOD being set to “direct” on the site and advises talking to systems admin about changing this. WordPress can’t change wp_config, so I’m in a bind!

    This looks like such a simple change (what I want to do), and it seems so close, but now I feel way over my head.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Tim W

    (@timwhitlock)

    Loco Translate honours the wishes of the site configuration. If you want to do things that go against that then switch to a hosting provider that allows you to make changes.

    The only work around is to ensure you can modify/create the files you need using the methods you are permitted. So in your case that means direct access for the PHP process to write to your disk. You may find that your hosting provider won’t allow that either, but this is between you and them.

    The only help I can provide with file system access is as documented here:
    https://localise.biz/wordpress/plugin/manual/filesystem

    Thread Starter happymonk

    (@happymonk)

    Hi Tim W …

    I have no interest in changing my hosting provider.

    What I am interested in doing is changing one word in the search box in my WooCommerce Storefront theme: from “Search products…” to “Search site…” WP Support recommended Loco Translate to find the string, then change it. Everything works great until I need to change it.

    If changing that is not possible, I can live with it, but it would be nice to get it done! Seems like such a simple task!

    Do you have any other suggestions?

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘WordPress Config Workaround?’ is closed to new replies.