How would I tell the (anonymous, or authenticated) users of my Plone site about a scheduled maintenance downtime?
I think of a "flash message" (like those "Your changes have been saved" messages) which is shown to every user exactly once (until explicitly receipted) before the downtime; after the downtime there should be another message (perhaps shown only to those who saw the pre-downtime message), or no message at all (but of course not the pre-downtime message anymore).
Which Plone product or builtin facility would I use for this purpose?
In addition to the proposed suggestions you may also have a look at:
https://pypi.python.org/pypi/collective.notices
https://pypi.python.org/pypi/collective.messagesviewlet/
Use Products.ContentWellPortlets and add a static-portlet above the content.
Related
Been struggling with this for hours.
This is a asp.net core 3.0 app.
It emails an activation link.
I then pick up that email in my inbox and click on it.
This link is:
https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.myserver.com%2FAccount%2FActivate%3Fpin%3DwDiC3S&data=02%7C01%7C%7C8311079d8b314d288f7a08d77e73c924%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637116908072496731&sdata=y80XhRTBI%2FOJq6UrN8Yw%2B3nWDjrb96IprWR2IKIouVU%3D&reserved=0
It then emails me a confirmation message 9#by calling that view). But it does this twice.
What is weird is that if I copy and past this url from 1 browser to another I just receive the expected 1 confirmation email.
The only difference I can see is that the safelink stuff add si removed from copying and pasting that link. ie:
https://www.myserver.com/Account/Activate?pin=wDiC3S
I do not know how to debug this?
I have just come across this situation. It has taken me a few days to track down. I have a link within an outlook message and I wrote code to make sure it was not called twice. This code was activated the first time I called it. Eventually I realised that the email client must be calling it twice. I'm going to have to write a work around.
I'm glad I found it. It was driving me mad!
I would consider this to be an outlook bug.
I had a similar problem a while back that seemed to be tied to the email client pre-fetching and visiting the link. You may want to try a different email provider and client as part of your debugging efforts.
Here is a related question on the topic -
How to stop e-mail clients from visiting links in e-mail automatically?
I have this issue couple of days already. With trial and error i just found out the solution with my own testing, you just need to set-up the SMTP configuration with your outlook account.
Using PHPMailer
I have this configuration before
$trans = Swift_SmtpTransport::newInstance()
->setHost("xxxxxxxxxxx.mail.protection.outlook.com")
->setPort(25);
I changed to
$trans = Swift_SmtpTransport::newInstance('smtp.office365.com', 587, 'tls')
->setUsername('xxxxx#xxxxxxx')
->setPassword('xxxxxxxxxxxx');
Now, it's working properly. I think ATP aka SafeLink Protection Feature will work only if the email address(sender) is not verified within your organization.
I am sending out a nightly email through rules scheduler, when I manually execute it sends out one email as it should, however when it runs on the schedule it sends me 10 duplicate emails. I've looked all over and can't seem to find any solution to the problem.
Thanks in advance for any suggestions
Use Job scheduler module. In this module you first insert the data in job_schedule and create a queue for each schedule . when crons run it start executing each queue and send mails then it delete its entry from the job_scheduler table. hence it will not send same mail again and again to the same person.. There is proper documentation in job_scheduler module in drupal7. Just go through it.
This sounds like a bug in the Rules module; it has its quirks. I see you have reported this issue in the Rules issue queue: http://drupal.org/node/1314916, which is what I was first going to suggest. So now I know your issue is for Rules 7.x-2.x dev integration with Views 7... both of which have more than a few bugs. I strongly suspect this issue has as much to do with Views as with Rules. (The 10x repetition seems unlikely to be a coincidence since 10 is a default value for results-per-page in Views, etc)
When you report an issue, it's helpful to include all pertinent information (Drupal version, steps to replicate, what's written to the log, etc). I'd personally suggest seeing if you can replicate your issue in a clean installation of Drupal with just the modules necessary to run your test. If you can replicate it that way, it's easier to provide enough information for the developers to identify the issue and resolve it. (e.g. use Devel generate to create some nodes and dummy users, then create a very simple view, e.g. just titles of the five most recent nodes, and use that view as the source for your email content. Does it send 5 copies? You may need to configure a localhost mail server to test this.
We’re running into an issue sending duplicate notifications to our users using the Notifications module on our Mercury Pressflow implementation. The duplicate messages are identical save one thing- the [node-url] token is being replaced with ‘default’ in one of the messages. All the other tokens in the message are being replaced correctly.
The duplicate emails do not happen consistently, maybe 10-15% of the notifications sent out, however a duplicate message always has the proper url & the ‘default’ url.
The only major modification we’ve made to Mercury was spinning off MySQL to it’s own server and adding replication. We currently have the reads set up to round robin between the 2 MySQL instances.
I have done the following troubleshooting based on finding similar issues
made sure the cron job is calling the correct url
replaced all configurations named ‘default’ with the site name (Memcached, Varnish, and Apache configs)
disabled caching in an init_hook in the notifications module
Has anyone out there experienced anything similar with Notifications and Mercury? Any and all advice is greatly appreciated.
The "Mercury" stack is external to Drupal and doesn't affect how email is queued or sent. Something within your messaging/notifications configuration or use is causing multiple messages to be created.
If you have any custom code here, I would look at that and try to trace the token variance.
I wanted to use tracing to capture errors and programmatically send reports via email and text message...that if the ADMIN is eating out at a restaurant on a saturday nite he can see the text message/email to notify and capture..any way to do this??
A site that lets you essentially post exceptions to it, and then you can configure message in a number of ways. I've not had a chance to use this much yet. I think it's more popular w/ ruby, but because it's using standard HTTP posts, you should be able to use it from anything.
http://www.getexceptional.com/
For something more .net-specific, check out: http://code.google.com/p/elmah/
This will save a ton of information locally, and there is then a handler that exposes the data as an RSS feed. From there, you should be able to find numerous ways to consume it. This one I've used to great effect.
I need to design a bug alert system, where the web support team is notified via email when a user of our website encounters an error of any sort (database exception, or a 404)
What would be the best way to design this section of the project? Any ideas would be appreciated.
You may want to look into using the global.asax file for application-wide error intercepting. A quick search yields this step-by-step walk-through:
http://aspnetresources.com/articles/CustomErrorPages.aspx
Depending on the volume of traffic you're expecting, sending an e-mail every time an error is intercepted may not be the best approach. At best, you'd flood inboxes (and make the support staff very unhappy), and at worst you'd get your mail servers blacklisted for spamming. The approach that I've used in the past on high-traffic sites is to queue up errors in a table that is read and purged at a set interval by a separate process. The process would aggregate the errors, grouping them by type, number of occurrences, etc, then send out an e-mail report to the support mailing lists.
ASP.NET health monitoring may be of interest: http://msdn.microsoft.com/en-us/library/ms998306.aspx. It's really simpler to use than this article first appears and doesn't require any additional components - it's all built-in.
I would implement an HTTPmodule that captures the onError event.
This is would allow the module to be reused over multiple applications. The destination email addresses, SMTP server etc, could be in the HTTPmodule, overriden in the web.config file for maximum flexibility.