Tab content non-editable in product page

[Nir]

Hi,

I’ve just installed v1.0.17 and getting the following error on the “XXX tab content” section as soon as I try to edit any of my products:

Warning: printf(): Too few arguments in /mounted-storage/………./wp-includes/class-wp-editor.php on line 247

Kindly advise how to fix this.

Many thanks,

Nir

[WebshopLogic]

Hi Nir!

Thank you for let us know this.
This seems to be a special problem occurring on your site, we have not realize this kind of problem yet.
The error message comes from WP core (not from our plugin), so this is too few information to identify the problem.

Please give us the following information:
What WordPress and Woocommerce versions do you use?
When does the problem occur? When you open the product editor page or when you save it?
Please send us the full error stack (usually it is appears in a table below the error message)? It is very important to see which part of the program call this Printf WP function.
You can also send us a screenshot.

If you give us this information, we can investigate what is the reason of the problem.

Thanks in advance.

Peter

[Nir]

Hello,

Wordpress 4.1.1, Woocommerce 2.3.5

The problem occurs as soon as the product editor page is loaded.

No additional error stack, just:

Warning: printf(): Too few arguments in /mounted-storage/………./wp-includes/class-wp-editor.php on line 247

But please note that this is not the first time you see this problem. See also your customers on:

Error on backend

https://wordpress.org/support/topic/printf-functionprintf-too-few-arguments-in-class-wp-editorphp-on-line-233

Kindly assist with solving this…

Thank you,

Nir.

[Nir]

Hello,

This has something to do with the direct URL created by the plugin for each custom tab (in the “product_tabpage” sub-folder). When the custom tab name as defined by the user is not in English the plugin creates a non-English direct link (by the same name) for this tab, and when then the product editor page fails, if specific non-ASCII characters exist in the tab name.

Manually editing each link name once a new custom tab is created and forcing only English characters in this URL solves the problem.

Cheers,

Nir.

[WebshopLogic]

Hi Nir!

Thanks for the detailed information.
We will see this problem and find a solution.

I have one more question for clarification: which page do you enter custom tab name? On product edit page, or on Product Tab Type edit page (it is in “Product Tabs” menu)? Custom tab names can be entered both of them, that is why I ask it.

Cheers,
Peter

[Nir]

Hi Peter,

I set the custom tab name on the product tab type edit page. This is where the custom URL seems to be created automatically according to the custom tab name, and also where I manually change it (in case that are “problematic” characters in that URL).

Cheers,

Nir.

[WebshopLogic]

Hi Nir!

Thanks for the information.
I think the problem is applying improper slug for custom post types. It is important to use always proper characters in WordPress slugs.
You can find information about this in the plugin documentation, in “What can be the slug of tab types?” section here:
http://webshoplogic.com/product/woocommerce-custom-tabs-pro-plugin/#tab-faq

Some more information about it:
Custom tab types are handled as WordPress custom content (custom post type), the code of custom tab type is a WordPress “slug”, generated by WordPress.

Slug is a text that can be part of any URL-s, so it must not contain special characters that can not be applied in URL-s. If it contains special characters, the links will be invalid and cannot be applied properly in different parts of the system, including our plugin.

Depending on your WordPress version slug can be modified (in case of oldest WP versions), but in latest WordPress versions it is not editable (as I see).

If you use a WP version that allow changing slugs, please ensure that the slug of the tab types does not contain invalid characters.
If you use a WP version that does not allow changing of slugs manually, than I suppose the generated slug will be valid and applicable in any URL. I have tested it using special characters, and it is converter automatically to ascii characters by WordPress. (Slug generation is a WordPress feature, and not the feature of our plugin).

You can find more information about WP slugs here (including “How to change post slug?” section):
https://rtcamp.com/blogger-to-wordpress/tutorials/user-guide/permalinks-and-slugs/

I hope this information is helpful, and you can set the proper slugs (according to the plugin documentation), that solve the problem.

If you have more question, please do not hesitate to contact us.

Peter

[Nir]

Thank you Peter

[Author]

Posts