Forum Replies Created

Viewing 15 replies - 16 through 30 (of 70 total)
  • Thread Starter definitio

    (@definitio)

    Changed my Caching plugin to Hyper Cache, yet still seeing the flickering in Chrome and a sizing issue with all browsers when responsiveness and max width are enabled

    It isn’t a problem because it does not cause any problem to your site or your plugin’s function…it only displays a false report you know is false…
    By the way, you shouldn’t unlock the htaccess file so as only to skip that false report…you are safer when your htaccess file is locked, and the false report doesn’t mean anything…

    If you upgrade Bulletproof Security, then you WILL HAVE to unlock the file and save your W3TC settings again to get the code into your htaccess file.
    You can also backup your htaccess file, but when you upgrade BulletProof Security, you should use the newest version of the htaccess rules. You can save any custom code in “My Notes” or the appropriate predefined places in “Custom Code”, but you should better ask Bulletproof Secyrity personnel if you can put your W3TC code there (supposing you are using the same settings – so no change in W3TC code – and W3TC is not updated to use new code)

    To sum up:
    – Your site works
    – Your caching plugin works
    Yet you are for some reason unhappy as if you want a REAL problem to match that false report.

    By the way, if you want to complain to someone you got the wrong guy.

    I don’t this is a problem at all…

    Bulletproof Security automatically locks the htaccess file with 404 permissions instead of the default 644 ones…
    That’s why W3TC displays this warning and WP Super Cache does exactly the same…

    Try Unlocking the file and see that the warning will go away (it does in my case that is).

    Thread Starter definitio

    (@definitio)

    bumping this up…

    1) Should I be using an htaccess rewrite rule to point http://www.mysite.com/* to mysite.com/* given that WP does that in some way?

    2) What’s the best way to do that?
    I have come across various suggested codes

    RewriteCond %{HTTP_HOST} ^www\.(.+)$ [NC]
    RewriteRule ^(.*)$ http://%1/$1 [R=301,L]

    or

    RewriteCond %{HTTP_HOST} ^www.(.*) [NC]
    RewriteRule ^(.*)$ http://%1/$1 [R=301,NC,L]

    or

    RewriteCond %{HTTP_HOST} ^www\.(.*)$ [NC]
    RewriteRule ^(.*)$ http://%1/$1 [R=301,L]

    or

    RewriteCond %{HTTP_HOST} ^www\.([^.]+)\.example\.com [NC]
    RewriteRule ^(.*)$ http://%1.example.com/$1 [R=301,L]

    or

    RewriteCond %{HTTP_HOST} ^www.example.com [NC]
    RewriteRule ^(.*)$ http://example.com/$1 [L,R=301]

    What do WP knowledgeable users recommend?

    Thread Starter definitio

    (@definitio)

    Thank you cageehv

    Getting the same warning on the backend…

    Thread Starter definitio

    (@definitio)

    I am also getting this notice on the backend, in the plugin’s settings

    Notice: Undefined index: submit in /wp-content/plugins/related-posts-via-taxonomies/includes/admin.php on line 60
    Thread Starter definitio

    (@definitio)

    Thank you very much for your prompt response.

    After installing this latest version, I am still getting some notices that may be coming from Easy Fancybox

    NOTICE: wp-includes/class.wp-scripts.php:163 - Undefined index: jquery-easing
    NOTICE: wp-includes/class.wp-scripts.php:163 - Trying to get property of non-object
    NOTICE: wp-includes/class.wp-scripts.php:163 - Undefined index: jquery-mousewheel
    NOTICE: wp-includes/class.wp-scripts.php:163 - Undefined index: jquery-metadata

    The backend notices are totally gone, though.

    PS I am running debug enabled on a closed to the public, test installation.
    I appreciate the warning

    Thread Starter definitio

    (@definitio)

    I have enabled debug and I am getting the following errors on the frontend…don’t really know if they are related to the issue at hand

    Notice: Use of undefined constant SHORTCODE_PRIORITY - assumed 'SHORTCODE_PRIORITY' in /home/mydomain/public_html/mysite/wp-content/plugins/youtube-embed/includes/aye-add-scripts.php on line 14
    
    Warning: Cannot modify header information - headers already sent by (output started at /home/mydomain/public_html/mysite/wp-content/plugins/youtube-embed/includes/aye-add-scripts.php:14) in /home/mydomain/public_html/mysite/wp-content/plugins/wp-super-cache/wp-cache-phase2.php on line 88
    Thread Starter definitio

    (@definitio)

    I’ve done the same thing (inserted the logo on a transparent image as wide as the template). Looks the same but not excited about the whole header area being linked though.

    The problem then is the added KBs of image data…my logo is around 8KB, the header image is around 50KB (minified)…
    I’m at a point where the whole page weight is under 200KB and -cached- paged load time is (just under) 1sec and I don’t want to add 50KB for the logo alone…

    It’s the best alternative if you absolutely need the logo…I really prefer to use it, but not at the cost of the overhead, so for now I a going “brazilian” on the site header (using site name and description instead, with a font that looks nice)

    Will be nice to get that flexible width header thing…

    Thread Starter definitio

    (@definitio)

    I have tried with the following popular themes: Twenty Twelve, Responsive, silverOrchid, Mantra, Catchbox….they are all giving me the same results.

    Thread Starter definitio

    (@definitio)

    I ran a quick test on a test WP installation: I tried totally disabling WPSC, clearing Youtube Embed’s cache (and browser cache), enabled the “dynamic resize” and “max width” options of the player and with Firefox I get
    – losing float value (in fact aligning to the opposite side)
    – no wrapping text
    – the video not quite fitting within the video player, i.e. the video is cut in its borders (not visible) as if it has been zoomed and cropped, somehow not keeping the set max width values…
    …these are kept for the player, but not the video…

    Screenshot
    http://postimage.org/image/673ws1chp/

    Thread Starter definitio

    (@definitio)

    Hello. Thank you for your patience.

    Part of the testing that I did involved disabling the plugin cache (set all at zero and checked the box to flush any cache). I also tried removing all WPSC code when testing for cache disabled.

    I checked several times, with several browsers, clearing the browser cache several times to make sure.

    The results just didn’t make much sense. I am going to recheck again in couple of days (got to get some other things out of the way) from another computer and report back

    Thread Starter definitio

    (@definitio)

    Is this feature being considered for implementation in future versions or is it possible to include it in a “to do” list? Would be very helpful

    Thread Starter definitio

    (@definitio)

    I mean supported with a shortcode.

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