psybertron

Still not resolved and none the wiser why, if you or anyone has any more specific ideas?

Thanks for that. I had seen that article, and another subscriber pointed out that the pingback needs to have the explicit https:// or https:// form to work, not the implicit or relative form … anyway, I have some things to test out now. Thanks again.

Thanks for that.

My immediate interest is in internal self-pings – later posts referring to an older post, resulting in a forward link in the comments of the older post.

Worked successfully for many years.
(Here an example old post with several later links via pingback)
https://www.psybertron.org/archives/11810

I checked the notify attempt / allow boxes were checked (they were). Then unchecked, saved and re-checked, saved – so far no sign of new pingbacks (yet).

I will check with external sites too, but that behaviour too seemed to work previously, but doesn’t recently – same as internal pings.

Also wondered if something new in JetPack or Akismet was blocking? Browsed around all settings, couldn’t see anything relevant.

Here, the test post I made after unchecking / rechecking (no pingback so far) https://www.psybertron.org/archives/16907

• This reply was modified 1 year, 9 months ago by psybertron.
• This reply was modified 1 year, 9 months ago by psybertron.
• This reply was modified 1 year, 9 months ago by psybertron.

The stats are there in JetPack / WordPress.com – the problem is the links to stats pages in the WordPress dashboard for the site (and the 48 hour icon in the top ribbon) fail to return the stats.

OK, looks like that’s fixed it. Thanks

Ah, OK. Wondered if there was also some deeper cacheing going on. I’ll give that a try. Thanks.

The most obvious upgrade would be to ensure the member creation dialogue allowed you to select from existing users and add if new. No?

I read the instructions first, and again and again!
What the instructions don’t mention is any relationships between these “members” of the site and “users” of the WordPress installation, names, unique emails and synch’ed pw’s etc.
The error messages were invisible. (I see this dialogue is actually adding WP users – so better integration of the UI would help – and at least the wording in the dialogue. Anyway eventually sorted after a little trial and error when I found the error message.)

Phew. Sorry. Fixed itself after 10 mins.

I see now, the actual query link remains real whatever form of permalink you choose. (I was thinking terms of changing links). And I’ve experimented on a couple of less massive sites, all seems to work fine.

Ready to activate WP-Super-Cache on my main site. Thanks.

Not sure I understand. At which point in that process are you switching the WP permalink setting? When was the page ?p=1725 itself published?

May have to try on a test / expendable site.

And all updates executed OK, and dashboard / post-editing all functioning. Thanks again.

Phew, I’m in! Thanks for your help. I know enough phpMySQL to be dangerous. (I shall now do all WP updates …. before I do anything else.) Many thanks for your help.

In fact I should add – the “wp_users” table (like all tables in this DB) now renamed “wp_lkemwt_users”

OK, thanks I see the problem – I’ve been hacked – many mysterious users. The lone user that was my admin user, has password and email that don’t work for me …. so, can I juts delete the rogue users, and edit my own details at the DB level?