Edit posts that are in HTML?

[mesteele101]

I was able to convert my site to 4.0 RC. When I choose to edit the post that is HTML I don't see the html code? When I select source is puts all the code together in a continuous stream.

[Adam S]

You will need to give your group permission to post HTML,

Go to Members > Groups > Edit > Group Settings

Under Permission you will see 'Can post HTML?' change this to yes.

Go to post and on edit, you can see source button.

[mesteele101]

It's confusing because I'm expecting something that tells me to activate HTML mode. I did see the source, and it was setup correctly.

There seems to be a major problem with the "source" function. This is an existing post that has about 2000 lines of HTML code. When I hit the "source" function all the 2000 lines are continuous code like below.

<link href="/data/images/winsnort.css" rel="stylesheet" type="text/css" /><p>&nbsp;</p><p>&nbsp;<div class="center"><h2><i>How to Install a Windows Intrusion Detection System (WinIDS)</i></h2><img style="border: 3px solid gray; border-image: none;" alt="" src="http://localhost/data/images/ids.gif" /><h2><i>Windows 7 / 8.1 / 2008 / 2012 running IIS, and logging events to a local PostgreSQL Database

I can add the add the HTML code exactly as you see it below, save the post, edit the post again, and the code looks like the above.

<link rel="stylesheet" type="text/css" href="/data/images/winsnort.css" />

<br />

<div class="center">

<h2><i>How to Install a Windows Intrusion Detection System (WinIDS)</i></h2>

<img src="http://localhost/data/images/ids.gif" alt="" style="border: 3px gray solid" />

<br />

<h2><i>Windows 7 / 8.1 / 2008 / 2012 running IIS, and logging events to a local PostgreSQL Database</i>

 This has similar connotations as to how IPB's HTML editor worked in 3.x

The above was using IE11. I just tried FF and the output is different (noted below). Not correct, but at least there are some line feeds (the last three are on their own separate line).

