Forum Replies Created

Viewing 15 replies - 16 through 30 (of 49 total)
  • Robert

    (@kinderrwindstreamnet)

    Same thing here after upgrading to v1.1.7. I use a Gmail App Password. Things were working great before the upgrade.

    Thread Starter Robert

    (@kinderrwindstreamnet)

    Is there a way to provide the actual URL to you outside of this forum? The “mysite” in the URL is a generic.

    Thanks

    Thread Starter Robert

    (@kinderrwindstreamnet)

    Showing a blank error message is the way WordPress handles incorrect form input like a missing name or email

    Right – the problem is how wp_die() operates because it displays an error on a new page. A jQuery AJAX input form event handler can intercept the Submit button action before it gets to WordPress, however some browsers may not have Javascript enabled.

    The WP Inline Comment Errors plugin is interesting because it’s a pure PHP solution that uses add_filter('wp_die_handler', "MyCustomCommentErrorHandler") to stay on the page, retain the user inputs and display user-friendly error messages. The result is an AJAX like solution.

    The plugin even has a hook for a user provided CAPTCHA. See the /examples/get-error-from-math-captcha.php file in the plugin directory.

    Using the add_filter(‘wp_die_handler’, ..) technique appears to be the ideal solution.

    Thanks

    Thread Starter Robert

    (@kinderrwindstreamnet)

    I apologize. After removing the exclusion for handler.image.js in Autoptimize on my staging site Simple Lightbox now works fine with Chrome! I verified it’s working on two different computers with the latest version Chrome, FireFox and IE.

    I’ve since enabled CSS optimization and it must’ve been due to some other interaction.

    Thank you for following up.

    Thread Starter Robert

    (@kinderrwindstreamnet)

    Is there an non-forum way to contact you so I can provide the URL to my staging site?

    Thread Starter Robert

    (@kinderrwindstreamnet)

    Marking as resolved.

    Robert

    (@kinderrwindstreamnet)

    FYI – After upgrading from v1.0.8 to v1.0.9 in the WordPress dashboard I couldn’t log in to wp-admin getting only a blank screen because the Sucuri plugin automatically sends login email notices.

    My fix was to fire up FileZilla (or use your favorite FTP client) and rename the plugin directory to _easy-wp-smtp (note the leading underscore _) to disable the plugin.

    I was then able to login to wp-admin, delete the old plugin, install Easy WP SMTP v1.0.9 and re-enter the mail account settings. If you’re using Google Apps for Business see the Gmail SMTP server settings.

    If you’re using 2-Step Verification with Gmail (and you should be!) you’ll need to regenerate an App Specific Password if you didn’t save the old app specific password. I don’t save app specific passwords offline security.

    Thread Starter Robert

    (@kinderrwindstreamnet)

    I wasn’t aware of that value in the database and edited the value via phpMyAdmin. It was initially set to “ed_size=620266667” and changed it to 550 pixels height and saved.

    When I opened the Visual Editor on a new post the huge window height problem was there.

    I added comments to a similar problem reported in a WordPress Trac Ticket: https://core.trac.www.ads-software.com/ticket/28000

    Thanks

    Thread Starter Robert

    (@kinderrwindstreamnet)

    OK – now the bug is happening when I log in as Administrator, too. Tried clearing the browser cookies and caches. No joy.

    Another symptom is sometimes the visual editor displays the scroll bar and other times it doesn’t.

    Thread Starter Robert

    (@kinderrwindstreamnet)

    I discovered if I’m logged in as the Administrator the post editor works fine and there’s never a problem:

    >>> getUserSetting(‘ed_size’);
    “558”

    If I log in under my Editor account the post editor size bug always occurs.

    This suggests it’s a permissions problem. I log into both accounts using SSL/HTTPS.

    Thread Starter Robert

    (@kinderrwindstreamnet)

    I now believe the pageviews issue was due to holiday traffic trends.

    Thread Starter Robert

    (@kinderrwindstreamnet)

    I checked the rendered page source code and found the Reduce Bounce Rate script appears after the closing footer tag. Could this skew the pageview results? If so, I can delete the plugin and insert the Reduce Bounce Rate script directly in footer.php.

    I’m using WooThemes Canvas 5.3.0 and WooThemes Framework 5.5.5. I placed the Google Analytics tracking code in header.php.

    The pertinent page tags, Google Analytics and Reduce Bounce Rate page source is:

    <html>
    <head>
    
    // contents omitted brevity...
    
    <script type="text/javascript">
    (function($){
        $(window).load(function() {
            if (this._gat) {
                tks = this._gat._getTrackers();
                ga_track = function(p) {
                    for (i=0; i < tks.length; i++) {
                        var n = tks[i]._getName() !== "" ? tks[i]._getName()+"." : "";
                        a = [];
                        for (i2=0; i2 < p.length; i2++) {
                            var b = i2===0 ? n+p[i2] : p[i2];
                            a.push(b);
                        }
                        _gaq.push(a);
                    }
                };
                $('a').filter(function() {
                    return this.href.match(/.*\.(zip|mp3|mpeg|pdf|doc*|ppt*|xls*|jpeg|png|gif|tiff)/);
                }).click(function(e) {
                    ga_track(['_trackEvent', 'download', 'click', this.href]);
                });
                $('a[href^="mailto"]').click(function(e) {
                    ga_track(['_trackSocial', 'email', 'send', this.href]);
                 });
                var loc = location.host.split('.');
                while (loc.length > 2) { loc.shift(); }
                loc = loc.join('.');
                var localURLs = [
                                  loc,
                                  'https://mysite.com'
                                ];
                $('a[href^="http"]').filter(function() {
                    for (var i = 0; i < localURLs.length; i++) {
                        if (this.href.indexOf(localURLs[i]) == -1) return this.href;
                    }
                }).click(function(e) {
                    ga_track(['_trackEvent', 'outbound', 'click', this.href]);
                });
            }
        });
    })(jQuery);
    
    </script><script type="text/javascript">
    	var _gaq = _gaq || [];
    	_gaq.push(['_setAccount', 'UA-xxxxxxxx'], ['_trackPageview']);
    	(function() {
    	var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
    	ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'https://www') + '.google-analytics.com/ga.js';
    	var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
    	})();
    </script>
    
    // html stuff snipped for brevity
    
    <script type="text/javascript">
    
      var _gaq = _gaq || [];
      _gaq.push(['_setAccount', 'UA-xxxxxxxx']);
      _gaq.push(['_setDomainName', 'mysite.com']);
      _gaq.push(['_trackPageview']);
    
      (function() {
        var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
        ga.src = ('https:' == document.location.protocol ? 'https://' : 'https://') + 'stats.g.doubleclick.net/dc.js';
        var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
      })();
    
    </script>
    </head>
    
    <body>
    
    <<footer>
       // content omitted for brevity
    </footer>
    
    // Reduce Bounce Rate script begins...
    <script>
    var _gaq = _gaq || [];
    (function (tos) {
      window.setInterval(function () {
        tos = (function (t) {
          return t[0] == 50 ? (parseInt(t[1]) + 1) + ':00' : (t[1] || '0') + ':' + (parseInt(t[0]) + 10);
        })(tos.split(':').reverse());
        window.pageTracker ? pageTracker._trackEvent('Time', 'Log', tos) : _gaq.push(['_trackEvent', 'Time', 'Log', tos]);
      }, 10000);
    })('00');
    </script>
    
    </body>
    </html>
    Thread Starter Robert

    (@kinderrwindstreamnet)

    Could a CDN possibly be a factor? I use CloudFlare and my site is hosted by WPEngine.com.

    I’ll give the new script a try and see how that affects pageviews.

    Thanks,
    Robert

    Thread Starter Robert

    (@kinderrwindstreamnet)

    I modified the .htaccess in /wp-content from:

    <Files *.php>
    deny from all
    </Files>

    to this:

    <Files *.php>
    deny from all
    </Files>
    <Files “superproxy.php”>
    Order Allow,Deny
    Allow from all
    </Files>

    Which allows access to only superproxy.php and while preventing access to all other PHP files for security.

    Real-Time Reports are working fine.

    Thanks!

    Thread Starter Robert

    (@kinderrwindstreamnet)

    Topic is resolved.

Viewing 15 replies - 16 through 30 (of 49 total)