WraithKenny

Sorry, you don’t include the script tags for this plugin. I’ll be adding a way to include external scripts in v3, but for now, this plugin is inline only.

Also, unless you are an Editor or Admin, you can’t access the plugin at all. If you are, you can place that code right in the editor and it should work.

The easier solution is to take out the line-break from your string. That’d completely avoid the line-break character getting converted into a

Change the code to:

$disp_gallery .= '<font size="3"'
 . 'style="text-align:center">Photo Title</font>'

which is how code formatting is done without introducing unwanted line-breaks.

Can’t think of a reason you’d want to keep the line-break in the string.

You’re user may have a plugin/theme that manipulates wpautop or unautop or something similar (assuming you are using shortcode_unautop() )

Oh, well, I was questioning the appropriateness of using a plugin’s example readme.txt for a theme’s readme.txt while developing a theme (as per recommendation by theme-check) but since the file isn’t yet parsed for any data, I guess it doesn’t matter (yet). Specifically, the data seem specific to plugins… but I’m assuming that if and when Theme’s get real support for readme.txt that’ll be updated to more Theme focused headers and such.

See https://www.ads-software.com/support/topic/plugin-theme-check-readmetxt-warning

I haven’t got the error since, and it’s reported, so I’ll mark this resolved…

Fixed (as of 3.0 I believe)

Take a look in https://core.trac.www.ads-software.com/browser/trunk/wp-admin/admin-header.php#L200

Looks like you’d just have to add an action (to the appropriate hook) that echoes the markup of your message. Doesn’t seem to be any tutorials, but it seems simple enough.

Alternatively, if it’s your plugin’s option page, you can do something similar to https://core.trac.www.ads-software.com/browser/trunk/wp-admin/update-core.php#L128 where the message is below the heading.

I’ve tested the Development version and the new code recognized my setting as strict enough (thanks!)… Except under “Directly Cached Files” which probably needs the newly updated code snippet ??

Also, I like having the menu item under the Network Admin -> Settings section, which implies that the settings are Network Wide. Having two more links on each site (under both Tools and Settings) is a bit redundant in MultiSite though (and slightly confusing), since the settings are global… Unless you are adding individual site configuration for the next build?

(I’ve also never noticed that clicking the Headings on the Advanced tab hides the text (must be new). Perhaps consider the WordPress style treatment for collapsible sections (widgets) and load with them closed… or Accordion maybe. Just a thought.)

third run worked as expected. first run was a timeout on my DB.

“PHP Notice: Undefined variable: wp_version in /wp-content/plugins/akismet/akismet.php on line 508”

I get 160 chars of unexpected output because I have WP_DEBUG turned on, (the notices are the output).

function save_meta_box( $post_id ) {
global $post, $meta_boxes, $key;

	foreach( $meta_boxes as $meta_box ) {
	$data[ $meta_box[ 'name' ] ] = $_POST[ $meta_box[ 'name' ] ];
	}

	if ( !wp_verify_nonce( $_POST[ $key . '_wpnonce' ], plugin_basename(__FILE__) ) )
	return $post_id;

	if ( !current_user_can( 'edit_post', $post_id ))
	return $post_id;

	update_post_meta( $post_id, $key, $data );
	}

Your error is here. The following is outside a function and the html comment is printed when the plugin is loaded (to early for any output). None of this should be outside of a function block.

add_action( 'admin_menu', 'create_meta_box' );
	add_action( 'save_post', 'save_meta_box' );

?>

<!-- Events Data -->

<?php

$key_event = "key";
$meta_boxes = array(

	"name" => array(
	"name" => "event",
	"title" => "Event",
	"description" => ""),

	"camber" => array(
	"name" => "startdate",
	"title" => "Start Date",
	"description" => ""),

	"shape" => array(
	"name" => "enddate",
	"title" => "End Date",
	"description" => ""),

	"contruction" => array(
	"name" => "location",
	"title" => "Location",
	"description" => ""),
);

I had the same, but after checking in my dotcom account’s “My Blogs” page and refreshing (and/or waiting a little bit) it cleared up.

Yes, take a look at Revisionary.

I was hoping for an implementation would take options (colors, font-family, padding, etc.) and pass those to the lessphp compiler, which on option update (wp api) would compile to static css, which would be included in the theme, rather then the .less file. Would work better with the boot-strap I think… I know how to do options pages, and I think I can do the boot-strap, but like obvio, I was wondering how tough passing php variables to lessphp is?