synthezoid

I found the problem. I changed the name of my plugins folder for security reasons, using these in in wp-config.php:
define('WP_PLUGIN_DIR', '/home/user/html/wp-content/[new folder name]');
define('WP_PLUGIN_URL', 'https://mydomain.com/wp-content/[new folder name]');

It looks like your backup plugin has the name of the the “plugins” folder hardcoded into it instead of getting it from WP_PLUGIN_DIR or WP_PLUGIN_URL, so it can’t find the .js assets files if the name of the plugins folder isn’t /wp-content/plugins.

Not going to complain that much about a free plugin, but I do like this plugin, so personally, I’m not crazy about having to choose between using it and having my custom plugin folder name, as is allowed by WP configs. I’d love it if you wanted to fix this.

Thanks for the quick and informative answer. I think your performance concerns are valid, as I looked into this I realized the idiosyncratic under-the-hood architecture of how WP handles these things isn’t so great. I just went ahead and did the work to manually copy all the alt tags into the Description fields, ultimately it was the least-bad solution.

I’d say, given the performance issue, maybe this isn’t such a high-priority request after all. It’s unfortunate that things are the way they are, but the fault is WP’s, not yours.

I could maybe imagine a complicated scheme where maybe you cache a block of alt tags as transient or something to save calls, but I could see that being a lot of complicated work for not much benefit, and still not a guaranteed performance gain, as you never even know when transients will get cleared.

Two months without a reply… great.

I have the same problem and the same question as has gone unanswered above. This CDN is fast but the service and configuration are extraordinarily confusing and difficult to understand, and none of the documentation is much better.

I am done with setup. I have set everything up. And still, it says “Main domain not generated yet”. I only have one domain, there is no “main domain”, just the one website, which is completely set up.

You provided a link above to a block post that said “navigate to CDN > Auto QUIC.cloud Setup” but Auto QUIC.cloud Setup does not exist on the CDN tab. There just isn’t anything there with that label.

It also says “For online services to work correctly, you must allowlist all QUIC.cloud server IPs.” but never tells me what “allowlisting” is or how to do it.

You might want to point out that Optimole is not compatible with cloudflare when their “Bot Fight Mode” feature is turned on. You cannot set up a WAF rule to bypass Bot Fight Mode, and it blocks connections from Optimole, preventing connecting Optimole and the WordPress back end. The only option is to turn Bot Fight Mode off. This took me a while to figure out, your documentation really should not say that it’s possible to add a rule to cloudflare’s WAF to allow Optimole’s agent. If Bot Fight Mode is on (which is the default) then it’s not possible.

• This reply was modified 11 months ago by synthezoid.

Thanks, I appreciate the response. I don’t know how I missed that, d’oh! I’ll try again with the critical css plugin disabled.

It changed again. I haven’t changed a thing since the above comment, and now, the custom attributes are back, in fact, just by reloading, they’re even in the final page… they’re not getting removed at all.

Every time I reload the page it functions differently.

No, belay that, the console logging changed again. The plugin is very clearly now removing my needed, intentional attributes BEFORE the plugin code is done running.

Unless it changes again.

I don’t know how anybody gets any constructive work done with wordpress. This is truly maddening. I just want to be able to modify the plugin’s output slightly and not have a computer “help” me by deleting what I added to completely ruin my changes

Wait, never mind, it’s not your plugin. BugFu or some other plug in broken, what gets logged to my console keeps changing without me changing anything. Now it looks like the shortcode is outputting correctly and some other process is changing my code.

So glad I chose wordpress… with any other system, I might get some productive development done on my website, and not just spend all day and all night troubleshooting weird, nonstandard and unpredictable behavior!

• This reply was modified 1 year, 2 months ago by synthezoid.

You know what, forget it. Apparently this post is some sort of danger to the boards so this is going to sit in “moderation”, so I have to sit on my thumbs waiting for it to even post, let alone get an answer. I could code my own plugin from scratch far more quickly than it looks like getting an answer here is going to take. I’m just going to do that. You don’t need to answer this, I’ll have uninstalled the plugin and probably written my own before you even see it.

I do hope in the future you’ll make it so your plugins default to not overruling programmers’ coding choices. Best of luck.

One exceptionally maddening thing about this is it’s intentionally inserting incorrect HTML. I’m using <details><summary> tags, and when I add the boolean “open” attribute to <details>, it is being converted from a boolean tag to an attribute with a value.

This is a prime example of why it’s a terrible idea for software to be allowed to overrule a living programmer’s decisions. There is no reason at all why if I enter correct code it should be automatically changed so as to be incorrect, without any way for me to tell it not to.

Take a look at the “gap” in your browser’s inspector. It looks like this plugin inserts a blank <li> element before the shortcode’s output, which might be appearing as a blank first menu item.

EDIT: Confirmed. I created a shortcode with output that is wrapped in “<!– START SC –>” and “<!– END SC –>” tags. This plugin added extra <li>…</li> tags around the “<!– START SC –>”. I’m not sure but this appears to be because it calls WordPress’s core menu walkers, and assumes your shortcode isn’t already outputing menu-ready content. Frustratingly, it doesn’t produce consistent classes or ID, they depend on the surrounding elements, so it’s harder to hide this extraneous <li> with CSS.

Question, I see this post is over a month old, is this plugin still maintained?

• This reply was modified 1 year, 2 months ago by synthezoid. Reason: found more info

Yes, I’ve tried all variations of the sort order settings. Maybe I wasn’t clear. The two marked “folder of documents” are subfolders, not documents.

I was able to fix this myself by going into the plugin and editing your sorting function to stop looking at whether $var->{.tag} was “folder” or not (well, actually I just replaced “folder” with “fxlder”.) However, if you update the plugin, obviously this will break… it would be great if there was a checkbox for this.