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
/showthread.php 28 require_once





× This forum is read only. As of July 23, 2019, the UserSpice forums have been closed. To receive support, please join our Discord by clicking here. Thank you!

  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Status Update 009
#1
I had hoped to add more to this myself, but Brandin carried the load on this one. His Cron Job tool is available at the top of the dashboard as well as the stuff from this post...
https://userspice.com/forums/topic/statu...#post-5604

My main contribution was changing a <? to a <?php in admin_page.php
  Reply
#2
What is your contribution! You cut yourself off lol

I will try to break this shortly
  Reply
#3
-need to run the SQL for Cron:
https://pastebin.com/9KbensmM
-need to put something somewhere about calling the cron job - maybe we can add this to the cron page in a danger box:
/users/cron/cron.php
-should update reAuth on user login
--I was doing this in my custom login script - but we can do this wherever you like - but it should only happen WHEN the user is logging in
Code:
$db->query("UPDATE users SET last_confirm = ? WHERE id = ?",array($current,$id));
-The deploy for permission level 1 and 2 and user number 1 was missed:
https://userspice.com/forums/topic/somet...#post-5612
-admin_verify.php is private but not assigned to a level
-USER_DEV_OPTION needs to be defined on admin_user.php:
Code:
User is {3bc1fe685386cc4c3ab89a3f76566d8931e181ad17f08aed9ad73b30bf28114d}m1{3bc1fe685386cc4c3ab89a3f76566d8931e181ad17f08aed9ad73b30bf28114d} a dev user
~ Lines 268-284

Other than that - everything is good!
  Reply
#4
Oh that's funny. I forgot to use code tags.

I changed
Code:
<?
to
Code:
<?php
on admin_page.php to fix an unexpected end of file. Your system must let you use those interchangeably, but most don't.
  Reply
#5
Sounds great. Those all look like pretty quick fixes!
  Reply
#6
THAT'S WHAT BROKE IT

Okay
So I installed localhost
And tried it
It didn't work
End of story I stopped trying lol

Ooopsies!!!!!
  Reply
#7
For this one...
-need to put something somewhere about calling the cron job – maybe we can add this to the cron page in a danger box:
/users/cron/cron.php

Are you talking about some sort of notification?

.010 is staged. I just need to get one more bit of code from you. This one was a bad link in the permissions post...

Replace the delete function from forms posted:
http://pasted.co/index.php?act=submit
  Reply
#8
Yes - something to let them know they need to call the cron job for it to actually work.

And sorry about that:
http://pasted.co/b49a9de2
  Reply
#9
Ok. I just had to fix one usersc error and I'm wondering if we also want to add a delete function. The ID columns on the cron tables weren't set to auto-increment, but that's about it.

I don't see an obvious place to put that notification on cron.php. Do you mean cron_manager.php?
  Reply
#10
That would be a smart idea!

I never thought of that sorry!

What was the issue?

Notification on cron manager sorry!
  Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)