-
-
Notifications
You must be signed in to change notification settings - Fork 406
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Primary Admin account notifications may not work in certain cases #4529
Comments
Edit the Admin account and setup it's email address. |
It is already done |
Okay, that's odd. Let me check. |
Okay, looked at the code, and I'm going to call bug. Updating |
Primary Admin account notifications not working in some cases
Thanks, so what should I do in my environment? |
Did you install from source? If so, the easy process, ntong to verify the user accounts for ownership and that the paths may be different.... cd /var/www/html
git clone -b 1.2.x https:/github.com/cacti/cacti.git cacti.new
/bin/cp -rfp cacti.new/* cacti
chown -r apache:apache cacti Then refresh your browser to upgrade. |
No, I followed the instructions at
|
It's likely going to be a bit more tricky adding @reubenfarrelly as he can add some clarity as to when a new build might be available. We plan to freeze later today after all the language stuff is finished. |
It's working for me now. I'm going to close now. Just wait on 1.2.20 to be released if you don't know how to merge. |
Good evening, So I've added the fix in my functions.php file, but I still get the same error. Versión: cacti 1.2.19 |
Describe the bug
I have a fresh new setup, 5 days ago, I have finalized admin user properties with email but still getting
To Reproduce
Steps to reproduce the behavior:
2.Warning displayed
Expected behavior
This should disappear otherwise, where can we setup the notification?
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information)
OS: Fedora 35
Edge, chrome, Firefox
Version 1.2.19
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: