dblinks
Forum Replies Created
-
Forum: Plugins
In reply to: [Visitor Maps and Who's Online] Deprecated functiongreat, thanks!
Forum: Plugins
In reply to: [Simple History – Track, Log, and Audit WordPress Changes] Unknown UserOauth2 consent when signup/login with Gmail – Google API via the Ultimate Member Social Login Plugin.
It recognizes user and prints name/login when:
logger Plugin_UltimateMembers_Logger
Ultimate Member may change some usermeta or other important value. Looking at the logs it appears when a user signs up without Oauth they are the ones not recognized.
I will ask them about the possibility to investigate.
thanks
stuCorrection: NGINX Ships with ngx_http_realip_module by default. On a vps in http directive nginx.conf:
include conf.d/*.conf; include /etc/nginx.custom.d/*.conf;…and create a file in nginx.custom.d named anything ending in .conf and set the rules.
Sorry for the late post.
stuI’m sorry I also use a plugin called “subscriptio” which is not a repo gpl item. I will have to check with the developer.
thanks for your time.
stuForum: Plugins
In reply to: [Simple History – Track, Log, and Audit WordPress Changes] WoocommerceI’m sorry, I do see it for woocommerce product changes. Just one of our Authors feed wasn’t showing up I thought she had made changes and had not. My bad.
Fantastic Plugin
stuFor Nginx webserver you can use the Module ngx_http_realip_module works especially well if you are behind Cloudflare or other reverse proxy.
So you either put your origin server ip in a custom conf file loaded by or in nginx conf or:
For a Cloudflare type setup
In a custom folder (include) by nginx we would put (after loading the module):
set_real_ip_from 103.21.244.0/22;
set_real_ip_from 103.22.200.0/22;
set_real_ip_from 103.31.4.0/22;
set_real_ip_from 104.16.0.0/12;
set_real_ip_from 108.162.192.0/18;
set_real_ip_from 131.0.72.0/22;
set_real_ip_from 141.101.64.0/18;
set_real_ip_from 162.158.0.0/15;
set_real_ip_from 172.64.0.0/13;
set_real_ip_from 173.245.48.0/20;
set_real_ip_from 188.114.96.0/20;
set_real_ip_from 190.93.240.0/20;
set_real_ip_from 197.234.240.0/22;
set_real_ip_from 198.41.128.0/17;
set_real_ip_from 199.27.128.0/21;
set_real_ip_from 127.0.0.1/32;
real_ip_header CF-Connecting-IP;set_real_ip_from 2400:cb00::/32;
set_real_ip_from 2606:4700::/32;
set_real_ip_from 2803:f800::/32;
set_real_ip_from 2405:b500::/32;
set_real_ip_from 2405:8100::/32;
real_ip_header CF-Connecting-IP;http://nginx.org/en/docs/http/ngx_http_realip_module.html
In conf file –
include /etc/nginx.custom.d/*.conf;If that helps.
stu
5 Minutes ago – for me was 9:13am EST
The line in the Simple History pop up.
Updated plugin
date 2016-05-16 13:13:14So even though it said “5 minutes ago” in the dashboard the actual stamp is UTC (-4) for me.
13:13 is the correct UTC time
My WordPress install is set to Detroit EST
On the linux server our “TZ” is set also to ESTI’m assuming your host or if you have ssh access can update the timezone of the server. The 2 hour error likely is on that box.
On Ubuntu:
sudo timedatectl set-timezone ESTIn Berlin it should be euberl00
Germany (most areas) UTC offset is +01:00 UTC and +DTC offset is +02:00. In 1945, the Trizone did not follow Berlin’s switch to DST, see Time in Germany – https://en.wikipedia.org/wiki/Time_in_Germany
I think that’s the missing 2 hours
Forum: Plugins
In reply to: [Comet Cache] Disabled Comet Cache Pluginahh, ok for security our config files are set what we think is best practice though you could disagree. Owner = readonly – no others rwe
I think that might be the reason the plugin does not remove the define(“WP_CACHE… statement.
Forum: Plugins
In reply to: [Comet Cache] Disabled Comet Cache PluginUnderstood and thanks.
I didn’t dig deeper into why the files are not removed or check permissions, and it’s not my intent to remove comet cache, just to disable it at times when doing a content intense edit to see changes in a non logged browser.
I found that disabling the plugin from the plugin screen works exactly as I want.
thanks!
stuForum: Plugins
In reply to: [Cloudflare] Flexible SSL@jwineman – all good now. For whatever reason that one particular site hiccuped all by itself. With all the plugins in their most current version I restored the database from Monday and it’s as good as new.
As far as unescaped htmlentities I don’t have any experience on how to go about finding them, and on the web it’s a very abstract topic. For now I’m happy to have it solved.
Thanks again for pointing me in that direction.
StuForum: Plugins
In reply to: [Cloudflare] Flexible SSLThanks @marhgil
I discontinued using the HTTPS Plugin about a year ago for what I believe is a more elegant solution (the subdomain issue above is an isolated case) working on several hundred installs.
I use these plugins:
CloudFlare
CloudFlare Flexible SSL
Insecure content Fixerwp-config.php – right before require_once(ABSPATH . ‘wp-settings.php’);
if (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] == 'https') $_SERVER['HTTPS']='on';If the site is being converted and not built from scratch I just replace all instances of http://url.url with //url.url in the existing database.
Forum: Plugins
In reply to: [Cloudflare] Flexible SSLThanks for your attentiveness on the support threads here @jwineman – makes sense I will check it out in the db and get that fixed up.
Stu
Forum: Plugins
In reply to: [Cloudflare] Flexible SSLThe particular site is a subdomain which never exhibited problems using Flexible SSL. Even now, when reverting back to 1.3.20 I have a red X in the browser address bar over the https after flushing everything and restarting php5-fpm and nginx
Plugin (SSL Tests) It looks like your server is behind a reverse proxy. The recommended setting for HTTPS detection is HTTP_X_FORWARDED_PROTO.
Your server environment shows this:
Array
(
[HTTPS] =>
[HTTP_CF_IPCOUNTRY] => CA
[HTTP_X_FORWARDED_FOR] => 216.8.156.215
[HTTP_CF_RAY] => 28b522077f863fc5-YUL
[HTTP_X_FORWARDED_PROTO] => https
[HTTP_CF_VISITOR] => {“scheme”:”https”}
[HTTP_CF_CONNECTING_IP] => xxx.8.xxx.215
[HTTP_CF_RESPECT_STRONG_ETAG] => 0
)I have Flexible SSL “On” in Cloudflare. I have Cloudflare Flexible SSL plugin (by Paul G.) installed. My page rule is *sub.domain/* – always uses https and the CF plugin, email address, api token etc all seem to be fine.
I have to turn it all back off at this point to give my client her site back temporarily until I can figure this out.
Thanks for any assistance you can provide. I’m stumped now that rolling back to 1.3.20 something is seriously stuck.
Forum: Plugins
In reply to: [Cloudflare] Flexible SSL@jwineman – I will bring back up the plugins and page rules and report back.
Thanks!
StuForum: Plugins
In reply to: [Clef Two-Factor Authentication] WP Email in General Settings[resolved] Yes & thanks Laurence.