Project

General

Profile

Task #901

add change notification to newdesign site

Added by Christian Lohmaier almost 4 years ago. Updated about 2 months ago.

Status:
In Progress
Priority:
Low
Assignee:
Category:
SilverStripe
Target version:
Team - Pool
Start date:
Due date:
% Done:

50%

Estimated time:
Tags:
URL:

Description

People want to get notified when pages are changed in the backend, so
add back simple change-notifications to newdesign silverstripe.
Full-blown cmsworkflow module is not needed.

History

#1 Updated by Florian Effenberger almost 4 years ago

  • Project changed from Generic to Infrastructure

#2 Updated by Florian Effenberger almost 4 years ago

  • Priority changed from Normal to Low

Setting priority to low
Might be something for Jean Spiteri to work on
Jean, would you be interested?

#3 Updated by Florian Effenberger almost 4 years ago

Can you poke Jean via mail maybe?

#4 Updated by Jean Spiteri almost 4 years ago

What is actually needed here? I am interested to do this during the holidays. Thanks.

#5 Updated by Jean Spiteri over 3 years ago

  • Assignee changed from Christian Lohmaier to Jean Spiteri
  • % Done changed from 0 to 80

This has started. Much of the code is ready but is not implemented in the production site yet.

#6 Updated by Dennis Roczek almost 3 years ago

  • Category set to Webserver

#7 Updated by Jean Spiteri over 2 years ago

The code needed for this task should be found at https://gist.github.com/Liongold/f0fcda4f39c9e8f33233

#8 Updated by Jean Spiteri over 1 year ago

  • Status changed from New to In Progress

The link above should be ignored. Updated code is available in the newdesign site, waiting to be copied to the main site.

#9 Updated by Jean Spiteri over 1 year ago

  • Category changed from Webserver to SilverStripe

#10 Updated by Florian Effenberger 9 months ago

  • Assignee changed from Jean Spiteri to Christian Lohmaier
  • Target version set to Pool

Cloph: Jean has been asking

Any progress on the pushing of these changes from newdesign.libreoffice.org to the official site?

Can you let us know if that is on your pile?
The ticket priority is low, but I'd like to know if there is anything blocking. :-)

Important to me is that any solution we deploy is update-proof and doesn't require lots of patching and manual work with each update, so we have to weight the benefits.

#11 Updated by Florian Effenberger 8 months ago

Talked to Cloph about this in person now
Using the onPublish function might be problematic, as it might trigger the mail sending too often and thus results in spam
A better variant would be to use daily tasks, he said
Jean, is this something you can look into and update your code accordingly, so we can push it then?
Thanks for chasing this!

#12 Updated by Jean Spiteri 7 months ago

Florian, thank you for chasing this yourself. OK, I can try to change it. I assume with daily tasks, you mean a sort of "Changes done today" email, right?

#13 Updated by Jean Spiteri 7 months ago

  • Assignee changed from Christian Lohmaier to Jean Spiteri
  • % Done changed from 80 to 50

#15 Updated by Jean Spiteri 4 months ago

I'll try converting it.

#16 Updated by Jean Spiteri about 2 months ago

I've reworked the whole code. I've contacted hostmaster@ with the links to the files to propose them for upload.

Also available in: Atom PDF