<link rel="stylesheet" type="text/css" href="/data/images/winsnort.css" /><p>&nbsp;</p><div class="center"><h2><i>How to Install a Windows Intrusion Detection System (WinIDS)</i></h2><img alt="" style="border: 3px gray solid" src="http://localhost/data/images/ids.gif" /><h2><i>Windows 7 / 8.1 / 2008 / 2012 running IIS, and logging events to a local PostgreSQL Database</i><br /><br />Written by: <i>Michael E. Steele</i></h2></div><p>&nbsp;</p><p>&nbsp;</p><h3><i>Introduction</i></h3><p>During my research, and development I&#39;ve found a lot of tutorials, and blogs describing the installation process for the UNIX environment. Yet, none of them specifically detailed setting this up in a Windows environment. I&#39;ve been working on, and updating these tutorials for the past 12 plus years, and managed to get through the complete process in the Windows environment.<br /><br />These tutorials gives all the basic instructions on how to create a complete, and functioning Windows Intrusion Detection System (WinIDS). This is all made possible by simply wrapping Snort, a very powerful Intrusion Detection Engine into a multitude of free open source programs. Best of all, other than the cost of the Windows operating system, it&#39;s completely free.<br /><br />These tutorials are the basic of what is needed, and the starting point for installing any functioning Windows Intrusion Detection System (WinIDS). Advanced problems not related to the basic install should <b>not</b> be posted to the forum where the tutorial resides, and where general help is available for problems during the initial tutorial set-up.</p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p><h3><i>Copyright Notice</i></h3><p>This document is Copyright &copy; 2002-2015 Michael Steele. All rights reserved. Permission to distribute this document is hereby granted providing that distribution is electronic, in it&#39;s original form, no money is involved, and this copyright notice is maintained. Other requests for distribution will be considered.<br /><br />Use the information in this document at your own risk. Michael Steele disavows any potential liability of this document. Use of the concepts, examples, and/or other content of this document are entirely at your own risk.<br /><br />This tutorial is written in the hope that it will be useful, but without any warranty; without even the implied warranty of merchantability or fitness for a particular purpose.<br /><br />All copyrights are owned by their owners, unless specifically noted otherwise. Third party trademarks or brand names are the property of their owners. Use of a term in this document should not be regarded as affecting the validity of any trademark or service mark. Naming of particular products or brands should not be seen as endorsements.</p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p><h3><i>Support Questions and Help</i></h3><p>&nbsp;</p><p>&nbsp;</p><div class="informationmsg errormsg center red">All support questions related to this specific tutorial <b>MUST</b> be directed to the specific forum for which this Windows Intrusion Detection System (WinIDS) tutorial resides, and this is a <b>FREE</b> service.<br /><br />By request, there is a premium fee service available for one on one support.<br /><br />If you haven&#39;t acquired this tutorial directly from the <a title="Click here to be transported to winsnort.com..." rel="external nofollow" href="http://winsnort.com">winsnort.com</a> website, then you most likely don&#39;t have the latest revision of this tutorial!</div><p>&nbsp;</p><h3><i>This is a basic Windows Intrusion Detection System (WinIDS) deployment</i></h3><p>&nbsp;</p><ul style="list-style-type:square;" class="red"><li><span class="black">Windows operating systems is the selected system software for these tutorials.</span></li></ul><div class="informationmsg">It is highly recommended to start with a fresh install of one of the supported 32bit or 64bit Windows operating systems listed below. It is imperative that <b>all</b> the latest security updates from the Microsoft update center have been installed.</div><ul><li><ul style="list-style-type:square;" class="black"><li><span class="black">Windows 7 Professional (SP1)</span></li><li><span class="black">Windows 8.1 Professional</span></li><li><span class="black">Windows Server 2008 Standard Edition (SP2)</span></li><li><span class="black">Windows Server 2012 Standard Edition</span></li><li><span class="black">Windows Server 2012R2 Standard Edition</span></li></ul></li></ul><div class="informationmsg">All the operating systems listed above have been tested using both the 32bit, and 64bit architecture for this tutorial. However, any another Windows operating system listed above, under the same framework will most likely work.</div><ul style="list-style-type:square;" class="red"><li><span class="black">WinPcap allows 3rd party applications to capture and transmit network packets bypassing the protocol stack.</span></li><li><span class="black">Snort performs real-time traffic analysis and network packet logging on Internet Protocol (IP) networks data streams.</span></li><li><span class="black">Barnyard2 is a dedicated spooler for Snort&#39;s unified2 binary output format, and on-forwarding to a PostgreSQL database.</span></li><li><span class="black">PostgreSQL-driven database stores processed events from Barnyard2 for analysis.</span></li><li><span class="black">Microsoft&#39;s Internet Information Services will drive the web based Windows Intrusion Detection Systems (WinIDS) GUI security console.</span></li><li><span class="black">BASE serves as the Windows Intrusion Detection Systems (WinIDS) web based GUI security console.</span></li></ul><p>&nbsp;</p><h3><i>History of Internet Information Services (IIS)</i></h3><p>&nbsp;</p><ul style="list-style-type:square;" class="red"><li><span class="black">IIS 7.0 - included with Windows Server 2008.</span></li><li><span class="black">IIS 7.5 - included with Windows 7, and Windows Server 2008 R2.</span></li><li><span class="black">IIS 8.0 - included with Windows Server 2012, and Windows 8.</span></li><li><span class="black">IIS 8.5 - included with Windows Server 2012 R2, and Windows 8.1.</span></li></ul><p>&nbsp;</p><h3><i>How this Hardware and Software was prepped for this Windows Intrusion Detection System (WinIDS) tutorial</i></h3><p>&nbsp;</p><ul style="list-style-type:square;" class="red"><li><span class="black">A fresh install of Windows 7 Professional (SP1) 64bit, but any 32/64bit Version of Windows listed above in will do.</span></li><li><span class="black">All available Service Packs and updates were applied from the Microsoft Download Center.</span></li><li><span class="black">A user account was created for &#39;Operator&#39;, the password was set to &#39;z1pp3r&#39;, and user &#39;Operator&#39; was assigned Administrative privileges.</span></li><li><span class="black">This complete Windows Intrusion Detection System (WinIDS) tutorial was installed logged on as user &#39;Operator&#39;.</span></li><li><span class="black">There was 4GB of memory installed, but 3GB should be the absolute minimum (more is always better).</span></li><li><span class="black">There were two partitions created - C: (System) with 300GB, and D: (WinIDS) with 1TB.</span></li><li><span class="black">This complete Windows Intrusion Detection System (WinIDS) was installed into the &#39;d:\winids&#39; folder.</span></li></ul><div class="informationmsg warningmsg red"><div class="center"><b>The Windows Intrusion Detection System (WinIDS) will fail if the default installation path is not Implemented correctly!</b></div><br />The default installation path noted above is hard coded into this tutorial, and is also hard coded into some of the install scripts. Installers will need to make the appropriate changes in both places if the default installation path is anything other then &#39;d:\winids&#39;, or the support files are located anywhere other than the &#39;d:\temp&#39; folder.<br />&nbsp;<div class="center"><b>The Windows Intrusion Detection System (WinIDS) will fail if the default installation path is not Implemented correctly!</b></div></div><p>&nbsp;</p><div class="center"><h2><i>Prepping for the Windows Intrusion Detection System (WinIDS) Tutorial</i></h2></div><p>&nbsp;</p><p>&nbsp;</p><h3><i>Downloading and extracting the core &#39;Windows Intrusion Detection Systems (WinIDS)&#39; Software Support Pack</i></h3><p>&nbsp;</p><div class="informationmsg">It is imperative to only use the files included in the &#39;WinIDS - (32/64bit) Software Support Packs&#39; below. These files have been thoroughly tested and compatible with this particular Windows Intrusion Detection Systems (WinIDS) tutorial.</div><div class="informationmsg warningmsg red">Depending on the processors architecture, download the appropriate &#39;WinIDS - (32/64bit) Software Support Pack&#39; below!</div><p><a title="This download is required for all supported 32bit Windows operating systems!" rel="external nofollow" href="/files/file/6-windows-intrusion-detection-systems-32bit-core-software-support-pack/"><img alt="" height="15" width="17" src="http://localhost/data/images/dload.png" /></a><em class="red"><b> 32bit Windows All:</b></em><b><i> Download and save the &#39;WinIDS - 32bit Core Software Support Pack&#39; to a temporary location.</i></b> Open an Explorer window and navigate to the location of the &#39;winids-cssp-x32.zip&#39; file, right-click the &#39;winids-cssp-x32.zip&#39; file, highlight and left-click &#39;Extract all...&#39;, in the &#39;Files will be extracted to this folder:&#39; dialog box type &#39;d:\temp&#39; (less the outside quotes), left-click and uncheck the &#39;Show extracted files when complete&#39; radio box, left-click extract, in the &#39;Password:&#39; dialog box type &#39;w1nsn03t.c0m&#39; (less the outside quotes), and left-click &#39;OK&#39;.<br /><br /><a title="This download is required for all supported 64bit Windows operating systems!" rel="external nofollow" href="/files/file/7-windows-intrusion-detection-systems-64bit-core-software-support-pack/"><img alt="" height="15" width="17" src="http://localhost/data/images/dload.png" /></a><em class="red"><b> 64bit Windows All:</b></em><b><i> Download and save the &#39;WinIDS - 64bit Core Software Support Pack&#39; to a temporary location.</i></b> Open an Explorer window and navigate to the location of the &#39;winids-cssp-x64.zip&#39; file, right-click the &#39;winids-cssp-x64.zip&#39; file, highlight and left-click &#39;Extract all...&#39;, in the &#39;Files will be extracted to this folder:&#39; dialog box type &#39;d:\temp&#39; (less the outside quotes), left-click and uncheck the &#39;Show extracted files when complete&#39; radio box, left-click extract, in the &#39;Password:&#39; dialog box type &#39;w1nsn03t.c0m&#39; (less the outside quotes), and left-click &#39;OK&#39;.</p><p>&nbsp;</p><h3><i>Downloading additional, and required support files for all supported Windows operating systems</i></h3><p>&nbsp;</p><div class="informationmsg warningmsg red">It is imperative to only use the files downloaded from the URL links below. All the files have been verified as compatible with this particular Windows Intrusion Detection Systems (WinIDS) tutorial. All the files below will need to be downloaded into the folder (d:\temp) that was created when the files from the above &#39;WinIDS - (32/64bit) Software Support Pack&#39; were extracted.</div><p><a title="" rel="external nofollow" href="http://www.winpcap.org/install/bin/WinPcap_4_1_3.exe"><img alt="" height="15" width="17" src="http://localhost/data/images/dload.png" /></a><em class="red"><b> WinPcap 4.1.3:</b></em><b><i> Download and save the file to the d:\temp folder.</i></b></p><p>&nbsp;</p><p>&nbsp;</p><div class="informationmsg">In some instances after downloading the Snort executable below, the &#39;.exe&#39; extension might be missing. After downloading, navigate to the location of the Snort executable, and if the &#39;.exe&#39; extension is missing, add &#39;.exe&#39; (less the outside quotes) to the end of the filename.</div><p><a title="" rel="external nofollow" href="https://www.snort.org/downloads/snort/Snort_2_9_7_0_Installer.exe"><img alt="" height="15" width="17" src="http://localhost/data/images/dload.png" /></a><em class="red"><b> Snort 2.9.7.0:</b></em><b><i> Download and save the file to the d:\temp folder.</i></b></p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p><div class="informationmsg">The following two files will require the installer to be a registered user on the <a target="_blank" rel="external nofollow" href="http://snort.org">snort.org</a> web site, and logged in. After logging into the <a target="_blank" rel="external nofollow" href="http://snort.org">snort.org</a> web site, come back to the Windows Intrusion Detection Systems (WinIDS) tutorial, and initiate the next two downloads.</div><p><a rel="external nofollow" href="https://www.snort.org/downloads/registered/snortrules-snapshot-2970.tar.gz"><img alt="" height="15" width="17" src="http://localhost/data/images/dload.png" /></a><em class="red"><b> snortrules-snapshot-2970:</b></em><b><i> Download and save the file to the d:\temp folder.</i></b><br /><br /><a rel="external nofollow" href="https://www.snort.org/downloads/community/opensource.tar.gz"><img alt="" height="15" width="17" src="http://localhost/data/images/dload.png" /></a><em class="red"><b> Rule Documentation (opensource.tar.gz):</b></em><b><i> Download and save the file to the d:\temp folder.</i></b></p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p><h3><i>Downloading additional support files based on a specific Operating System, and Architecture</i></h3><p>&nbsp;</p><p>&nbsp;</p><div class="informationmsg warningmsg red">There may be several groups of additional support files below. Only download the files in the group for the operating system, and hardware architecture that the Windows Intrusion Detection System (WinIDS) will be installed on. Do not download out of any other group, as the Windows Intrusion Detection System (WinIDS) install will likely fail. Again, the additional support files must end up in the &#39;d:\temp&#39; folder.</div><p><b>All 32bit versions of Windows 7, Windows 8.1, and Server 2008</b><br /><a title="" rel="external nofollow" href="http://strawberryperl.com/download/5.14.2.1/strawberry-perl-5.14.2.1-32bit.msi"><img alt="" height="15" width="17" src="http://localhost/data/images/dload.png" /></a><em class="red"><b> Strawberry Perl 5.14.2.1:</b></em><b><i> Download and save the file to the d:\temp folder.</i></b><br /><br /><a title="" rel="external nofollow" href="http://get.enterprisedb.com/postgresql/postgresql-9.4.1-1-windows.exe"><img alt="" height="15" width="17" src="http://localhost/data/images/dload.png" /></a><em class="red"><b> PostgreSQL Database 9.4.1-1:</b></em><b><i> Download and save the file to the d:\temp folder.</i></b><br /><br /><a title="" rel="external nofollow" href="http://windows.php.net/downloads/releases/archives/php-5.6.5-nts-Win32-VC11-x86.zip"><img alt="" height="15" width="17" src="http://localhost/data/images/dload.png" /></a><em class="red"><b> PHP 5.6.5 NTS (VC11):</b></em><b><i> Download and save the file to the d:\temp folder.</i></b><br /><br /><b>All 64bit versions of Windows 7, Windows 8.1, Server 2008, and Server 2012</b><br /><a title="" rel="external nofollow" href="http://strawberryperl.com/download/5.14.2.1/strawberry-perl-5.14.2.1-64bit.msi"><img alt="" height="15" width="17" src="http://localhost/data/images/dload.png" /></a><em class="red"><b> Strawberry Perl 5.14.2.1:</b></em><b><i> Download and save the file to the d:\temp folder.</i></b><br /><br /><a title="" rel="external nofollow" href="http://get.enterprisedb.com/postgresql/postgresql-9.4.1-1-windows-x64.exe"><img alt="" height="15" width="17" src="http://localhost/data/images/dload.png" /></a><em class="red"><b> PostgreSQL Database 9.4.1-1:</b></em><b><i> Download and save the file to the d:\temp folder.</i></b><br /><br /><a title="" rel="external nofollow" href="http://windows.php.net/downloads/releases/archives/php-5.6.5-nts-Win32-VC11-x64.zip"><img alt="" height="15" width="17" src="http://localhost/data/images/dload.png" /></a><em class="red"><b> PHP 5.6.5 NTS (VC11):</b></em><b><i> Download and save the file to the d:\temp folder.</i></b></p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p><h3><i>Installing the core support files, and making basic configuration changes</i></h3><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p><div class="informationmsg">It is highly recommended when this tutorial requires the installer to &#39;Open a CMD window&#39; that a CMD window is opened with &#39;Administrator&#39; privileges.</div><p><em class="red"><b>Windows 8.1 / 2008 / 2012:</b></em> The original Windows CD/DVD media is now required to be inserted into the CD/DVD-Player.</p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p><div class="informationmsg">The correct source drive letter of the CD/DVD-Player that holds the original Windows media must be inserted into the &#39;<span class="red"><b>x</b></span>&#39; position below.</div><p><em class="red"><b>Windows 8.1 / 2008 / 2012:</b></em> Open a CMD window and type &#39;dism.exe /online /enable-feature /all /featurename:NetFX3 /Source:<span class="red"><b>x</b></span>:\sources\sxs&#39; (less the outside quotes), and tap the &#39;Enter&#39; key.</p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p><div class="informationmsg">The following is a confirmation that the &#39;.NET Framework 3.5 Features&#39; were installed successfully.<br />&nbsp;<pre>Deployment Image Servicing and Management tool
Version: (redacted)
Image Version: (redacted)
Enabling feature(s)

 

