The following warnings occurred:
Warning [2] Undefined variable $unreadreports - Line: 26 - File: global.php(961) : eval()'d code PHP 8.1.2-1ubuntu2.14 (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.1.2-1ubuntu2.14 (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-20-2017

I didn't have a lot of time today, but I made a few changes.

There is a new SQL dump. Much to @Chris 's pushing I got rid of all the db fields in users/settings that were not necessary. Again, we won't pull them out during the upgrade process, but they just won't be there for future uses.

Recaptcha is in the db you can change the keys in the admin panel. I added 3 new hooks in usersc. You can now add stuff to the footer. The copyright message is in usersc in case someone wants to add something custom there. So is the google analytics snippet.

I also divided out the hooks for navigation so there is one place for adding links to the top left, one for the top right, and one for dropdowns. Let's face it...bootstrap menus are not intuitive. I probably should add one for the hamburger menu as well. Thoughts?

I hate coming across development projects and seeing my huge recaptcha message at the bottom, so I got rid of that and added it as a danger alert in the admin dashboard and only if recaptcha is enabled for either join or join/login. I installed default recaptcha keys and enabled it so you can see the warning.

There is also a danger alert for having the default admin password. I debated about doing one for the 'user' account, but I don't see that as a huge deal. Thoughts?



Status Update 018 - Brandin - 09-20-2017

In agreement with all you did - I will test this tonight if I have time.

I don't think we need one for the user no. But definitely the admin account.

I really want the nav in the db...but I know that would turn into a big project...didn't someone work on this?


Status Update 018 - mudmin - 09-20-2017

It's part of Us 5. Here's my thought.

I actually don't think the menu would be too complicated to design. I'm just a little worried about the load on the db. If you guys want it, I could give it a whirl.

Thoughts?


Status Update 018 - mudmin - 09-20-2017

It's part of Us 5. Here's my thought.

I actually don't think the menu would be too complicated to design. I'm just a little worried about the load on the db. If you guys want it, I could give it a whirl.

Thoughts?


Status Update 018 - Brandin - 09-20-2017

I don't see any issue in trying it - if we're gonna do it in the future, we can try it and have the code.


Status Update 018 - Brandin - 09-20-2017

Thoughts about forcing Proper on Fname and Lname?


Status Update 018 - mudmin - 09-21-2017

What do you mean by forcing proper? ucfirst?


Status Update 018 - Brandin - 09-21-2017

Yes, ucfirst


Status Update 018 - karsen - 09-21-2017

I saw your post in the other thread about the menu in the db and pulled up the US5 code to check it out, then saw here you guys were already doing the same!

How about we set a default for a forced password reset for the admin when doing a fresh US install?


Status Update 018 - Brandin - 09-21-2017

I'm okay with that...Good idea @karsen!