I may consider adding this to my personal server’s .htaccess file…
hacks secure htaccess phpnuke code hacks PHP-Nuke modules, blocks, themes
I’m tryin’ ta think but nuthin’ happens!
I may consider adding this to my personal server’s .htaccess file…
hacks secure htaccess phpnuke code hacks PHP-Nuke modules, blocks, themes
Once upon a time, we had a vexing problem where we couldn’t set the @target (OT: @target is tech-speak/jargon/euphemism for ‘target attribute’). Actually, you could set it, but when you ‘saved’ the post or story, TinyMCE (that nifty toolbar interface for formatting blog posts used by WordPress and a million other places). Here’s where I figured out what was wrong. I don’t know why they ‘broke’ the @target attribute, although I do know that the ‘target’ attribute was deprecated in HTML 4.01, as well as XHTML 1.0. However, there are ways around it, like via JavaScript and XHTML modules which are pretty darn cool.
Anyway, when we upgrade WordPressMU to the next version, we’ll likely need to ‘fix’ this again, so here’s $98 bucks worth of direction:
Changeset 1022 – WordPress MU Trac – Trac
Just change this:
$allowedposttags = array(
‘address’ => array(),
‘a’ => array(
‘href’ => array(), ‘title’ => array(),
‘rel’ => array(), ‘rev’ => array(),
‘name’ => array()
),
to this:
$allowedposttags = array(
‘address’ => array(),
‘a’ => array(
‘href’ => array(), ‘title’ => array(),
‘rel’ => array(), ‘rev’ => array(),
‘name’ => array(), ‘target’ => array()
),
NOTE: This change was downgraded to determine if it inexplicably affects bandwidth performance.
Once upon a time, we had a vexing problem where we couldn’t set the @target (OT: @target is tech-speak/jargon/euphemism for ‘target attribute’). Actually, you could set it, but when you ‘saved’ the post or story, TinyMCE (that nifty toolbar interface for formatting blog posts used by WordPress and a million other places). Here’s where I figured out what was wrong. I don’t know why they ‘broke’ the @target attribute, although I do know that the ‘target’ attribute was deprecated in HTML 4.01, as well as XHTML 1.0. However, there are ways around it, like via JavaScript and XHTML modules which are pretty darn cool.
Anyway, when we upgrade WordPressMU to the next version, we’ll likely need to ‘fix’ this again, so here’s $98 bucks worth of direction:
Changeset 1022 – WordPress MU Trac – Trac
Just change this:
$allowedposttags = array(
‘address’ => array(),
‘a’ => array(
‘href’ => array(), ‘title’ => array(),
‘rel’ => array(), ‘rev’ => array(),
‘name’ => array()
),
to this:
$allowedposttags = array(
‘address’ => array(),
‘a’ => array(
‘href’ => array(), ‘title’ => array(),
‘rel’ => array(), ‘rev’ => array(),
‘name’ => array(), ‘target’ => array()
),
NOTE: This change was downgraded to determine if it inexplicably affects bandwidth performance.
Yahoo! UI Library: Graded Browser Support
A-Grade Browser Support is probably what we should adopt, as well.
Are we there yet? Are we there yet? Are we there yet? Are we there yet? Are we there yet? Are we there yet? Are we there yet? Are we there yet? Are we there yet? Are we there yet? Are we there yet?
More playing… More playing… More playing… More playing… More playing… More playing… More playing… More playing… More playing… More playing… More playing… More playing… More playing…
Just laying around.
TinyMCE is a powerful WYSIWYG editor control for web browsers such as MSIE or Mozilla that enables the user to edit HTML contents in a more user friendly way. The editor control is very flexible and it’s built for integration purposes (usage within systems like Intranets, CMS, and LMS, for example).
TinyMCE:Installation – Moxiecode Documentation Wiki
This is the Text Editor available for WordPress posting (Visual Edit mode). Pretty neat. Perhaps we’ll add a few items…
Here’re some more interesting TinyMCE links:
Perhaps, if I can ever find some time, I’ll be able to play around with this stuff.
I’m a Mac, but the Sun looks inviting…
OCRegister.com | Multimedia: Joey’s A Dad
This is really sweet.