[The Jimmo]

It is compressing the HTML to save it and use it more efficiently. Though it is harder to read this is actually a GOOD thing

[mesteele101]

It is compressing the HTML to save it and use it more efficiently. Though it is harder to read this is actually a GOOD thing

​Well, we both know that is not the official reason why it is condensing things.

It appears that the developers have yet again to get the HTML editor right. Once after you have created and saved the correct HTML output. Now take IE11, FF, or chrome, open the post to edit, and in all three browsers the output is displayed differently, and its nothing like the original.

[The Jimmo]

Now take IE11, FF, or chrome, open the post to edit, and in all three browsers the output is displayed differently, and its nothing like the original.

Not sure what you're getting at here. Is the actual HTML different, as in the elements are in different places or is your CSS/HTML not styling correctly on output? If it's the latter, that is not IPS' fault.

EDIT: Lastly, it is not an HTML editor, it is a WYSIWYG editor that displays the source in HTML. That difference may answer some of your questions why things aren't appearing like you would expect in an actual code editor or IDE.

[mesteele101]

As an example, and there are 2000 lines of HTML code that I'm pasting into the editor.

This is 13 lines of code, although there are some blank lines.

<link rel="stylesheet" type="text/css" href="/data/images/winsnort.css" />

<br />

<div class="center">

