anotherhero

hmm, it seems it’s been removed for unregistered users – we are going to check the situation

@spotcream: mentioned PHP warnings are not related to product external logic, but indicates administrative interface work (in this case a bit incorrect, because chained optimization can be performed, but nothing critical)

It’s very strange – because WEBO Site SpeedUp doesn’t delete aby files (just some rules from .htaccess) on deactivation.

Maybe you can’t just access to this folder? Anyway you can try to ask hoster about backup or recover it manually. Hope DB isn’t damaged.

We are very sorry if this was caused by WEBO Site SpeedUp.

The first issue is clear and was fixed about a week ago.
The seconds issue (with CSS/JS merging) isn’t clear. Please submit full description to
https://code.google.com/p/web-optimizator/issues/

Are you sure that this issue is related to WEBO Site SpeedUp plugin?

You can disabled WEBO Site SpeedUp (bring it to debug mode) if you go to wp-content/plugins/web-optimizer/config.webo.php file and just replace
$compress_options[‘active’] = “1”;
with
$compress_options[‘active’] = “0”;

This will deactivate plugin (so the whole website will be loaded w/o its processing).

I agree with this topic. FCG maybe not so bad, but has a lot of compatibility issues. So other developers have to fix somehow consequences of this plugin to get it work with our plugins. It’s awful.

Small remark to creator(s): please switch lines

header(“Content-type: text/css”);
include(“../../../../wp-load.php”);

in the file jd.gallery.css.php – sometimes (or every time?) it leads to text/html Content-Type for CSS file. Switched order (header the second) serves the file normally.

It seems there are JS errors. You need to configure JavaScript merging params.

@daiv thx for your comment. But can you please remove this hack description? It violates license agreement.

@travelhorizon, it’s OK. If you can find any ‘bad’ behavior (with set of files before and set of broken files after) – please submit an issue here
https://code.google.com/p/web-optimizator/issues/list

WEBO Site SpeedUp can emulate all .htaccess options, but latter can speedup server side processing of accelerated resources.

So you can safely combine / gzip your CSS / JavaScript files (but they will be processed via PHP, not raw files) to prevent any fails for your visitors.

You need to disable .htacces usage – your server lacks of mod_mime support. More info about static gzip functionality
https://www.speedingupwebsite.com/2010/01/09/static-gzip-or-compression-without-compression/

After this all styles won’t be gzipped (badly) and you will have ‘normal’ website.

So to restore situation please (in Settings)
Settings -> .htaccess -> Use .htaccess -> No (uncheck)
or just disable gzip for CSS / JavaScript files
Settings -> Gzip -> Gzip CSS / Gzip JavaScript -> No (uncheck)

This bug will be fixed in the next update, which can be performed internally.

If there is no such favicon.ico — it was downloaded. It seems WEBO Site SpeedUp v1.0 will detect favicon.ico from website itself and will try to duplicate it in the website root.

There is also one more solution with smush.it (and coming punypng) support – www.ads-software.com/extend/plugins/web-optimizer/

There is a set of articles about WordPress speedup on a shared hosting: https://www.speedingupwebsite.com/

Here are several posts related to WordPress performance. Maybe they can help: https://www.speedingupwebsite.com/