farbfinal home · jFinalizer · jFinalizer technotes

jFinalizer joomla plugin

documentation, how-to and support

jfinalizer logo

Download

Please select your version. Note that jFinalizer 2 requires joomla 1.6 or later.

joomla
jFinalizer v2 v1
current release 2.0.1 BETA
please bugreport - beta version.
1.1.5
no further development planned for 1.x
PHP PHP5.3
older PHP5 versions might work
PHP5
Never install on PHP4!
major changes - CSS exclusion list
- complies PHP5.3 strict standards
- some option changes, divided into basic / advanced
- plugin order change if system.cache plugin is used
supports Joomla 1.6 Update System yes no
tested against joomla 1.6.5
joomla 1.6.6
joomla 1.7.0
joomla 1.5.23

DOWNLOAD

DOWNLOAD

 

Important Change on V2: jFinalizer 2.x uses a different plugin order because of joomla 1.6. As before, jFinalizer should be the last plugin in your chain. But if you use joomla's SYSTEM - CACHE plugin, this must be last even after jFinalizer.

Install: right click, copy URL and paste into joomla for installing by URL. Otherwise just download the plugin and upload manually. See changelog. License: GPL, no registration required, free of charge. Component developers please see the tech notes.

Please bugreport to This e-mail address is being protected from spambots. You need JavaScript enabled to view it or feel free to leave bug reports and comments below

Warning: Do not install jFinalizer on PHP 4!

jFinalizer setup screencast

Overview

Use jFinalizer if you want to reduce HTTP requests to site, reduce traffic, speed up page loading or decrease HTML page size if you have big templates. On big templates, you can gain 10+ YSlow points, sometimes more than 20. There are many other libraries which do similar things, but we built and run jFinalizer because most of the templates we used would not work with other plugins.

Key Features:

  • compress & merge CSS files
  • compress & merge JS files
  • compact HTML output
  • gZip file ouput
  • fast
  • no database access

Do not use jFinalizer if you want the last bit of compression. Its designed for runtime performance, not for super-high compression.

