The following warnings occurred:
Warning [2] Undefined variable $unreadreports - Line: 26 - File: global.php(961) : eval()'d code PHP 8.2.25 (Linux)
File Line Function
/global.php(961) : eval()'d code 26 errorHandler->error
/global.php 961 eval
/printthread.php 16 require_once
Warning [2] Undefined property: MyLanguage::$archive_pages - Line: 2 - File: printthread.php(287) : eval()'d code PHP 8.2.25 (Linux)
File Line Function
/printthread.php(287) : eval()'d code 2 errorHandler->error
/printthread.php 287 eval
/printthread.php 117 printthread_multipage



UserSpice
Status Update 018 - Printable Version

+- UserSpice (https://userspice.com/forums)
+-- Forum: Support Center (https://userspice.com/forums/forumdisplay.php?fid=23)
+--- Forum: UserSpice 4.3 and Below (https://userspice.com/forums/forumdisplay.php?fid=26)
+--- Thread: Status Update 018 (/showthread.php?tid=760)

Pages: 1 2


Status Update 018 - mudmin - 09-21-2017

That's a great idea. The feature is there, might as well use it.


Status Update 018 - Brandin - 09-21-2017

@mudmin

Do you have an update to push soon?


Status Update 018 - mudmin - 09-21-2017

I don't. I've got a busy couple of days so if you have something push it and I'll merge.


Status Update 018 - Brandin - 09-22-2017

Can I replace tomfoolery with the system logs? Main reason being the clear button isn't working...2nd being we don't need to have two logging systems.


Status Update 018 - mudmin - 09-23-2017

What about modifying the tomfoolery table instead of adding another one? Like basically making a few changes to turn the new logging system into an improved version of the old one? This way we don't have an orphaned feature/table/functions? It would break a lot of my stuff to get rid of that.


Status Update 018 - karsen - 09-23-2017

I keep it as well. I use tomfoolery for security-related events while the system logs are simply searchable logs. I know I could use the logs for both but it was easier to keep than go through and change every tomfoolery audit line to a logger line.


Status Update 018 - mudmin - 09-23-2017

I'm having a terrible time trying to get mail to send over the new phpmailer.

When I try to send from gmail I get "message sent" but no message goes through.

When I try to send from smtp, I get authentication errors.

I'm pushing out an 019 and maybe someone else will get luckier than I am.


Status Update 018 - Brandin - 09-23-2017

No worries - just thinking of condensing solutions!

I will take a look I haven't really played with the mailer in the alpha script - I think I did once but I don't remember the result.