Comments (5)
Yes - that will solve the issue and your TS settings proposal is better than mine.
from typo3-formlog.
Sorry for late response. I was trying to find the best solution.
Actually I was inspired by the conditions here #15 and I have made a condition per form identifier like below. This solves my issue. If you want I can make a PR with docs for that solution or maybe you want to solve that possibility differently? For example by defining some way to inject TS per form identifier on TS level. (f.e. something like module.tx_formlog.settings.list._form-identifier.f1-5685 { }
)
My working solution:
[traverse(request.getQueryParams(), 'tx_formlog_web_formloglist/filters/identifier/value') == 'f1-5685']
module.tx_formlog {
settings {
list {
// some custom columns settings per form
}
export < .list
}
}
[global]
The idea of #17 is nice however. I suppose when my PMs will start to make own form they will need that definitely.
from typo3-formlog.
Giving this another thought the suggested TypoScript setup could indeed help to get this achieved.
Currently we have this:
module.tx_formlog.settings.list.columns
module.tx_formlog.settings.export.columns
Another option could be added to specify dedicated columns
for each form identifier:
module.tx_formlog.settings.list.columns
module.tx_formlog.settings.export.columns
module.tx_formlog.settings.form.<identifier>.list.columns
module.tx_formlog.settings.form.<identifier>.export.columns
This could then prefer the 2nd paths if only entries from the form <identifier>
are to be listed; we can determine this from the fact that the matching filter is applied. Tasks for this:
- Introduce the new settings path
- Have the dedicated columns respected in the list
- Have the dedicated columns respected in the export
- Add an indicator to the log module if form-specific column settings are used (hopefully reduces confusion about varying display and export)
from typo3-formlog.
What do you mean exactly with that?
Maybe related to #17
Here you can see that it's not that easy to implement but maybe you have a good idea.
from typo3-formlog.
Your workaround may work but it relies on two facts which cannot be taken as given:
- Log entries of a single form are listed
- The form definition never changes
By default we the list contains entries of all forms mixed, filtering by a single identifier may open up the path for exporting entries of a single form. But that form definitions may change cannot be avoided; the same form identifier can contain slightly or even completely different fields over time.
Thus this requires a good concept for a general solution which covers the most cases.
from typo3-formlog.
Related Issues (20)
- The finisher preset identified by "LogFormData" could not be found. For TYPO3 V11. HOT 4
- TYPO3 V11: Export Button -> No effect/function HOT 5
- Disabled pages missing in log/export HOT 1
- Export not working on TYPO3 11 HOT 3
- Error after updating 1.x to 2.x HOT 29
- Display of logging entries not possible HOT 1
- exception after updating HOT 9
- variants condition 'finisherIdentifier in ["LogFormData"] not working HOT 5
- Feature request: add upload file path to log data HOT 4
- Feature request: add scheduler task to clear log entry older than x days HOT 1
- missing date fields in the data-result in DB HOT 2
- Date range filter lost on page switch
- TYPO3 v12 compatibilty bug: the sys_language table is no more used HOT 2
- [Feature Request] Delete single entries in the Backend HOT 1
- Finisher Icon in Form Editor broken
- Provide compatibility with EXT:repeatable_form_elements HOT 11
- Check TYPO3-PSA-2021-002 HOT 1
- TYPO3 v11 compatibillity HOT 4
- fields like "date" or "date_picker" would not be displayed in the BE-list!? HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from typo3-formlog.