Do not use jFinalizer if you have components, extensions or templates which generate dynamic CSS on the fly (no - you usually don't have that, even on complex templates).

Do not expect jFinalizer to work out of the box. Default settings are compatible for most sites, but tuning HTML output is a tricky task and highly depends on your template, CSS, Java Script, components, plugins and modules. Give yourself 10 minutes to get this plugin configured properly.

Demo

Simply right click and view the source of this page or view the source code of our corporate main site www.farbfinal.de to see what jFinalizer does. Actually, both use the same joomla! installation but different templates.

Description

The idea of jFinalizer is to replace tons of JS and CSS files with a single CSS and JS file. This is done by processing the final joomla output HTML. Additionally, you can compact & compress a few things and make your HTML look more compact.

jFinalizer uses another approach than most libraries we've found: It does not do anything to CSS, HTML and JS code except for stripping whitespaces and stuff which is not needed. The plugin merges all CSS and JS files used in a page into a single file, preventing the loading order of the html source. Note that only CSS and JS files within the region are processed. We've found that processing body CSS and JS usually harms on complex templates.

jFinalizer is designed for live performance. This requires a bit more tuning on the developer side, but reduces runtime CPU usage at runtime a lot. jFinalizer has its name not only because our company is called farbfinal, but also because its usually the last plugin in the system chain and finalizes your output. Your goal is to develop your site, then turn on jFinalizer and see what happens. If your code is clean, you're on the way to go.

Even though joomla! is a great CMS, it has a few drawbacks. Joomla's flexibility is awesome, but at the same time it introduces a lot of file I/O on the application server. jFinalizer can help a little to improve that. It does not check for updated CSS or JS files since the developer knows anyway when design is changed. Imagine you have a template with 9 CSS and 7 JavaScript file includes. Makes 16 all together. jFinalizer reduces it to 2 (see limitations). This reduces Server file I/O. Since jFinalizer does not check the modified date of the source files, 14 file system calls are saved.

Limitations

  • CSS and JS files outside the <head></head> section are ignored
  • files containing a questionmark after the extension are ignored (my.css?v=10) because we assume they are danamic
  • inline CSS and JS is ignored
  • some features are not available on all platforms and server configurations (see Options)
  • HTML compression does no fixing like tidy

Performance

In Production mode, the plugin performs quite well and does not consume a lot of CPU. For performance analysis and before / after comparison, please use external tools such as YSlow (FF Plugin). Since jFinalizer is a system plugin we want to keep it slim, there are only a very few analyis options build into plugin (see configuration).

Installation Workflow

1. install the plugin and set it to plugin order "last". For joomla 1.6 only: If you use the SYSTEM.CACHE plugin, put this even after jFinalizer.
2. set plugin option Site Mode to development (install default - your site becomes slow)
3. check your fontend pages for design breaks
4. tune jFinalizer options
5. reload site, make sure browser cache is cleared
6. repeat (4) and (5) until everthing works
7. turn Site mode into production

PLUGIN ORDERING: Make sure your plugin ordering chain is right. This setting must be different for different versions of joomla.
Joomla1.5+: jFinalizer absolutely last
Joomla1.6+: jFinalizer absolutely last, except you use joomlas system.cache plugin.

Tip: Whenever you change a CSS or JS file later or install new joomla! components / plugins, turn jFinalizer into Development Site Mode and check life site again.

Tip: While configuring, do one thing at a time. If you want HTML compression, start there and disable all CSS / JS processing. See HTML setup guide

Don't give up tuning to fast. Allow yourself 10 minutes to get it working properly. If there is no combination to get your template working, this plugin is probably not for you. Try a different approach like CssJsCompress or JACompress.

When installing a jFinalizer upgrade, simply install it. The plugin does not need to be uninstalled before.

Configuration Tips

If your site does not work properly, your goal is to turn jFinalizer off, see your HTML source code, then turn the plugin on, reload, see your source code again and compare. First steps for setup could include this procedure:

  1. Turn jFinalizer into Site Mode Development
  2. disable all options (no HTML processing, no JS processing, no CSS processing, all compacting to off, no gZip). If your site still breaks, something is wrong and this plugin is not for you. Otherwise, continue turning on step by step and reload after every step. Try this order:
  3. Turn on CSS processing
  4. Turn on CSS compacting (now your site gets slower)
  5. Turn on JavaScript processing
  6. Turn on JavaScript compacting (now your site gets slower)
  7. Turn on HTML processing, try DeTab mode (default) first
  8. if you have a working site now with some combination of the modes above, continue to configure gZipping, removing HTML comments etc. if you wish.

Tip: Any Compacting can break layout. If your server supports runtime gZip compression, thats probably not a big deal and you can turn it off

Tip: if your site uses many joomla components, make sure to also check the pages where they appear! For example, you could get a perfect layout and performance with HTML compression set to ultra, but some poorly coded component might break it or not work as expected.

Tip: If HTML compression is what you want most, work the other way around. Disable CSS and JS processing first, enable HTML processing and be sure to try all available modes! If you have the system.cache plugin enabled, disable it while tuning. Try to start with DeTab mode (default). Read the HTML Setup Guide.

To see an example, right click and look at the source code of this page. Farbfinal.de is run against jFinalizer with HTML processing mode set to fast using moderate compression and check contitional exceptions, JS on and optimize, CSS on and optimize, remove comments and deliver using gzip htaccess.

Setup Guide: HTML compression

HTML processing is the most tricky part. Stick on this workflow to get it working. Be sure your browser reloads properly and dont try to get CSS / JS aggregation to work before HTML processing if you want both.

  1. install jFinalizer
  2. optional: temporary disable the system.cache plugin if you use it.
  3. in jFinalizer, disable CSS processing, JS processing, gZip delivery, HTML comment removal, generator Tag removal
  4. set process HTML to fast - builtin
  5. try all available compression levels, a good start is DeTab
  6. save the settings, reload your front end, see what happens
  7. if design and / or functionality breaks, repeat steps 5-6
  8. once your design and functionality works, you may try to enable HTML comment removal and generator tag removal. Be sure to check front end again!
  9. optional: when you finished all jFinalizer configuration, enable system.cache again if you used it
Tip: for bypassing HTML processing for only a specific block of Text or content plugin, wrap it with My bypassed content goes here in the article editor.

Setup Guide: CSS / JS processing

If you dont want HTML output processing, try this workflow to setup CSS / JS processing properly. This may help to to get your site working a bit faster.

  1. install jFinalizer
  2. disable the system.cache plugin if you use it
  3. set jFinalizer to site mode: development
  4. in jFinalizer, disable HTML processing, CSS processing, JS processing, gZip delivery, HTML comment removal, generator Tag removal
  5. start with enabling CSS / JS processing, on switch at a time
  6. save the settings, reload your front end, see what happens
  7. if design and / or functionality breaks, repeat steps 5-6
  8. when everything works as expected, remember so set jFinalizer site mode into production
  9. optional: when you finished all jFinalizer configuration, enable system.cache again if you used it

Setup Guide: use both together

See instructions above. Be sure to first get HTML compression working properly at first, then start CSS / JS file processing - not the other way arround!

Options

the default configuration should work for most installations:

jFinalizer default settings

Site Mode

Your most important switch while tuning and developing. Controls how jFinalizer handles its internal cache. Yes, you want cache! The cache system on jFinalizer operates independent of all joomla! cache settings, because its always content independent. Caching in jFinalizer means that JS and CSS files are stored to disk and not re-processed on every page load. HTML output is never cached by jFinalizer. Using jFinalizer without cache does not make sense because you would decrease HTTP requests but at the same time increase execution.

While developing design (CSS) or functionality (JS) you want to turn Site mode into development. When your site is up, fixed, steady and running - go for production.

Note: development mode reduces performance big time - your site will slow down drastically.

Tip: while in designing layout in development mode, disable JavaScript & CSS compacting

  • production: live site mode, caching enabled
  • development: cache disabled, files are always re-created, cache cleared on every page load.

process HTML

removed in version 1.1.0. Also, Tidy support is not available in jFinalizer 1.1.0+

HTML Compression

Sets the compression level of HTML output.

Depending on how clean your template is, you can reach different compression levels. Compression levels also affect CPU usage on the server side a bit. Please note that the most efficient and fastest mode is ultra, but unless your template is super-clean, ultra mode will probably break your layouts.

All modes try to remove as many white spaces as possible. Ultra also removes all line breaks. The difference in the operating modes is how deep the plugin digs and how much whitespace is removed. Some modes do additional checking to prevent design breaks. Please try and see which option works best for your template.

The different options are available because the idea if jFinalizer is to perform as fast as possible and do as few checks as possible at runtime.

  • Off: No HTML processing
  • DeTab: remove Tabs and leading white spaces. Safest, most efficient and fastest algorithm
  • other options: vary - try them yourself. They might break layout.

Tip: Published starting at jFinalizer 1.1.0, DeTab seems to be most compatible. Its also the current installation default setting. We did a lot of testing and performance comparison. While being much more compatible and 2x faster than our best algorithm so far, Safe mode C+, HTML size increases typically between 0.5-1% only when using DeTab compared to Safe Mode C+. Also, source code looks very clean now. So we strongly recommend DeTab now.

Note: Starting from some of the next releases, only compression modes DeTab, Safe Mode C+ and Ultra will be available. Others will be removed an depreciated!

HTML comments

Keep or remove HTML comments. It takes a bit CPU but usually is a good thing if you want to clean your output. Please note that multiline comments are always kept!

  • remove: remove HTML comments
  • keep: keep HTML comments

Pre Tag Support

Never touch <pre> tags. Don't remove linebreaks, whitespaces etc. This option is available on jFinalizer 1.0.11+. Useful for plugins like CodeCitation. If you know your site does not have any <pre> tags, turn it off for a tiny bit of extra performance.

  • Yes: support checking of <pre> tags
  • No: skip <pre> tag checking

Generator Tag

Keep or remove the joomla! generator meta tag. Can help a bit to not expose joomla. Note that there are other ways to do that but they require joomla ource code editing.

  • remove: remove generator meta tag
  • keep: keep generator meta tag

process JavaScript

Does what it says. Process all JavaScript tags, read the files, merge them into one and cache them. Note that having external url (from another server) javascript within your <head> tag will probably break the script.

All JavaScript files outside the header <head>...</head> tags are ignored.

  • Yes: process JavaScript
  • No: ignore JavaScript tags

compact JavaScript

remove whitespaces and other unused stuff from JS files. Usually saves a couple bytes. In some cases, compacting JS can break JavaSvript functionality. If thats the case, try disabling it.

Performance note: compacting JavaScript files is usually the most time consuming task of jFinalizer. While this is not a problem in production (cache) mode, you might want to turn JS compacting off when in development mode.

  • Yes: compact JS
  • No: leave JS untouched and simply merge the files into one

jQuery NoConflict() support

resolve jQuery conflicting Ajax libraries - added by feature request, v1.1.4+

Some Ajax libraries might fight each other. The jQuery library contains a switch which can resolve this issue when used together with other libraries, such as joomla's default MooTools. However, jFinalizer has the option to inclide that switch because sometimes, 3rd Party components already call this JavaScript statement, so it's not needed a second time.

  • Yes: include jQuery.NoConflict() patch
  • No : leave JavaScript as is

Skip Files

Never process those files. Type any phrase in there. Case unsensitive.

You can manually enter a comma-separated list here to exclude specific files. These files will always be skipped. For example, the default setting tini_mce.js ensures that the joomla default TinyMCE editor will still work in the front end when users edit content.

UPDATE: jFinalizer 1.x can only exclude JS files. jFinalizer 2.x can exclude both JS and CSS.

  • default: tiny_mce.js,xajax.js

process CSS

same thing as as process JavaScript but for CSS files

compact CSS

same thing as compact JS but for CSS

check conditional Exceptions

Check it the template contains conditional <!--if... --> CSS includes for client browsers. If it does, they are ignored. The option is available because if YOU KNOW your template does not have any conditional includes, you can turn this option off and save some extra performance.

  • Yes: check for conditional includes (recommended)
  • No: bypass check

gZip output

compress cached JS and CSS files using gZip.

gZipping JS & CSS files can drastically reduce file size and download time. When run in .htaccess delivery mode, additional PHP calls are bypassed and runtime compression by the delivery server (eg. apache) is skipped. This can reduce overall load and File I/O on your server. Please note that .htaccess mode is not available on all platforms. If you run a dedicated server, this option is for you to tune the last bit. The modes explained for experts:

PHP delivery: the client browser calls a PHP file which delivers the JS / CSS file dynamically and adds necessary css headers. The files are already compressed, but PHP needs to be opened and a fopen() function is involved.

.htaccess delivery: a .htaccess file is placed into the delivery folder (usually /cache/assets). The web server checks if gZipped content is accepted by the client and rewrites the request file name to deliver the gzipped version. Fast, no additional PHP calls. On apache, mod_rewrite must be enabled and allow_overrides must be properly set for the cache path. If Apache is set to compress .js and / or .css files by default on the fly using DEFLATE, this will be bypassed for those files saving CPU time.

To customize the content of the .htaccess file depending on your server configuration, copy the file /plugins/jfinalizer/htaccess.default.php to htaccess.custom.php and edit this file. This way, your changes remain after you upgrade jFinalizer. Note: .htaccess configuratio requires jFinalizer 1.0.4+

Please note that apache knowledge is required when editing the .htaccess file contents. The goal of the .htaccess file is to check if the client accepts compressed data, and if thats the case redirect the request to the gzipped version of CSS / JS files.

  • off: no compression
  • gzip PHP delivery: compress & deliver files using PHP
  • gzip .htaccess delivery: compress & deliver files using .htaccess rewrite (recommended)

cache lifetime in s

As CSS and JS files dont change once you finished designing, cache lifetime is usually set to 0 meaning the files never expire. However, you have the option to enter an amount of seconds to force rebuilding the merged files after that period. Do not confuse "expired" here with http expiring / client cache lifetime: HTTP send Headers are not touched by jFinalizer.

  • 0: never expire (recommended)
  • (number): lifetime for merged files in seconds

debug

Append some debug info comments or show performance data

Debug mode help you to see what jFinalizer does and how it performs. In html comments mode, a html comment containing the name of the removed JS / CSS files is placed into placed into output HTML source code. This can be useful if you want to see what files were merged.

In full and performance mode, jFinalizer displays performance data such as total runtime of the plugin, number of merged files an HTML byte savings on top of your site. Full & performance breaks design and cookies. So don't use it on a live site - or if you do, turn it off quickly again. While tuning jFinalizer compression settings, don't run full and performance since you can't see compression design breaks.

  • off: no debug
  • html comments: write file information into output HTML as comments
  • full and performance: html comments + display runtime information - improved in 1.1.0

Advanced: Place Tags

where to place output file tags in HTML.

By default (auto), the first found tag (CSS / JS) in your source template is replaced by the merged output file. However, you can optimize tag placement by manually placing tags. For example, if you have a minimal template which has not a lot of JavaScript, you could move all JavaScript from the <head> to the bottom of your body. Anyways, manual template editing is necessary.

If you want to do so, call the loading event at the appropriate place within your template and then switch to manual . Usually this is the section which outputs head data. It does not matter if other CSS or JS files are loaded after manual placement. The parsing and collecting always comes later.

PHP Placement code CSS: $mainframe->triggerEvent('getCompressedCSS');
PHP Placement code JS: $mainframe->triggerEvent('getCompressedJS');

($mainframe refers to the joomla mainframe object).

  • auto: auto tag placement
  • manual: manual tag placement

Advanced: Delivery Path

delivery output path for CSS and JS files in client HTML

Now thats tricky. By changing the delivery path, you can tell the client to load the merged JS and CSS files from another source path. Its great for hiding the default joomla /cache/xxx directory.

Cached files are always stored physically on disk into the joomla cache directory, subfolder /assets. So, usually thats /cache/assets. You can't change that because thats the only way to clean jFinalizer cache using the joomla builtin cache manager.

Re-routing the delivery path works by placing a symlink to /cache/assets. You need shell access. Login to your server and create a softlink. For example on linux, if you want you delivery path to be example.com/inc, you would create the symlink using

bash># ln -s /my/absjoomlarootpath/cache/assets /my/absjoomlarootpath/inc

and then insert inc/ into the delivery Path field. Note that Apache might check symlink permissions. They need to be set correctly.

  • (empty): dont re-route include path
  • inc/ : re-route include path to example.com/inc

Advanced: Remote File support

Let Finalizer try to include asset files that are not stored on the actual server. This option is experimental - we need feedback on this!

The PHP directive allow_url_fopen must be enabled. Also, please note that any files containing a "?" or other suffixes, like style.css.php, are considered dynamic and are always skipped.

  • (yes): try to include remote CSS files
  • no : don't

Advanced: joomla subdirectory

Tell jFinalizer if joomla is installed in a subdirectory.

Unfortunately, joomla might do strange things sometimes when installed in a subdirectory. Although there is a $live_site directive in joomla's configuration.php, this setting might break some 3rd party components. jFinalizer itself is not affected by that issue, but other than most joomla core components it needs to reconstruct url's that are already parsed out. So, to be more compatible, we decided to give that extra switch. Also, it accelerates a bit because we have less string processing to to.

Please not the spelling: if your site is installed into www.example.com/joomlarootdir, you must enter /joomlarootdir - not joomlarootdir/, joomlarootdir, /joomlarootdir/ or example.com/joomlarootdir

  • (empty): root instalation
  • (/somedir) : joomla's install directory.

tips, tricks, troubleshooting

  • Inline JavaScript Code
    may break when using HTML output compression. In general, when optimizing a site, you want to avoid inline JS at all if possible. If you have out-commented inline JS and your site breaks, try to turn off HTML comment removal first. Be sure to then try all available HTML compression levels.
    As we figured out so far, 90% of broken functionality is caused by inline JavaScript Code when using HTML compression. A good starting point is compression level DeTab, since this fixes a couple JS issues.
  • .htaccess gZip delivery
    is a strong feature but usually needs modification to your specific server needs to work properly on your server. While in development mode, the .htaccess file is always recreated so you can check your changes.
  • be patient on HTML compression
    If you want HTML output compression and it does not work out of the box, disable all other options and try different compression levels. See HTML setup guide. jFinalizer's HTML compression algorithms are not designed to be smart but fast. So they require testing on your specific site. Of course that takes time, but you gain performance as soon as it works.
  • Upgrade to the latest version
    To not break compatibility with sites already using jFinalizer, we will never change existing HTML compression algorithms once published, but rather add new ones. So you can safely upgrade jFinalizer.
    Edit: Wrong. We will remove some algorithms which seem to not work for most users - thanks for the tons of feedback we've got so far!
  • valid HTML, please!
    Using valid HTML / XHTML in your template makes it easier to figure out problems. If your site contains valid HTML and jFinalizer is setup properly, it will also output valid HTML. Keep in mind that jFinalizer does not do any fixing. Having invalid HTML / XHTML before HTML processing might cause many problems and is never a good idea anyway. So before using jFinalizer, make sure your site validates against W3C
  • bug report
    Please help us to improve jFinalizer and bug report. We'll try to fix as soon as possible and get back on you. So far, we could get jFinalizer running with all of our self-made and third-party templates without modifying a single line of template code.
  • PHP Error: unexpected T_OBJECT_OPERATOR
    Your site is probably running PHP4. Don't use jFinalizer!
  • PHP Error: Warning: fopen(/some/path/somefile.css) [function.fopen]: failed to open stream:
    You run CSS / JS processing mode and your site actually misses a file! Check your error logs and you will probably see a 404. This can happen if a joomla! extension appends a CSS / JS file to HTML output which is physically not existing on your server. jFinalizer won't check for that. It assumes that the files needed to display the page are actually existing.
  • jFinalizer is active but seems to not do anything
    its possible that jFinalizer conflicts with the joomla build-in system.cache plugin. If you use system.cache, make sure you use jFinalizer Version 1.0.7+
  • WAMP compatibility on local windows development servers
    There seem to be some issues when trying to run jFinalizer on local Windows development machines. Currently, we do not plan to integrate dedicated WAMP support, since jFinalizer needs to be re-configured on the final live site anyway. Workarround: Design your site, upload it and install jFinalizer on your live server as the very last step of development.
    Try upgrading to jFinalizer 1.1.0 which has some windows workarrounds. They are still beta, but please tell us if they help or what's wrong!
  • bypass html processing
    Starting from jFinalizer 1.0.11+, you can bypass HTML processing by wrapping anything with my unprocessed content goes in here, for example in the joomla! article editor. This way you can bypass HTML processing for content plugins or specific text blocks. Note that anything can be bypassed, also inline JavaScript and inline CSS, as long as its not within the <head> tag.
  • process HTML only and use another CSS / JS plugin
    If for some reason you cannot get CSS / JS processing working but still want the HTML output compression functionality of jFinalizer, you can safely try other CSS / JS aggregation plugins like CssJsCompress or JaCompress. You will not drop performance: All CSS / JS aggregation functions of jFinalizer are only loaded dynamically into PHP if CSS / JS processing is active and files actually need to be aggregated. Make sure to disable all CSS / JS functionality when using other plugins.
  • IMPORTANT: Joomla is installed in a subdirectory like www.example.com/joomla. This can cause asset file not found errors.
    Since v1.1.0 we have added dedicated subdir support - unfortunately we had to. One more config setting but at tradeoff for better speed. Read more on how to configure
  • No CSS / JS files are processed: make sure the type definition is set (eg type="text/css"). This can be a problem especially with HTML5 since HTML5 is a bit lazy here.

known issues

  • 2.0.1: HTML5 issues with conditional header definitions. We currently investigate.
  • CSS files beginning with @charset can cause invalid CSS - design is not affected
  • RokBox does not like HTML comment removal - try jFinalizer 1.1.0 + DeTab Mode
  • CodeCitation joomla! plugin requires <pre> tag checking (jFinalizer v. 1.0.11+)
  • There seem to be issues with jFinalizer when working in PHP Safe mode on some server setups. We still investigate. If jFinalizer is not working for you and you know your server runs PHP in Safe mode, please drop us a bug report with your system info.
  • TinyMCE Fronend editor might break even in DeTab compression mode. v1.1.4+ (alpha) solves that issue due to exclusion. Sorry folks, no other workaround found yet.

A Primer On Compression Efficiency

When you apply output compression or optimization, either on HTML, JS or CSS, you have 2 things in your mind: You want to reduce server load and you want to speed up your clients page loading.

Unfortunately, involving compression is always a tradeoff. No matter how efficient the algorithms are - the better the compression, the more CPU usage is needed on the server side. For example, speaking of HTML compression, this involves a lot of additional checking to make sure no inline JavaScript functionality or CSS design breaks.

When we first designed jFinalizer, our goal was to reach maximum compression with minimum server CPU load while being as compatible as possible. To keep the tradeoff between compression ratio and CPU usage as balanced as possible, we have setup a reference page and kicked all algorithms which cause jFinalizer to exceed a total runtime of 5ms. We figured that it does not make sense to build a system plugin which requires Page Caching to keep performant.

Since we got lots of feedback from jFinalizer users while (still) being in beta, we could evaluate many different 3rd party components and their behavior on compression. After lots of comparison, we decided to give the go for our newest DeTab compression algorithm: Compared to all others, it does not completely remove line breaks. At first, we did not like that at all. But after statistics evaluation, we were quite surprised. The total increase of HTML size is only minimal, typically between 0.5-1% compared to other algorithms.

Now that was good news. Removing line breaks causes heavy problems with inline JavaScript and needs a lot of reconstructing. We have a great balance now: execution time on our reference Page reduced to <2ms and the algorithm did not break any JavaScript yet. So with the help of many jFinalizer users, we think that we have found the perfect tradeoff for jFinalizer and plan to go from beta RC to the first official release.

changelog

1.0.0
- initial release
1.0.1
- changed some descriptions
- switched internal File I/O to builtin class instead of JFile
1.0.2 - download archive plg-system-jfinalizer-1.0.2.zip
- fixed issue on files with "?" appended to CSS or JS URL
1.0.3
- some bugfixes
1.0.4 - download archive plg-system-jfinalizer-1.0.4.zip
- changed safe mode HTML processing algorithm for more compatibility
- add: another HTML processing mode (now Safe Mode A and Safe Mode B)
- add: option to remove Joomla! generator tag
- add: added support for custom .htaccess file contents
1.0.5 - download archive plg-system-jfinalizer-1.0.5.zip
- add: Simple Mode B html processing mode
- fix: German language file missing Tag
1.0.6
- fix: PHP deprecated Warning on some server setups
1.0.7
- fix: added compatibility for use with system.cache plugin
- add: added yet another HTML compression level (Safe Mode C)
- change: changed install default HTML compression level to Safe Mode C
1.0.8 - download archive plg-system-jfinalizer-1.0.8.zip
- fix: inline JavaScript Bug in Safe Mode C
1.0.9 - download archive plg-system-jfinalizer-1.0.9.zip
- change: set Tidy Developer mode to UTF-8 / XHTML output
1.0.10 - download archive plg-system-jfinalizer-1.0.10.zip
- add: added Safe Mode C+ HTML compression level, keep more spaces
1.0.11 - download archive plg-system-jfinalizer-1.0.11.zip
- add: added switch
- add: added <pre> tag support
- fix: fixed Warning: get_class() error on certain PHP5.3 installations

1.1.0 - download archive plg-system-jfinalizer-1.1.0.zip
- major code rewrites
- changed CSS optimization engine
- improved overall performance
- fixed some issues with remote asset files
- fixed a jomsocial problem with facebook connect (thanks to the azrul team for providing a jomsocial dev copy)
- fixed a problem with google maps plugin
- added error handling engine
- separated code to include debugger only of in Debug Mode
- improved debugger messages
- added DeTab HTML compression mode (way faster, very effective, very compatible) - this fixed most 3rd party component issues. Please try this mode first!
- removed TIDY support
1.1.1 - download archive plg-system-jfinalizer-1.1.1.zip
- fixed: error handler loader bug (thanks to Douglas Machado)
1.1.2 - download archive plg-system-jfinalizer-1.1.2.zip
- fixed a bug with JomSocial news feeds
- fixed a php undefined notice
1.1.3 - download archive plg-system-jfinalizer-1.1.3.zip - current release
- fixed a setup xml bug for the errorhandler class
1.1.4 - download alpha version plg-system-jfinalizer-1.1.4.zip
- added by feature request: jQuery.NoConflict() support
- added by feature request: custom exclude JS files
- bug fix: tiny MCE exclusion fix, moved to exclude JS files section
1.1.5 - download alpha version plg-system-jfinalizer-1.1.5.zip
- fixed a bug with textarea tags (thanks to Mic)

2.0.0
- joomla 1.6+ support only
- PHP5.3+ rewrite
- Strict Standards compatible

2.0.1
- supports joomla 1.7+
- FIX: exclude css type media="print", bug report from Alex 2011-06-17 17:08
- FIX: corrected a bug in error 200 message handling
- ADD: File skip list now supports both JS and CSS, by feature request (CSS exclusion)
- CHANGE: File Skip list not case sensitive anymore
- CHANGE: Re-arranged backend options (simplify), divided into basic an advanced options
- FIX: language bugs
- CHANGE: Debug window redesigned, validates against W3C
- ADD: Supports 1.6 joomla update system


please note: when upgrading to 1.1.4 from an older version, be sure to hit "apply" in the backend plugin editor once (initialize newly added parameters)

Comments & Bug Reports

When posting a bug report or problem, don't forget to post the jFinalizer version. If you use HTML compression, tell us what Mode you use.

 

Comments  

 
+4 # jFinalizer joomla! pluginReinaldo Deprera 2010-02-17 11:04
- Problems using gzip via htaccess
- Problems compress html. The plugin is putting js in a declared CDATA and not closing this parameter correctly. This causes the extensions that use js to stop work. In my case the plugin rokbox and a module for the LiveZilla

Even so, I stopped using CssJsCompress because JFinalizer is a little more sophisticated, it provides some features (which does not work) that does not provide CssJsCompress. As the compression of html.
To solve the problems I encountered, I deactivated compression html (which was what most excited me) and put to gzip using PHP instead of htccess: (

If you resolve the problems, the plugin will most wanted genre without a doubt.
My site is the site-desenvolvimento .com.br and my personal e-mail the rdeprera@gmail.com
Reply | Reply with quote | Quote
 
 
+3 # fixedstefan 2010-02-17 11:14
Thanks for the report. The current release 1.0.4 has some modified HTML compression algorithms. Maybe you can check them out and see if one of them works.
Also, as of release 1.0.4 we added the ability to have a custom .htaccess file for specific server configurations. I hope that can help you serving gZip using htaccess. Unfortunately, .htaccess delivery highly depends on server configuration and need almost expert apache knowledge to configure. Please see the gZip config section of this page for some more hints on how to implement.
Reply | Reply with quote | Quote
 
 
+3 # RE: jFinalizer joomla! pluginErin 2010-02-17 11:06
took me about 15 mins to configure and works like a charm. I was a bit disappointed first because it would not work right after installing, but I read the documentation and got it working.

So whoever wants to use it: Read what the developers say everywhere and consult the documentation!

Thanks for this plugin!
Reply | Reply with quote | Quote
 
 
+2 # RE: jFinalizer joomla! pluginHansen 2010-02-17 11:08
Hallo,

Ich vermisse die Möglichkeit bestimmte css und Jacscript auszuschließen.

Ich habe bei mir jomsocial und Cometchat am laufen, bei beiden werden danach die css und javascipt Dateien nicht richtig geladen.

lg
Reply | Reply with quote | Quote
 
 
+1 # RE: RE: jFinalizer joomla! pluginstefan 2010-02-23 15:52
leider haben wir keinen Zugriff auf jomsocial, um die Komponente prüfen zu können :(
Reply | Reply with quote | Quote
 
 
0 # RE: RE: RE: jFinalizer joomla! pluginstefan 2010-04-24 07:21
jFinalizer v1.1.0+ wurde bei uns mit jomsocial getestet und läuft (DeTab Kompressionslev el).
Reply | Reply with quote | Quote
 
 
+3 # RE: jFinalizer joomla! pluginKai Schöning 2010-02-18 09:23
Richtig gut gemacht! Beide Daumen hoch! Funktioniert prächtig. Ergebnisse kann man zum Beispiel gut mit pingdom.com/tools messen!
Reply | Reply with quote | Quote
 
 
+2 # RE: jFinalizer joomla! pluginsascha 2010-02-18 23:22
hi,

one short question. in tidy mode the charset in source code is set to "us ascii" but i need UTF8. how can i change it to the right setting?

cheers
sascha
Reply | Reply with quote | Quote
 
 
+1 # fixedstefan 2010-02-19 09:21
fixed in v1.0.9 - set Tidy mode to UTF8 / XHTML
You cannot really change this by yourself since its hardcoded. But you are right, utf8 makes more sense. Unfortunately, Tidy does not recognize the input char encoding automatically. Thanks for the hint!
Please remember to not use Tidy on production sites since it will add lots of unnecessary bytes.
Reply | Reply with quote | Quote
 
 
+2 # Great Work !Silicon Farm Design 2010-02-20 15:24
Thanks a lot for this excellent plugin and documentation !! This plugin is on my must have list from now on !

Everything works really well. The only thing I had to limit was the html compression level due to a googlemap plugin (extensions.joomla.org/.../1147).
Only safe mode A worked, otherwise I believe that "if" & "else" statements in the javascript written without brackets { } break...
Reply | Reply with quote | Quote
 
 
0 # RE: Great Work !stefan 2010-02-20 17:37
thanks for the report. We´ll check out the maps plugin as soon as possible!
Reply | Reply with quote | Quote
 
 
0 # RE: Great Work !stefan 2010-02-21 09:52
We've checked the google maps plugin. At HTML compression level Safe Mode C+ it seems to work. Please note that Safe mode C+ is available only starting at jFinalizer 1.0.10+. You might try an jFinalizer upgrade and see if this works for you. Also Safe mode C+ is the new default compression mode when installing.

Safe mode C+ is almost identical to Safe Mode C but keeps a little bit more whitespaces. Its also a very efficient / fast algorithm.
Reply | Reply with quote | Quote
 
 
+1 # googlemaps not workingFrederik 2010-03-07 19:47
Hello,
Fantastic pluging !!
But i have the same problem with google-maps.
I believe this due to the fetching of js from google-server and not from local filesystem ?

Would be great if this could somehow be considered and solved in upcomming release.

thx very much
Frederik
Reply | Reply with quote | Quote
 
 
0 # mrsarmeet 2010-02-22 09:34
no man ... i cant get it to work T_T
Warning: get_class() expects parameter 1 to be object, array given in C:\wamp\www\its mypik\plugins\s ystem\jfinalize r.php on line 152
for now i have disabled the plugin .
i cant get the firststep to work lol .
forget about goin to next once X_X
Reply | Reply with quote | Quote
 
 
+1 # RE: mrstefan 2010-02-22 12:56
this is a bug of jFinalizer which seems to appear on sites running PHP version 5.3 with certain joomla versions. Will be fixed jFinalizer v. 1.0.11
Reply | Reply with quote | Quote
 
 
0 # Got some problem with register to site after installed Jfinalizer..?ssnobben 2010-02-23 12:48
Hello all !

Thanks for Jfinalizer. I have started to use it but got a problem that I think can have to do with Jfinalizer but not sure. I have a register page that work fine in Firefox but it doesnt work in IE 8.

travelmate.com/.../... Here is the reg form that doesnt work as it should in IE 8. Thanks!
Reply | Reply with quote | Quote
 
 
+1 # RE: Got some problem with register to site after installed Jfinalizer..?stefan 2010-02-23 15:15
after some email communication, we have figured out that the site works in Safe Mode C+, but one component would not work. The component mentioned is com_hotspots. Unfortunately, we could not get the component installed and properly running in order to do any tests.
Reply | Reply with quote | Quote
 
 
+2 # DrLawrence Weathers, P 2010-02-24 02:25
Could HipHop be in future Jfinalizer versions.

developers.facebook.com/.../
Reply | Reply with quote | Quote
 
 
-1 # RE: Drstefan 2010-02-24 07:12
The idea definitely sounds great for scaling up big sites and gain performance! We must evaluate carefully how many people could benefit from it. You need shell access and probably at least a dedicated server. As we can see, many system libraries needed by HipHop are not even installed or accessible on web hosting servers, see wiki.github.com/.../... .
Of course, the idea of having a "recompile joomla!" button in the backend sounds very charming :)
Reply | Reply with quote | Quote
 
 
+2 # Implications if Already Using htaccessRich 2010-02-24 07:25
Hi Guys,

Great plug in! Was wondering if there were any implications with using the htaccess method if you are already using an htaccess file on a site.

Thanks again.
Reply | Reply with quote | Quote
 
 
-1 # RE: Implications if Already Using htaccessstefan 2010-02-24 07:44
actually, it should not. Even better, you know your site works with .htaccess :)

But please note: make sure the jFinalizer .htaccess file is compatible with the settings of your own .htaccess file. Maybe you do path overrides that need to be included.

This is how jFinalizer .htaccess works: it copies a .htaccess file into /cache/assets. Only this directory is influenced by the jFinalizer .htaccess file. However, you can edit the jFinalizer .htaccess file to your personal server needs.

Please read the gZip documentation on htaccess very carefully (especially on how to copy the file)!
Reply | Reply with quote | Quote
 
 
0 # RE: RE: Implications if Already Using htaccessRich 2010-02-24 08:11
OK think I'm getting it, "allow_overrides " must be enabled in apache.

So am thinking that I would have to add

AllowOverride (Path to the plug in htaccess file.

That correct?
Reply | Reply with quote | Quote
 
 
0 # RE: RE: RE: Implications if Already Using htaccessstefan 2010-02-24 09:00
if you already use htaccess, that usually means that AllowOverride is already active. Apache's htaccess files always work downwards the path, so if any directive is active for your sites root (/) directory, its also active downwards until another htaccess files in a specific directory overrides a directive.

Did you try to use htaccess delivery already out of the box of jFinalizer? What happens? For example, if you use joomla SEF URLs with mod_rewrite, everything should be correct already.

If some of your htaccess files disallow htaccess files for the /cache directory or deeper by using AllowOverride None, then you might need to change it somewhere to AllowOverride All.

A simple check to see if htaccess files work in a specific subdirectory it to place a htaccess file in there which disables total access by asking for a valid User. But before doing that, make sure you can manually delete the file again using ftp / shell access! example .htaccess file:

RewriteEngine on
AuthType Basic
require valid-user

If everything works, Apache must give you an misconfiguratio n error when you try to access this directory since no password file is found. So if you get an ERROR, you know that htaccess files WORK :)
Reply | Reply with quote | Quote
 
 
0 # RE: jFinalizer joomla! pluginRich 2010-02-24 09:08
If I use it out of the box it just breaks the template.

Currently using mod rewrite with no problems. SEF urls and non www redirect as well

I'll have a look at what you're saying and let you know!
Reply | Reply with quote | Quote
 
 
0 # RE: RE: jFinalizer joomla! pluginstefan 2010-02-24 09:40
I assume that you already found your right settings for jFinalizer and your site works with gZip delivery disabled? If thats the case, you should be able to get it running. In any case, when using htaccess delivery, first thing to check is if the jFinalizer generated .htaccess file is located in /cache/assets.

If your template totally breaks (looking like there is no css file at all), you might have to adjust the htaccess file (see gzip notes above - again).

You can check if gZipped htaccess delivery works be using firefox with the firebug plugin: If you load your site, take a look at the Network tab, locate the /cache/assets/xxxxxxxxxxxxxx.css file and see if the headers say that its compressed (gzipped).

There are several issues on customizing the htaccess file. Take a look at htaccess.default.php and understand what it does. For example, if your server compresses CSS files by default and the disable deflate switch would not work as expected, your files get double-compressed and the client cannot open it anymore.

I'm sorry we cannot really help here. But as stated above, htaccess delivery highly depends on your very specific server setup and usually needs to be adjusted, which requires a bit apache rewrite knowledge.
Reply | Reply with quote | Quote
 
 
-1 # RE: jFinalizer joomla! pluginRich 2010-02-24 11:51
Yes it works fine w/o gzip and also with php gzip.

Interestingly enough I have it on another domain (same server) where it works fine in htaccess.

I'll have to compare the two more closely!
Reply | Reply with quote | Quote
 
 
-1 # RE: RE: jFinalizer joomla! pluginstefan 2010-02-24 14:24
yap, in this case chances are very good to get it working on the second domain too. Please let us know how you fixed it for your server!
Reply | Reply with quote | Quote
 
 
-1 # RE: jFinalizer joomla! pluginarxe 2010-02-24 16:50
Hallo

Wenn ich habe "protsess CSS" und "check conditional exception" umgehängt, entstandene zwei Probleme:
-"Core Designe Login" Modul arbeitet nicht so korrekt - popup Fenster ist immer vordergründig.
-im Bauteil K2 ändert Größe und Stil von Einreise.

Ich benutze in meine Seite VirtueMart Software mit VM Junction, Blade Ausstattung. Wenn ich habe "fast - builting crunch"
umgehängt, dann tab arbeitet nicht im Seite Beschreibung von Produkt.
Reply | Reply with quote | Quote
 
 
-1 # camulatz 2010-02-24 19:52
Hi,

joomla 1.5.14 - WIMP - jfinalizer last version

I have problem with process CSS: yes and gzip: PHP

jslow says me new css is

www.url_removed/.../

but nothing in assets, the url is not correct and the file i see in jslow is like this:
Reply | Reply with quote | Quote
 
 
-1 # RE: www.stefan 2010-02-25 08:10
That seems very strange. No matter what delivery mode you use, there must be .css and .js files in /cache/assets. If you use php delivery, there must also be 2 php files in that directory.

If no files are in the /cache/assets directory, it might be possible that the directory is not writeable by joomla. Could that be the case?

The URL you posted is missing slashed. They seem to be URL encoded. jFinalizer does not do that, it always uses the joomla DS constant for adding directory separators.
Reply | Reply with quote | Quote
 
 
0 # RE: jFinalizer joomla! pluginJonathan 2010-02-24 22:16
Hello there,

The plugin works on HTML and CSS but cant seem to work on IE when I enable javascript processing. From what i understand from my IE developer debugger, it seems unable to load the mootools library because it keeps on saying that the addEvent method of window doesnt exist...

solving this would really help alot.

Thanks for the plugin anyway! ;)
Reply | Reply with quote | Quote
 
 
-1 # RE: RE: jFinalizer joomla! pluginstefan 2010-02-25 08:01
1. make sure to disable JS cmpacting
2. turn off CSS and HTML processing totally, just enable JS processing
3. If the error you mentioned still happens, give us another feedback.

