Feature #26840
Disable Ext JS for categories widget
| Status: | New | Start date: | 2011-05-16 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | - | % Done: | 0% |
|
| Category: | Feature | |||
| Target version: | - | Estimated time: | 0.50 hour | |
| Votes: | 3 (View) |
Description
Since version 1.1.1 t3blog adds additional header data (some inline script and ExtJS via google CDN) which is a problem when using for example jQuery.
Related issues
| blocks t3blog uses jQuery - Bug #27403: Remove Ext JS inclusion and not needed JavaScript | Accepted | 2011-06-13 |
History
Updated by Hauke Hain almost 2 years ago
- File 1.1.1_includeJS_TSproperty added
I would like to see the JavaScript of getExpandCollapseJavaScript included via TypoScript. The advantage of the actual solution is, that it is included only if the widget is used.
Therefore I attached a patch that includes a new TypoScript property "includeJS" for the categories and archive widget. (Instead of writing everything to a TypoScript object.) If set to true (default) the JavaScript gets included. If not, nothing is done. If set to false the admin may want to remove "globalFuncs.js" too. t3blogjquery shows how to do that.
I would really appreciate t3blog as being very flexible and therefore very powerful. All the time it was possible to adjust the widgets to the own needs because of the flexible TypoScript. So there was no need to write an own widget. At the moment the flexibility is limited, an own widget must be written to exclude the JavaScript or t3blog must be adjusted. I hope you agree that it must be possible to let the administrator also control the insertion of the JavaScript.
Updated by Hauke Hain almost 2 years ago
- File 1.1.1_includeJS_TSproperty.diff added