Forum Replies Created

Viewing 7 replies - 31 through 37 (of 37 total)
  • I have the same issue at read.twedt.com – when I try to update any blog post, I get this error message. I’ve tried disabling all of my plugins first, and I still get this error.

    Thread Starter ostinatofreak

    (@ostinatofreak)

    Actually, it’s a little more than that. Paypal isn’t even <i>available</i>. There are no options – the customer is forced to use Stripe.

    Also I should note that when customers placed orders on my site before, they were able to pay using Paypal, so Paypal is evidently set up correctly in Woocommerce. The difference here is that this is the first time I’ve created the order for the customer and had the invoice sent to them. Even when I select Paypal as the payment method, the customer is forced to use Stripe.

    Thread Starter ostinatofreak

    (@ostinatofreak)

    Sorry, my post above has some errors that make this look like a Wordfence issue. It isn’t a Wordfence issue, it’s just an issue that can happen to anyone whose www.remarpro.com password is compromised. The third paragraph should have read (corrections in caps):

    Luckily, I had backed up my site maybe a month ago, so I just FTP’d to my account, deleted the WORDPRESSS folders, re-uploaded the backed up WORDPRESS folder, then updated VARIOUS WORDPRESS PLUGINS, all within about 3 minutes of originally enabling the plugin.

    The fifth paragraph should have read:

    I’m also going to eagerly await the next automated Wordfence scan of my site to see if anything else was compromised when the fake “WORDFENCE” plugin was enabled. (I don’t subscribe to Wordfence premium so I can’t manually scan the site.)

    Thread Starter ostinatofreak

    (@ostinatofreak)

    What if you only log a user’s attempted password if 1) that particular username does not exist in the system, or 2) the login attempt originates from some country other than the user’s specified country? Additionally, users can enable or disable this logging feature, and you could have it default to “off.”

    I have multiple WordPress sites hosted on Bluehost, and I just started another one that a friend of mine installed on a completely different server (December 2017). Even the fresh install has this bug.

    Given how this seems to happen everywhere, no matter the server, even with fresh installs, it seems to me that this is a bug with WordPress, not with users’ settings with the web host. Making matters worse, I can’t even add media to WordPress because it keeps on forcing me to crop after I select the image, even if I have no desire to do any cropping. If I exit out of the cropping, the image upload is canceled. if I try to crop, I get an error. So I can’t even upload a single image. This bug is truly debilitating.

    • This reply was modified 6 years, 11 months ago by ostinatofreak.
    Thread Starter ostinatofreak

    (@ostinatofreak)

    Thanks. At first it didn’t work after re-saving the administrator role, I saved just one more time, and for some reason, it worked the second time.

    Thread Starter ostinatofreak

    (@ostinatofreak)

    I was logged in as myself (Administrator access) when I did everything described above, and indeed I’m using Advanced Access Manager (basic) to make it so different members of this non-profit organization can only update their own sections of the website. (My, my, you have good instincts… I feel almost as if a fortune teller just read my palm….) I’m crossing my fingers that you aren’t going to say these two plugins are and always will be utterly incompatible with each other!

Viewing 7 replies - 31 through 37 (of 37 total)