riw

What you are doing here is refusing to support software I paid for. Two points.

FIRST, I paid for your software.

SECOND, I am not asking you to design my web site. I am asking you to fix two very specific defects in your software. That you refuse to tells me a lot about your competence as a company and as a person.

I will now write a complete review of the uninitialized variables and process failures in your software and post it publicly.

I have changed my rating to one star because about 75% of the coconut jobs now fail. If this is not going to work, remove coconut support entirely–OR FIX IT. I am not paying you for a support ticket to fix something that is completely not related to my web site, my local computer, or my videos.

I would understand more completely if I were using the open source version … but I chose to pay for this plugin specifical so I could support the work y’all are doing. To receive absolutely no support, even though I was trying to do the right thing, unless I pay more, is more than a little irritating.

What’s the point of paying to use the software if I must also pay for support?

As for the two major defects … I’ve stripped my site down to a bare minimum, and the blank page when trying to upload a new video persists. The reported problem is an uninitialized variable, which does not seem like it has anything to do with any other plugins. Further, if I change the order in which I do things by going through specific “coconut screens” first, the error is no longer present. This clearly indicates a defect in the plugin someplace.

The second major defect I’m still facing is consistent failures in the coconut processing. This always occurs after the video has completely uploaded, is being processed by coconut, so the problem has nothing to do with anything local to my computer or my web site. The error coconut always returns is that the url is not accessible, and it always happens about five minutes after coconut starts processing the file. There is clearly a timeout problem in the connector between coconut and digital ocean that needs to be found and fixed. This error happens for about one in every four files I try to upload.

The result of these errors is a re-upload, and paying coconut to process the file twice. The re-upload requires a file name change, which then messes up my file naming. Since I’m working on a training site, it is important videos are sorted in the correct order. Blowing up the file names makes this impossible–and there is absolutely no way to rename the player once coconut has processed the file.

Again, this is decent software, but it has a lot of defects and problems that need to be resolved before it is ready for professional use.

If this is possible in gutenberg–without recreating it on every page and post–can someone explain how to do it? Can the header be moved to the left side of the page?

Selecting some other size just replaces wp-full with another size class … Is there any way to have it not insert any size class at all?

The plugins do not matter … To give an example, when I insert an image, wordpress inserts …

<img src="https://rule11.tech/wp-content/uploads/wr092520.png" alt="" width="399" height="160" class="alignnone size-full wp-image-12573" />

The wp-full tag forces the image to be displayed full-size in some places where I don’t want it to be displayed full-sized. The wp-image-xxx tag seems to cause other problems in other places. Troubleshooting the plugins by disabling them all on a production site, then re-enabling them one at a time, then talking to the plugin owner to ask them to ignore these tags — which I suspect, btw, they cannot ignore, because wordpress is going to render images with these tags a specific way regardless of what any individual plugin might want to do — would be really, really time consuming and painful.

What would be MUCH better is if wordpress had some way of simply not adding these classes to every image inserted into a post. Is there any way to turn wordpress’ auto-insertion of these tags off?

/r

Thanks for the tip on finding the rather well hidden source code. Note that since a long time ago, if you switch to the visual editor, any custom css/html you place in the post while in the text only mode will be removed by wordpress. I tried your suggestion with the “block editor” (which needs to be renamed, because it’s not an editor), and it does the same thing.

For now, I’m going to leave off this thread and focus on finding another solution, as it’s obvious those who care have already left the conversation. I will begin by canceling my wordpress.com professional account, and I will urge everyone I know who uses wordpress to do the same. If wordpress.com dies, perhaps the original project will be returned to the community, where it can be brought back to its original principles.

@ipstenu — I am using the classic editor plugin for right now, while I work out what platform to move to. I have read the statements on the part of wordpress about discontinuing support for the classic editor over time, and forcing people to use the new page builder interface, which also means being forced to use react, and hence putting a full development process in place for simple changes.

I understand wordpress is trying to “move into the big time,” and compete with simpler platforms. In the process, however, it is becoming more of “me too,” and less of an interesting platform. It is becoming more of a place for site developers, and less of a place for individuals who like to build a blog that is both simple and unique. In essence, it is moving away from being a local boutique to being mcdonald’s — serving up bland overcooked (but pretty) junk instead of real products.

I’m certain there’s a lot of money to be made in this change. But making lots of money is not the same thing as building and supporting a community. Whether or not this is good for wordpress as a company — and that is part of the problem here — a company who wants to takes what they perceive to be a captive audience down a path that will extract more money from them — is one question.

However, it’s clearly bad for the community, it’s bad for the ‘web, and, it’s ultimately going to be bad for wordpress. There is money to be made in exploiting the platform, but once people get sick of being exploited, they will move on to something different that does support a real community, rather than just professional developers.

I would suggest you both brush up your resumes, or save the tons of money you’re going to make in the transition. This is a train that will eventually crash, and is going to harm a lot of people while you’re driving it down these tracks. But, whatever — people don’t matter, just the money, right?

You want to support the community? Instead of creating a forcing funnel that turns the temp up on the pot slowly, give people who don’t agree with your vision the tools they need to smoothly move to another platform. This, at least, would be honest to the community you are exploiting for monetary gain.

Ummm… I’m already working on dumping wordpress, and I know a ton of other people who are, as well. Beyond that, this is not “just a technical forum…” It specifically says “complaints” at the top.

I am complaining. A lot of people are complaining. Apparently wordpress does not want to listen — and we know what happens to companies that stop listening.

It might not “stop,” but it will, ultimately, make wordpress into a medium look-a-like, which will destroy the user base. Which just means wordpress will stop being a widely used platform for anyone who actually cares about what their blog look like. So, in a sense, it will “stop,” because wordpress will no longer be a platform anyone cares about.

I will spend the three years looking for an alternative to wordpress, I suppose — because gutenberg is clearly focused on the full time coder and “site developer,” rather than the average person who just wants to run a blog.

It is Appearance->Editor that I am complaining about — it is a poor way to edit css.

Thanks — both of these worked. I put the test code in the footer so it shows up on my site. It might actually be nice to have a widget that displays the is_ssl() state for easier testing, but this works.

??

Russ

Hmmm… The fix wasn’t in my wp-config.php, but when I tried to put it in there, the site became inaccessible. I tried disabling wordfence, but the problem persists. Can I check to make certain is_ssl() is returning true somehow so I can toss the ball back into the Caldera forms camp? In other words, is there a simple way to tell?

Thanks!

Russ

So, in other words “we don’t see anyone else having this problem, so we don’t believe it’s happening, and we warned you, so its your fault.” Yet more reasons not to use this plugin. After diagnosing the problem, what the plugin did was to zero out the htaccess, wp-config, and some other files. We had to restore those files to bring the site back up.

As for other users flooding the forum — no, they’re just silently shutting down the plugin. I know I’ve moved off it for four or five sites, and several other folks have said they have similar problems, and have moved off the plugin.

But don’t bother trying to troubleshoot it, just claim the problem doesn’t exist, and say, “we warned you.” That’s so very productive.