Feature #29342
closed
More detailed Mail from scheduler task
100%
Description
Having a system with thousands of pages makes it hard to decide who has to fix the broken links ;)
Currently the scheduler task sends out a mail like this:
Total broken links: 224 (last report: 224) Page: Mandanten All links types: 224 (last report: 224) Internal link: 21 (last report: 20) External link: 96 (last report: 97)
In my opinion it would be better to have more information e.g.:
+-----+-----+------------------+--------------------------------+ | pid | uid | CE Title part ...| a node value part / uri part | +-----+-----+------------------+--------------------------------+ | ... | +-----+-----+------------------+--------------------------------+
The above table should not exceed 80 or 72 chars per line ;)
Beside this small feature which - big thanks for this great tool ;)
Updated by Philipp Gampe about 13 years ago
- Complexity changed from easy to medium
Good idea ... I don't now if I will find the time until beta3. Something for TYPO3 4.7?
Updated by Kay Strobach about 13 years ago
would be ok either ;) - thanks for taking care
(as i thought time is over for 4.6 I've not added a target version ;) )
Updated by Michael Miousse about 13 years ago
- Target version set to 4.7.0
When i created the task and the mail notification i had in mind that usualy people will have sections of their site to run and there for i decide to a the page selection in the scheduler task.
The idea was to create a task for each section so you could send a notification mail to someone for a specific section of your site.
Exemple
you have a site with the following arbo:
root
>About us
>>Team
>>Presence
>>COA
>Media Center
>>press Releases
>>Multimedia Library
lets say the section About us is taken care by john smith and the media center section is taken care by jane smith, you should create 2 seperated task one for the About us section that send a notification mail to john smith and on fo the media center that send the notification to jane smith.
The general idea for this was to use the module to handel broken links so we would not have to repeate all informations about those broken links but only send a notification that there is some new broken links on the web site and that they sould go to the linkvalidator module to investigate those broken links.
This is how i saw the task system, but i'm open to see other kind of use of the tasks
Thanks for your concernes
Updated by Kay Strobach about 13 years ago
for sure - i understand the idea - but in my scenario there too much people working in the installation to make a job for every customer.
+ page with default settings | + customer 1 ... | + customer 300 ...
The uri part can be a part of the rootline also (started from the point that is given to the task).
Another solution could be that i wrap you task and use a more generic approach.
Anyway there too much clicks (to reinspect the links) for many users, if the information can be shipped by mail.
Thanks for your great work
Kay
Updated by Soren Malling about 13 years ago
May I suggest a hook instead - then one can decide what a detailed mail should consist of? It will be hard to decide, what markers should go in to the template on behalf of every single user :) A hook, makes it possible to customize it
Updated by Kay Strobach about 13 years ago
mhmm, hook would be ok either - but a default "extended report", which is selectable in em / task setup would also be great.
regards
Kay
Updated by Philipp Gampe about 13 years ago
I would suggest adding another checkmark to the schedular task configuration "Extended report" and then just add support for a subpart with markers.
As the collection of detailed info takes more time, I think this checkbox should be there.
A more automated solution would be to parse the template first and then get the information for all used markers like it is done in cal (calendar base).
A hook should be added in addition.
Updated by Kay Strobach about 13 years ago
mhmm what about the following solution:
checkbox + field for selecting a file from fileadmin
use the fluid template if checkbox is activated.
Updated by Philipp Gampe about 13 years ago
Well, the field for selecting a template file is already there, AFAIK a file chooser is still missing.
Updated by Kay Strobach about 13 years ago
very cool - do you use the FLUID way to render the template or the oldstyle one with markers?
FLUID standalone Doku ;)
The fileselector is just a gimmick for me ;) - not important, as most admins know what they do ;)
Thanks in advice
Kay
Updated by Soren Malling about 13 years ago
I've created a "standalone" issue for the hooks, as I see this as a separate change for linkvalidator (#30296)
Please test and vote: http://review.typo3.org/5354
I have "twitted" with Xavier, this is not considered a feature, and will be a part of TYPO3 4.6 if merged before RC1 (11/10)
Updated by Philipp Gampe about 13 years ago
- Status changed from New to On Hold
We can deal with this after 4.7.
Updated by Philipp Gampe over 12 years ago
- Target version changed from 4.7.0 to 6.0.0
Updated by Michael Stucki almost 11 years ago
- Project changed from 1510 to TYPO3 Core
- Category changed from Linkvalidator to Linkvalidator
Updated by Mathias Schreiber almost 10 years ago
- Status changed from On Hold to Needs Feedback
- Assignee set to Mathias Schreiber
I think we can safely assume today if "after 4.7.0".
Shall we continue?
Updated by Alexander Opitz over 9 years ago
- Target version deleted (
6.0.0)
What's the state of this issue?
Updated by Alexander Opitz about 9 years ago
- Status changed from Needs Feedback to New
- Assignee deleted (
Mathias Schreiber) - Target version set to 8 LTS
Updated by Riccardo De Contardi over 7 years ago
- Target version changed from 8 LTS to 9.0
Updated by
Updated by Kay Strobach almost 7 years ago
- PHP Version deleted (
5.3)
is someone still interested in his thingy?
Updated by Georg Ringer over 6 years ago
plans are to rewrite linkvalidator completly, so yes
Updated by Georg Ringer over 4 years ago
- Related to Task #90727: Migrate ValidatorTask to FluidEmail added
Updated by Georg Ringer over 4 years ago
- Related to Feature #59502: EXT:linkvalidator hooks added
Updated by Sybille Peters over 4 years ago
I don't think having a list like that above with the list of broken links would be very helpful. You get a few broken links. Maybe have that, but more of an overview with aggregated information as well?
I think, to decide "who" must fix: aggregated information would be more useful, e.g.
- Number of broken links per subpages
- Number of broken links per editor / group (that is probably not a good idea, GDPR etc. wise)
Now, in a big site with a number of editors and groups which partially overlap, this is not very helpful either. I have a site with this kind of usecase.
Previously, if you don't enter 1 pid in the scheduler task but several, you already got an aggregated list. (I would add an example here, but it seems the behavior has changed and you can no longer add several pids in the scheduler, see #90848).
Updated by Georg Ringer over 4 years ago
- Target version changed from 10 LTS to Candidate for Major Version
Updated by Gerrit Code Review about 4 years ago
- Status changed from New to Under Review
Patch set 1 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/65549
Updated by Gerrit Code Review about 4 years ago
Patch set 2 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/65549
Updated by Gerrit Code Review about 4 years ago
Patch set 3 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/65549
Updated by Gerrit Code Review about 4 years ago
Patch set 4 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/65549
Updated by Gerrit Code Review about 4 years ago
Patch set 5 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/65549
Updated by Gerrit Code Review about 4 years ago
Patch set 6 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/65549
Updated by Gerrit Code Review about 4 years ago
Patch set 7 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/65549
Updated by Gerrit Code Review about 4 years ago
Patch set 8 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/65549
Updated by Gerrit Code Review about 4 years ago
Patch set 9 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/65549
Updated by Gerrit Code Review about 4 years ago
Patch set 10 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/65549
Updated by Gerrit Code Review about 4 years ago
Patch set 11 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/65549
Updated by Gerrit Code Review about 4 years ago
Patch set 12 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/65549
Updated by Gerrit Code Review about 4 years ago
Patch set 13 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/65549
Updated by Gerrit Code Review about 4 years ago
Patch set 14 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/65549
Updated by Gerrit Code Review about 4 years ago
Patch set 15 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/65549
Updated by Gerrit Code Review about 4 years ago
Patch set 16 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/65549
Updated by Gerrit Code Review about 4 years ago
Patch set 17 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/65549
Updated by Gerrit Code Review about 4 years ago
Patch set 18 for branch master of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/65549
Updated by Oliver Bartsch about 4 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 46d695f2e8ae0eb52b5079d0eb3d7c6219177df3.
Updated by Benni Mack almost 4 years ago
- Status changed from Resolved to Closed