If you are receiving an error similar to the following while activating Breadcrumb NavXT, please continue reading.
Parse error: parse error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or ‘}’ in /wp-content/plugins/breadcrumb-navxt/breadcrumb_navxt_admin.php on line 53
This should be only caused by PHP4. The line of code PHP is failing on is protected $version = '3.5.1';. Specifically, it is the protected part that PHP4 does not know about, and subsequently chokes on. Some users have claimed to receive this in a PHP5 environment. If you receive this error, please insert
<?php
if (current_user_can('administrator')){
phpinfo();
}
?>
somewhere in your footer. Then, open up a page on your site and look in the output from phpinfo for your PHP version. If the version is not PHP5.2 or newer, please inquire with your webhost on how to migrate to a modern PHP installation. If the output states you have a version of PHP that is 5.2 or newer, please copy the output and e-mail it to me (full output). Feel free to provide an abridged output in the comments section of this page.
-John Havlik
[end of transmission, stay tuned]
This is a minor improvement to the previous release of WP Lynx. It fixes a few issues reported by users. These include fixing an issue involving non UTF-8 encoded sites, and a fix for users on hosts with php safemode enabled. Finally, error reporting is improved slightly. As always, if you thing you found a bug please report it.
The next planned release, 0.2.0, will have some cool new features. Additionally, the settings page will be reorganized a little to make it easier to use. More on this as development progresses.
-John Havlik
[end of transmission, stay tuned]
As part of my goals last week, I was working heavily on Breadcrumb NavXT’s custom post type support (after I finished up replacing my desktop’s motherboard with a more stable one). This work is ready for testing. So far, it has passed my development test cases and is ready for end user testing.
The implementation in the SVN trunk has one flaw. It doesn’t handle the “hierarchy flip” situation, where a post hierarchy can terminate with a post that is flat (e.g. it uses taxonomies to be located, not a post hierarchy). One standard example of this “hierarchy flip” is attachments to posts. They are hierarchical, but the parent post is not. Currently, this is handled using an “exception” for attachments. A proper solution would check and continue until it gets to the very top. However, this would impact performance, and is unnecessary for most sites (I need feedback on this, if it is an issue, I will provide support).
It looks like the 3.6 release will be moved up to late July, from August. I plan on having it ready for the translation team by July 14th. It looks like I’ll punt the multisite support extensions to the 3.7 release this fall.
-John Havlik
[end of transmission, stay tuned]
Since I managed to complete the four goals I set out to do last week, I’m creating the list again for this week.
Complete custom post type support in Breadcrumb NavXT. The testbed and cases are ready, the initial code it there. I just need to finish it up. This may be a two week goal due to the amount of work required.(done)- Create a screencast that demonstrates the work flow of WP Lynx. Last week this didn’t make the list, but was something I wanted to get done. (Can’t seem to get audio to work correctly.)
Clean up the code to Quick Key NavXT and submit it to the WordPress.org plugins database. This was something I wrote a long time ago and never released. It was inspired by an idea from Charles Stricklin when he was still doing the WordPress community podcast.(Cleaned up, available here)Run at least 3 times this week. Last week I did it, time to repeat.(done)
-John Havlik
[end of transmission, stay tuned]
As of a few minutes ago, Breadcrumb NavXT has preliminary support of custom post types. Note that this support is very basic. It essentially sees hierarchical custom posts and pages as the same thing, and all other post types as posts. This will be refined further in the coming weeks, where each post type will have it’s own options, a la taxonomies.
-John Havlik
[end of transmission, stay tuned]
WordCamp NYC
