Feature #29342

More detailed Mail from scheduler task

Added by Kay Strobach over 8 years ago. Updated almost 2 years ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
Linkvalidator
Target version:
-
Start date:
2011-08-30
Due date:
% Done:

0%

PHP Version:
Tags:
Complexity:
medium
Sprint Focus:

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 ;)


Related issues

Related to TYPO3 Core - Task #30296: Linkvalidator should have a hook for report markers Closed 2011-09-26

History

#1 Updated by Philipp Gampe over 8 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?

#2 Updated by Kay Strobach over 8 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 ;) )

#3 Updated by Michael Miousse over 8 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

#4 Updated by Kay Strobach over 8 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

#5 Updated by Soren Malling over 8 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

#6 Updated by Kay Strobach over 8 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

#7 Updated by Philipp Gampe over 8 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.

#8 Updated by Kay Strobach over 8 years ago

mhmm what about the following solution:

checkbox + field for selecting a file from fileadmin

use the fluid template if checkbox is activated.

#9 Updated by Philipp Gampe over 8 years ago

Well, the field for selecting a template file is already there, AFAIK a file chooser is still missing.

#10 Updated by Kay Strobach over 8 years ago

very cool - do you use the FLUID way to render the template or the oldstyle one with markers?

FLUID standalone Doku ;)

http://forge.typo3.org/projects/typo3v4-mvc/wiki/How_to_use_the_Fluid_Standalone_view_to_render_template_based_emails

The fileselector is just a gimmick for me ;) - not important, as most admins know what they do ;)

Thanks in advice
Kay

#11 Updated by Soren Malling over 8 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)

#12 Updated by Philipp Gampe over 8 years ago

  • Status changed from New to On Hold

We can deal with this after 4.7.

#13 Updated by Philipp Gampe almost 8 years ago

  • Target version changed from 4.7.0 to 6.0.0

#14 Updated by Michael Stucki about 6 years ago

  • Category set to Linkvalidator

#15 Updated by Michael Stucki about 6 years ago

  • Project changed from Linkvalidator to TYPO3 Core
  • Category changed from Linkvalidator to Linkvalidator

#16 Updated by Mathias Schreiber about 5 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?

#17 Updated by Alexander Opitz over 4 years ago

  • Target version deleted (6.0.0)

What's the state of this issue?

#18 Updated by Alexander Opitz over 4 years ago

  • Status changed from Needs Feedback to New
  • Assignee deleted (Mathias Schreiber)
  • Target version set to 8 LTS

#19 Updated by Riccardo De Contardi almost 3 years ago

  • Target version changed from 8 LTS to 9.0

#20 Updated by Susanne Moog about 2 years ago

  • Target version deleted (9.0)

#21 Updated by Kay Strobach about 2 years ago

  • PHP Version deleted (5.3)

is someone still interested in his thingy?

#22 Updated by Georg Ringer almost 2 years ago

plans are to rewrite linkvalidator completly, so yes

Also available in: Atom PDF