<h2><i>How to Install a Windows Intrusion Detection System (WinIDS)</i></h2>

<img src="http://localhost/data/images/ids.gif" alt="" style="border: 3px gray solid" />

<br />

<h2><i>Windows 7 / 8.1 / 2008 / 2012 running IIS, and logging events to a local PostgreSQL Database</i>

After entering in the code above, saving, and the editing the code using the source button, I get this:

<link rel="stylesheet" type="text/css" href="/data/images/winsnort.css" /><p>&nbsp;</p><div class="center"><h2><i>How to Install a Windows Intrusion Detection System (WinIDS)</i></h2><img alt="" style="border: 3px gray solid" src="http://localhost/data/images/ids.gif" /><h2><i>Windows 7 / 8.1 / 2008 / 2012 running IIS, and logging events to a local PostgreSQL Database

I not getting the same HTML format back as I entered in

There are <p> </p> &nbsp; being entered in that was not in my original code

Why am I not being allowed to edit exactly what I'm saving?

I've used other CMS's with no problem in the editor. What I enter in or past in, I get back.

What I'm doing in 3.x now is using an external editor to do all my editing and then just pasting in the code into IPB. I'm the only one allowed to post HTML code. This works and I'm satisfied with doing it this way so I can have the redundancy. The developers said 4.0 would be resolving all my issues as they were completely revamping the editor.

