vb.org Archive

vb.org Archive (https://vborg.vbsupport.ru/index.php)
-   vB4 General Discussions (https://vborg.vbsupport.ru/forumdisplay.php?f=251)
-   -   Signature showing HTML codes (https://vborg.vbsupport.ru/showthread.php?t=241462)

kenng 04-29-2010 02:40 AM

Signature showing HTML codes
 
Hi all,
need help here..
after migration from 3.6.8 to 4.0.2 using impex 1.96, everything works except that the signatures will display the plain HTML codes. It is not phasing errors since if i redo the exact signature codes, preview and save, it will show up nicely.

The problem is... how can it be done to all existing users? (trying not to ask the users to redo their signatures manually again)

Pls enlighten me!

Thanks

Videx 04-30-2010 02:58 AM

Because it's such a security risk, users are normally not allowed to post HTML in sigs or anywhere else. You can change that in permissions, but it's really not recommended. Presumably you're the admin, so when you do it, it works.

You could, in theory, go through the old db and translate all the HTML to bbcode, but that would be painful. Just forget it. Who really cares if old archived posts show unparsed html?

kenng 05-03-2010 07:30 AM

Hi Videx,
thanks for replying. Yes allowing HTML sign is dangerous, but it has been like that since years ago and it would be 'unfriendly' to disable it altogether now.

What would be the best way to do it? How can I not show the signatures(for everyone) and encourage users to resubmit bbcode friendly signatures?

Thank you very much!

Videx 05-03-2010 02:50 PM

I don't think you have to disable it; it already doesn't parse by default. I would just put up a sticky somewhere explaining things. When I occasionally see someone trying to include html, I PM them. If there aren't too many that refuse to do it themselves, I suppose you can always go in and change theirs to bbcode yourself.

kenng 05-04-2010 12:39 AM

Lets just for the sake of knowledge, if management insist on allowing HTML parsing. How do I go about doing it? (since you mentioned it doesn't parse by default).

* new forums already has "HTML is on"

Thanks!

Videx 05-04-2010 12:53 AM

I dunno. I think it's a combination of usergroup perms and forum perms. And I guess sig perms too.

FWIW, I witnessed personally the type of havoc this can cause just last week. My co-admin mistakenly left a closing center tag off a notice, and by the time I tracked it down the forum was in an uproar. I have no idea how I would have found it had it been in a sig somewhere.

kenng 05-04-2010 01:05 AM

Ok got it.. its usergroup perms.

Thanks so much Videx!


All times are GMT. The time now is 10:24 PM.

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.01087 seconds
  • Memory Usage 1,715KB
  • 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
  • (1)footer
  • (1)gobutton
  • (1)header
  • (1)headinclude
  • (6)option
  • (1)post_thanks_navbar_search
  • (1)printthread
  • (7)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
  • bbcode_fetch_tags
  • bbcode_create
  • bbcode_parse_start
  • bbcode_parse_complete_precache
  • bbcode_parse_complete
  • printthread_post
  • printthread_complete