tf5_bassist

Thanks!

Thanks for the reply. The CSS code worked, but I also needed this one to update the border color on the left-hand date block as well

.ebec-minimal-list-wrapper .ebec-list-posts.style-1.ebec-simple-event {
border-left: 4px solid #5bbd8a;
}

Oddly enough the border is on the parental div, not the same one for the color block haha.

I found that the offending plugin was Rank Math. Unsure why yet, still troubleshooting.

But I have turned off each module that is active within Rank Math one by one and none of them allow the indexing to work.

• This reply was modified 1 year, 5 months ago by tf5_bassist.

Thanks!

Thanks for the response, no, it doesn’t seem to only be the OpenAI API key input, it also affects the Pexels API key input and the Google Images (API) API key input.

But I think I figured out that it’s actually Chrome’s autofill that was dropping in the password based on the domain of the site. After I deleted the saved password from Chrome’s manager, it’s no longer overriding the previously stored password. Not sure how to really go about addressing that, but at least I’m fairly sure it’s not the plugin or 1Password.

Sorry for the shitty troubleshooting and rushing to submit a ticket lmao.

Ahh, it’s a 1Password issue where it’s autofilling where it thinks is a password. There’s now an attribute data-1p-ignore that 1Password can recognize to tell it to not auto-fill. Could this be applied to the API fields in the plugin? Thanks!

Nevermind, I figured it out. I’m in transition between password managers and didn’t notice it was auto-filling despite not having a username field. Guess I need to find out how to stop these fields from autofilling passwords.

Thanks for the reply! Having an option to disable the Offers would definitely help with the housekeeping, appreciate looking into it!

For the description, yes, on one post I did not have this enabled when I thought I did. I’ve turned it on for the affected post and populated it.

On the Product Snippets GSC page, there was a “review” field that was missing, but I’m not sure what that is. I have everything else populated to the best of my knowledge.

Ahh, gotcha. Thanks for the info!

Wordfence lists it as Abandoned now, just a heads up.

That’s odd, for sure. These, however, were categories that I had literally just created. It seems to be caused by an overlap in category termIDs and WooCommerce custom product attribute termIDs. At least based on my rudimentary knowledge of what I found.

Since these can’t be deleted via the UI because of the missing checkbox and Delete link, I went into phpMyAdmin to a) delete them and b) try to figure out wtf.

I’m not terribly familiar with the db structure used for taxonomies, but I was able to find my terms IDs and confirm that they were showing the correct terms taxonomy types. Interestingly enough, the parent of the terms was actually reflecting the expected parent term ID, but they wouldn’t show this in the Categories UI.

I don’t see anything in the terms DBs (termsmeta, terms, term_relationships, term_taxonomies, etc) indicating permissions or anything like that.

I tried to use a functioning Edit link with the termID of a broken cat and got this error page:

You need a higher level of permission.

This is occurring even with all plugins disabled. So I deleted all of the broken categories from the db and noticed they’re still showing up. I cleared my RunCloud (server is on RunCloud and running nginx) cache again and they disappeared.

After this, I tried to create a cat and it worked fine. I deleted and tried again and it failed. I cleared the RC cache and it worked again. I was finally able to make the correct category I’ve been trying this whole time, but now I noticed there were TWO identical terms in the db, with IDs 948 and 949, the latter being the one in the UI.

Attempting the URL trick on 948 returned an error stating that it was already deleted (weird). Just out of curiosity, however, I checked the other dbs for termID 948 and found that there was a term_taxonomy entry referencing termID 948 with a taxonomy type of pa_weight.

It appears that, for some reason, terms are being created with identical IDs of various WooCommerce terms for product attributes. That’s… not good.

I still have WooCommerce installed from way back when, but it’s disabled since I’m not currently selling. I may reenable it down the line though.

Isn’t WP supposed to not create categories with pre-existing term IDs? Or does this only occur when that plugin that created the term ID is active?

It’s all very confusing.

I disabled all of my plugins again and, after a few failed attempts, categories started creating properly. I’ve been activating plugins one by one, refreshing the categories page, and adding a new category as a subcategory, and if it’s successful I move on to the next one.

I got to a failure and deactivated that plugin again to test, and it’s still failing. Tried a few more tests with failures. I deactivated the plugin before where it worked fine, and it’s still failing.

This really makes zero sense and I’m losing my mind here.

Edit: After disabling a few more plugins, it was still failing–until it wasn’t anymore. Nothing changed between failure and success, it just started working.

• This reply was modified 2 years, 4 months ago by tf5_bassist.

Well, I just installed Firefox and am seeing the same behavior there that I saw in Chrome and Edge. Meanwhile, Safari is still 98% functioning. This keeps getting weirder and weirder.

Alright, I’ll copy-paste all this over to a ticket there, thanks.

I’m on WordPress 6.0 and using PHP 7.4 on a 2 vCPU 4GB RAM Vultr VPS with RunCloud managing the VPS.

I have a bunch of WAV files that I’ve been trying to use, as these are for some mic tests. They’re all 24-bit 44.1kHz WAV files, between 7-12MB in size. The last time I was testing a microphone with similar files I had the same issues but I had less files to work with and just powered through.

But I believe I recall how I worked around the issue last time. Which brings me to…

I forgot to mention browser info, I knew I left something important out. I’m using Chrome, which is updated. I’ve tested with Edge and it does the same thing. I have barely any extensions in Edge, either, because I just rarely use it.

That said, I forget that I have Safari, because who even uses it lmaooo.

I tested in Safari and it actually works much more normally there. The timeline inspector shows a constant stream of javascript events, but the Network waterfall looks pretty much identical to what it did in Chrome.

It seems that Safari is able to process the Ajax requests better than Chrome. I believe this is how I got around this issue the last time I had a review with audio samples, it’s just been like.. 8 months since then.

But it still doesn’t resolve the issue that I’m experiencing in Chrome. And I’m not able to actually play the audio files in Safari within the post. All of the audio blocks show “Error”. But at least it’s something to go on.

Any thoughts on Gutenberg and issues with rendering engines?