Turn off autoparsing (vB3)

[Zachery]

Originally Posted by Sooner95

$checked[parseurl]

i searched for that...in all the templates and changed it too

$unchecked[parseurl]

and that worked too, tho i didnt find any thing the quick reply as of yet...

the wyswyg will always parse links, you would need to change how it works at the js level to make it work differntly.

[Zachery]

Originally Posted by Sooner95

$checked[parseurl]

i searched for that...in all the templates and changed it too

$unchecked[parseurl]

and that worked too, tho i didnt find any thing the quick reply as of yet...

thats not a real varible, thats why it worked, you in enssense removed that varible.

[SloppyGoat]

Is this really that tough to do, or does nobody (who knows how to code) want to mess with it? Man, I'd be simply ecstatic if this can be done. I'm still using 2.3 until this hack is accomplished, and I really want to upgrade. I have a certain forum that absolutely cannot parse url's. Mainly used by mods/admins for posting semi-dangerous code in a hidden forum. There are a few other hacks I absolutely must have to go live with vB3, but this is probably the most problematic, I guess. I'd even be willing to pay someone a reasonable fee to help with this. Does vB do any custom coding for a fee? I'd love to discuss this with anyone who's interested and capable. (Although, I'm not wealthy, or anything.)

[Zachery]

Originally Posted by SloppyGoat

Is this really that tough to do, or does nobody (who knows how to code) want to mess with it? Man, I'd be simply ecstatic if this can be done. I'm still using 2.3 until this hack is accomplished, and I really want to upgrade. I have a certain forum that absolutely cannot parse url's. Mainly used by mods/admins for posting semi-dangerous code in a hidden forum. There are a few other hacks I absolutely must have to go live with vB3, but this is probably the most problematic, I guess. I'd even be willing to pay someone a reasonable fee to help with this. Does vB do any custom coding for a fee? I'd love to discuss this with anyone who's interested and capable. (Although, I'm not wealthy, or anything.)

You can turn off auto parsing in the standard editor and the regular text box, why not just turn off the ability to use the advanced wysiwyg. ?

[SloppyGoat]

Originally Posted by Zachery

You can turn off auto parsing in the standard editor and the regular text box, why not just turn off the ability to use the advanced wysiwyg. ?

I would, but that's one of the features everyone seems to like. I have no problem disabling it in the one forum, but that hasn't been figured out either, I don't guess. Man, I wish I was a php coder. :ermm: If I could disable the WYSIWYG editor in just the one forum, then disable parsing, my problems would be solved. It's not necessary in that forum, since it's private anyway. I don't want to deprive my members of the nice new features of vB3, though.

[SloppyGoat]

Did anyone ever solve this? Although I pretty much gave up for awhile, I'm still waiting for some kind PHP guru to help me figure this out.

[EZ-Dozet]

And your not the only one????

Anyone. Looking for some peeps that know this stuff.

THanx

[Jadelit]

this has always worked for me... it's old and might need some adjustments.

Disables all parsing of links.
================================================
================================================

newthread.php

find:
$checked['parseurl'] = HTML_CHECKED;

replace with:
$checked['parseurl'] = HTML_UNCHECKED;
================================================
================================================
newreply.php

find:
$checked['parseurl'] = HTML_CHECKED;

replace with:
$checked['parseurl'] = HTML_UNCHECKED;
================================================
================================================
private.php

find:
'parseurl' => true,

replace with
'parseurl' => false,
================================================
================================================
includes/functions_newpost.php

find: 
function convert_url_to_bbcode($messagetext)
{

below add:
return $messagetext;

find:
'parseurl' => iif($post['parseurl'], HTML_CHECKED),

replace with:
'parseurl' => iif($post['parseurl'], HTML_UNCHECKED),
================================================
================================================
includes/functions_bbcodeparse.php

find: 
// standard URL hyperlink
		return "<a href=\"$rightlink\" target=\"_blank\">$text</a>";

replace with:
// standard URL hyperlink
		return "$text";

find:
	$text = htmlspecialchars_uni(substr($tmp, 0, 35) . '...' . substr($tmp, -15));

replace with:
	$text = htmlspecialchars_uni(substr($tmp, 0, 500));


=================================================
in showthread.php find:
	$showsig = iif($bbuserinfo['signature'], 1, 0);

under add:
		if (!isset($checked['parseurl']))
	{
		$checked['parseurl'] = HTML_UNCHECKED;
	}


=================================================

showthread_quickreply

<input type="hidden" name="parseurl" value="1" />


<input type="hidden" name="parseurl" value="0" />

[EricaJoy]

Originally Posted by SloppyGoat

That's a damn good observation. So, can a conditional be used to first; specify a specific forum, then use the remove links command(or whatever you'd call it) to remove them as you post? In other words, can a conditional do something like this? I'm sure a hack can, if not.

If forumid=XX
then remove links
else normal operation

This would probably be the ideal way to accomplish this.

Or, use this hack, which disables parsing completely, but use an if statement with it to specify the forum. Found in this thread.

In functions_newpost.php FIND

PHP Code:

function convert_url_to_bbcode($messagetext) 
{ // the auto parser - adds [url] tags around neccessary things 


BELOW that ADD

PHP Code:

return $messagetext; 


This will disable autoparsing of URLs everywhere.

i did this but now all my users quotation marks are showing up like this \" . I am using vB 3.0.6. Help?

*Edit* Nevermind, i fixed it.

[SloppyGoat]

So what exactly did it do? Does it disable all parsing globally, even in WYSIWYG? How did you fix the problem with the backslashes? If that works, then all I need is someone to tell me how I can apply it to a single forum.