AstroNerdBoy

Error

SQL query:

ALTER TABLE wp_XXXXX_top_ten ADD PRIMARY KEY(postnumber, blog_id)

MySQL said: Documentation
#1062 – Duplicate entry ‘20640-1’ for key ‘PRIMARY’

• This reply was modified 6 years, 4 months ago by AstroNerdBoy.

Still no changes in Visit times, though the Daily Visit count still seems right.

For the wp_XXXXX_top_ten_daily table, the DROP PRIMARY KEY worked (I didn’t grab the text for that).

Error

SQL query:

ALTER TABLE wp_XXXXX_top_ten_daily ADD PRIMARY KEY(postnumber, blog_id)

MySQL said: Documentation
#1062 – Duplicate entry ‘16417-1’ for key ‘PRIMARY’

Error

SQL query:

ALTER TABLE wp_XXXXX_top_ten DROP PRIMARY KEY

MySQL said: Documentation
#1091 – Can’t DROP ‘PRIMARY’; check that column/key exists

Remember what I said before.

Under “Indexes” for “wp_<some_ID>_top_ten it is saying, “No index defined!”

And then there’s this.

Error

SQL query:

ALTER TABLE wp_XXXXX_top_ten ADD PRIMARY KEY(postnumber, dp_date, blog_id)

MySQL said: Documentation
#1072 – Key column ‘dp_date’ doesn’t exist in table

• This reply was modified 6 years, 4 months ago by AstroNerdBoy.

How was it difficult before?

> It’s now definitely confirmed that the Gutenberg editor will not be opt-in as suggested by you & others.

It is this “FU” attitude that keeps my rage levels off the scale.

I agree with you completely. On my sandbox, the only block thing I used was the classic, and it is not as good as the original editor IMO.

> TINY MCE Advanced

I’m going to look that up. Will it be available for use when Gutencrap is rammed down our throats? (I’m in a foul mood after spending hours screaming in rage at trying to do what I used to do easily in the original WP editor.)

Yeah, I concur. I have nearly shattered every bone in both hands pounding my desk in rage at the stupidity that is Gutenberg. I’m glad it is currently only polluting my sandbox, but I now dread the day this travesty is rammed down my throat.

What’s “awesome” is that the classic block doesn’t work as well for me as the current WP editor. Most of the time, I was unable to select multiple images for upload. Most of the time, I could not insert an image into my articles where I attempted to. 90% of the time, the image would insert at the top of the article rather than where I wanted it.

I hate it that the old text editor for modifying HTML is buried. Obviously, the thought here is that WP should do everything and nothing should be in my hands in terms of HTML.

The two tables I mentioned are all that’s out there. I’ll have to run those commands, once I figure out how to do that. (Never manually done SQL commands for my site.)

Sorry for the delay.

> If you have access to phpMyAdmin when you browse the Structure of the table you can see the various indexes at the bottom of the table – see the wp_top_ten and wp_top_ten_daily tables in your database.

Under “Indexes” for “wp_<some_ID>_top_ten it is saying, “No index defined!”

For wp_<some_ID>_top_ten_daily, it says the keyname is PRIMARY and the type is BTREE.

Query variable based is set (or should be).

Also, worth checking your database to see what the structures of the primary keys are as something that button doesn’t work (I’m not sure why as it has worked in all my tests)

I’m somewhat ignorant in MySQL, so how would I determine this?

Words cannot describe how much I despise Yoast right now. I didn’t realize this was broken right away because I handle my comments on the backside. But readers of my blog who weren’t using the mobile version of the site started complaining that they could no longer reply to comments. I verified this on all PC browsers, so I went to my sandbox and even when all other plugins except Yoast were removed, the reply functionality was still broken.

It irritates me to no end that someone thought, “Yeah, lets remove reply functionality for some sites ’cause ‘reasons.’ That’s awesome development by half!” And then the real, awesome response on the part of Yoast is for us to modify our child themes (or make them if we don’t have them) to include a line of code.

The problem may have been Jetpack. Several Jetpack features stopped working for me until the most recent upgrade they put out. Today’s post did auto-publish and Jetpack appears to be working again.

That aside, I *think* my issue is resolved. Thanks for looking into this for me. ^_^

• This reply was modified 8 years, 4 months ago by AstroNerdBoy.

I just updated to the latest version of Jetpack and that resolved the issue. Suddenly, the icon flooded with alerts for older comments, but it is flagging them as today. The comments are still flooding in so I’m presuming this will eventually catch them all up.

Thanks for the help!