Adan0s

Hi there,

after upgrading to 0.9.4 I have the same problem. The site is not working as soon the plugin is activated. Just like Tybaze I’m using Ubuntu 10.04.4.

Other versions:

Apache: 2.2.14
PHP: 5.3.2
WP: 3.8.2
W3TC: 0.9.4

There’s nothing else in the logs, just a Segfault

[Wed Apr 09 09:39:51 2014] [notice] child pid 28026 exit signal Segmentation fault (11)

0.9.3 worked without any problem. The above mentioned fix does not work for me. :/

Hey there,

just tried the new version. So far I didn’t noticed any more undefined indexes. Thank you!

Just tried the current Dev-Version (1.3.4.10dev6) and found some new errors:

PHP Notice:  Undefined index: id in /wp-content/plugins/easy-fancybox/easy-fancybox.php on line 50
PHP Notice:  Undefined index: default in /wp-content/plugins/easy-fancybox/easy-fancybox.php on line 50
PHP Notice:  Undefined index: default in /wp-content/plugins/easy-fancybox/easy-fancybox.php on line 79
PHP Notice:  Undefined index: default in /wp-content/plugins/easy-fancybox/easy-fancybox.php on line 210
PHP Notice:  Undefined index: id in /wp-content/plugins/easy-fancybox/easy-fancybox.php on line 462
PHP Notice:  Undefined index: default in /wp-content/plugins/easy-fancybox/easy-fancybox.php on line 462

Hey mavrick,

yes, even though it’s a combination of a modificated page-template, an addition to the functions.php and a custom table in the wordpress-database

functions.php (put at the end)

add_filter('query_vars', 'partner_queryvars' );

function partner_queryvars( $qvars )
{
  $qvars[] = 'slug';
  return $qvars;
}

add_action('generate_rewrite_rules', 'partner_add_rewrite_rules');

function partner_add_rewrite_rules( $wp_rewrite )
{
  $new_rules = array(
     'partner/([^/]*)$' => 'index.php?pagename=partner&slug=' .$wp_rewrite->preg_index(1) );

  //Add the new rewrite rule into the top of the global rules array
  $wp_rewrite->rules = $new_rules + $wp_rewrite->rules;
}

page-partner.php (put at top)

$slug = get_query_var('slug');
if($slug != "") {
	$partner = $wpdb->get_row($wpdb->prepare("SELECT * FROM partner WHERE slug=%s LIMIT 1",$slug));
}
else {
// no slug, do something generic
}

the custom table (in my case called partner) has multiple rows, one of them called slug includes the desired part of the url.

code should be pretty self-explanatory, just replace partner with your page and slug with your desired variable. if not, don’t hesitate to ask.

Sure, the whole thing would probably much more cleaner with a custom post type. But in that case I would need to create a whole plugin out of that small script. ??
Currently I have my profiles in an independent database which I simply query via wpdb.

I think I’ll simply go with the .htaccess-solution until my client approves the budget for converting it into a plugin.

Awesome, thank you!

I’m most of the time developing with notices activated so I can see some early things which could result in a pita in the end. ?? If I find more of them I’ll post.

Here’s another one, probably a typo:

PHP Notice: Undefined index: Enalbe in /wp-content/plugins/easy-fancybox/easy-fancybox.php on line 340