thanks again for your feedback
Maybe i have to modify first the 2 core-files?i use it without core changes
that's correct. With the public SP6 you don't need the patch anymore. However, you have to activate OpF explicitly in the settings for Frontend Output Filter. If you were involved in the pre-alpha testing you might have to run a manual install of the classical outputfilter module (only do this if you don't see all options (Canonical, CssToHead, Droplets, Email, OpF, RelUrl, WbLink)
i upgrade the module and it works without problems for me, no missing icons etc, but i'll try a new install later
the notices, reported in my last post, are only show'n on the filter-add-dialog, not more on the filter-modify-dialog
the symptom looks the same, but it's a different bug, fixed in 1.4.8 now (see attachment)
the field for Type is not changableit's a part of the filter setting - see allowedit in the module plugin_install.php
but i wondering, thats its not possible to set this in the filter-modify-dialog
It's currently only supported to set it in plugin- or module filters. The intention is that you develop filters as inline filters and when you are confident that it works, you create a plugin- or even a separate module out of it and then it makes sense to prevent other users from spoiling the filter - either in your own installation (if it's managed by several authors) or in other WB installations if you share the filter
- in the database you use a number in the front of the type-field. Why?
modules is first applied, so it should be at the top of the list, then modules (last), then pages and finally pages (last).
Actually, the way this is implemented, has been like this in the previous versions (at least in the 1.03-series) and I didn't want to change much of the internal filter algorithms. The aim of the 1.4 series was mainly to disentangle the whole thing from PMF and use more core-features where possible. Of course one could start changing this now, but well... it's working and there were many more things to improve and to clean up, and there are still some new features on the agenda (see TODO file), which might be more urgent than this.
- you use a absolute link for the files in the database. this makes trouble, if you move later from server A to Server B. it's better to use there only the file name or the path without the WB_URL and build the complete URL in the script
Actually, Stefek has fixed this problem in 1.4.4 but we simply forgot to update the example plugins and the documentation. They are up to date now. in order to take advantage of this feature, you have to delete the example filters (correct date format and cachecontrol) before upgrading
The examples are re-installed during upgrade. If you don't want to have them, just disable the filters or delete them again after the update.
i use for a test a simple replace-filter from dietmar. its works, if i select one special page or all pages, but not, if i select only one or all modules. i didnt see any function for the module select, but maybe, i use it on the wrong way
hmm... I don't quite understand "i didnt see any function for the module select" maybe we clarify this in German?
And maybe post the filter here and explain what you would expect.
i'm not sure about the field "Spracheinstellung:" in the filter "Correct Date Format"
see the filter-help: there you can set a different locale string in case the filter is not working correctly, but I must admit that I don't use that one actively, but I decided to keep it in the examples, because it shows how to use additional fields.