So far, mootools loaded fine on all sites we've tried on. Maybe we need a bit more information on your issue...
Reply | Reply with quote | Quote
 
 
+1 # RE: RE: RE: jFinalizer joomla! pluginJonathan 2010-02-25 08:52
I have tried that too... disabling the other settings and just enabled JS processing... still same problem... am thinking of disabling the javascripts one at a time to see which script might be causing this... but its strange that everything works fine having the scripts all separated and not when they are combined...
Reply | Reply with quote | Quote
 
 
-1 # RE: RE: RE: RE: jFinalizer joomla! pluginstefan 2010-02-25 13:48
it could be about the loading order. You might have to check if there is line JavaScript between the JS files by disabling JS processing. Not nice, but possible. Also, please note that jFinalizer has no built-in jQuery / MooTools conflict resolver (just in case you use both).
Reply | Reply with quote | Quote
 
 
0 # RE: jFinalizer joomla! pluginsascha again 2010-02-25 15:21
one question again: i'm using jomsocial and there are prolems with the generated rss feeds on profiles and so one. these problems are caused by jfinalizer. tried every possible combination. only solution is to disable jFinalizer :,( maybe someone has the same problems... or an solution :)

to the developer: VERY GOOD JOB!
Reply | Reply with quote | Quote
 
 
+1 # RE: RE: jFinalizer joomla! pluginstefan 2010-02-25 21:15
hi Sascha,

We will try to get a hold on the developers of jomsocial and see if we can grab a developer copy. Its an important component to joomla, we understand that. We really need to do tests, but as you can imagine, we just cannot buy comercial components for testing :(

We will get back on you, but it will probably take a couple days...
Reply | Reply with quote | Quote
 
 
+1 # RE: RE: RE: jFinalizer joomla! pluginsascha 2010-02-26 10:05
yeah i understand that. i didn't try if it works with joomla created rss feeds. but i think so. keep on the very good work :)
Reply | Reply with quote | Quote
 
 
0 # RSSAvi 2010-04-02 20:37
Quoting stefan:
hi Sascha,

We will try to get a hold on the developers of jomsocial and see if we can grab a developer copy. Its an important component to joomla, we understand that. We really need to do tests, but as you can imagine, we just cannot buy comercial components for testing :(

We will get back on you, but it will probably take a couple days...

Hi guys,
it looks like it has problems with RSS this time, Simple RSS Feed Reader from Joomla Works, the plugin does not let generating the RSS, any idea what to do?
thanks,
Avi
Reply | Reply with quote | Quote
 
 
-1 # SuggestionsMikeyB 2010-03-01 16:40
First of all. Great job on this plugin it works almost flawlessy. A couple of things I would like to see added that can be found in competing offerings is the ability to filter out certain scripts that you don't want processed, as well as the addition of a JSQuery/Mootools conflict resolver. These two things would make this a must-have plugin for any joomla installation.

The only two problems I have run into so far is the issue with Googlemaps (HTML compression Safe A fixes that), and highslide.js seems to break as well.

Not bad for a plugin that does so much. Thanks again and keep working on it :)
Reply | Reply with quote | Quote
 
 
-1 # RE: Suggestionsstefan 2010-03-02 18:15
We currently work on the Google Maps issue. Unfortunately, we could not reproduce the error yet. Our test cases all worked with safe mode C+. But we will figure that out.

The jQuery conflict resolver might become an option at one of the following releases.
Reply | Reply with quote | Quote
 
 
-1 # RE: jFinalizer joomla! pluginJoe 2010-03-02 16:58
if zip code html, this compression does not affect search engines in terms of optimization?
Reply | Reply with quote | Quote
 
 
+2 # RE: RE: jFinalizer joomla! pluginstefan 2010-03-02 18:11
jFinalizer does not zip HTML. It removes unnecessary white space.

Zipping is a different approach. By removing whitespace, the file gets more compact, its size decreases. When simply zipping a file, the client browser (or search engine) unzippes all data and the size is the same as before.

Some search engines rate a file-size-to-readable-content ratio. In this case, optimization might help a bit!

Also, most web servers gzip output anyway. So when you use jFinalizer, your compacted HTML gets gzipped before delivery. This way, you get smallest possible document size using both methods together.
Reply | Reply with quote | Quote
 
 
0 # RE: RE: RE: jFinalizer joomla! pluginJoe 2010-03-02 20:21
Thanks Stefan
Reply | Reply with quote | Quote
 
 
0 # css processing problemmazhar840 2010-03-03 06:51
erroe comes while css processing
fFinalizer Error: cannot write to file jFinalizer
Reply | Reply with quote | Quote
 
 
0 # Mr.Jonathan 2010-03-07 12:35
Had JFinalizer working smoothly a few days back, till we had to launch or facebook application on our site... apparently, we are stuck on a dynamically generated javascript file (hosted by facebook : .../en_US ) which we have no control over... any work-around on this guys? you can check out the site www.financeroll.com
Reply | Reply with quote | Quote
 
 
0 # RE: Mr.stefan 2010-03-07 12:49
Unfortunately, your site is not working at the moment - I assume you work on it. If you have the chance, first thing you could to try is to move the dynamic JavaScript from the html Head into the document body. jFinalizer will ignore that.
Reply | Reply with quote | Quote
 
 
0 # RE: RE: Mr.Jonathan 2010-03-07 13:27
yup, was just working on it, but is back now and you can check... moving the script to the html body is the last resort we would like to go into because it would definitely do alot of modification to the logic flow... but anyway, a work around on this matter would be really worth the next version for JFinalizer :D Thanks for this great plugin anyways!
Reply | Reply with quote | Quote
 
 
0 # WEBO Softwaresunnybear 2010-03-07 23:10
Well, good initiative. Maybe it will live for a longer time than PHP Speedy one.

Anyway there are a lot of things to implement - correct client side caching for assets, correct (CPU efficient!) HTML minify / comments striping, dynamic files handling. And so on. Good luck :)
Reply | Reply with quote | Quote
 
 
0 # RE: WEBO Softwarestefan 2010-03-08 09:05
Thanks for the comment! Since the features you mention are implemented but don't seem to work for you, it would be nice to have a bug report. Please remember that we don't sell commercial products, so we need feedback from users :)
Reply | Reply with quote | Quote
 
 
0 # Premature end of data in tag html line 1ssnobben 2010-03-08 08:48
I got this error coming from Wc3 validator validator.w3.org/check validator.w3.org/

Line 355: Premature end of data in tag html line 1

…r) {}
Reply | Reply with quote | Quote
 
 
0 # Some code missing abovessnobben 2010-03-08 08:50
Some code above is missing pls email me to get it bcs here it is stripped out rgds {}
Reply | Reply with quote | Quote
 
 
0 # RE: jFinalizer joomla! pluginJohn Smith 2010-03-09 04:48
I hope you fix the compatibility with Yoologin and Joomslide (highslide)...

Both are not working :

tools.yootheme.com/.../...

extensions.joomla.org/.../...
Reply | Reply with quote | Quote
 
 
0 # RE: RE: jFinalizer joomla! pluginstefan 2010-03-09 07:20
Thank you for the report! We will check this on the next release.
Reply | Reply with quote | Quote
 
 
+1 # RE: jFinalizer joomla! pluginJohn Smith 2010-03-09 05:00
Basically, what this plugin needs is an exclusion list. It would really help !

Thank you for your hard and excellent work.
Reply | Reply with quote | Quote
 
 
0 # RE: RE: jFinalizer joomla! pluginstefan 2010-03-09 07:23
Our goal was to actually get things to work without an exclusion list. But since we've got more than one request for this feature, we will evaluate the pros and cons again.

Can you tell us what was specifically not working for you?
Reply | Reply with quote | Quote
 
 
0 # Windows Bugmagj 2010-03-10 15:17
Hi
Thanks for this great plugin

It has bug (at least xampp on windows) it implements compressed files in this way that (at least) css won't load:

the url of embeded css that creates 404 error is like:
/cache\assets\d0 63c76c443613cf9d89788459af6 c6e.css

and if I change the \'s with / it with generate a 500 server error

Looking forward to hear from you
magj
Reply | Reply with quote | Quote
 
 
0 # RE: Windows Bugstefan 2010-03-11 06:52
Thanks for the report! We'l check that for the next release. jFinalizer uses PHP / joomla constants for path separators, so there could be some setup related issue.
Reply | Reply with quote | Quote
 
 
0 # RE: jFinalizer joomla! pluginJohn Smith 2010-03-10 20:53
Stefan, Joomslide doesn't load its images (by clicking the thumbnails).

I think Yoologin has some css compression enabled by default and it has problems with jfinalizer. The buttons disappear altogether.

I've noticed some minor issues with other modules but I disabled those just to have jfinalizer enabled.
Reply | Reply with quote | Quote
 
 
0 # RE: RE: jFinalizer joomla! pluginstefan 2010-03-11 06:55
Thanks for the report John. I guess you already tried to disable CSS compression. Anyway, we'll check Joomslide on the next release. Our goal is to have jFinalizer working on most setups without modifying plugin code or disabling modules.

Please expect the next upcoming release arround March 25th.
Reply | Reply with quote | Quote
 
 
+1 # Rok and MooFaqsarrene 2010-03-13 08:59
So far I love this little program. However, I have found that RokStories and Rockslideshow do not work with any "process HTML" settings enabled.

