anotherhero
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: speed up the blogThere is a good post about enabling / debugging gzip in WordPress http://www.speedingupwebsite.com/?p=60
Please, here is official bug tracker
http://code.google.com/p/web-optimizator/issues/listIt seems no one optimization solution allows you to manage scripts’ placement this way – it’s too professional for newbies and is too simple for profi to do this manually.
Forum: Plugins
In reply to: [Plugin: Web Optimizer] another problem after updateing to 0.6.6I don’t see here any ‘valid’ errors.
1) progress.html is ued for standalone application. It’s a minor bug that it can’t be written (and this doesn’t influence the main logic, it’s just installation troubles)2) ExpiresActive is being checked via dummy .htaccess. So this error is a ‘good’ one. Web Optimizer disabled mod_expires usage operating data from this error.
Maybe cache clean-up? Can’t tell for sure what is wrong with CSS basing on this info.
Forum: Plugins
In reply to: [Plugin: Web Optimizer] another problem after updateing to 0.6.6thx for this notice. It seems 600 are default permissions PHP set for files on creation. There has been made a fix for that (very strange) PHP behavior.
You can apply a new version (from repository) via
a) deactivating plugin
b) deleting current web-optimizer folder (maybe w/o config.webo.php file)
c) activating plugin once more. All new files will be downloaded from repository.Forum: Plugins
In reply to: [Plugin: Web Optimizer] another problem after updateing to 0.6.6There is complete user guide how to install and tune Web Optimizer
As Wiki: http://code.google.com/p/web-optimizator/w/list
As .pdf: http://code.google.com/p/web-optimizator/downloads/detail?name=web-optimizer.v0.6.4.ug.en.pdfThere must be available for writing cache folder(s). It seems in your case there is no such folder on the server
Forum: Plugins
In reply to: [Plugin: Web Optimizer] plugin could not be activatedWeb Optimizer checks this directory for writing permissions. If there is no such permissions, it can’t write to it. Usually (in the most cases) 0775 for directory is enough.
If there is any way to detect from PHP how it’s run (via Apache or suPhp) – to change this number to 0755 for some cases — please write here.
Forum: Plugins
In reply to: [Plugin: Web Optimizer] problems with the .htaccess partA lot of .htaccess rules are listed here
http://code.google.com/p/web-optimizator/wiki/IntegrationWithWebsite#.htaccess_changesForum: Plugins
In reply to: [Plugin: Web Optimizer] why chose to promote hyper cache?Comparison of different WordPress plugins for client side optimization
http://www.web-optimizer.us/web-optimizer/wordpress-comparison.htmlForum: Plugins
In reply to: [Plugin: Web Optimizer] very weird behavior on 2 pages only!It’s ‘standard’ errors. Web Optimizer tries to check .htaccess possibility (and enabled modules). But it seems if you have errors, .htaccess can be applied, but you have options disabled… It seems to be strange.
What core version are you using? (file web-optimizer/version indicates the version of core). In 0.6.3 there were added some improvements to check Apache modules. It’s not the clue to resolve your trouble, but maybe there is a possibility to improve Web Optimizer behavior for your system.
Forum: Plugins
In reply to: [Plugin: Web Optimizer] very weird behavior on 2 pages only!I can’t reproduce this issue on a test machine (.htaccess is disabled, only complete CSS merging + HTML Minify are enabled). All 14 external stylesheets have been succesfully downloaded and combined into 1 (with all inline styles).
This issue seems to be reproduced on a few environments. Maybe there is PHP error gracefully degraded. Maybe — just broken functionality due to small PHP timeout on execution. Maybe — CGI system incompatibilities with Web Optimizer logic. Maybe something else.
If you can provide initial HTML code, its working version (which is parsed succesfully), and its non-working version (i.e. current one) with the minor differencies between them (and a set of options which leads to this situation) — this will definitely help us to find a clue and resolve this trouble.
Forum: Plugins
In reply to: [Plugin: Web Optimizer] very weird behavior on 2 pages only!@ovidiu: bug tracker is here
http://code.google.com/p/web-optimizator/issues/listForum: Plugins
In reply to: [Plugin: Web Optimizer] problems with the .htaccess partyour hoster environment is incompatible with .htaccess options. I’ve already written about this. Web Optimizer checks if it’s possible to use .htaccess and use it. Otherwise .htaccess isn’t applied.
Forum: Plugins
In reply to: [Plugin: Web Optimizer] problems, features and suggestions@ovidiu; please give me the URL of your website — and we will check HTML Minify for this document.
We will definitely add a number of tools to debug Web Optimizer actions but now we are just choosing the best way to perfrom this. I.e. there can be ‘prewiew’ where you can (semi) automatically debug all plugin features.
Also please note that Web Optimizer plugin for WordPress isn’t the main branch of the product, it’s just an ‘envelope’ for main functionality.
Forum: Plugins
In reply to: [Plugin: Web Optimizer] well i am facing few issue@xinfo: thank you for notices.
1. Gzip. It seems WordPress gzip (or gzip of any other plugin) conflicts with Web Optimizer’s one. So you need to use Gzip for HTML (CSS and JS files can be served via Web Optimizer w/o any issues) in only one place. It can be WordPress, cache plugins, or Web Optimizer itself. It’s not the issue (but there was added a text about gzip disable in installation instructions, such text is on Troubleshooter page).
2. Website w/o images. There was a bug with wo.static.php file (proxying images’ caching for your website), it wasn’t copied to cache folder. It has been fixed. You can download the last version (0.6.1.4) of Web Optimizer plugin and deactivate/activate it or just copy this file (wo.static.php) from web-optimizer/libs/php/ to web-optimizer/cache/ .
3. .htaccess usage is allowed only for Apache websites. If your website is hosted via php as CGI, and .htaccess isn’t supported, it’s disabled (enabling .htaccess logic on an unsupported environment leads to a disaster for your website).
@ovidiu: how do you update plugin? I think now it misses update functionality, it will be added in a few next builds.