[The Jimmo]

This is an issue with the CKEditor. It is escaping break lines ( <br /> ). In all honesty you shouldn't be designing or using break lines, you should use paragraph tags ( <p> content </p>), they are more efficient in styling and easier to control with CSS.

I'm busy right now but tomorrow I'll post how to not escape the break lines in CKE. It's pretty easy and you have to make an edit to the config file.

 

[mesteele101]

I have just gotten my 3.x site into a temp offline site and converted to 4.0. I'm only testing at this time. There were other issues with implementing HTML that prevented me from using the built in editor. I really haven't gotten to verify the other problems that I was having. The continuous output of lines were never a problem with 3.x.

Like I said it's easier for me to work with the HTML files saved on my local device using my HTML code editor, then paste, and save the final code back into the IPB editor.

However it would nice if the internal editor worked correctly, and it may. Like you said I should be using <p> and not <br />, but is that in fact a reason for the internal editor not to allow using <br />?

Will the fix you are talking about be part of the official release?

[The Jimmo]

I have just gotten my 3.x site into a temp offline site and converted to 4.0. I'm only testing at this time. There were other issues with implementing HTML that prevented me from using the built in editor. I really haven't gotten to verify the other problems that I was having. The continuous output of lines were never a problem with 3.x.

Like I said it's easier for me to work with the HTML files saved on my local device using my HTML code editor, then paste, and save the final code back into the IPB editor.

