Hmmmm. I'm umming and ahhing over that one SkyBoy. I like it because it saves a few bytes per page in b/w, but it makes the HTML code a hell of a lot harder to read... it really comes down to user preference. I guess I could add this commented out in the extension and mention it in the readme as an option for people to enable if they're desperate for a few more bytes saving? Thoughts?
I quite agree. It make comments' HTML code more harder to read, also on the "block comment" function. Sometime, I have to disable it to find some comment's error. But if someone (like me and my forum's member) don't care the HTML code, may be like it, it make comment's code slight, saves some bytes, easy to check other HTML code. :P
Quote: [-Stash-] You will want to change line 17 of default.php from:define('HTML_CONVERT_NEWLINES', 1);to:define('HTML_CONVERT_NEWLINES',0); Hey [-Stash-], this worked for the lists but now, HTML Formatter strips out ALL of the <p> tags in all of the comments.
Would you mind pasting me your extensions.php (whisper if you'd prefer)? I've done a little testing with the extensions ordering, but there's so many combinations and I have a feeling that may be part of it. I say this because I have HTML Formatter 1.7.2 working just fine this end with AutoP. Admittedly PreviewPost isn't picking up on the AutoP goodness, but it does actually display properly when you hit that submit button.
So not quite back to the drawing board. What I really need to figure out is how to make AutoP and PreviewPost behave...
Thanks for that. So this isn't formatting your posted comments properly? Time I sign up for your forum methinks...
Regarding the Preview Post thing, I've been doing a little digging on the forum and come up with two interesting discussions regarding other things not working with PreviewPost: One, two.
Unfortunately they offer conflicting advice, so I'm not sure which is better. Whichever works I guess.
I've tried One and had some success with getting HTML comments to preview and post the same, which is nice. The same, however, cannot be said for BBCode, which is a complete swine. The search continues.
Comments
return $pee;change to$pee = str_replace( "\n", '', $pee); return $pee;Any suggestion?
But if someone (like me and my forum's member) don't care the HTML code, may be like it, it make comment's code slight, saves some bytes, easy to check other HTML code. :P
Thanks SkyBoy. Keep going with the suggestions, this is great
Quote: [-Stash-] You will want to change line 17 of default.php from:
define('HTML_CONVERT_NEWLINES', 1);to:define('HTML_CONVERT_NEWLINES',0);Hey [-Stash-], this worked for the lists but now, HTML Formatter strips out ALL of the <p> tags in all of the comments.
Back to the drawing board mate!
Posted: Tuesday, 9 January 2007 at 8:09AM (AEDT)
So not quite back to the drawing board. What I really need to figure out is how to make AutoP and PreviewPost behave...
<?php // Enabled Extensions if (!defined('IN_VANILLA')) exit(); include($Configuration['EXTENSIONS_PATH']."ExtendedApplicationForm/default.php"); include($Configuration['EXTENSIONS_PATH']."GuestWelcome/default.php"); include($Configuration['EXTENSIONS_PATH']."InviteFriends/default.php"); include($Configuration['EXTENSIONS_PATH']."NewsMailer/default.php"); include($Configuration['EXTENSIONS_PATH']."PageMng/default.php"); include($Configuration['EXTENSIONS_PATH']."PreviewPost/default.php"); include($Configuration['EXTENSIONS_PATH']."SavedSearches/default.php"); include($Configuration['EXTENSIONS_PATH']."PanelLists/default.php"); include($Configuration['EXTENSIONS_PATH']."YellowFade/default.php"); include($Configuration['EXTENSIONS_PATH']."WindowLinks/default.php"); include($Configuration['EXTENSIONS_PATH']."Vanillacons/default.php"); include($Configuration['EXTENSIONS_PATH']."UserFilters/default.php"); include($Configuration['EXTENSIONS_PATH']."comments_permalinks/default.php"); include($Configuration['EXTENSIONS_PATH']."WhosOnline/default.php"); include($Configuration['EXTENSIONS_PATH']."LiveSearch/default.php"); include($Configuration['EXTENSIONS_PATH']."Statistics/default.php"); include($Configuration['EXTENSIONS_PATH']."CommentRemoval/default.php"); include($Configuration['EXTENSIONS_PATH']."ApplicantEmailVerification/default.php"); include($Configuration['EXTENSIONS_PATH']."NewApplicants/default.php"); include($Configuration['EXTENSIONS_PATH']."HideSuccess/default.php"); include($Configuration['EXTENSIONS_PATH']."DCalendar/default.php"); include($Configuration['EXTENSIONS_PATH']."GuestPost/default.php"); include($Configuration['EXTENSIONS_PATH']."RoleHistory/default.php"); include($Configuration['EXTENSIONS_PATH']."DiscussionOverview/default.php"); include($Configuration['EXTENSIONS_PATH']."Meta Tags/default.php"); include($Configuration['EXTENSIONS_PATH']."Gabbly/default.php"); include($Configuration['EXTENSIONS_PATH']."Discovery/default.php"); include($Configuration['EXTENSIONS_PATH']."LatestPostsIntegration/default.php"); include($Configuration['EXTENSIONS_PATH']."Google Adsense/default.php"); include($Configuration['EXTENSIONS_PATH']."HtmlFormatter/default.php"); include($Configuration['EXTENSIONS_PATH']."Quicktags/default.php"); include($Configuration['EXTENSIONS_PATH']."AutoP/default.php"); ?>I don't see that the PreviewPost doodad has anything to do with final rendering though?
Posted: Tuesday, 9 January 2007 at 10:16AM (AEDT)
Regarding the Preview Post thing, I've been doing a little digging on the forum and come up with two interesting discussions regarding other things not working with PreviewPost: One, two.
Unfortunately they offer conflicting advice, so I'm not sure which is better. Whichever works I guess.
I've tried One and had some success with getting HTML comments to preview and post the same, which is nice. The same, however, cannot be said for BBCode, which is a complete swine. The search continues.