eyewinder's Replies | WordPress.org

Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)

Forum: Plugins
In reply to: Unit test errors with importer

eyewinder
(@eyewinder)

13 years ago

I tried emailing automattic.com (they appear to host the unit test file), but I’m not sure whether they are responsible for revisions. No response yet.

I may use the following WP sample content, but it isn’t nearly as comprehensive for testing:
http://wpcandy.com/made/the-sample-post-collection/

Good luck!

Forum: Plugins
In reply to: [Simple Share Buttons Adder] Error notices and some feature requests

Thread Starter eyewinder
(@eyewinder)

13 years ago

Hi David,

I can officially say the notice messages are gone! The other additions are easy to use and understand.

Thanks,
Kim

Forum: Plugins
In reply to: [Yoast SEO - Advanced SEO with real-time guidance and built-in AI] Warning after activation: The plugin generated 241..

eyewinder
(@eyewinder)

13 years ago

WordPress version 3.5.1
WordPress SEO version 1.4.3

The plugin generated 243 characters of unexpected output during activation...

Errors occur with custom child theme (based on Hybrid parent theme) as well as default Twenty Twelve theme with no other plugins active.

Tried development version with same results. Downgrading to version 1.3.4.4 eliminates the errors. Not sure is downgrading will result in XML sitemap issues.

Forum: Plugins
In reply to: [Simple Share Buttons Adder] Error notices and some feature requests

Thread Starter eyewinder
(@eyewinder)

13 years ago

Thanks for the speedy response! It’s nice when people have such a great attention to detail.

As for suggestion 2, perhaps increased custom css control would address most conditions for positioning etc. (eg. buttons inline with the author byline).

Cheers,
Kim

Forum: Plugins
In reply to: Unit test errors with importer
eyewinder
(@eyewinder)

13 years ago
I’m also experiencing the same problem. Clean install of WordPress with no other plugins active. Also tried replacing the WordPress import plugin. No luck.

The undefined offset errors all reference one of the following lines within the plugin parsers.php file: 413, 418, and 423.

Opened up the file and found that the errors correspond to the following statements within the parse function (lines are commented). Don’t know enough about parsing or these specific variables to debug though…
```
if ( false !== strpos( $importline, '<wp:category>' ) ) {
	preg_match( '|<wp:category>(.*?)</wp:category>|is', $importline, $category );
	$this->categories[] = $this->process_category( $category[1] ); // Line 413
	continue;
}
if ( false !== strpos( $importline, '<wp:tag>' ) ) {
	preg_match( '|<wp:tag>(.*?)</wp:tag>|is', $importline, $tag );
	$this->tags[] = $this->process_tag( $tag[1] ); // Line 418
	continue;
}
if ( false !== strpos( $importline, '<wp:term>' ) ) {
	preg_match( '|<wp:term>(.*?)</wp:term>|is', $importline, $term );
	$this->terms[] = $this->process_term( $term[1] ); // Line 423
	continue;
}
```
Also of interest, the theme unit test file was updated on 03/06/13. However, I don’t have access to an older version for testing.
Forum: Themes and Templates
In reply to: Getting custom fields on blog page (for internal styles in doc head)
Thread Starter eyewinder
(@eyewinder)

14 years, 6 months ago
Update:
After a bunch of experimentation and reading about the loop (outside of template files), I think I have a workable solution. Below is the latest version of the function. Any suggestions to improve/simplify the code are more than welcome…
```
// Get styles from custom field 'css' in blog loop and embed into document head
function footprint_blog_custom_css() {
	global $post;

	if ( is_home() ) {
		$custom_css_array = array();

		while ( have_posts() ) : the_post();
			$blog_post_css = get_post_meta( $post->ID, 'css', true );
			if ( !empty( $blog_post_css ) ) {
				$custom_css_array[] = $blog_post_css;
			}
		endwhile;

		$blog_custom_css = implode( "\n", $custom_css_array );

		if ( !empty( $blog_custom_css ) ) {
			echo '<style type="text/css" media="screen, projection">' . "\n" . $blog_custom_css . "\n" . '</style>' . "\n";
		}
	}
}
```

Viewing 6 replies - 1 through 6 (of 6 total)