However it would nice if the internal editor worked correctly, and it may. Like you said I should be using <p> and not <br />, but is that in fact a reason for the internal editor not to allow using <br />?

Will the fix you are talking about be part of the official release?

​I would certainly expect it to be easier to edit HTML in an HTML code editor.

CKEditor is designed to not allow null elements without content or definitions so "<br />" is escaped. You have to tell it to not escape these elements if you want to use them. You can do so by editing the config file of CKEditor at /applications/core/dev/ckeditor/config.js

You want to add the following statement in this function: "CKEDITOR.editorConfig = function( config ) {"

config.protectedSource.push(/<br[\s\S]*?\/\>/g); //allows <br /> tag

I do not work for IPS so anything I recommend you of course are taking into your own hands in implementing and potentially will not be part of any official release by IPS so you will have to continue to manage it moving forward.

[mesteele101]

I'm using V4.0RC

That location does not exist. However I did find a config.js file at the 3 other locations below:

1) applications\core\interface\ckeditor\ckeditor

2) public\js\3rd_party\ckeditor

3) public\js\3rd_party\ckeditor\_source\core

I did edit the file in location two above. It's still coming out continuous.

/*
Copyright (c) 2003-2010, CKSource - Frederico Knabben. All rights reserved.
For licensing, see LICENSE.html or http://ckeditor.com/license
*/

CKEDITOR.editorConfig = function( config )
{
config.protectedSource.push(/<br[\s\S]*?\/\>/g); //allows <br /> tag
	// Define changes to default configuration here. For example:
	// config.language = 'fr';
	// config.uiColor = '#AADC6E';
};

 

 

[The Jimmo]

Sorry, my brain wasn't completely awake when I made this comment. Forgot to mention in order to access the above file I mentioned, you will need to be in developer mode: http://community.invisionpower.com/4docs/advanced-usage/development/developer-mode-r70/