- This topic has 21 replies, 4 voices, and was last updated 8 years, 9 months ago by
.
-
Posts
-
-
When trying to save a CPT with a custom taxonomy item checked I receive the following errors:
Warning: Illegal offset type in isset or empty in /home/wwcbiz/public_html/debbie/wp-includes/taxonomy.php on line 231
Warning: Illegal offset type in isset or empty in /home/wwcbiz/public_html/debbie/wp-includes/taxonomy.php on line 231
Warning: Cannot modify header information – headers already sent by (output started at /home/wwcbiz/public_html/debbie/wp-includes/taxonomy.php:231) in /home/wwcbiz/public_html/debbie/wp-includes/pluggable.php on line 876
-
@txhorselady– Can you post the code you are using to register the CPT and Taxonomy?
-
Hi Steve,
I tried activating a taxonomy for a CPT but received the error. As a test I installed Piklist on a blank 3.5 site and created a Demo Type in the Piklist Demo Taxonomy. I then added a Piklist demo and selected my demo type taxonomy item . Upon trying to save the Demo I received the same error. I have not implemented any of my own code on this site.Thanks,
Carla -
I can reproduce same error message from my install with Demo Type taxonomy and Demo CPT with WP development version (3.5-RC6-23166)
Also, selecting/editing Demo Type taxonomies for Demos works fine in quick edit menu.
Further, when editing a Demo, unchecking the current Demo Type and saving works fine, however, after the page reloads, the previous Demo Type is still selected.
-
-
-
@Steve – thanks. I thought maybe you had Romny on the brain when you were coding it.
The taxonomy_exists() function isn’t to happy about handing it a nested array. I guess you can’t create those taxonomy field checkboxes with field names like: name=”taxonomy[piklist_demo_type][]”.
You can fix the warnings by modifying the function get_field_name() in class-piklist-form.php with something like the following:
if ($scope == 'taxonomy')
{
$name = 'tax_input[' . $field . '][]';
}
else
{
$name = $prefix . ($scope ? $scope . (self::is_media() && isset($GLOBALS['piklist_attachment']) ? '_' . $GLOBALS['piklist_attachment']->ID: '') . '[' : null) . $field . ($scope ? ']' : null) . (is_numeric($index) ? '[]' : null);
}
Not sure if this is how you would want to actually fix this, there might be side effects somewhere else. But it works it seems.
-
-
-
-
@txhorselady – I agree, Piklist is pretty cool. I am patiently waiting for it to develop into something that has all the features I need (actually, all I really need is for relationships to mature :hint:) to do some cool plugins/add-ons as well. Ultimately its authors are going to develop it to suit their immediate needs first. Can’t wait for the customer and product add ons!
-
-
@txhorselady– We’re having a difficult time duplicating this error. Still working on it!
-
I just installed Piklist on a new blank single site WP 3.5 install. I am able to create the Demo Type. I clicked save without changing the status and it saved as a draft. Then I went back in and changed the status to Demo and clicked ok. The status didn’t change. Then I clicked on Update and I received the same error as before. There are no other plugins installed on this site.
-
-
-
-
@txhorselady– We haven’t been able to duplicate, however, I have a temporary solution for you. Log these error notices instead of showing them on screen.
1) Open your wp-config.php file (probably through ftp) and edit it.
2) Paste this code in. Make sure it’s above the line that says That’s all, stop editing! Happy blogging.
define('WP_DEBUG', true); // or false
if (WP_DEBUG) {
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
@ini_set('display_errors',0);
}
That should temporarily solve the issue.
You can view detailed instructions on the WP Codex.
-
-
@txhorselady– That is really odd. Either way, we will still try and fix.
-
-
-
- You must be logged in to reply to this topic.