quantaweb

Thanks for your reply Bob. It does sound like a caching issue, doesn’t it? But we’re not using a caching plugin, so it’s a little strange.

Thanks again!
Denise

Well, that is strange. After over an hour of struggling with the issue above, all of a sudden it started working. I did log out, then back in after that – maybe that’s what it took?

Thanks for this beautiful plugin!

This is happening for me, too! Otherwise I love the plugin – so I hope it can be fixed.

Yeah, I don’t understand what’s going on.

The only thing I use that affects logins/logouts is iThemes Security, which does track if people try to hack into the site. It bans them from the site after a number of attempts. But they are never able to log in.

I’ve been using iThemes Security and Simple History both for quite a long time and this is new behavior. But something must have changed, somewhere.

This is what I get when I click the date on one of the “logged out” entries (which never have a corresponding “logged in” entry).

This is just one (new just now) “logged out” entry:

Key Value
id 1276
logger SimpleUserLogger
level info
date 2015-03-03 21:25:39
message Logged out
type
initiator other
occasionsID abfee0819f198c2782490c4ccb735367
subsequentOccasions 1
rep 1
repeated 1
occasionsIDType abfee0819f198c2782490c4ccb735367
context_message_key user_logged_out
_message_key user_logged_out
_server_remote_addr 108.162.254.149
_server_http_x_forwarded_for_0 94.153.10.213

This one had 239 logged out similar events:

Key Value
id 1108
logger SimpleUserLogger
level info
date 2015-03-03 09:49:28
message Logged out
type
initiator other
occasionsID abfee0819f198c2782490c4ccb735367
subsequentOccasions 1
rep 1
repeated 12
occasionsIDType abfee0819f198c2782490c4ccb735367
context_message_key user_logged_out
_message_key user_logged_out
_server_remote_addr 108.162.254.149
_server_http_x_forwarded_for_0 94.153.10.213

Thanks for any insight you can provide! (And, for your terrific plugin.)

all best,
Denise

Wow! That was fast…the plugin was just updated and all’s remedied. Thank you!

Glad I’m not the only one! I love this plugin, too and use it on all my sites.

I am experiencing the same thing after updating today. There are actually two sets of share buttons, in different places.

You can see an example here:
https://www.emptymirrorbooks.com/features/poems/poems-by-sarah-ghoshal.html

Before the update, only the first set was there (and that’s where I wanted it).

Never mind! We figured it out.

qaws, did you ever figure this out? I don’t want to install another plugin, and don’t know how to change the default time in the database.

I’m having the same issue, would really like to get it working —

I did that several days ago, but haven’t had any reply. Sure hope it’s resolved soon! My inbox s full of these messages.

Hi! I’ve been using this plugin for well over a year, and can answer your question.

It will not publish posts with draft status. Until you shift post from “draft” (or “pending”) to “scheduled” status, they will remain unpublished drafts.

This is so even if a draft is on the calendar. If that date & time comes and the post is still in draft status, it’ll remain unpublished.

I use the calendar just as you describe – as a visual planning tool. I can easily see how many posts I have planned for a given week, and on which days and it’s easy to drag them from one date to the other until I’m satisfied. When I have it all figured out I move them from “draft” to “scheduled” status.

You can move a post from “draft” to “scheduled” status right on the calendar, if you like. Just go to the calendar, and mouse over the post’s title. Choose “quick edit” and you’ll see a drop-down where you can choose “scheduled.” You can also choose the time of day it’ll post.

(Alternatively, you can still schedule a post on the post’s editing screen, just as you would if you didn’t have this plugin.)

And, of course, you can always skip the scheduling altogether and just manually click “publish” whenever you’re ready to do so.

I hope this helps!

I’m getting this error repeatedly – and we’re not even using minification. What a mess.

I posted a question about this several days ago still it’s not been answered.

Did you ever figure this out?

We installed W3TC too and I’m not sure of the cause but our non-www address isn’t working any longer either.

I’ve encountered the same issue and would love to know what this indicates. Thanks!