Hmm were you able to see what the fatal error was? Did you remove the current version’s folder before uploading the RC?
Im sorry, i should have copied it down but the site is running at peak hours so I can’t run something thats not working.
I did fresh install yes. I did notice it still said 1.2.3
When you activate the plugin and there’s a fatal error the plugin will not be used so I don’t think that will break your site, perhaps you could try activating again and copy the error?
Don’t worry about the version number, it should still be 1.2.3 to WordPress.
Parse error: syntax error, unexpected ‘)’, expecting T_PAAMAYIM_NEKUDOTAYIM in /nas/wp/www/cluster-1238/[site name]/wp-content/plugins/bwp-minify/includes/class-bwp-minify.php on line 448
Thats the error – Please note that [site name] is my install directory.
Ah, that was an issue with your PHP version. Uploaded a new version, it should work now: http://betterwp.net/downloads/bwp-minify-1.3.0rc1.zip
Thank you.
I installed and it does indeed work.
However, the friendly URL function does not. I have activated it, adding the necessary changes to the .htaccess file. In addition, I have turned on CDN. My site looks completely broken (CSS wise)
Any suggestions?
Do you see any warning when enabling friendly minify url? Is your cache directory writable? Can you post the contents of your .htaccess file (the one inside cache directory, unless you are using multi-site)?
I assume that you have tried friendly minify url with CDN turned off as well?
Also take a lookat the FAQ section for some insights: http://betterwp.net/wordpress-plugins/bwp-minify/faq/
When I first went to enable the friendly URL, I got a warning label. It mentioned adding a piece of code to the .htaccess file.
The cache directory is writable. I’ve tried doing it with and without CDN options in the plugin.
My CDN is running in the background already and I believe does not require to be added to the plugin (seems to use minified files created by BWP).
Here is what it requested me to add:
# BEGIN BWP Minify Rules
# BEGIN BWP Minify Headers
<Files "*.js.gz">
ForceType application/x-javascript
</Files>
<Files "*.css.gz">
ForceType text/css
</Files>
<IfModule mod_mime.c>
AddEncoding gzip .gz
AddCharset utf-8 .js .css
</IfModule>
<IfModule mod_deflate.c>
<IfModule mod_setenvif.c>
SetEnvIfNoCase Request_URI "\.gz$" no-gzip
</IfModule>
</IfModule>
<IfModule mod_headers.c>
Header set Cache-Control "public, max-age=7200"
Header set Vary "Accept-Encoding"
Header unset ETag
</IfModule>
# END BWP Minify Headers
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{HTTP:Accept-Encoding} gzip
RewriteRule .* - [E=ZIP_EXT:.gz]
RewriteCond %{REQUEST_FILENAME}%{ENV:ZIP_EXT} -f
RewriteRule (.*) $1%{ENV:ZIP_EXT} [L]
RewriteRule ^minify-b(\d+)-([a-zA-Z0-9-_.]+)\.(css|js)$ /index.php?blog=$1&min_group=$2&min_type=$3 [L]
</IfModule>
# END BWP Minify Rules
Hmm that looks fine to me. It’s kinda hard to debug if you don’t have a dev server.
Is it possible for me to have a temporary admin account and FTP access to bwp-minify folder on your site? When debugging I will enable BWP Minify only for the account you give me, so it should not affect other users.
Sorry, but I won’t be able to do that. I have tried everything and I get the same result.
Hopefully Im not the only person with this issue.
Ok, one last thing to try. When you re-enabled the friendly minify url feature (CDN should be disabled), take a look at your site’s source code and look for a friendly url, it looks similar to: http://yourdomain.com/wp-content/plugins/bwp-minify/cache/minify-......css
Try clicking on that url and see if there’s any error or just WordPress’s 404 not found error.
I assume that your site is a single blog and is setup like below?
http://yourdomain.com/{your index.php}
http://yourdomain.com/{your wp-includes,wp-admin}
You can paste that url here or send it to me via http://betterwp.net/contact/
Thing is, my CDN is applied to my site before I even need to put it in BWP Minify. As in, the CDN takes the minified URL automatically. Folks like WP Engine do this. If you are indeed releasing 1.3.0 soon, I’ll retest it and see if it works.
Hmm you’re on WP Engine? Even the staging site is not available for debugging purpose? The only thing that keeps me from better understanding this issue is the lack of a development environment.
Actually 1.3.0 can be released any time now, but I really want to figure out what’s wrong in case like yours before I release it, because there might be other users out there that might have exactly the same issue.
