WordPress 5.4.1 and AWS

  • Does the WordPress AWS plugin work at all with WP 5.4.1? I have many days invested in trying to get the plugin to work. I have dealt successfully (I think) with the absurd AWS security overkill and AWS appears to be working correctly. I have too much invested in making this thing go and don’t want to throw in the towel, but that may be necessary.

    The only thing you can set or change in the entire plugin is the User name. When the secret key is entered and saved it is truncated to about half its length.

    What on earth is going on?

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

  • For what it’s worth, after the plugin update to version 4.x – bulk updates don’t work, which has now over-spilled into website page revisions not updating either.
    – All compounded by the fact that there isn’t a button to force updates, resulting in the mp4 version after a document has been updated, being of the old web-page.

    There was an issue a while ago whereby one poor chap was running up data charges at an astronomical rate, $45 a month and rising; never did find what happened to that problem.

    The Plugin Author is apparently aware of these issues, but not fixed them as yet.

    Personally it’s got to the point where I’ve disabled the plugin because I simply can’t get it running properly, and like you: I have spent far too much time and effort on it that I’m not prepared to uninstall the thing, but I will if the next update doesn’t fix these nagging issues.

    Currently I’m just watching to see if these problems can be resolved at some point in the future. I’m still on the free band, (and yes: it was overly complicated to get an AWS account), but I will delete it soon, for basically not being in charge, and living with the innate fear of running up a massive bill: to which I can’t afford.

    Not really a helpful response, but at least you now know that you’re not alone.
    Stay safe.

    Thread Starter cedialogs

    (@cedialogs)

    Thanks for your response. It looks to me that most or all of the problems with the AWS plugin are on the plugin side, not the AWS side. With some charity, the AWS setup was a success (as far as I know) despite its having security that was designed for the CIA. This plugin’s problems are a tragedy since there are many WP plugins that are stunningly good pieces of engineering.

    After going through hundreds of plugins, AWS is the only one that does not work even a little bit under any known conditions. If it weren’t for many other excellent plugins, WP would be engineering rubbish.

    Being an author of sorts, I wanted to spend my time on generating content and not on constantly having to reverse-engineer the ill-thought-out basic design of WP itself and debugging flawed code. I have spent almost as much time outsmarting design and coding bugs as I have on building content.

    For instance, the WP design’s fragmented modularization precludes having an orderly, centralized control panel, and using absolute links where relative links would do creates much grief in staging and relocating sites. Automattic Airline seems to have implemented many great ideas in building and flying its Boeing 737 Max 8. BTW, why is automattic spelled the way it is?

    After 7 spending years, part-time, learning how to outsmart WP’s design flaws I am finally (except for AWS) spending most of my time on content and presentation issues.

    Thanks again for your response. Here is hoping that the AWS plugin can be made to work and that our efforts will not have been wasted.

    Stay safe, and hope that the likely second wave will not happen.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘WordPress 5.4.1 and AWS’ is closed to new replies.