Also, MooFaq stays expanded on all compression levels minus safe mode A (Only when "process HTML" is enabled.

This is a great little program. Thank you. I hope that there can be a fix somewhere for the RokSlideshow and RokStories.

On a side note, RokBox works perfectly. Thank you again.

Other then that, it seems to work great on all the other several components and modules I have installed.
Reply | Reply with quote | Quote
 
 
+1 # RE: Rok and MooFaqsarrene 2010-03-13 10:05
I did find one other aspect that does not like to work 100%

Ajax search (RokAjaxSearch, YooSearch) These will bring up 0 results when you do a search. I have tried both of these on Rhuk and Dominion templates.

It happens when you have either "process JS" and/or "process CSS" to yes.

All compression levels.

Im sorry to post a second time. For now, I can keep these off. I do not know if you have many people that use any of the RocketTheme templates and or mods. If not, then I fully understand if these are on the end of the list of things to do.
Reply | Reply with quote | Quote
 
 
0 # RE: RE: Rok and MooFaqstefan 2010-04-23 16:42
Hi Sarrene,

thanks for the report. With the current release, 1.1.0, we could get RokAjaxSearch running in the new DeTab compression mode. Unfortunately, Yoosearch requires purchasing the component so we don't have access.
Anyway, RokAjaxSearch does not return any results on our site for "local" at all, no matter if jFinalizer is running or not. Google works fine.
Reply | Reply with quote | Quote
 
 
0 # DIRECTORY_SEPERATOR problemsHari Karam Singh 2010-03-15 17:23
Hi,

I've been testing your plugin. Very impressed so far.

On windows machines, the issue with DS is that DS meant really for file I/O. HTTP uses / on all systems.

Using DS causes problems in 2 areas as far as I can see:
1. The and lines in _writeJs and _writeCSS. The backslash is seen (by FF at least) as an escape code so you end up with "....assets3465..." instead of "...assets/12345..."

2. CSS url()'s get corrupted, especially if you have a "../" in the original. Thus BG images tend to disappear.

The first issue can be "hacked" by changing _writeJS (and _writeCSS resp) to the following:

$fly = $this->gzipmode == 1 ? 'js.php?' : '';

// Build URL
$url = '/'.$this->outPath.$fly.$jsFile;
if ( DS != '/' ) $url = str_replace( DS, '/', $url );// HTTP uses '/' universally

$l = ''.PHP_EOL;

I haven't worked out the workaround the CSS issue yet. Have you by any chance?

Your plugin seems much more feature rich and sensibly constructed then the others. I look forward to working out the kinks and using it on my sites.

-HKS
Reply | Reply with quote | Quote
 
 
0 # RE: DIRECTORY_SEPERATOR problemsstefan 2010-03-16 08:02
That really is a helpful report. We confirm the slash bug. Unfortunately, we dont have direct access to a windows server machine since we develop on Linux and Mac, so we know there are possible Windows issues.
The CSS bug you mentioned will be observed on the next release too.

Good work - thank you!
Reply | Reply with quote | Quote
 
 
0 # RE: RE: DIRECTORY_SEPERATOR problemsHari Karam Singh 2010-03-16 10:35
Quoting stefan:
Unfortunately, we dont have direct access to a windows server machine since we develop on Linux and Mac, so we know there are possible Windows issues.
The CSS bug you mentioned will be observed on the next release too.


I'll see if I can work it out for you when I get into that phase of the website I'm building. What's the best way to get word about the latest releases? Do you have a list?
Reply | Reply with quote | Quote
 
 
0 # RE: RE: RE: DIRECTORY_SEPERATOR problemsstefan 2010-03-16 11:01
The version history is posted on this page. Since we publish updates to the joomla extension directory extensions.joomla.org/.../... you should be able to be notified using favourites.
Reply | Reply with quote | Quote
 
 
0 # FIXED!Hari Karam Singh 2010-05-08 17:50
Hi Stefan!

Issue #2 You can fix in the latest release by changing lin 72 in helper.php from:

$this->tmp = substr($fn, 0, strrpos($fn, '/')).DS;

to:

$this->tmp = substr($fn, 0, strrpos($fn, '/')).'/';

Cool!
Reply | Reply with quote | Quote
 
 
0 # RE: FIXED!stefan 2010-05-09 10:00
Hi again,

Thank you for checking and the code! That's another important fix for the Windows setups. Verified and committed into 1.1.6.
Reply | Reply with quote | Quote
 
 
0 # jceutilities.jsHari Karam Singh 2010-03-15 17:25
Oh, and there seems to be glitch with jceutilites.js. When activated, even without compression, the error "s is undefined" is generated. I haven't looked into this in detail yet...
Reply | Reply with quote | Quote
 
 
0 # RE: jceutilities.jsstefan 2010-03-16 08:03
thank you - added to task list :)
Reply | Reply with quote | Quote
 
 
0 # RE: RE: jceutilities.jsstefan 2010-04-23 16:48
JCE Editor seems to work starting from 1.1.0 in the new DeTab compression mode, even with compacting.
Reply | Reply with quote | Quote
 
 
0 # Joomla subdirectoryKirck 2010-03-16 17:32
I have the joomla installation in a subdirectory not in the root folder, and I get this error when css/js process is enabled.

Warning: fopen(/root_path/joomladir/joomladir/path_to_css/file.css)

As you can see the joomladir repeats.
Reply | Reply with quote | Quote
 
 
0 # RE: Joomla subdirectorystefan 2010-03-16 18:20
thank you for the report. Can you confirm that other functions, like joomla's cache, work properly?
Reply | Reply with quote | Quote
 
 
0 # RE: RE: Joomla subdirectoryKirck 2010-03-16 18:27
I think so, no other errors get.
The asset folder created correctly inside cache folder.
Reply | Reply with quote | Quote
 
 
0 # RE: RE: Joomla subdirectoryKirck 2010-03-17 09:16
I hardcoded a fix for my problem (read and write files in correct directory) but the file permissions set 666 instead of 644 for css/js and 755 to php.
Reply | Reply with quote | Quote
 
 
0 # RE: RE: RE: Joomla subdirectoryKirck 2010-03-25 11:48
Sorry again, for some extrange reason your plugin was installed with different default file permissions. When copy/create the new files had this permissions.

Thanks for your support
Reply | Reply with quote | Quote
 
 
0 # Advanced: Place TagsKirck 2010-03-17 11:14
I've another issue with "Advanced: Place Tags"

1.- You need to declare global $mainframe to work, my template hasn't this.
2.- I'm testing only with js, and I only get the first jsp var value (jFJSxPL)
Reply | Reply with quote | Quote
 
 
0 # RE: Advanced: Place TagsKirck 2010-03-17 11:21
forget to say I switch Place tags to manual mode, sorry.

And thanks for your support.
Reply | Reply with quote | Quote
 
 
0 # RE: RE: Advanced: Place Tagsstefan 2010-03-17 11:39
1:
the variable name "$mainframe" is just an example. You need to know how to program joomla, thats why we say its "advanced": $mainframe, in the example above, refers to the joomla application framework object. You need to get an instance of it and then trigger the events.

2: I'm sorry, please explain a bit more detailed
Reply | Reply with quote | Quote
 
 
-1 # RE: RE: RE: Advanced: Place TagsKirck 2010-03-17 18:41
2.- Fixed, I had a problem with my template. Sorry

There any way to include the return value from addScript, addScriptDeclar ation Joomla functions inside the unified js file instead inside the html file?

Or How can I do to order the javascript declarations?

I have javascript errors because I have function calls before their statements.

