vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vBulletin 3.0 Full Releases (https://vborg.vbsupport.ru/forumdisplay.php?f=33)
-   -   Advanced Editing Options For Mods & Admins (https://vborg.vbsupport.ru/showthread.php?t=61412)

the Sandman 04-20-2004 04:40 PM

Thanks much for the super quick response - that seems to have fixed it! Sweet hack! :D

the Sandman 04-20-2004 04:42 PM

Sorry - one more question. How would you restrict the Advanced Editing Options to Admins only?

Xenon 04-20-2004 09:38 PM

very easy as well :)

you just have to replace these appearances:
PHP Code:

$bbuserinfo['editlevel'] > $editlevel['author'

with
PHP Code:

$bbuserinfo['editlevel'] == $editlevel['admin'

not tested, but should do the trick :)

the Sandman 04-20-2004 11:37 PM

Thanks Xenon - now it's perfect! :D

Xenon 04-21-2004 09:08 AM

:)

you're welcome

Natch 04-23-2004 03:53 PM

We've had some issues with this hack:

It seems for my SuperMods that when they are editing a post, prior to having used the ModCP (having logged in the second time) they cause the post edited to lose all timestamp and Poster info - timestamp is reset to the unix Epoch, and the poster is reset to Guest - this causes the thread to seem like it's been started by a Guest, with a post that's replying to posts below it ...

Any thoughts why this might happen ?

Natch 04-24-2004 12:17 AM

Quote:

Originally Posted by One of my SuperMods
Just noticed what happens when i edit my own post and not being logged in as a moderator.
If i edit the post before the timelimit of aprox 1 min, the timestamp is ok.
But if i wait longer or edit the post "second time around" the timestamp resets and shows 0-0-1970.
Forgetting to change it will cause the error of moving the post to first place.

I hope this helps ...

Xenon 04-24-2004 10:08 AM

hmm, very wierd...

i cannot reproduce it, and did not get such reports before.

I'll check it out a bit more, maybe i can reproduce it somehow...

Natch 04-24-2004 10:39 AM

Is it possible that it's linked to either or both of the "Doublepost check" hack and/or the "Editing Heirarchy" hack - or a combination of them ?

Xenon 04-24-2004 10:42 AM

Hmm, maybe, i already got reports the the Message editing hierachy hack doesn't work together with this hack.

I will have to check this out, it's a bit wierd, as i don't see why they shouldn'T work together, but maybe i have overseen something..


All times are GMT. The time now is 09:10 AM.

Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.

X vBulletin 3.8.12 by vBS Debug Information
  • Page Generation 0.01264 seconds
  • Memory Usage 1,736KB
  • Queries Executed 10 (?)
More Information
Template Usage:
  • (1)ad_footer_end
  • (1)ad_footer_start
  • (1)ad_header_end
  • (1)ad_header_logo
  • (1)ad_navbar_below
  • (2)bbcode_php_printable
  • (1)bbcode_quote_printable
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)pagenav
  • (1)pagenav_curpage
  • (4)pagenav_pagelink
  • (1)pagenav_pagelinkrel
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (10)printthreadbit
  • (1)spacer_close
  • (1)spacer_open 

Phrase Groups Available:
  • global
  • postbit
  • showthread
Included Files:
  • ./printthread.php
  • ./global.php
  • ./includes/init.php
  • ./includes/class_core.php
  • ./includes/config.php
  • ./includes/functions.php
  • ./includes/class_hook.php
  • ./includes/modsystem_functions.php
  • ./includes/class_bbcode_alt.php
  • ./includes/class_bbcode.php
  • ./includes/functions_bigthree.php 

Hooks Called:
  • init_startup
  • init_startup_session_setup_start
  • init_startup_session_setup_complete
  • cache_permissions
  • fetch_threadinfo_query
  • fetch_threadinfo
  • fetch_foruminfo
  • style_fetch
  • cache_templates
  • global_start
  • parse_templates
  • global_setup_complete
  • printthread_start
  • pagenav_page
  • pagenav_complete
  • bbcode_fetch_tags
  • bbcode_create
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • printthread_post
  • printthread_complete