beardedgit

+1

These plugins that load nag messages are becoming more common by the week. Whenever I find that a plugin has invaded my dashboard, and has planted a nag message without my permission, it gets uninstalled regardless of its usefulness.

Like many other plugins, this one gets 10/10 for functionality but 0/10 for manners.

Hopefully the OP’s site has been fixed too.

Mine has sorted itself out… sort of…

I had the “recent posts” Jetpack widget showing post thumbs in the sidebar, I had an inkling that it might be caching the post thumbs so I removed the widget.

Straight away it went screwy, with “bad gateway” errors when trying to load front-end or back-end. After clearing the caches and rebooting, it was no better, so I decided to let it be and get a good night’s sleep before asking the host to fix the bad gateway thing.

And this morning, before contacting the host, I booted up, went to the back-end, and logged in straight away with no probs. Going from there to the front-end also worked, I’ve been shown as logged in all day, no need for the Ctrl+F5, no need to get the host involved at all (unless they found the bad gateway thing themselves and fixed it while I was asleep).

Whatever it was, it’s gone now.

I had tried Ctrl+F5 before I reported the error here but it made no difference to me, probably because I don’t have a login there.

Anyway, it’s not throwing the error now, it loaded OK and I can see your message there regarding the problem.

Sadly, nobody seems to want to jump on this problem. If I hear of a fix I’ll let you know via this support thread. Good luck!

@neilovan:

FWIW, when I click the link to your site, I’m seeing the following:

Warning: require(/home3/toklosh/public_html/soccer-betbrain.com/wp-includes/version.php): failed to open stream: No such file or directory in /home3/toklosh/public_html/soccer-betbrain.com/wp-settings.php on line 29

Fatal error: require(): Failed opening required '/home3/toklosh/public_html/soccer-betbrain.com/wp-includes/version.php' (include_path='.:/opt/php54/lib/php') in /home3/toklosh/public_html/soccer-betbrain.com/wp-settings.php on line 29

Not sure what that means, but it doesn’t look good.

I hope the OP doesn’t mind me adding to this thread, but to the question “Do you know of this ever happening?” I can say that I have a similar problem which started minutes after my installation was auto-updated to 4.7.4

When logged into the back-end all is fine, I go from there to the front-end using the link in the menu-bar, and the front-end comes up and displays me as logged out. Pressing F5 reloads it as logged out, pressing Ctrl+F5 reloads it as logged in, another F5 shows logged out etc. etc..

It’s a strange thing that I’ve not seen before in over a decade of WP blogging.

I disabled all of the 59 plugins which I have installed and which were working fine without conflicts, but the problem was still there so I don’t think it’s a plugin problem. Clearing the cache made no difference.

I consulted my host’s help staff, they downgraded me to 4.7.3 but it has not fixed the issue (although it has fixed all other problems I was having with 4.7.4).

It’s got me baffled. Perhaps it needs a database table rebuild?

https://beardedgit.com

• This reply was modified 7 years, 7 months ago by beardedgit. Reason: Edit: added URL
• This reply was modified 7 years, 7 months ago by beardedgit.

I don’t know if this was ever resolved for the OP but I’m having the same issue, nothing I try will centre the link. It displays and saves centrally in the visual editor but displays left-aligned in the saved post.

Here’s an example post: https://beardedgit.com/?p=17024

If you can fix this I’d be much obliged.

Thanks.

FWIW, I gave up and used WP Rollback to go back to v2.0.3 which still works fine.

• This reply was modified 7 years, 10 months ago by beardedgit.

Hmm…

Now it’s stopped expanding too.

Done.

I’ll just go in there and edit the code myself – I’m not willing to have two sets of nav arrows which are at variance with each other.

Here’s what Firefox’s Inspect Element says about your next/prev buttons on my blog:

I don’t see the logic in associating rel=”next” with title=”Previous post”, and associating rel=”prev” with title=”Next post”.

In fact, here’s how my current theme’s inbuilt “previous” and “next” links work, they are displayed at the end of each single post:

Happy New Year!

“This is the same order, I see on your category page here.”

Bear in mind that posts are displayed in reverse-order of date/time published, not reverse-order of date/time created, and also not in reverse-order of the post number (e.g. ####/?p=16399).

• This reply was modified 7 years, 11 months ago by beardedgit.
• This reply was modified 7 years, 11 months ago by beardedgit.

But look at the order that they actually display on the blog… “One edge done” displays before (earlier than) “Observing Report 16th etc”, and the post after (later than) “Observing Report 16th etc” is “Ferritin downer 2”.

Ultimate case: go to my home page and the latest post (currently “Nobody expects the Spanish Indecision”) is at the top. Click on that post title to open it as a single post. As this is the latest post there is a previous post but there cannot be a next post. Yet the “Previous post” button is inactive, and the “Next post” button links to the previous post (currently “Quantum parcel”).

• This reply was modified 7 years, 11 months ago by beardedgit.