Forum Replies Created

Viewing 15 replies - 61 through 75 (of 82 total)
  • Thread Starter admintiger

    (@admintiger)

    Thanks for the status info.

    admintiger

    (@admintiger)

    I also am extremely disgusted and disappointed by this. I have the Fast Secure Contact Form plugin installed at three sites. The email addresses at two of those sites previously received spam, but the address at one site was known only to a couple people and never received any spam whatsoever until this affair. Now it is trashed.

    There is nothing wrong with trying to make money with a commercial venture, but there is a lot wrong with taking advantage of trust. If you want to help market vCita, you should do it in ways that don’t mislead and that don’t steal data from people who have trusted you and considered you a friend. I suspect your donation income will drop by far more than you receive from vCita.

    The directory and file permission system under Windows is entirely different than under Linux. I can confirm that the directory security changes you made in Version 0.7 are not compatible with the Windows server directory and file permission system.

    There is a second Windows compatibility problem in Version 0.7 that also exists in 0.6. Each time the Update button on the PHP Settings page is clicked the number of slash characters in the entered path to the snippets directory doubles. For example, if this path is entered:

    C:\public\www.domain.com\php-snippets

    After the button is clicked the path changes to this:

    C:\\public\\www.domain.com\\php-snippets

    If the button is clicked again the path becomes this:

    C:\\\\public\\\\www.domain.com\\\\php-snippets

    Normally, I could offer you admin login credentials to a test WordPress installation running under Windows, but I am using my test server myself to develop something critical at the moment.

    That is true. Changing all the ‘<?’ tags to ‘<?php’ makes it possible to activate the plugin without a continual stream of ugly errors, but after doing that a page of trash characters displays when clicking the icon that the plugin adds to the WordPress Page/Post text editor. The plugin is not compatible with typical PHP server configurations.

    @hydn, our comments should be AutOptimize forum posts, so people considering that plugin will see them. However, I want to confirm that what you wrote above is true. Over the past several days I have installed and throughly tested all the various minification/caching/cdn plugins I could find at a test site that has pages loaded with unusually rich content (multiple large css files, multiple htc files, many images, audio, video, multiple JavaScript files, etc.). Most of the plugins I tried are seriously flawed by coding mistakes, fallacious underlying design logic, poor html header parameter choices, misleading setup information, and/or operating system incompatibilities. In contrast, AutOptimize and WP SuperCache work together flawlessly on both Linux and Windows servers (running Apache, I haven’t tested with other web servers). Both plugins are simple to install and configure, and when used together page loading times half way around the planet are phenomenal.

    @hydn, it appears after some quick tests that you are right about AutOptimize. I hadn’t tried it before, because the developer no longer seems to support it and because of concern that moving all JavaScript to the bottom of pages would break functionality. However, it is refreshing to find a plugin that in contrast most others I have tried recently is well-written and actually works as described. So far the JavaScript issues I was concerned about haven’t caused any problems and if there are compatibility issues with future WP versions I can fix them myself.

    Thanks for taking time to post your recommendation.

    Thanks hydn, I will give AutOptimize a try.

    After adding a function to fix the problem on line 859 I discovered the same problem on two other lines in the same file. After those problems were fixed another PHP error occurred due to other code that is not compatible with the Windows operating system. All those problems could be fixed, but I have decided look for a Windows-compatible plugin or write my own.

    I traced the cause of “get HTTP/1.0 400 Bad Request” to a PHP error on line 859 of “wp-content\plugins\wp-minify\wp-minify.php”. I am using a Windows Server and there is a deeply-seated problem with filemtime() under Windows due to the fact that it calls the Windows stat() function, which implements DST (according to this bug: https://bugs.php.net/bug.php?id=40568). The detection of DST on the time of the file is confused by whether the CURRENT time of the current system is currently under DST.

    A fix for that problem is available here:
    https://www.php.net/manual/en/function.filemtime.php#100692

    Same problem here. I also get HTTP/1.0 400 Bad Request using WP-Minify 1.1.6 with a fresh WP 3.1.2 installation at a test site. (No other plugins and an unmodified Twenty-Ten theme)

    The rewrite rules probably change with different W3 Total Cache option selections.

    I am also using 0.9.2.1

    My installation has these /.htaccess Rewrite rules under the “Install” tab:

    # BEGIN W3TC Page Cache core
    <IfModule mod_rewrite.c>
        RewriteEngine On
        RewriteBase /
        RewriteRule ^(.*\/)?w3tc_rewrite_test$ $1?w3tc_rewrite_test=1 [L]
        RewriteCond %{HTTP_USER_AGENT} (2\.0\ mmp|240x320|alcatel|amoi|asus|au\-mic|audiovox|avantgo|benq|bird|blackberry|blazer|cdm|cellphone|danger|ddipocket|docomo|dopod|elaine/3\.0|ericsson|eudoraweb|fly|haier|hiptop|hp\.ipaq|htc|huawei|i\-mobile|iemobile|j\-phone|kddi|konka|kwc|kyocera/wx310k|lenovo|lg|lg/u990|lge\ vx|midp|midp\-2\.0|mmef20|mmp|mobilephone|mot\-v|motorola|netfront|newgen|newt|nintendo\ ds|nintendo\ wii|nitro|nokia|novarra|o2|openweb|opera\ mobi|opera\.mobi|palm|panasonic|pantech|pdxgw|pg|philips|phone|playstation\ portable|portalmmm|\bppc\b|proxinet|psp|qtek|sagem|samsung|sanyo|sch|sec|sendo|sgh|sharp|sharp\-tq\-gx10|small|smartphone|softbank|sonyericsson|sph|symbian|symbian\ os|symbianos|toshiba|treo|ts21i\-10|up\.browser|up\.link|uts|vertu|vodafone|wap|willcome|windows\ ce|windows\.ce|winwap|xda|zte) [NC]
        RewriteRule .* - [E=W3TC_UA:_low]
        RewriteCond %{HTTP_USER_AGENT} (acer\ s100|android|archos5|blackberry9500|blackberry9530|blackberry9550|blackberry\ 9800|cupcake|docomo\ ht\-03a|dream|htc\ hero|htc\ magic|htc_dream|htc_magic|incognito|ipad|iphone|ipod|kindle|lg\-gw620|liquid\ build|maemo|mot\-mb200|mot\-mb300|nexus\ one|opera\ mini|samsung\-s8000|series60.*webkit|series60/5\.0|sonyericssone10|sonyericssonu20|sonyericssonx10|t\-mobile\ mytouch\ 3g|t\-mobile\ opal|tattoo|webmate|webos) [NC]
        RewriteRule .* - [E=W3TC_UA:_high]
        RewriteCond %{HTTP_COOKIE} w3tc_referrer=.*(google\.com|yahoo\.com|bing\.com|ask\.com|msn\.com) [NC]
        RewriteRule .* - [E=W3TC_REF:_search_engines]
        RewriteCond %{HTTPS} =on
        RewriteRule .* - [E=W3TC_SSL:_ssl]
        RewriteCond %{SERVER_PORT} =443
        RewriteRule .* - [E=W3TC_SSL:_ssl]
        RewriteCond %{REQUEST_METHOD} !=POST
        RewriteCond %{QUERY_STRING} =""
        RewriteCond %{REQUEST_URI} \/$
        RewriteCond %{REQUEST_URI} !(\/wp-admin\/|\/xmlrpc.php|\/wp-(app|cron|login|register|mail)\.php|wp-.*\.php|index\.php) [NC,OR]
        RewriteCond %{REQUEST_URI} (wp-comments-popup\.php|wp-links-opml\.php|wp-locations\.php) [NC]
        RewriteCond %{HTTP_COOKIE} !(comment_author|wp-postpass|wordpress_\[a-f0-9\]\+|wordpress_logged_in) [NC]
        RewriteCond "%{DOCUMENT_ROOT}/wp-content/w3tc/pgcache/%{REQUEST_URI}/_index%{ENV:W3TC_UA}%{ENV:W3TC_REF}%{ENV:W3TC_SSL}.html%{ENV:W3TC_ENC}" -f
        RewriteRule .* "/wp-content/w3tc/pgcache/%{REQUEST_URI}/_index%{ENV:W3TC_UA}%{ENV:W3TC_REF}%{ENV:W3TC_SSL}.html%{ENV:W3TC_ENC}" [L]
    </IfModule>
    # END W3TC Page Cache core

    This doesn’t appear there:

    <IfModule mod_ext_filter.c>
        AddOutputFilterByType DEFLATE text/css application/x-javascript text/html text/richtext image/svg+xml text/plain text/xsd text/xsl text/xml image/x-icon
    </IfModule>

    W3 Total Cache hasn’t added that to the .htaccess file in the root of a test site where it is installed. Are you sure it was added by W3TC? If so, do you know which W3TC option causes it to be added?

Viewing 15 replies - 61 through 75 (of 82 total)