Thanks
Reply | Reply with quote | Quote
 
 
-1 # Improve url relative images in css filesKirck 2010-03-19 15:47
Improvement: You can add a procedure to replace all tags in css with "url(/" text for relative images to url(siteurl/ to load this images. :)
Reply | Reply with quote | Quote
 
 
-1 # RE: Improve url relative images in css filesKirck 2010-03-19 23:35
Hello again and sorry :)
I did more tests and my previous comment is related to the same error with the joomla subfolder.
Reply | Reply with quote | Quote
 
 
-2 # problem with yoo-sliderjimg 2010-03-20 06:35
version: 1.0.11
template: rt_versatility4 _J15
compression: moderate (c+ didn't work with yooslider)

tried to process css, got an fopen warning:

fopen(/var/www/server/public_html/modules/mod_yoo_slider/mod_yoo_slider.css.php" type="text.css) [function.fopen]: failed to open stream: no .... /file/php line 240
(note the quote placements...)

Also of interest - if you load a css from a cdn, you get a similar fopen error :
fopen(/var/www/server/public_html/http://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.min.js)
Reply | Reply with quote | Quote
 
 
0 # RE: problem with yoo-sliderstefan 2010-04-23 09:48
thanks for the report! We will include experimental remote file support in the next relase, 1.0.12+
Reply | Reply with quote | Quote
 
 
+1 # next release ?Frederik 2010-03-29 15:00
Hello,
as there are no more posts since a week or so, i thought it might be a good idea to ask if there are any concrete details for next release.

I still have problems with googlemaps and wonder if this is solved with next version.

Are there any beta-testing-options ?

brgrds and have a nice week.

Frederik
Reply | Reply with quote | Quote
 
 
+1 # RE: next release ?stefan 2010-03-29 16:59
yes indeed, we work on the next release. I suppose that after additional checking, we should have it available at the end of this week.
Reply | Reply with quote | Quote
 
 
0 # ThanksÁlvaro González 2010-03-30 19:23
Thank you very much
Reply | Reply with quote | Quote
 
 
0 # JFinalizer not workingInformation Madness 2010-04-06 16:01
Hello there,
I tried to install JFinalizer but when I activate it, I get bunch of "File not found" errors for many js files and css files. Looks like the path of the file adds my root folder twice. I have installed joomla under /cms and it looks for files under /cms/cms .. can you please help me fix it and speedup my site?
Reply | Reply with quote | Quote
 
 
0 # RE: JFinalizer not workingstefan 2010-04-21 17:05
This seems to be related to the subdirectory bug. Please see comments below by ybas.
Reply | Reply with quote | Quote
 
 
0 # bypass commandbarkley 2010-04-09 21:19
I see this tip: "for bypassing HTML processing for only a specific block of Text or content plugin, wrap it with My bypassed content goes here in the article editor."

what is the exact command I need to use??? Thanks!
Reply | Reply with quote | Quote
 
 
0 # path cssybas 2010-04-10 15:38
I'm working for develope in a subfolder of my site with another installation of joomla and testing your plugin... firebug say me a 404 not found cause the path is to root/cache/assets/xxxxxxxxxxxxxx.css and not root/subfolder/cache/assets/xxxxxxxxxxxxxx.css

can not be used in a subdirectory?
Reply | Reply with quote | Quote
 
 
+1 # RE: path cssstefan 2010-04-21 17:03
Thanks for the report! This bug is confirmed and fixed in 1.0.12 which will be released this week.
Reply | Reply with quote | Quote
 
 
0 # errors on live siteavi 2010-04-12 21:34
Warning: fopen(/home/avush96/public_html/components/com_community/assets/jquery.qtip-1.0.0-rc3.min.js) [function.fopen]: failed to open stream: No such file or directory in /home/avush96/public_html/libraries/joomla/filesystem/file.php on line 240
Reply | Reply with quote | Quote
 
 
0 # hwdVideoShareLuca 2010-04-13 16:14
Hi..
I have problem with the rating and the other Ajax fuction with the componet hwdVideoShare.. can you help me?
Reply | Reply with quote | Quote
 
 
0 # RE: hwdVideoShareLuca 2010-04-14 14:29
The problem is that this component insert javascrit whith some comment line (//). How I can resolve this problem?
Reply | Reply with quote | Quote
 
 
0 # RE: jFinalizer joomla! pluginmilad 2010-04-13 21:08
hi, i have installed this plugin, but after enabling the submit button from tinymce editor does not work anymore
Reply | Reply with quote | Quote
 
 
0 # RE: RE: jFinalizer joomla! pluginstefan 2010-04-23 16:52
Thanks for the report! We work on that. Since JCE editor just works in 1.1.0, this must be another issue. We'll post as soon as we found out.
Reply | Reply with quote | Quote
 
 
0 # RE: jFinalizer joomla! pluginmp 2010-04-16 04:05
Thanks for this great plugin
This is a must for all my joomla sites.
I have just one issue could not resolve.
When ever I delete cache search link component gives following error
fFinalizer Error: cannot write to file: /www/xxxxxxxxx/xxxx/cache/assets/d41d8cd98f00b204e9 800998ecf8427e.js

I have to expire cache since my site update frequently. As soon as I refresh (not come back to the page) the page issue get resolved.
Any body had this issue?
Reply | Reply with quote | Quote
 
 
0 # RE: RE: jFinalizer joomla! pluginstefan 2010-04-23 15:59
thanks for the report! Unfortunately, we just cannot reproduce this behavior but we'll do some more testing.
Reply | Reply with quote | Quote
 
 
0 # RE: jFinalizer joomla! pluginybas 2010-04-23 10:35
now work css with the site online in root, great thanks, but i can't enable process javascript because don't work an image plugin downloaded here home.boncko.it/.../... and can't enable gzip, don't work (enabled in hosting)
Reply | Reply with quote | Quote
 
 
0 # RE: RE: jFinalizer joomla! pluginstefan 2010-04-23 15:58
I am sorry - you posted before we released. Please try v1.1.0 which just got online. It has experimental subdirectory support.
Reply | Reply with quote | Quote
 
 
0 # RE: jFinalizer joomla! pluginsascha 2010-04-25 18:15
again, THANKS for that fine work! but...

the jomsocial feed is not working with any settings :-(

error: Fatal error: Class 'JFeedItem' not found in...


best regards
Reply | Reply with quote | Quote
 
 
0 # RE: RE: jFinalizer joomla! pluginstefan 2010-04-26 07:36
Hi Sascha,

I´m sorry you still have problems with JomSocial. Unfortunately, we cannot reproduce them here. Can you please contact us by email at techsupport@far bfinal.de ? We are curios to work on this issue.
Reply | Reply with quote | Quote
 
 
0 # RE: RE: RE: jFinalizer joomla! pluginstefan 2010-04-26 08:38
There we go again - we found a possible bug which might be related to the News Feed problem on JomSocial. Please download v1.1.2 an tell us if it works now. We highly appreciate your feedback Sascha - thanks!

PS: according to JomSocial, we cannot get news feed contents in Safari, no matter if jFinalizer is active or not. Can you verify this?
Reply | Reply with quote | Quote
 
 
0 # RE: RE: RE: RE: jFinalizer joomla! pluginsascha 2010-04-26 18:19
Thank you stefan... it works! very good tool!
Reply | Reply with quote | Quote
 
 
0 # error in jomsocialavi 2010-04-28 01:10
Hi,
getting this error: jFinalizer Error 401: asset file not found: derberliton.de/.../...
after process JavaScript , can you help?
thanks
Reply | Reply with quote | Quote
 
 
0 # RE: error in jomsocialstefan 2010-04-28 06:53
Unfortunately, this seems to be a JomSocial problem. Please see jomsocial.com/.../... for more information.
Reply | Reply with quote | Quote
 
 
0 # error with cssavi 2010-04-28 01:46
Hi,
after using process CSS I get this erors:
jFinalizer Error 401: asset file not found: components/com_community/templates/default/css/style.css
jFinalizer Error 401: asset file not found: plugins/content/calendar_stamp/classic_red_dar k.css
I had to turn it off again and use only compact CSS and check conditional exceptions,
any idea how to fix that?
thanks
Reply | Reply with quote | Quote
 
 
0 # RE: error with cssstefan 2010-04-28 07:02
Since jFinalizer does HTML/XHTML processing and uses HTML optimized regular expression functions for more speed, it's never a good idea to use jFinalizer on a site which is not W3C valid.
So before using jFinalizer you should make sure your site validates against W3C. Please understand that debugging on a non-valid page is a huge challenge.
Reply | Reply with quote | Quote
 
 
0 # Joomla 1.5.17 problem ?Marco 2010-04-28 12:31
Hello!

Plugin works GREAT. Like the author said, it goes from host to host so you must play around - but it's worth it your time.

Now for my question, has anyone tried this with Joomla 1.5.17 ?
I get the error :

Fatal error: Cannot assign by reference to overloaded object in /xxx/xxx/public_html/plugins/system/jfinalizer.php on line 156

This is not a configuration problem, it seems that line in the code:
$mainframe->jFinalizer =& $this;

Any ideas ?
Reply | Reply with quote | Quote
 
 
0 # RE: Joomla 1.5.17 problem ?stefan 2010-04-28 16:53
We have jFinalizer running without any problems on joomla 1.5.17.

Anyway, we will investigate that issue deeper since we cannot reproduce that behavior on any of our test sites yet.
Reply | Reply with quote | Quote
 
 
0 # RE: jFinalizer joomla! pluginMic 2010-04-29 00:52
First of all, let me say what an excellent plugin this is! Fantastic work, and best of all, it's free!

I have managed to get it up and running but am encountering a slight problem.

The issue is the level of HTML compression, now I am running Joomla and phpBB3 with the jFusion bridge, when I have the DeTab HTML compression on, whenever a user edits or quotes a post, all line breaks are removed. This happens in all compression levels except "Safe Mode A" would there be any way to fix this? I know I could just stick with Safe Mode A but if I can fix this small issue I can use the faster DeTab one.

Cheers!
Reply | Reply with quote | Quote
 
 
0 # RE: RE: jFinalizer joomla! pluginstefan 2010-04-29 15:50
Thanks for the report Mic! After some email configuration and testing, we have found a jFinalizer Bug causing the line break issue. Fixed in v 1.1.5.
Reply | Reply with quote | Quote
 
 
0 # RE: jFinalizer joomla! pluginMic 2010-04-29 16:32
Thanks for the fix Stefan!

Just like to say that this guy does a top job at what he does, very helpful, insightful and he'll help you as best he can.

Unfortunately there are a few problems with my site which stop jFinalizer working to its full potential but he advised me on the problems and the reasons.

Support like this, I'm surprised it isn't a commercial plugin.

Top job!
Reply | Reply with quote | Quote
 
 
0 # Problem GzipLuca 2010-04-30 02:13
I did the upgrade from version 1.1.2 to the new version 1.1.5 and now I have a problem with "gzip output. This problem I had not before. Before I used "PHP gzip delivery" and it worked fine .. in the new version no longer works ..
Reply | Reply with quote | Quote
 
 
0 # RE: Problem GzipLuca 2010-04-30 02:43
I have even prblem with all fction of the last version.. :-(
Reply | Reply with quote | Quote
 
 
0 # RE: RE: Problem GzipLuca 2010-04-30 12:43
Thanks for the answer.. I have send you a reply mail..
Reply | Reply with quote | Quote
 
 
0 # ClickCartPro supportSteven Munro 2010-04-30 23:47
Hey buddy, excellent plugin. Works flawlessly on my site however I recently purchased clickcartpro (www.kryptronic.com) which integrates with Joomla and your plugin appears to prevent that software from "inserting" itself into the joomla template when enabled. Any idea?
Reply | Reply with quote | Quote
 
 
0 # getCompressedCSS - no outputvani 2010-05-01 10:53
When using getCompressedCS S and manual tag placement it outputs the comments around css links but does not output the combined css file.
getCompressedJs works ok.
Reply | Reply with quote | Quote
 
 
0 # RE: getCompressedCSS - no outputvani 2010-05-04 14:59
update: I've managed to get $mainframe->triggerEvent("getCompressed...") to output something, in fact it's an array but I don't know what to do with it?
Reply | Reply with quote | Quote
 
 
0 # manual tag placementvani 2010-05-10 15:01
I've tried debugging manual tag placement and ended up in dispatcher.php. On line 167 there is:
if (method_exists( $observer, $event))
...
with $observer being the jFinalizer plugin and $event being the 'getCompressedCS S', and it seems to evaluate to false!
Please shed some light on why that is so.
Reply | Reply with quote | Quote
 
 
0 # RE: jFinalizer joomla! pluginConrad 2010-05-05 15:54
Hi, your plugin is quite good but I found a bug when using it with SH404SEF. If your plugin is activated and user is logged in on frontend all is well. But if the user is not logged in and your plugin is activated then the urls in articles are not rewritten as they should. If I purge cache, I find correct urls on first load of the page, but if I reload the urls becomes wrong and stays wrong until I purge cache again.

Because of this I had to deactivate your plugin. Hope you can find what is wrong so I can reactivate it soon, since it is giving some very good results.
Reply | Reply with quote | Quote
 
 
0 # RE: RE: jFinalizer joomla! pluginConrad 2010-05-06 23:57
Solved by disabling the joomla cache module !
Reply | Reply with quote | Quote
 
 
0 # RE: RE: RE: jFinalizer joomla! pluginStenki 2010-05-09 21:57
The order of your plugins is not correct. I had the same problems with rewriting my urls. Just move it to the last position, after sh404sef and jFinalizer.

e.g.
system - all other plugins
system - sh404sef
system - jFinalizer
system - Cache
Reply | Reply with quote | Quote
 
 
0 # GzipRick 2010-05-15 21:12
how do you know if Gzip is working on your server..

If it is where do you find this and if so how do you know or waht do you see.

Just currious on how Gzip works..

thank and great product.. SHould i use this with smartoptimizer or is that OVERKILL

Just still on my test site for the time being..
Reply | Reply with quote | Quote
 
 
0 # JV LD ErrorEdfel 2010-05-18 01:18
Please see error related with rating.js

politicaboricua.com/.../page1

Thanks
Reply | Reply with quote | Quote
 
 
0 # RE: JV LD Errorstefan 2010-05-20 15:41
hi,
I´m sorry, but I can't really see what the problem is. Can you explain please?
Reply | Reply with quote | Quote
 
 
0 # RE: jFinalizer joomla! pluginyun 2010-05-19 20:24
getting this error:
jFinalizer Error 401: asset file not found: myweb/.../jomsocial.css | hide
i havent install jomsocial yet!
after i have checked remote CSS YES, it's no display error
dont u think this is error need to fix do u?
Reply | Reply with quote | Quote
 
 
0 # RE: RE: jFinalizer joomla! pluginstefan 2010-05-20 15:37
This can not be a jFInalizer issue, since we dont do any checking for specific 3rd party files.

Some part of your joomla installation, maybe a component, the template itself or a module, must push a link to that file into the output html. jFinalizer does not do that. It only processes what it finds in your HTML source.
Reply | Reply with quote | Quote
 
 
0 # css problemPeter 2010-05-20 15:26
Hy
Thanks for great plugin, works great, just one thing. When I turn CSS process on, my website doesn't show up with CSS. It's "naked". Any idea how to fix this?

Thank you!
Reply | Reply with quote | Quote
 
 
0 # RE: css problemstefan 2010-05-20 15:38
hard to say without any error messages. Can you give us a little more information? Please turn on jFinalizer debug mode and see what it says.
Reply | Reply with quote | Quote
 
 
0 # RE: RE: css problemPeter 2010-05-20 22:23
This is debug report:

process: /home/perop/public_html/terbo/plugins/system/cdscriptegrator /libraries/highslide/css/highslide.css
process: /home/perop/public_html/terbo/templates/yoo_symphony/css/template.css
process: /home/perop/public_html/terbo/templates/yoo_symphony/css/custom.css
process: /home/perop/public_html/terbo/templates/yoo_symphony/lib/js/mootools.js
process: /home/perop/public_html/terbo/plugins/system/cdscriptegrator /libraries/highslide/js/highslide-full.min.js
process: /home/perop/public_html/terbo/plugins/system/cdscriptegrator /libraries/jquery/js/jquery-1.4.2.min.js
process: /home/perop/public_html/terbo/plugins/system/cdscriptegrator /libraries/jquery/js/jquery-noconflict.js
process: /home/perop/public_html/terbo/plugins/system/cdscriptegrator /libraries/jquery/js/ui/ui.core.js
process: /home/perop/public_html/terbo/media/system/js/caption.js
process: /home/perop/public_html/terbo/templates/yoo_symphony/lib/js/addons/base.js
process: /home/perop/public_html/terbo/templates/yoo_symphony/lib/js/addons/accordionmenu.js
process: /home/perop/public_html/terbo/templates/yoo_symphony/lib/js/addons/fancymenu.js
process: /home/perop/public_html/terbo/templates/yoo_symphony/lib/js/addons/dropdownmenu.js
process: /home/perop/public_html/terbo/templates/yoo_symphony/lib/js/template.js
jFinalizer runtime Information
plugin total runtime: 3.00589s
JS files merged: 11
CSS files merged: 3
HTML Bytes saved: 3028 (20.4%)

DESIGN MODE (develop - slow!)

Do you have any idea how to fix this?
Reply | Reply with quote | Quote
 
 
0 # RE: RE: RE: css problemstefan 2010-05-24 11:51
well, everything looks good actually. No errors. Make sure all caches are cleared and the jFinalizer plugin is set to to order "last". Also, please check you delivery settings (php / htaccess / php gzip) and try all 3. See if it makes a difference. may, your server doesn't support all of them.

For further debugging with jFinalizer enabled, you might load your page, take a look you HTML source code and find the line that loads jFinalizer CSS (something like /cache/accets/82678Ab7268XXXX .css)

Then, you can copy this URL and see if you can open the CSS manually in the browser or using some other GET command.
Reply | Reply with quote | Quote
 
 
0 # Bugkai 2010-05-23 19:09
Installed 1.1.5 on Joomla 1.5.17 with JoomSef. My Joomla Install is in Root. but jf says everytime:

jFinalizer Error 200: Subdirectory path set but incorrect:
jFinalizer Error 201: Resulting physical path from given subdir does not exit: /srv/xxx/xxx/xxx/httpdocs
jFinalizer Error 202: Tip: if your joomla installation subdirectory is example.com/joomladir, use /joomladir, not joomladir/ or /joomladir/ or joomladir as subdirectory entry
Reply | Reply with quote | Quote
 
 
0 # RE: Bugstefan 2010-05-24 11:45
When joomla is installed in a domain root dir (www.exaple.com), the jFinalizer option "joomla subdirectory" must be empty (default). Your error sounds like you've entered a value there.
Reply | Reply with quote | Quote
 
 
0 # manual tag placementIvan Švaljek 2010-05-28 11:26
Can anyone please tell me why does $mainframe->triggerEvent('getCompressedJS ') return an Array[0] and how to get it to work in the head tag?

I've tried different templates, set jFinalizer position to last, tried debugging, but I just can't seem to get manual tag placement to work.
Reply | Reply with quote | Quote
 
 
0 # jFianlizer error: file not foundnewmediachick 2010-05-28 17:02
This plugin is god's gift to Joomla people who like speed! Thank you for developing it.

Now, the issue has been mentioned above but I don't think it was addressed. I moved a Joomla install between servers and everything was dandy. I uninstalled the last version I had (1.1.3) and installed 1.5, but as soon as I disabled all other custom plugins and tried to process CSS, JS, or enable any other option, I get:

jFinalizer Error: cannot create file: /home/mydomain/public_html/cache/assets/a39cce7d571673fd91d2b9a56c6e7fd3.css

mod_rewrite is active, as is symlinks, and the directory location doesn't seem to be an issue. Any ideas? (I disabled cache and re-enabled cache too, to no avail.)

Thanks!
Reply | Reply with quote | Quote
 
 
0 # RE: jFianlizer error: file not foundstefan 2010-05-29 06:39
This very much sounds like a permission issue. jFinalizer probably has no access rights to create the file. The path seems fine. Make sure the cache and assets directory are both writeable through PHP (usually, joomla should make them writeable by default). Maybe PHP error logs can help you.
Reply | Reply with quote | Quote
 
 
+2 # ThanksJoomla Expert 2010-06-03 10:06
Excellent post. Just wanted to say thanks for taking the time to write it!
Reply | Reply with quote | Quote
 
 
0 # Javascript processing doesn't seem to workMarko 2010-06-04 16:12
Javascript processing fails on my (correct) installation on localhost.

jFinalizer Error 401: asset file not found: /hp/templates/yoo_vox/lib/js/mootools.js
jFinalizer Error 401: asset file not found: /hp/media/system/js/caption.js
jFinalizer Error 401: asset file not found: /hp/templates/yoo_vox/lib/js/addons/base.js
jFinalizer Error 401: asset file not found: /hp/templates/yoo_vox/lib/js/addons/accordionmenu.js
jFinalizer Error 401: asset file not found: /hp/templates/yoo_vox/lib/js/addons/fancymenu.js
jFinalizer Error 401: asset file not found: /hp/templates/yoo_vox/lib/js/addons/dropdownmenu.js
jFinalizer Error 401: asset file not found: /hp/templates/yoo_vox/lib/js/template.js
jFinalizer Error 401: asset file not found: localhost/.../...
jFinalizer Error 401: asset file not found: localhost/.../...

The files are there and another Js combiner that I tested worked. Is there anything else required to make this work?

Thanks.
Reply | Reply with quote | Quote
 
 
+1 # RE: Javascript processing doesn't seem to workstefan 2010-06-04 18:15
It looks like your joomla is installed in a subdirectory. You might try to enter /hp into the joomla subdirectory setup option of jFinalizer.
Reply | Reply with quote | Quote
 
 
0 # RE: jFinalizer joomla! pluginadi 2010-06-11 05:10
Hi,thanks for great work,but I have a problem..

my frontpage shows "PAGE LOAD ERROR: The page you are trying to view cannot be shown because it uses an invalid or unsupported form of compression."

here my setting,
a.imagehost.org/.../...
Reply | Reply with quote | Quote
 
 
0 # RE: RE: jFinalizer joomla! pluginstefan 2010-06-17 11:46
Please try first to setup another gZIP delivery mode, maybe PHP delivery or even disable. See if your site works not.

If thats the case, your server probably does dynamic runtime compression already. In this case, you have to either adjust the .htaccess file (see tutorial above), switch delivery mode or even disable compressed output.
Reply | Reply with quote | Quote
 
 
0 # RE: jFinalizer joomla! pluginpaulo 2010-06-12 23:41
Warning: fopen() [function.fopen]: SAFE MODE Restriction in effect. The script whose uid is 10061 is not allowed to access /var/www/vhosts/bttmatosinhos.com/httpdocs/cache/assets owned by uid 48 in /var/www/vhosts/bttmatosinhos.com/httpdocs/plugins/system/jfinalizer/helper.php on line 169

Warning: fopen(/var/www/vhosts/bttmatosinhos.com/httpdocs/cache/assets/76a6ff790d4d88e 2ebee60f64ee136a6.css) [function.fopen]: failed to open stream: Permission denied in /var/www/vhosts/bttmatosinhos.com/httpdocs/plugins/system/jfinalizer/helper.php on line 169
jFinalizer Error: cannot create file: /var/www/vhosts/bttmatosinhos.com/httpdocs/cache/assets/76a6ff790d4d88e 2ebee60f64ee136a6.css
Reply | Reply with quote | Quote
 
 
0 # RE: RE: jFinalizer joomla! pluginstefan 2010-06-17 11:52
Safe mode can be difficult. Please try first if regular joomla caching works in FILE MODE. If thats NOT the case, jFinalizer will not work, because we do not support other caching mechanisms due to performance issues.

Guess: are you using the backend FTP mode? It could be possible that your files where installed by the FTP user (see UID) and joomla runs as another user, either under Apache or some own UID.

If thats the case, you must change the permissions on the /cache directory so the user/uid of running joomla (maybe 10061 in your case) can write. Use CHMOD or some FTP program to change permissions.
Reply | Reply with quote | Quote
 
 
0 # No gain in speed :(Martin 2010-06-17 06:35
Hi

I just installed an configured jf.
Before I did, I ran a speed test @ analyze.websiteoptimization.com

I am getting 20.81 seconds load time for T1 line.

After installing and configuring jf, clearing my cache, and reloading the site, I ran it again..

20.81 seconds...

And yes, I did switch it into production mode.

I got a few of the mentioned 'assets not found' errors, even though the files are present..

I had hoped for some serious improvements!

I still do...!

Martin
Reply | Reply with quote | Quote
 
 
0 # RE: jFinalizer joomla! pluginstefan 2010-06-17 11:59
Hi Martin,

as long as you get "asset file not found", there is definitely something wrong and you can't really expect a performance boost. Please review or post the output of the jFinalizer debugger.
Reply | Reply with quote | Quote
 
 
0 # RE: RE: jFinalizer joomla! pluginMartin 2010-06-19 09:52
Hi

thank you for the answer.
Error report says:

process: /web/akvarieplantete st/templates/yoo_phoenix/css/template.css
process: /web/akvarieplantete st/templates/yoo_phoenix/css/custom.css
process: /web/akvarieplantete st/modules/mod_agoriansonl ine/agorians_online /agorians_online .css
process: /web/akvarieplantete st/modules/mod_agora_lates t/agora_latest/agora_latest.css
process: /web/akvarieplantete st/modules/mod_vitallogin/css/modVitallogin.css
process: /web/akvarieplantete st/components/com_sobi2/templates/standard_advanc ed2/css/standard_advanc ed2.css
jFinalizer Error 401: asset file not found: templates/yoo_phoenix/css/ie.css
jFinalizer runtime Information
plugin total runtime: 0.01910s
JS files merged: (JS processing disabled)
CSS files merged: 7
HTML Bytes saved: 6425 (9.6%)

DESIGN MODE (develop - slow!)
hide

Now the file it refers to.. ie.css is not missing.. but maybe that's not what it is referring to?
Reply | Reply with quote | Quote
 
 
0 # RE: RE: RE: jFinalizer joomla! pluginMartin 2010-06-19 10:01
hi again.

I just found this error:

Warning: strstr() [function.strstr]: Empty delimiter in /web/akvarieplantete st/plugins/system/jfinalizer.php on line 392
listed about 14 times on agora forum on my site... it goes away when I disable javascript processing
Reply | Reply with quote | Quote
 
 
0 # RE: RE: RE: RE: jFinalizer joomla! pluginstefan 2010-06-21 16:14
you probably removed the entries in the "exclude / skip JS" box. Since there are default entries, they should never be removed. If your site works perfectly even without the default exclude entries (congratulation s!), enter a comma separated dummy entry there. These files must not exist. So you prevent the error.
Example: dummy.js,dummy2,js
Reply | Reply with quote | Quote
 
 
0 # RE: RE: RE: RE: RE: jFinalizer joomla! pluginMartin 2010-06-25 11:28
hi

no, I haven't removed any entries. They're still there untouched.

Are you sure it can only be related to that?
Reply | Reply with quote | Quote
 
 
0 # Error 401 with jomsocial RC1Avi 2010-06-20 15:58
Hello,
getting this error after upgrading to 1.8 rc1 jomsocial.
any idea or help will be most welcome,
thanks,
Avi

jFinalizer Error 401: asset file not found: /media/system/js/openid
Reply | Reply with quote | Quote
 
 
0 # RE: Error 401 with jomsocial RC1stefan 2010-06-21 16:17
please make sure (test in browser) that the file www.yourdomain.com/.../openid actually exists. If not, drop us a line again.

We have had some trouble on jomsocial with the plugin causing errors because it writes links to JS / CSS files into the HTML output of files that do not exist. Of course, jFinalizer will raise an error then. A workarround it to create a empty file on that location until the jomsocial team fixes the template / output.
Reply | Reply with quote | Quote
 
 
0 # Phoca mapsvani 2010-06-21 21:51
When using Phoca Maps on a page I get this error:
asset file not found: /components/com_phocamaps/assets/js/geoXML3.js
Reply | Reply with quote | Quote
 
 
0 # RE: Phoca mapsstefan 2010-06-22 06:40
When posting "asset file not found" errors, please check if the file really exists and drop a note. Most times, there is a HTML error in the joomla output because some module / plugin / template writes a link to a file which does not exist.
Reply | Reply with quote | Quote
 
 
0 # RE: RE: Phoca mapsvani 2010-06-22 07:24
It really was a file error, I guess the author was developing the component on windows and didn't care about lower/uppercase.

Thanks.
Reply | Reply with quote | Quote
 
 
0 # Process CSSvani 2010-06-22 13:14
Do you have any idea why enabling CSS compression:

process CSS ? No [Yes]
compact CSS ? [No] Yes
check conditional exceptions ? No [Yes]

...causes problem with @fontface declaration in Chrome(other css works fine), and other browsers don't have any problems.
Reply | Reply with quote | Quote
 
 
+1 # RE: jFinalizer joomla! pluginshoulders 2010-07-04 20:20
Hello

I have written some of the things that might improve jfinalizer. hope these help.

Version 1.1.5 for joomla! 1.5.10+
Joom;a 1.5.18

- option to move / compress inline javascripts to bottom/top or leave alone
- ability to add inline js files to the aggregated file
- gzip htaccess mode, add note to tooltip that jfinaliser creates a .htaccess files in its cache folder
- rather than this automode for script placement have the following options for javascript auto/manual/ after / just before , this would stop the need for template altering, do we need the same for CSS
- cache lifetime in s , additional note that this is the seperate cache for the aggregated CSS and JS files, not main cache
- explanation of the different compression modes
- additional tooltip note that production mode = cache on, and development = cache off
- additon to 'Quick workflow guide for setup:' - if you get errors check the system plugin order (i had issues with this where it moaned about my geshibot js file being missing, i moved jfinalizer to load after the content plugin. i only figured this out because i have been messing with plugin orders).

thanks for the plugin

shoulders
Reply | Reply with quote | Quote
 
 
0 # Bugshoulders 2010-07-04 22:58
Version 1.1.5 for joomla! 1.5.10+
Joomla 1.5.18
Yootheme Phoenix

in the HTML source code of my browser on my homepage and when jfinalizer is running the CSS is refernced by 1 CSS link. when i ran YSlow it kept saying there were too many CSS files. All the template CSS were listed. So i looked at the cache file and rather that the CSS all in on file i got several references like the following which sort of makes the aggregation a bit pointless.

@import url(/templates/yoo_phoenix/css/layout.css);

so in this cached file were more links rather than it as one great big CSS file.

please help

Thanks shoulders
Reply | Reply with quote | Quote
 
 
0 # custom tagsshoulders 2010-07-27 17:51
please add support similiar to support but for user enterd custom tags eg:

{geshibot}

a text box where you could enter these so when i paste code snippets on a page they are left alone.

thanks
Reply | Reply with quote | Quote
 
 
0 # jcemediabox.jsDaniel 2010-08-03 22:55
I have done analysis with analyze.websiteoptimization.com

and it seems to be ignoring jcemediabox.js
----------------------------------------
Header size = 240 bytes
Up to 29430 bytes could have been saved through compression.
Reply | Reply with quote | Quote
 
 
0 # RE: jcemediabox.jsDaniel 2010-08-03 22:58
What i meant to say:
jFinalizer is ignoring jcemediabox.js
Reply | Reply with quote | Quote
 
 
0 # Gzip doesn't work with IE6D0gSoldi3r 2010-08-09 16:49
I cannot use Gzip Php compatible with Jfinalizer, as my site doesn't display correctly with ie6, i hate ie6 however alot of people still use it making the Gzip option useless to me but i want to activate Gzip but it breaks my site in ie6 somebody please help me :(
Reply | Reply with quote | Quote
 
 
0 # ForgotD0gSoldi3r 2010-08-29 21:51
Forgot to mention the It doesn't say anywhere what version of Jfinalizer i'm using so how am i suppose to tell you, the zip file only says "plg-system-jfinalizer-current" and in the backend it says no version either, so i have no way of knowing what version i have so why ask us if you don't put it anywhere. It does Say April 2010 in the readme.

And oh yeah still having this Gzip IE issue can anybody help me (read above) Gzip works on all browsers apart from ie6 making the option useless to me :(
Reply | Reply with quote | Quote
 
 
0 # RE: Gzip doesn't work with IE6VG 2010-09-12 16:48
Quoting D0gSoldi3r:
I cannot use Gzip Php compatible with Jfinalizer, as my site doesn't display correctly with ie6, i hate ie6 however alot of people still use it making the Gzip option useless to me but i want to activate Gzip but it breaks my site in ie6 somebody please help me :(


I think the easiest way is to put a check for IE6. If someone uses a product that is not supported even by the manufacturer, will charge uncompressed files.
Reply | Reply with quote | Quote
 
 
0 # Skip JS files issueNicola 2010-08-22 10:17
Hi, I've added the ipGmapScript.js file to the list of the JS files to skip, but when "Process Javascript" is enabled that js crashes. It seems that jFinalizer ignores my skip list...
Reply | Reply with quote | Quote
 
 
0 # RE: jFinalizer joomla! pluginCarsten 2010-08-23 13:20
Hello jFinalizer Team,

i have a problem concerning my jfinalizer. if i have at least 10 textareas in my html buffer it seems like jfin puts the last digit after the textarea closure tag.

has anyone the same problems?

jFinalizer Version: 1.1.5
Compression: deTab
Mode: Live

kind regards and thank you in advance
carsten
Reply | Reply with quote | Quote
 
 
0 # Amazing Plugin!!Jeremy Phillips 2010-08-29 17:12
This product is absolutely brilliant. It works perfectly and dramatically increased my site's load time.
Reply | Reply with quote | Quote
 
 
0 # Awesome Plugin!!!!!Burner 2010-09-02 02:21
Not only a simple and effective as promised plugin but a great plugin to use to learn the ins and outs of FireBug. Also, great that other plugins work in hand and the Joomla cache.

Looking forward to seeing the next version :-)
Reply | Reply with quote | Quote
 
 
0 # java error tmpurlkai 2010-09-21 20:20
when i activate java script handeling:

Details zum Fehler auf der Webseite

Benutzer-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; Win64; x64; Trident/4.0; GTB6.5; .NET CLR 2.0.50727; SLCC2; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; Media Center PC 5.0; SLCC1; .NET4.0C)
Zeitstempel: Tue, 21 Sep 2010 19:19:50 UTC


Meldung: 'tmplurl' ist undefiniert
Zeile: 1262
Zeichen: 1
Code: 0
URI: szenenight.de/.../...


What could be the problem?
Reply | Reply with quote | Quote
 
 
0 # Website speed recordFábián Gábor 2010-09-22 00:51
I tried 2 other compression plugins for Joomla, I used each for several months, but I wasn't satisfied. Now, I tried jFinalizer on my new template I just finished, and it works great even on ultra compression! My website smashed the 2 years of speed record!

Thank you!
Reply | Reply with quote | Quote
 
 
0 # HELPmatt 2010-10-20 05:13
After I activated the plugin everythink is donw. I cant open my joomla administration menu. just blank and this message, can anybody help? ->

Parse error: syntax error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or '}' in /var/www/web1165/html/joomla/plugins/system/jfinalizer.php on line 64
Reply | Reply with quote | Quote
 
 
0 # RE: jFinalizer joomla! pluginGert 2010-10-20 06:07
It looks as if CSS3 code for gradients is not always done right. For reproduction, you can use Colorzilla Gradien Editor (www.colorzilla.com/.../).
Reply | Reply with quote | Quote
 
 
0 # jFinalizergabriela 2010-10-20 09:45
hi there,

as soon as I enable css or js processing on user side error messages show up that none of the existing js/css files can be found. what am I doing wrong?
Reply | Reply with quote | Quote
 
 
0 # Break with php 5.3.3ssnobben 2010-10-23 15:45
Hi I got a problem when using Jfinalzer v. 1.1.5 rc1 with php 5.3.3 J 1.5.21

Got this error breaking my site.

Warning: get_class() expects parameter 1 to be object, array given in /home/site/public_html/plugins/system/jfinalizer.php on line 152

Warning: get_class() expects parameter 1 to be object, array given in /home/site/public_html/plugins/system/jfinalizer.php on line 152

Warning: get_class() expects parameter 1 to be object, array given in /home/site/public_html/plugins/system/jfinalizer.php on line 152

Any tips how to fix this?
Reply | Reply with quote | Quote
 
 
0 # Thumbnails will not expandBob 2010-10-29 02:41
Is there a way to block a component? The thumbnails on my pictures will not expand when I process css. The component I need to block is rd_autos, you can see an example page at muscle--cars.com/.../

The css is not processed at this time, as far as I can tell there were no other issues.

Thank you,

Bob
Reply | Reply with quote | Quote
 
 
0 # RE: jFinalizer joomla! pluginBob 2010-10-29 02:47
updat, the thumbs do expand, however instead of being at the top of the page they are at the bottom and half the image is not showing
Reply | Reply with quote | Quote
 
 
0 # CSS crash under IE why?Simo 2010-11-04 13:03
Hello, I am using 1.1.5 rc1 version of this very nice plugin. I noticed that on this site zdrawe.eu when viewing with IE 6,7,8 it acts like there is no CSS applied. I am stuck with this and figure it out. Please take a look I am leaving it that way with broken design so you may check it out.

Thanks I appreciate the support.
Reply | Reply with quote | Quote
 
 
0 # designerJosh 2010-11-08 20:03
When using jfinalizer, sometimes I get a window that pops up to download index.php. What function is causing this so I can disable. It does not happen all the time so it is hard to debug.

Version 1.1.5 for joomla! 1.5.10+
html compression moderate
no gzip.
Reply | Reply with quote | Quote
 
 
0 # jFinalizer Error 100J. Boer 2010-11-14 15:15
Hi, I followed your tutorial. After setting it up I get the following message at the frontend: "jFinalizer Error 100: cannot create cache path: /var/www/vhosts/MY SITEdotcom/httpdocs/cache/assets/"

I already have created he path manually and set the privileges to 766 for that folder with no result. Next to that I see no decrease of loading times and Yslow does not show a decrease of loading CSS and JS.

Something must go wrong but I can't figure out what.

Any hints are welcome.

J. Boer
Reply | Reply with quote | Quote
 
 
0 # settingsJ. Boer 2010-11-15 18:42
settings used. Though other settings show the same problem

artlantisobjects.com/.../...
Reply | Reply with quote | Quote
 
 
0 # no background imagesandy nagai 2010-11-25 07:59
I noticed that jfinalizer is modifying my css files wherever I set a background image. It adds a path to the css dir to the path that is already in the url(). It does this wherever there is url() in the stylesheets. Of course this breaks the background images. My site has no background images because of this? This is a bug?
Reply | Reply with quote | Quote
 
 
0 # no background imagesSteve 2011-08-11 04:14
I also am having this problem. At the moment I am just working on a local host but it looks for the images at site/css../images/logo.png rather than where it should be. Background css images work fine with plugin disabled.
Reply | Reply with quote | Quote
 
 
0 # RE: no background imagesstefan 2011-08-11 07:59
Can you mail us a set of your css files for testing to techsupport@far bfinal.de ?
Reply | Reply with quote | Quote
 
 
0 # Cookieless domainslikemandrake 2010-11-26 01:13
PageSpeed test if static contents (like images, styles and scripts) are downloaded from cookieless domain. Maybe You should add support it? I think it maybe very simple...

In preferences:
Cookieless domain: mydomain.com

Example description: If You have many (sub)domains for single Joomla site, You may decide which should be used for cached content like styles or scripts (e.g. cookieless domain).

In action:
$content = "/cache/assets/123456789.css";
$domain = "mydomain.com";
$path = "http://" . $domain . $content;

etc...
Reply | Reply with quote | Quote
 
 
0 # IE Conditional Commentslikemandrake 2010-11-29 11:45
Hello,

I'm using JFinalizer Version 1.1.5 for joomla! 1.5.10+ with "Simple Mode A" HTML Compression. JFinalizer not works properly for the following code:

Quote:



JFinalizer removes "" and "", but this is properly and working code (In Example, served by code.google.com/.../...).
Reply | Reply with quote | Quote
 
 
0 # RE: IE Conditional Commentslikemandrake 2010-11-29 11:49
Hmmm, code was truncated... I'll try again...

<!--[if ! lte IE 6]><!-->
<link rel="stylesheet" href="/templates/mytemplate/styles/styles.css" type="text/css" />
<!--<![endif]-->
<!--[if lte IE 6]>
<link rel="stylesheet" href="/templates/mytemplate/styles/styles-ie6.css" type="text/css" />
<![endif]-->

REMOVES:

"<!--[if ! lte IE 6]><!-->" and "<!--<![endif]-->"
Reply | Reply with quote | Quote
 
 
0 # jFinalizer and System CacheRafael 2010-12-03 14:19
Hi,

Congratulations for the plugin, thanks to you i'm getting 94 in YSlow

But i have one problem.

If I enable the Jommla's system - cache plugin, my grade in YSlow goes to 85.

The html, css, and js are not merged and compressed.

My Joomla version is 1.5.20
My jFinalizer version is 1.1.5

The order of my plugins are:
System - cache 7
jFinalizer - 8

No matter the order, it never work together.

Can you help me?
Reply | Reply with quote | Quote
 
 
0 # jsapiGaz 2010-12-12 13:54
Hi,
seem to be getting jFinalizer Error 402: remote file inclusion enabled but file could not be loaded: www.google.com/jsapi

only every now and then.

Thanks
Garry
Reply | Reply with quote | Quote
 
 
0 # ProductionGaz 2010-12-12 18:03
Production mode is giving errors front end can't use it like this. I don't want to correct some errors.
Reply | Reply with quote | Quote
 
 
0 # jFinalizer cacheGentchev 2010-12-14 09:23
When I make changes to a css file and delete the cache, the changes are not reflected in the browser.
This means that this change will not be visible to any client.
I think the problem is that after deleting the cache, the new file that is created is with the same name as deleted.

Is there a way to solve this problem?
Thank you.
Reply | Reply with quote | Quote
 
 
0 # Css filesKr3ck3n 2010-12-22 15:11
Hi,
This is a great plugin... but i have a little problem.

The problem is that the css files for ie6,7,8 are not loading...
What should i do?

Thx.
Reply | Reply with quote | Quote
 
 
+2 # jcomment is brokenavi Efroni 2010-12-23 15:09
Hi, looks like that it has a conflict with jcomment, what to do to make it work?
Avi
Reply | Reply with quote | Quote
 
 
-1 # Configure entity tags (ETags)dedi123 2010-12-27 04:20
This Plugin is working perfectly, but only Configure entity tags (ETags) with misconfigured ETags. How to solve it?

Thanks
Reply | Reply with quote | Quote
 
 
+1 # RE: jFinalizer joomla! pluginlikemandrake 2010-12-28 14:38
I think the project is dead...
Reply | Reply with quote | Quote
 
 
+1 # project deadDado 2010-12-28 14:59
it really seems jfinalizer developers don't maintain it any more.

It could be one of those must have extensions,..... what a shame :(

cheers
Reply | Reply with quote | Quote
 
 
+1 # project dead ?eorisis 2010-12-28 16:24
is it you think ? shame indeed if it is, cause it's the best one I ever used by FAR.

shame if it is dead.
Reply | Reply with quote | Quote
 
 
+1 # RE: project dead ?Dadoa 2010-12-28 18:10
i also think it is the best...at least among the ones i tried ....

shame if it is dead.
Reply | Reply with quote | Quote
 
 
+1 # A note from the Developersstefan 2011-01-08 11:57
Dear jFinalizer users,

the project is not dead. We currently work on some bugfixes for a new release. Since joomla 1.6 RC1 is available, we want to also do some testing with this.
Reply | Reply with quote | Quote
 
 
+1 # Happy Hearing the upcoming releases !!!dedi123 2011-01-08 12:06
Hope it will be released soon..

Thanks
Reply | Reply with quote | Quote
 
 
+1 # cannot create fileschwarzy2 2011-01-18 14:46
Hi,

your plugin looks great, but I've got a problem when I activate js process or css compress, I got the error:"cannot create file cache/ced456628fredeo lijl.css "
I'm on a Linux server and the two directories css or js created have 755 for rights and apache as owner. That's why I think the file cannot be created. Do you have an idea of what I can do?

in advance thanks
Reply | Reply with quote | Quote
 
 
+1 # ImpressiveEsperado 2011-01-28 15:14
Very impressive.
On a very complicated site and forum, using a lot (A LOT !) of dynamicaly loaded javascript and css files, using severall Js libraries (mootools + Jquery +Ajax etc )
it worked in less than 5 minutes with full options and no errors. (My site was 100% W3C compliant, both on html and css before activation of your plugin. It still is.)

Amazing ! Thanks and congratulation.

BTW: i used Smartoptimizer, and, before i modify my htaccess to deactivate-it, no conflict neither.
Reply | Reply with quote | Quote
 
 
0 # RE: jFinalizer joomla! pluginEsperado 2011-01-28 15:42
OOoops, in fact not, i was too fast: a lot of javascript does not work any more.
Will try to figure out and be back.
Reply | Reply with quote | Quote
 
 
0 # RE: jFinalizer joomla! pluginChristian 2011-01-28 23:44
Has anyone figured out a way to block individual components in this program?

Christian
Reply | Reply with quote | Quote
 
 
+1 # CBob Lee 2011-01-28 23:49
Thank you for all your work stefan, looking forward to the new 1.6 plugin
www.wefell.com/
Reply | Reply with quote | Quote
 
 
0 # Perfect.Esperado 2011-01-29 14:38
Everything working now, with little changes in code of some external modules.
So fast, now, solid feeling for visitors due to unique files, Js changed on top is a goodpractice(so metimes 10 files on my site). PERFECT !
Suggestion: to add compression on online JS in headers.
www.street-photo.fr
Reply | Reply with quote | Quote
 
 
0 # Auto copy of css.php and js.phpAlex 2011-02-17 12:10
Hi !
I've a problem with this plugin, when i activate it, my CSS and JS are not loaded. The plugin works find when i copy manually in the folder "cache/assets" the two files css.php and js.php. I dont understand because the right seems to be ok on the "assets" folder. Its the Jfinalizer script who create it... Have you an idea for what this two files are not copied in this folder ? (I used the latest version of Jfinalizer and joomla 1.5.22)Sorry for my english and thanks in advance.
Reply | Reply with quote | Quote
 
 
0 # safe_mod deactivatedschwarzy2 2011-02-17 14:14
Hi Alex,

Looks like we had the same problem, I solved mine by deactivating safe_mod in PHP, have you tried this?
Reply | Reply with quote | Quote
 
 
0 # RE: safe_mod deactivatedAlex 2011-02-17 15:12
Thank you for your reply. My php config local_value of safe_mod is "off". I don't understand, because the css file and the js is correctly generated and write to the assets folder but the css.php and the js.php are not copied. Another idea ? ;-)
Reply | Reply with quote | Quote
 
 
0 # what is your error?schwarzy2 2011-02-17 15:17
I don't succeed in understanding you very well....what are the files css.php and js.php you're speaking?(and what is your language?)
Reply | Reply with quote | Quote
 
 
0 # RE: what is your error?Alex 2011-02-17 17:28
I'm french so sorry for my english... ;-)

Files which should be copied automatically in the file assets by the script of the plugin when I activate the compression Gzip in the plugin. Because when this function (gzip) is activated in the plugin, the url of my files becomes in case of CSS : /cache/assets/ css.php?C2c19359d85d6e4d6ba94 7417788f39b.css
As PHP files are not copied, the link of my CSS and JS is broken... But if I desactivate the Gzip function of the plugin everything is OK.
Reply | Reply with quote | Quote
 
 
0 # french tooschwarzy2 2011-02-18 08:43
c'est bien ce qu'il me semblait, on est frenchies tous les deux!
je vais essayer de voir de mon côté dès que j'ai un moment, là je ne peux pas, sans doute dimanche.
Reply | Reply with quote | Quote
 
 
+1 # RE: french tooAlex 2011-02-18 09:21
Ca c'est fort ^^ ! Merci pour ta réponse et ta réactivité. J'attends ton retour avec impatience. Bon weeek end. Merci d'avance.
Reply | Reply with quote | Quote
 
 
0 # même problèmeschwarzy2 2011-02-20 11:53
Bonjour,

j'ai donc constaté que j'avais le même problème, mais je n'ai pas pu aller plus loin, j'ai constaté en fait des problèmes supplémentaires ...seuls les fichiers de mes modules sont compressés pas ceux de mon template!
je crois que je vais réessayer cssjscompress...je verrais ça plus en avant lundi! pour toi si ton seul problème est cette histoire de fichiers, tu devrais les laisser dans le cache...
@ +
Reply | Reply with quote | Quote
 
 
+2 # RE: même problèmeAlex 2011-02-20 14:04
Merci pour ta réponse.
Chez moi les fichiers de mon template sont bien compressés. C'est effectivement ce que je voulais faire les laisser dans le cache mais le problème est le suivant, lorsque je fais une modifs dans mes CSS par exemple, je dois vider le cache joomla pour que les modifs soient effectives. Et lorsque je vide le cache, le dossier assets complet est supprimer avec mes fichiers css.php et js.php... C'est là le problème. Puis quand le dossier assets est régénéré, ces deux fichiers sont à nouveau absents. Comme ce dossier est créé par le script, en passant par le ftp, impossible de copier les fichiers php dans ce dossier manuellement. Je dois donc passer par le composant extplorer pour joomla pour modifier les droits en écriture dans ce dossier et après la copie de ces fichiers php devient possible. Mais c'est une opération fastidieuse en cas de modifications régulières des CSS. J'ai donc pour l'instant désactiver la compression gzip du plugin, comme ça plus besoin des fichiers css.php et js.php, le lien est donc direct :
/cache/assets/c2c19359d85d6e4d6ba94 7417788f39b.css
A++
Reply | Reply with quote | Quote
 
 
0 # RE: jFinalizer joomla! pluginlikemandrake 2011-02-22 12:05
Hello,

in file jfinalizer/helper.php on line 103 I think instead of $fn = $this->jf->HTDocRoot.$fnc['path']; should be $fn = $this->jf->HTDocRoot.'/'.ltrim($fnc['path'], '/');

Some components (modules, plugins etc.) adds relative path to css or js (without adding the character '/' at the beginning of path) using JDocument class (addStyleSheet, addScript). jFinalizer not cope with these cases (shows "asset file not found" error) and this patch solves this problem.

Regards
Reply | Reply with quote | Quote
 
 
0 # RE: RE: jFinalizer joomla! pluginAlex 2011-02-22 16:37
Thank you for your response.
I've tested this modification, but it does'nt solve my problem. My problem is not on the path of my CSS and JS files but in the no copy of the files css.php and js.php in the assets folder. Required files when Gzip is activated in the plugin.
So it works when i desactivate the Gzip function...

Best regards
Reply | Reply with quote | Quote
 
 
0 # RE: RE: RE: jFinalizer joomla! pluginlikemandrake 2011-02-22 18:27
Could you tell me more? Normally I do not use the gzip feature from jFinalizer, but I turned it (both options) and I can't see any problems. How to trigger this error?
Reply | Reply with quote | Quote
 
 
+1 # RE: RE: RE: RE: jFinalizer joomla! pluginAlex 2011-02-27 17:04
I've tested on another server and when i activate the gzip function, the php files are correctly copied in the assets folder... So it's probably the serer config. I have to find the difference. Thank you for your response. ;-)
Reply | Reply with quote | Quote
 
 
0 # Errorgrobadicto 2011-02-27 03:10
When i try enable process javasript i have this errors.How can i fix it?
Warning: file_get_conten ts() [function.file-get-contents]: URL file-access is disabled in the server configuration in .../plugins/system/jfinalizer/helper.php on line 93

Warning: file_get_conten ts(gasafondo.com/.../...) [function.file-get-contents]: failed to open stream: no suitable wrapper could be found in .../plugins/system/jfinalizer/helper.php on line 93

Warning: file_get_conten ts() [function.file-get-contents]: URL file-access is disabled in the server configuration in .../plugins/system/jfinalizer/helper.php on line 93

Warning: file_get_conten ts(gasafondo.com/.../...) [function.file-get-contents]: failed to open stream: no suitable wrapper could be found in .../plugins/system/jfinalizer/helper.php on line 93

Warning: file_get_conten ts() [function.file-get-contents]: URL file-access is disabled in the server configuration in .../plugins/system/jfinalizer/helper.php on line 93

Warning: file_get_conten ts(gasafondo.com/.../ajax_1.3.js) [function.file-get-contents]: failed to open stream: no suitable wrapper could be found in .../plugins/system/jfinalizer/helper.php on line 93

Tryin enable prcess css the same errors.
Bye
Reply | Reply with quote | Quote
 
 
0 # Gallery plugin is not workingRetro Alfa 2011-03-08 09:44
I have a little problem with the plugin, my gallery plugin (sigplus Image Gallery Plus) is not working anymore even when I turn off jFinalizer the gallery is not working.
Here is my setup i52.tinypic.com/2hfkvp0.jpg, any other settings will break the page, I might mention that this is done on localhost and I know there will be differences on the server but my gallery plugin is not working on lacalhost so I dont wanna try it on a live site before I dont know a reason why it stopped working completely.
Reply | Reply with quote | Quote
 
 
+1 # ForbiddenJay 2011-04-25 04:17
When I turn on processing of CSS, I see the compressed file but my server gives a forbidden (403) error and tells me that I am not allowed to access it so I get no CSS at all. Any thoughts about why that might be?
Reply | Reply with quote | Quote
 
 
+1 # PerfectTunç Tataker 2011-05-08 21:34
I used this product on my personal web site www.tataker.com It's working very good. Thank you very much!
Reply | Reply with quote | Quote
 
 
+1 # Same problem with acajoom cssAlex 2011-05-24 13:34
Hi say mi please how i can rezolve this - jFinalizer Error 401: asset file not found: components/com_acajoom/css/acajoom.css
Reply | Reply with quote | Quote
 
 
0 # RE: Same problem with acajoom csslikemandrake 2011-05-24 19:23 Reply | Reply with quote | Quote
 
 
0 # RE: RE: Same problem with acajoom csslikemandrake 2011-05-24 19:25
Ehhhh, sorry.... www.farbfinal.de/.../
Reply | Reply with quote | Quote
 
 
+1 # RE: jFinalizer joomla! pluginMailinator 2011-06-08 00:03
Hi!

When will be jFinalizer available for Joomla 1.6. I have tried to install current version of JF without success..

Thanks
Reply | Reply with quote | Quote
 
 
0 # 1.6Old Classic Cars 2011-06-10 12:44
You do great work Alex, I appreciate the hard work developers such as yourself do. I am looking forward to the future release of this extension for 1.6. I have a classic cars site muscle--cars.com that I will convert to Joomla as soon as more extensions are made available for 1.6
Reply | Reply with quote | Quote
 
 
0 # Exclude CSSAlex 2011-06-17 17:08
Hi !
I've created an external CSS for media="print", when i activate Jfinalizer and the "process CSS" function, this style sheet is combined with my media="sreen" CSS, so my layout is disrupted...
Can i exclude a CSS file ? If yes how can i proceed ? Else, another idea ?
Thank you in advance.
Best regards.
Reply | Reply with quote | Quote
 
 
0 # Fix for 1.1.5?Darwin 2011-12-07 18:14
I have the same issue, but I'm stuck on J 1.5 for the time being. I saw there was a fix posted in response to this for jF 2.0.0, is there a fix forthcoming for 1.1.5? Thanks! Fantastic plugin.
Reply | Reply with quote | Quote
 
 
0 # Outdated Google Cached page versionsorasis 2011-06-21 00:58
Hi, I would like to ask about something that I am not sure how important it can be at last, but anyway.

Google's Cached versions of the pages that use jFinalizer are almost always at some level outdated. This means that the cached version will have the old css path that jFinalizer created in joomla cache. for example:

Once the webmaster clears the cache of the joomla site, then Google will show a "broken" cached version without css or js etc.

I am not sure of how important that is ... neither how it can be solved. It is all related to the random filename that gets created in the cache of joomla.

thanks and keep up.
your software works excellent and it is the best one we ever used.
Reply | Reply with quote | Quote
 
 
0 # RE: Outdated Google Cached page versionsorasis 2011-06-21 01:01
the code wasn't posted above so, I was talking about this path in source code:
/cache/assets/81e9a41007fc01f0b2e55fbee9585 86e.css
Reply | Reply with quote | Quote
 
 
0 # JFinalizer Problem IE7Andre 2011-06-27 15:10
Hi,
I love your tool, but I can't get it to work with IE7. The report says, there are a lot of js-errors. If I disable "combine JS), everything works fine. If I enable it, it still looks fine in every other browser, except IE7.
Can you help me out here?

Thanks
André
Reply | Reply with quote | Quote
 
 
0 # jFinalizer Error 200: Subdirectory path set but incorrect:Mahek 2011-07-24 11:23
jFinalizer Error 200: Subdirectory path set but incorrect:

My site is installed on sub-domain - store.activeanalytic.com/ , Main website is different - www.activeanalytic.com/.
(I used plugin on sub-domain site)

jFinalizer Error 200: Subdirectory path set but incorrect: store.activeanalytic.com/
jFinalizer Error 201: Resulting physical path from given subdir does not exit: C:\Domains\acti vean\store.a
jFinalizer Error 202: Tip: if your joomla installation subdirectory is example.com/joomladir, use /joomladir, not joomladir/ or /joomladir/ or joomladir as subdirectory entry
Reply | Reply with quote | Quote
 
 
0 # RE: jFinalizer Error 200: Subdirectory path set but incorrect:stefan 2011-07-24 11:30
Leave the subdirectory field empty. Your site is installed into a subDOMAIN, not a subDIRECTORY.
Reply | Reply with quote | Quote
 
 
0 # RE: RE: jFinalizer Error 200: Subdirectory path set but incorrect:Mahek 2011-07-25 17:54
Yes, it was blank and still the error kept coming, i tried entering few combinations but nothing seems to work...
Reply | Reply with quote | Quote
 
 
0 # RE: RE: jFinalizer Error 200: Subdirectory path set but incorrect:Mahek 2011-07-25 18:06
jFinalizer Error 200: Subdirectory path set but incorrect:
jFinalizer Error 201: Resulting physical path from given subdir does not exit: C:\Domains\acti vean\store.activeanalytic.com\wwwroot
jFinalizer Error 202: Tip: if your joomla installation subdirectory is example.com/joomladir, use /joomladir, not joomladir/ or /joomladir/ or joomladir as subdirectory entry

check the site: store.activeanalytic.com/
(error still there)
Reply | Reply with quote | Quote
 
 
0 # RE: RE: RE: jFinalizer Error 200: Subdirectory path set but incorrect:stefan 2011-07-25 18:15
The only way we can reproduce your problem is this:

The jFinalizer field "joomla subdirectory" is not REALLY EMPTY. When we put a SPACE CHARACTER (" ") in, we get this error. Can you verify its really empty?
Reply | Reply with quote | Quote
 
 
0 # RE: RE: RE: RE: jFinalizer Error 200: Subdirectory path set but incorrect:Mahek 2011-07-25 18:24
yes, i just checked again, it was empty, deleted again just in case, same error, used keyboard ctrl+A del,same error still there.... The plugin is very good, reduced the site load time by 6 secs. Thanks for plugin.

(now, how to remove this error :( )
Reply | Reply with quote | Quote
 
 
0 # RE: jFinalizer joomla! pluginstefan 2011-07-25 19:01
The bad news: This seems like a server configuration issue since jFinalizer cannot determine the joomla root installation folder (physical storage path, not web root).

What Joomla and PHP versions are you running?
Reply | Reply with quote | Quote
 
 
0 # RE: RE: jFinalizer joomla! pluginstefan 2011-07-25 19:42
I noticed you run a windows server. Can you confirm that this directory exists (according to the jFinalizer error message): C:\Domains\acti vean\store.activeanalytic.com\wwwroot ?
Reply | Reply with quote | Quote
 
 
0 # RE: RE: RE: jFinalizer joomla! pluginMahek 2011-07-26 04:20
Yes, the directory exists, It is windows server.

(check this file: store.activeanalytic.com/.../) (it is in the folder)

PHP Version 5.2.6
(www.activeanalytic.com/.../)
Joomla Version 1.5.22
Reply | Reply with quote | Quote
 
 
0 # RE: RE: RE: RE: jFinalizer joomla! pluginstefan 2011-07-26 07:58
That's a different story. Your link points to the webserver front end path. That does not mean that the physical storage path on the server is correct. Please post your joomla / PHP / Web server versions.
Reply | Reply with quote | Quote
 
 
0 # RE: RE: RE: RE: RE: jFinalizer joomla! pluginMahek 2011-07-26 15:33
PHP Version 5.2.6
Joomla Version 1.5.22
Classic ASP: Enabled
ASP.NET 2.0: Enabled
PHP 5: Enabled
Perl: Enabled
CGI-BIN: Enabled
IIS 7


- That is correct physical storage path, I have been using it for over a year now.
Reply | Reply with quote | Quote
 
 
0 # RE: RE: RE: RE: RE: RE: jFinalizer joomla! pluginstefan 2011-07-26 16:21
Digging a bit into PHP bugs, its possible that either PHP 5.2.6 hast a bug with the results of the function FILE_EXISTS(), or your server might run PHP in safe mode, which is not supported by jFinalizer. In this case, the PHP function FILE_EXISTS() might also report a false negative.

So most likely, it's not a jFinalizer bug.
Reply | Reply with quote | Quote
 
 
0 # RE: RE: RE: RE: RE: RE: RE: jFinalizer joomla! pluginMahek 2011-08-01 12:21
:( , I am not much of a coding pro to understand that.
PHP running is in safe mode, i think... not sure though.

So, I will have to hope for miracle to get over this or shift back to old slow version.
Reply | Reply with quote | Quote
 
 
0 # jFinalizer 2.0.1 Update for joomla 1.6 and 1.7 releasestefan 2011-07-27 15:47
Please see top links for more information. Currently, we beta test 2.0.1. It runs stable so far for Joomla 1.6 and 1.7.
Reply | Reply with quote | Quote
 
 
0 # RE: jFinalizer joomla! pluginMarrett 2011-08-14 10:49
Have installed Jfinalizer for Joomla 1.7 .It works fine but when browsing under Chrome 14 ..it exhibts the following charcteristics

1.If you use Cpanel to password protect the Joomla 1.7 site..Chrome hangs

2.If you use Chrome 14.o to access Joomla Administrator, the browser keeps on acessing the page for at least 2 minutes before it stops .
It seems to work fine under Firefox 5.0.1 and Internet Explorer 9.0.8
Any feedback?
Reply | Reply with quote | Quote
 
 
0 # RE: RE: jFinalizer joomla! pluginstefan 2011-08-23 07:33
we cannot reproduce this behavior.

jFinalizer is not running when logged into backend. Are you sure module orders are set right?
Reply | Reply with quote | Quote
 
 
0 # spritesnbserg 2011-08-21 09:33
can you make a Combine images to sprites in next versions??
Reply | Reply with quote | Quote
 
 
0 # RE: spritesstefan 2011-08-23 07:40
Not in the next planned versions.

Sprite processing would involve both CSS template and HTML output processing and will be excessive on the HTML end without any guarantee of a right layout.

It's way better to combine sprites right after finishing the templates.
Reply | Reply with quote | Quote
 
 
0 # Background Images broken after css processKeith Sorbo 2011-08-22 18:50
I noticed someone else had this problem but never saw a solution.

All my background images disappear when I turn on process CSS. Here is an example
Before process:
background-image: url(../images/verticalcontent slice.jpg);

After Process:
background-image: url(/templates/journeyanswers/css\../images/verticalslice.jpg);

This breaks in FF and Chrome.

It appears that the \.. should be /..

Best I can tell is this happens in the rebuildCssURL private function in the helpers file.

Not being a regex expert, I am not sure exactly where the error is.

Version 2.0.1 on Joomla 1.7.0 on IIS
Reply | Reply with quote | Quote
 
 
0 # RE: Background Images broken after css processstefan 2011-08-23 07:30
Hi Keith,

Since we do not have access to a IIS machine, can you please try to either:

- helper.php, function replaceURLs, line 72: replace the .DS; with .'/';

- if that does not work, put absolute paths in your TEMPLATES, like /templates/journeyanswers/css/images/verticalslice.jpg.

please let us know what worked for you
Reply | Reply with quote | Quote
 
 
0 # RE: Background Images broken after css processKissaki 2011-08-23 13:50
See my comment below. Includes introduction for a fix.
(Although I do not have IIS, should be the same issue and thus same solution.)
Reply | Reply with quote | Quote
 
 
0 # Bug: Process CSS fails on url()-s on windows systems [includes Solution]Kissaki 2011-08-23 13:48
On windows enabling processing CSS will break url(../img.png) URLs in the CSS files and thus on the site.


Version 2.0.1,
helper.php line 72 adds DS (directory separator) to the end of url-path for CSS-URLs. Unfortunately, this is "\" on windows based systems and thus the replaced CSS URLs fail.

The following being processed
background:url( img1.png);
background:url( /img2.png);
background:url( ./img3.png);
background:url( ../img4.png);

will result in
background:url( /templates//css\img1.png);
background:url( /img2.png);
background:url( /templates//css\./img3.png);
background:url( /templates//css\../img4.png);

where *at least* css\../img4.png fails for me in FF 6.


To fix this issue DS should be replaced by '/' and everything works fine.
Reply | Reply with quote | Quote
 
 
0 # RE: Bug: Process CSS fails on url()-s on windows systems [includes Solution]Keith Sorbo 2011-08-23 13:54
Just want to confirm that this fix works.

This is probably because DS is for the file system, where we are dealing with a URL separator here.
Reply | Reply with quote | Quote
 
 
0 # RE: RE: Bug: Process CSS fails on url()-s on windows systems [includes Solution]Kissaki 2011-08-23 14:02
Indeed, that is the problem. Hence just replacing it.
Reply | Reply with quote | Quote
 
 
0 # RE: RE: RE: Bug: Process CSS fails on url()-s on windows systems [includes Solution]stefan 2011-08-23 15:23
Thank you guys for checking our fix and confirming it working on IIS systems! We will include this bug fix into the next release.
Reply | Reply with quote | Quote
 
 
0 # :( my error still persistsMahek 2011-08-23 15:43
replaced DS with '/' nothing happened. Same error on front page.

store.activeanalytic.com

jFinalizer Error 200: Subdirectory path set but incorrect:

jFinalizer Error 201: Resulting physical path from given subdir does not exit: C:\Domains\acti vean\store.activeanalytic.com\wwwroot

jFinalizer Error 202: Tip: if your joomla installation subdirectory is example.com/joomladir, use /joomladir, not joomladir/ or /joomladir/ or joomladir as subdirectory entry
Reply | Reply with quote | Quote
 
 
0 # RE: jFinalizer joomla! pluginAndre 2011-08-28 21:16
Hi Stefan,
ich hab ein komisches Problem, ich nutze jFinalizer auf einem Domainfactory Account und es funktioniert wunderbar. Jetzt bin ich zu strato umgezogen und hier werden die Dateien zwar richtig gebildet, aber vom Browser nicht richtig erkannt. hier sind nur wirre Zeichen und Fragezeichen in der Datei, obwohl die Dateien selbst auf dem Server korrekt sind.
Hast du zufällig eine Idee, was ich da machen könnte?
Danke und viele Grüße
Reply | Reply with quote | Quote
 
 
0 # v2 for 1.5Noah 2011-08-29 06:50
There are still so many people using 1.5 still, any chance your come out with an update for 1.5 of your upgrades?
Reply | Reply with quote | Quote
 
 
0 # FrageGuido 2011-08-29 20:29
Habe jFinalizer installiert u. gzip über htaccess aktiviert. Trotzdem rät mir yslow, ich solle die components mit gzip komprimieren. Versteh ich nicht so ganz.. Was fehlt, was stimmt nicht?

Danke für Tipp - Guido
Reply | Reply with quote | Quote
 
 
+2 # I have problem using jcomments after i installed jfinalizerhello 2011-09-11 07:53
as posted, I have problem showing/submitting comments from front end, it happens after I installed Jfinalizer, I think it has to do with cache , can you help me? thanks
Reply | Reply with quote | Quote
 
 
0 # RE: I have problem using jcomments after i installed jfinalizerhello 2011-09-23 19:14
is here anyone who can help or give some hints ?Quoting hello:
as posted, I have problem showing/submitting comments from front end, it happens after I installed Jfinalizer, I think it has to do with cache , can you help me? thanks
Reply | Reply with quote | Quote
 
 
0 # Css background images still a problemWill 2011-09-20 06:36
I have the same problem with background images on my site.

The images are stored in a sub folder of my template called "Images"
My original CSS is stored in "CSS"

So all my references to images in my css goes as follows:

Quote:
background: url("../images/overlays/productBack_Spr ite.png");


Now i see when i compact css i get url's as such in source on page load (checked with firebug)

Quote:
background: url("/templates/rt_modulus_j16/css../images/overlays/productBack_Spr ite.png");


So from what I can tell, its missing one trailing slash in the url. It should be
Quote:
css/..


If I put that in the code in firebug then it works.
Now my question is...
I see in helper.php between line 71 and 85 it rebuilds the css url so i need to change it there somehow but I dont know how.

Your quick help would be greatly appreciated.
Thanks!
Reply | Reply with quote | Quote
 
 
0 # RE: jFinalizer joomla! pluginWill 2011-09-30 05:33
Quoting Will:
I have the same problem with background images on my site.

The images are stored in a sub folder of my template called "Images"
My original CSS is stored in "CSS"

So all my references to images in my css goes as follows:

Quote:
background: url("../images/overlays/productBack_Spr ite.png");


Now i see when i compact css i get url's as such in source on page load (checked with firebug)

Quote:
background: url("/templates/rt_modulus_j16/css../images/overlays/productBack_Spr ite.png");


So from what I can tell, its missing one trailing slash in the url. It should be
Quote:
css/..


If I put that in the code in firebug then it works.
Now my question is...
I see in helper.php between line 71 and 85 it rebuilds the css url so i need to change it there somehow but I dont know how.

Your quick help would be greatly appreciated.
Thanks!


Anybody??? No support on this plugig for a month now??!
Reply | Reply with quote | Quote
 
 
0 # RE: jFinalizer joomla! pluginnewbiie 2011-09-30 10:06
I encounter with ERROR 100..
what is the remedy ?
Reply | Reply with quote | Quote
 
 
0 # A tricky bug and its solutionHenry C. Lavau 2011-10-01 15:13
You have a rather tricky bug with text areas when there are more than 10 of them in a page.

On compression, you use this

public static function _putTextArea(&$buffer, &$plugin) {
$buffer = str_replace($pl ugin->_ta[1], $plugin->_ta[0], $buffer);
}

Looks fine...but, Look at what happens if you have 10 or more textareas :
$plugin->_ta[1] is then
0 => string '' (length=9)
1 => string '__xxasup1' (length=9)
2 => string '__xxasup2' (length=9)
...
10 => string '__xxasup10' (length=10)
11 => string '__xxasup11' (length=10)
12 => string '__xxasup12' (length=10)
13 => string '__xxasup13' (length=10)
14 => string '__xxasup14' (length=10)
15 => string '__xxasup15' (length=10)
so, after the second change, you have
__xxasup10 that has become {replacement of __xxasup1}0
same for all subsequent upto 19, etc.

SOLUTION : just reverse the arrays :

public static function _putTextArea(&$buffer, &$plugin) {
$buffer = str_replace(arr ay_reverse($plu gin->_ta[1]), array_reverse($ plu gin->_ta[0]), $buffer);
}
Reply | Reply with quote | Quote
 
 
0 # RE: jFinalizer joomla! pluginMeredith 2011-10-05 16:37
I found a couple of comments here regarding the same issue - JComments stops working. I have tested all items, list by list and still only works when Finalizer is turned off ( NOT unistalled)

Are they any tips for this?

Other than that, went from 76/75 to 78/78 and not done yet.

Note in IE9, capcha doesn't work on yours either ( mine either)
Reply | Reply with quote | Quote
 
 
0 # RE: jFinalizer joomla! pluginDaz 2012-01-15 09:17
It works fine (both comments and captcha), just use DeTab html compression.
Reply | Reply with quote | Quote
 
 
0 # Replace url for sites with subdirectoryFlowman 2011-11-10 18:24
This little code is good if you have a dev site ex: site.url/joomla_folder/ and use absolute urls in css 'background: url("/folder/images/foo.jpg")'. On the dev site you need to add /joomla_folder to see images. But we this small change in the helper.php it adds them for you.

private function replaceURLs($in , $fn){
$this->tmp = substr($fn, 0, strrpos($fn, '/')).'/';
if ($this->jf->subDir) {
$in = preg_replace_ca llback('/url\([\'"]?(?![a-z]+:|[\.])([^\'")]+)[\'"]?\)/i', array($this, 'rebuildCssBaseU RL'), $in);
}
$in = preg_replace_ca llback('/url\([\'"]?(?![a-z]+:|\/+)([^\'")]+)[\'"]?\)/i', array($this, 'rebuildCssURL'), $in);
return $in;
}

private function rebuildCssBaseU RL($matches) {
$fp = JURI::base(true ).$matches[1];
return 'url('. $fp .')';
}
Reply | Reply with quote | Quote
 
 
0 # Css items are lostJohn 2011-11-17 04:20
I have tried this plugin and whil eit does process the css and js file the css results are a bit different to the non processed site, for example background images are gone for the page, menu items and other backgrounds.

Looking at the css source I note in the background items in the css it has added the text 'css\../' which is why it is not working, is this meant to do that?

Cheers
Reply | Reply with quote | Quote
 
 
+2 # Community Builder - ProblemJack 2011-11-19 22:07
Hey!

First of all, very good optimization plugin - even the best I tried so far.

But I encoutered a problem with the community builder component. The Problem exists in both the "edit proifl" and the "userlist" menu.
I can see lots of code on the top of the page and the design is broken - functionality seems to be all right.
This Issue occurs after activating the process js option.

I tried to exclude the CB .js files - but either I didn't exclude the right ones, or this isn't the problem's solution. Could you look into this?

Other than this, my site is working great!
(I'm using the latest CB and latest jfinalizer versions. HTML Mode: DeFlat.)
Reply | Reply with quote | Quote
 
 
0 # RE: jFinalizer joomla! pluginnegosyopilipinas 2011-12-02 08:09
thanks for sharing
Reply | Reply with quote | Quote
 
 
0 # RE: jFinalizer joomla! pluginnegosyopilipinas 2011-12-02 08:10
thanks for sharing

www.negosyopilipinas.com
Reply | Reply with quote | Quote
 
 
0 # Manual place tagsAlexx 2011-12-05 12:08
Thanks for your brilliant plugin! I have only one question (cant resolve by myself for 2 days): how to implement you example " $mainframe->triggerEvent('getCompressedJS '); " into Joomla 1.5.25 ?
WHAT IS "getCompressedJS " ???

PLEASE HELP !
Reply | Reply with quote | Quote
 
 
0 # CSS exclusion for 1.1.5Darwin 2011-12-09 23:18
I've added the CSS skipping feature to 1.1.5 by including some code changes from 2.x. I have the installable zip file if anyone wants it (or if the dev wants to include it in the next 1.x release). :)
Reply | Reply with quote | Quote
 
 
0 # security issueArdacid 2011-12-17 21:42
firts i want to said that i love this plugin and how work, but today i run page speed from google and i notice a big drop in my score from 94 to 70, saying enable compress wich is throuht jfinalizer and in global config on the site, one more thing i got ssl in my back end and say is compromise as soon as i open the plugin, any help will be apreciate, thanks.
Reply | Reply with quote | Quote
 
 
0 # RE: jFinalizer joomla! pluginJürgen 2011-12-17 23:56
The .htaccess code did not work for my site. I do not know why but the “RemoveType application/x-gzip .gz” did not work and I always got the wrong Content-Type for my files.

I found a solution I want to share. My .taccess code as follows:

RewriteEngine On
RewriteBase /cache/assets/
RewriteCond %{HTTP:Accept-Encoding} .*gzip.*
RewriteRule (.*)\.css $1.css.gz
RewriteRule (.*)\.js $1.js.gz
AddEncoding x-gzip .gz
ExpiresActive on
ExpiresDefault A604800
ExpiresByType text/css "A604800"
ExpiresByType application/x-javascript "A604800"

RemoveOutputFil ter DEFLATE


ForceType text/css


ForceType application/javascript
Reply | Reply with quote | Quote
 
 
0 # RE: RE: jFinalizer joomla! pluginJürgen 2011-12-18 00:03
Code got damaged/filtered here ist the proper code on patesbin
pastebin.com/YD2LhWPC
Reply | Reply with quote | Quote
 
 
0 # no answerArdacid 2011-12-25 20:27
Does anyone knows how serious is this issue??? my https connection got compromise as soon as i open this plugin in the administrator area, plus is giving errors to my site ( Uncaught TypeError: undefined is not a function ) any support????
site: www.americanenvios.com
Reply | Reply with quote | Quote
 
 
0 # Advanced: Place TagsNick 2012-01-01 14:22
This plugin is one of the best I've used, however are there any further hints on how to use "Place Tags"?

On J1.7 I've done:


However this generates an empty array - Am I doing something wrong or do I need to write the code generating trigger myself?

Thanks for any help!
Reply | Reply with quote | Quote
 
 
0 # RE: Advanced: Place TagsNick 2012-01-01 14:24
Sorry seems it stripped the code tags:

$app = JFactory::getAp plication();
$app->triggerEvent('getCompressedJS ');
Reply | Reply with quote | Quote
 
 
0 # Error 401 and subdirectory issueAlex 2012-01-13 14:03
Hi!

Joomla 1.7.3, localhost, jfinalizer v 2.0.1. After enabling gzip:

jFinalizer Error 401: asset file not found: /jfinaliser/media/system/css/modal.css
jFinalizer Error 401: asset file not found: /jfinaliser/components/com_k2/css/k2.css
...
and so on, with all the files being processed. The output of several extensions is messed.

Tried to add "/jfinaliser" as a subdirectory param value. Now it gives this:

jFinalizer Error 200: Subdirectory path set but incorrect:/jfinaliser
jFinalizer Error 200: Subdirectory path set but incorrect:/jfinaliser
jFinalizer Error 201: Resulting physical path from given subdir does not exit
...

But on some (not all) pages the output is restored to normal. Tried different, even delusive, values of the subdir param - the 200 errors are there and the output is rather correct.
Reply | Reply with quote | Quote
 
 
0 # RE: Error 401 and subdirectory issueAlex 2012-01-13 14:06
I tried all the values of gzip, purging and enablind/disabling joomla cache - no difference.
Reply | Reply with quote | Quote
 
 
0 # RE: jFinalizer joomla! pluginMarco 2012-01-15 22:30
This plugin is the best in the category. Thanks a lot!

I have a weird bug going on and perhaps you could assist me..

I have this site I developed hosted both locally and on the server with the same plugin configuration.

Both places I have set ON to "compress" and "compact" Javascript.

The weird thing is that on the live site I get a Javascript error (due to the compression I suppose) while locally I don't.

Do you have any suggestions of what I should check? Or what might be causing this?

Or is it just bad formed code?
Reply | Reply with quote | Quote
 
 
0 # Order in pluginsIan Shere 2012-01-28 19:13
Firstly, great plugin. Went from 53 to 68 on Google's Page Speed test.

This was a not-so-important site I thought I'd test run the plugin on. I read a little and then basically went for as aggressive as I could. I turned on everything that didn't require template code hacking and set HTML at "Ultra".

The funny thing was, though I set the plugin to last position, every time that I did an "Apply" it reverted back to position 1. If I used "Save" it stayed in the position I'd put it. I changed its position by typing into the plugin list order and saved.

Other than that, a 28% increase in page load speed was worth 5-10 minutes. Now on to the other sites I administer!
Reply | Reply with quote | Quote
 
 
+1 # RE: jFinalizer joomla! pluginryo 2012-01-31 22:26
hi,

have you planned to release a version for joomla 2.5 ?
Reply | Reply with quote | Quote
 

Add comment


Security code
Refresh

(c) FARBFINAL 2011. JFINALIZER IS LICENCED GPL - HOME