IntegraMOD

This is an odd request, but perhaps someone can point me in the right direction. I utilize Knowledge Base as a repository for stories, essays, interviews, etc. I would like to be able to change the background within the content to distinguish content. For instance, the interviewer could be defined as row1 and the interviewee as row2, thereby creating a visual distinction between the two parties (text color and background could vary). I am certain there is no way to do this in BBCode, but what if HTML is enabled?

If the above is not possible, could I reference the CMS styles in an HTML page which is called through IM Portal?

Surprisingly, I have managed partial success in my efforts. Enabling the span statement within ACP as acceptable HTML allows for application of valid IM CSS elements. However, since I wanted to display the content in a cell format in lieu of only applying the CSS to the text, I further allowed the use of table, tr and td as acceptable HTML. This works, though the table statements appear to introduce a line break before the table content for every statement called. Example follows:[code]Literature Is Entertainment Or It it Nothing: An Interview With Thomas Ligotti
By: Neddal Ayad
http://www.fantasticmetropolis.com/i/ligotti/)

Thomas Ligotti is North Americas pre-eminent writer of weird horror fiction. His work has appeared in dozens of magazines and anthologies. In 1997, his collection The Nightmare Factory won the Bram Stoker Award for Best Fiction Collection. à¢Ãƒ ¢Ã¢â‚¬Å¡Ã‚ ¬Ãƒâ€¦Ã¢â‚¬Å“The Red Tower,à¢Ãƒ ¢Ã¢â‚¬Å¡Ã‚ ¬Ãƒâ€š

The whitespace is from the carriage returns in the HTML structure. When writing HTML you literally have to remove all extra carriage returns and spaces in between the > and the < of each consecutive HTML element. It can be a major pain, but should be easy to accomplish with a simple find-and-replace in a text editor, then paste the condensed code into your post.

Understood. Thanks for the clarification, Jason. I have further established that HTML is not being allowed in Knowledge Base to any extent. Even bold and italics tags are being ignored within KB, therefore it has nothing to do specifically with my allowing span and table tags. Again, these tags appear properly in the preview, but not when viewing the final article. Is HTML in KB working for others? If so, does anyone know which file handles this so that I may attempt a reconstruction?

I installed a separate clean version of IM 1.40 on my server for testing purposes. I have determined through testing with this installation that HTML statements are not being formatted when viewing Knowledge Base articles. The preview shows the content properly, but the articles display the HTML code as standard text when viewed. This appears to be a bug, though I do not know if it is exclusive to IntegraMOD or if it is a general phpBB Knowledge Base problem. Can anyone help?

phpBB doesn't have a knowledge base, this was one of the mods added to IntegraMod. It is a known issue at this point, with no known resolution (that I'm aware of).

Sorry, I was sure I clicked submit in this thread after Jason's post. Real bad day!

The problem of posting HTML in the KB has been known for some time. I cannot see the article straight away but I know it is an acute one for many.

A further point on the html front, the latest phpbb updates have really tried to obliterate html posting functions. the issue being that they feel the risk is greater than the gain of having html functionality. <img>

Looking at the example you gave, the main differences appear to be just the background change on each character of the interview. Whilst HTML enhancement is out, you can use bbcode enhancement to help denote the different speakers. Plain bold, italics and colour of text can do this. You could even consider changing the font if need be. This would give instant delineation between speakers and is the way that most people do it.

To change the background of a line of text, I would think could be done by modifying a bbcode. If you can easily add a bold tag, I would have thought it it is not a giant leap to add a style code.

A