Hedley

Hi James:

I’ve already updated, and it looks like you fixed it.

Thanks for the great service!

I had a problem today in which the “link” button in my visual editor would not work on a new site I was working on. I deactivated all of my plugins and it started working again, so I then turned the the plugins on again, one by one. Everything was fine until I reactivated IWP, and the link button stopped working again.

At the time that I had this problem, the IWP plugin was activated, but I had not yet set the activation code in the IWP Manager, so the reminder was displayed at the top of all admin pages. Subsequent tests have shown that this condition, for some reason, prevented the link entry popup from functioning (though popups from other, non-core, plugins worked fine). I tried this with both 1.3.4 and 1.3.6 IWP versions and the results were the same.

Not sure if this matches your situation, but there it is, if it helps.

H.

Okay, just because I’m the easily distracted sort, I tried a couple more experiments:

• Installed GoodReviews on another site (WP 3.9, also running Weaver, no shortcodes used.) As soon as it was activated, admin panel icons disappear on public side only – in Firefox, but not in Chrome.
• Installed GoodReviews on another site (4.0-RC1 running Twenty Fourteen theme, no shortcodes used.) As soon as it was activated, admin panel icons disappear on public side only – in Firefox, but not in Chrome.

Hi James:

Thanks for the quick response.

My reponses to your other questions:

• Issue occurs on all public pages (as I am currently site building, I presently have a GoodReviews shortcode on only just one page);
• I was already using the shortcode with the bookinfo parameter set to “off”;
• Here is the shortcode I have been using: [goodreviews isbn="9781770864016" grminimum="3" buyinfo="off" bookinfo="off" border="on" width="475"] I also tried using the base code ([goodreviews isbn="9781770864016"]);
• I tried disabling all plugins except GoodReviews, and the issue still occured. I then also disabled my Weaver II child theme and enabled the default 2014 theme, still with only the GoodReviews plugin activated, and the issue still occurred. I can’t think of anything non-core else that might be affecting the admin bar.

Now, the first thing I did earlier – after clearing all of my browser’s cache and history, of course – was to try viewing the site in different browsers. I use Firefox, primarily, for WordPress work. First I tried it in Firefox using a different profile (one that had not visited the site url previously). Issue persisted. Then I tried it in Chrome, and the problem was happening there as well.

Somewhere in the last half hour, however, the issue seems to have vanished in Chrome (even with the plugins turned back on), and now only persists in both Firefox profiles. Perhaps it’s a browser issue, or maybe Chrome compensates for something that Firefox does not… It seems somewhat cache related, though maybe that wouldn’t explain why it happened in the first place…

That’s great, I’ll give the override a try.

Thanks for the quick and thorough response!

H.

I experience something similar: I have the timeout set to 60 minutes, and routinely take more than 60 minutes to work on longer posts (we tend to publish more essay-like posts than asides). Despite the fact that I periodically click “Save draft”, I still get logged out automatically 60 minutes after my last login. Since the setting is called “Idle timeout”, I would have expected that the plugin would only log me out if I’m actually idle, not if I’m using the interface (ie: frequently clicking “save draft” ought to be evidence of non-idleness). I have since disabled the option altogether. (I prefer not to copy-and-paste from Word or LibreOffice, as the formatting that appears in the subsequent html is nightmareish, contrary to WordPress’s claim that it gets cleaned up automagically).

If detecting a non-idle login is beyond the scope of the plugin, perhaps it would be best to rename the setting from “Idle timeout” to “Automatic logout”, and indicate that all logins will be logged out regardless of activity.

Otherwise, I like the plugin!

No, in the end I used the paid version of Event Espresso for that job.

H.

Thanks, Austin.

I’d been using Post Notification on several sites until I also encountered problems installing on new sites. This solution worked perfectly for me:

https://www.ads-software.com/extend/plugins/subscribe2/

The plugin Tweet Blender seems to work, and has numerous setting options, some of which relate to API calls.

Rather than have HG whitelist specific rules, @hledwards, I recommend using the live chat web support. They can watch their logs as you test the fuctions that aren’t working, and with luck catch whatever it causing the problem. I’ve found their web support pretty cooperative and helpful.

Interesting suggestion, Nick. I haven’t been thinking about this project much since I posted, but I’ll see if I can give your solution a go. I’m hardly a scripting whiz, but it might be a good learning experience!

Thanks!

H.

I had this problem suddenly arise on just one site in a HostGator reseller account. I tried the suggested theme-switching thing, but it didn’t work.

I contacted HG and suggested that perhaps the php.ini needed updating, as @pafoster suggested, but the tech replied with:

“This is not due to php.ini. This is due to hitting Rlimits on the server. I have raised the rlimits to allow the user to use the full 256 MB that we allow.”

This seems to have solved my problem.

Also want to reiterate what @gnarzilla wrote. I’ve had a Hostgator reseller account for several years now, and on the rare occasion that I’ve had problems, they’ve provided excellent customer service and have solved my problems very quickly. In fact, I’d say that I can’t think of a single online business that has service as good.

H.

Okay, Hostgator fixed it. Just a couple of more rules that had to be whitelisted. Apparently they were:

999022
340594
340162

H.

Okay, using the above information I was able to connect Social to FB and Twitter after I contacted Hostgator and had the rule whitelisted. That works.

What isn’t working is when a reader tries to click on “Sign in with [Twitter or Facebook].” Rather than sign in, the pop-up window simply displays my home page with this URI:

https://www.mydomain.com/?social_controller=auth&social_action=authorize&target=https%3A%2F%2Fsopresto.mailchimp.com%2Ftwitter%2Fauthorize&post_id=1791

I’ll try talking to HostGator again about this, but has anyone experienced this separate-but-possibly-related issue? If so, was it a different mod_sec rule?

Thanks,

H.