Comment deleting, search, history and headers

5 years ago by k4st

So, now you can delete comments. That's nothing too impressive, but while I was doing that I was forced to remake the k4History and k4Page classes and make them actually do stuff. I created a history post filter to deal with the creation of referers and I also made it not record and information pages.

I also made the search a bit better, giving users the option to choose where there search and what in those places. I also put that option in a nifty/sexy drop-down menu that you can access by pressing the down arrow in the quick search field above to the top right.

Finally, I made a class to get all of the headers of a current page. Then I made a pre filter to pass the k4Headers object to the registry. The reason why I've done all this is because it's a nice extra step to be able to check for the 'X-Requested-With: XMLHttpRequest' that JQuery puts in.

I'm off to bed.

Tags: feature, search, delete, comment, ddmenu, xmlhttprequest
OneLobby
QueryQuery TimeAffected Rows
SELECT o.object_name,o.object_perms,p.perm_grant,p.perm_deny FROM k4_objects o, k4_perms p, k4_roles r, k4_user_roles u WHERE u.user_id=1  AND u.role_id=r.role_id  AND p.role_id=r.role_id  AND o.object_id=p.object_id ORDER BY r.perm_level ASC

 0.1514 

 3 

 
SELECT DISTINCT t.thread_id, t.*, ts.tag_name, GROUP_CONCAT(ts.tag_name SEPARATOR ',') AS tags, u.name AS user_name, uu.name AS edit_user_name FROM k4_thread_tags tt, k4_tags ts, k4_threads t, k4_users u, k4_users uu WHERE t.thread_id=26 AND t.thread_id=tt.thread_id AND ts.tag_id=tt.tag_id AND t.user_id=u.user_id AND t.edit_user_id=uu.user_id GROUP BY t.thread_id LIMIT 1

 0.1552 

 1 

 
UPDATE `k4_threads` SET views=285 WHERE thread_id=26

 0.0013 

 1 

 
SELECT tu.*, u.name AS user_name FROM k4_thread_users tu, k4_users u WHERE tu.thread_id=26 AND tu.user_id = u.user_id GROUP BY tu.user_id ORDER BY u.name ASC

 0.1682 

 1