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 028 - Progress - 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 028 - Progress (/showthread.php?tid=775)

Pages: 1 2 3 4 5 6 7 8


Status Update 028 - Progress - dan - 10-04-2017

My thought is that maybe we can add account to the user table and if they get it wrong two or three times their account deactivates. Even with three guesses out of a million I feel pretty secure with that


Status Update 028 - Progress - dan - 10-04-2017

Sorry... Add a count



Status Update 028 - Progress - karsen - 10-05-2017

There was a comment for them in my build notes, you might not have seen the file though:
Code:
SQL:
Code:
Added 'title' column to 'pages' table, updated insert sql with default titles

I increased my own vericode length and implemented the brute force checks that I listed in another thread, along with other password changes.


Status Update 028 - Progress - Brandin - 10-05-2017

I seen it...but it broke the SQL for some reason on import...we'll have to take a look at it again...


Status Update 028 - Progress - karsen - 10-05-2017

It seems like a version difference in phpMyAdmin caused this problem. My version lists table alterations within the create table blocks, while the US version has them at the end of the file. I tested my updated branch and it works for me.


Status Update 028 - Progress - mudmin - 10-06-2017

I've definitely had that problem. I broke something with that recently.


Status Update 028 - Progress - mudmin - 10-07-2017

So what's on the to-do list? What kind of issues are you all having with the menu system? Maybe we can get this knocked out and go beta. Things are still busy at work, but I can get away to do some coding now.



Status Update 028 - Progress - mudmin - 10-07-2017

From what I can tell the "new" buttons don't work on the menu system. I did repair the sql dump.


Status Update 028 - Progress - Brandin - 10-07-2017

Vericode security
Password security (try x times)
Username Ajax
(other things that were discussed in that thread)

Not sure what else tbh


Status Update 028 - Progress - mudmin - 10-07-2017

I fixed the new menu item bugs. We're getting closer.